From f0fc14cd7bb519c2740b8488928a2b0f1215fd4b Mon Sep 17 00:00:00 2001
From: gvasquezvargas <gaby.vasquez@enterprisedb.com>
Date: Fri, 22 Nov 2024 12:16:04 +0100
Subject: [PATCH] restore epas v16 docs

---
 .../02_packages/01_package_components.mdx     |  385 +++++
 .../02_packages/01a_display_packages.mdx      |  141 ++
 .../02_packages/02_creating_packages.mdx      |  139 ++
 .../02_packages/03_referencing_a_package.mdx  |   26 +
 ...using_packages_with_user_defined_types.mdx |  192 +++
 .../02_packages/05_dropping_a_package.mdx     |   30 +
 .../02_packages/index.mdx                     |   24 +
 .../12_debugger/configuring_debugger.mdx      |   38 +
 .../12_debugger/debugger_interface.mdx        |   52 +
 .../12_debugger/debugging_a_program.mdx       |  115 ++
 .../12_debugger/index.mdx                     |   30 +
 .../12_debugger/starting_debugger.mdx         |   31 +
 .../comment_command.mdx                       |  164 +++
 .../index.mdx                                 |   16 +
 .../logical_decoding.mdx                      |   17 +
 .../obtaining_version_information.mdx         |   39 +
 .../ecpgplus_guide/02_overview.mdx            |  126 ++
 .../ecpgplus_guide/03_using_embedded_sql.mdx  |  374 +++++
 .../ecpgplus_guide/04_using_descriptors.mdx   |  570 ++++++++
 ...lding_executing_dynamic_sql_statements.mdx |  812 +++++++++++
 .../ecpgplus_guide/06_error_handling.mdx      |  198 +++
 .../ecpgplus_guide/index.mdx                  |   36 +
 .../ecpgplus_guide/installing_ecpgplus.mdx    |  145 ++
 .../02_spl_block_structure.mdx                |   96 ++
 .../02_spl_programs/03_anonymous_blocks.mdx   |   17 +
 .../01_creating_a_procedure.mdx               |  175 +++
 .../02_calling_a_procedure.mdx                |   37 +
 .../03_deleting_a_procedure.mdx               |   27 +
 .../04_procedures_overview/index.mdx          |   20 +
 .../01_creating_a_function.mdx                |  180 +++
 .../02_calling_a_function.mdx                 |   55 +
 .../03_deleting_a_function.mdx                |   27 +
 .../05_functions_overview/index.mdx           |   22 +
 ...positional_vs_named_parameter_notation.mdx |  106 ++
 .../02_parameter_modes.mdx                    |   32 +
 .../03_using_default_values_in_parameters.mdx |   75 +
 .../declaring_parameters.mdx                  |   87 ++
 .../index.mdx                                 |   20 +
 .../01_creating_a_subprocedure.mdx            |  128 ++
 .../02_creating_a_subfunction.mdx             |   75 +
 .../03_block_relationships.mdx                |   81 ++
 .../04_invoking_subprograms.mdx               |  355 +++++
 .../05_using_forward_declarations.mdx         |   57 +
 .../06_overloading_subprograms.mdx            |  165 +++
 .../07_accessing_subprogram_variables.mdx     |  411 ++++++
 .../index.mdx                                 |   34 +
 ...ion_errors_in_procedures_and_functions.mdx |   74 +
 .../01_execute_privilege.mdx                  |   41 +
 .../02_database_object_name_resolution.mdx    |   27 +
 .../03_database_object_privileges.mdx         |    9 +
 .../04_definers_vs_invokers_rights.mdx        |   23 +
 .../05_security_example.mdx                   |  281 ++++
 .../09_program_security/index.mdx             |   24 +
 .../epas_compat_spl/02_spl_programs/index.mdx |   22 +
 .../01_declaring_a_variable.mdx               |   55 +
 ...2_using__type_in_variable_declarations.mdx |  128 ++
 ...using__row_type_in_record_declarations.mdx |   59 +
 ...ined_record_types_and_record_variables.mdx |  111 ++
 .../03_variable_declarations/index.mdx        |   20 +
 .../06_transaction_control/01_commit.mdx      |   66 +
 .../06_transaction_control/02_rollback.mdx    |  183 +++
 .../03_pragma_autonomous_transaction.mdx      |  419 ++++++
 .../about_transactions.mdx                    |   17 +
 .../06_transaction_control/index.mdx          |   34 +
 .../epas_compat_spl/07_dynamic_sql.mdx        |  122 ++
 .../01_declaring_a_cursor.mdx                 |   35 +
 .../08_static_cursors/02_opening_a_cursor.mdx |   28 +
 .../03_fetching_rows_from_a_cursor.mdx        |   75 +
 .../08_static_cursors/04_closing_a_cursor.mdx |   42 +
 .../05_using__rowtype_with_cursors.mdx        |   59 +
 .../06_cursor_attributes/01_isopen.mdx        |   35 +
 .../06_cursor_attributes/02_found.mdx         |   64 +
 .../06_cursor_attributes/03_notfound.mdx      |   64 +
 .../06_cursor_attributes/04_rowcount.mdx      |   66 +
 ...ummary_of_cursor_states_and_attributes.mdx |   18 +
 .../06_cursor_attributes/index.mdx            |   20 +
 .../08_static_cursors/07_cursor_for_loop.mdx  |   66 +
 .../08_parameterized_cursors.mdx              |   39 +
 .../08_static_cursors/index.mdx               |   22 +
 .../01_ref_cursor_overview.mdx                |   13 +
 ...laring_a_sys_refcursor_cursor_variable.mdx |   23 +
 ..._user_defined_ref_cursor_type_variable.mdx |   27 +
 .../02_declaring_a_cursor_variable/index.mdx  |   23 +
 .../03_opening_a_cursor_variable.mdx          |   34 +
 ...4_fetching_rows_from_a_cursor_variable.mdx |   31 +
 .../05_closing_a_cursor_variable.mdx          |   49 +
 .../06_usage_restrictions.mdx                 |   24 +
 ...returning_a_ref_cursor_from_a_function.mdx |   55 +
 .../02_modularizing_cursor_operations.mdx     |  165 +++
 .../07_examples/index.mdx                     |   16 +
 .../08_dynamic_queries_with_ref_cursors.mdx   |  127 ++
 .../index.mdx                                 |   20 +
 .../10_collections/01_associative_arrays.mdx  |  229 +++
 .../10_collections/02_nested_tables.mdx       |  233 +++
 .../10_collections/03_varrays.mdx             |  127 ++
 .../10_collections/about_collections.mdx      |   43 +
 .../epas_compat_spl/10_collections/index.mdx  |   25 +
 .../12_working_with_collections/01_table.mdx  |   32 +
 .../02_using_the_multiset_union_operator.mdx  |  264 ++++
 .../03_using_the_forall_statement.mdx         |  111 ++
 .../01_select_bulk_collect.mdx                |  112 ++
 .../02_fetch_bulk_collect.mdx                 |  110 ++
 .../03_execute_immediate_bulk_collect.mdx     |   32 +
 .../04_returning_bulk_collect.mdx             |  144 ++
 .../index.mdx                                 |   20 +
 .../05_errors_and_messages.mdx                |   83 ++
 .../12_working_with_collections/index.mdx     |   20 +
 .../13_triggers/01_overview.mdx               |   17 +
 .../13_triggers/02_types_of_triggers.mdx      |   25 +
 .../13_triggers/03_creating_triggers.mdx      |  209 +++
 .../13_triggers/04_trigger_variables.mdx      |   51 +
 .../05_transactions_and_exceptions.mdx        |   17 +
 .../13_triggers/06_compound_triggers.mdx      |   74 +
 .../01_before_statement_level_trigger.mdx     |   35 +
 .../02_after_statement_level_trigger.mdx      |   60 +
 .../03_before_row_level_trigger.mdx           |   35 +
 .../04_after_row_level_trigger.mdx            |  114 ++
 .../05_instead_of_trigger.mdx                 |   63 +
 .../06_compound_trigger.mdx                   |  260 ++++
 .../13_triggers/07_trigger_examples/index.mdx |   20 +
 .../epas_compat_spl/13_triggers/index.mdx     |   20 +
 .../epas_compat_spl/14_packages.mdx           |   22 +
 .../01_attributes.mdx                         |   15 +
 .../01_basic_object_concepts/02_methods.mdx   |   13 +
 .../03_overloading_methods.mdx                |   11 +
 .../01_basic_object_concepts/index.mdx        |   23 +
 .../01_object_type_specification_syntax.mdx   |  127 ++
 .../02_object_type_body_syntax.mdx            |  104 ++
 .../02_object_type_components/index.mdx       |   24 +
 .../01_member_methods.mdx                     |   59 +
 .../02_static_methods.mdx                     |   59 +
 .../03_constructor_methods.mdx                |   87 ++
 .../03_creating_object_types/index.mdx        |   34 +
 .../04_creating_object_instances.mdx          |   76 +
 .../05_referencing_an_object.mdx              |  137 ++
 .../06_dropping_an_object_type.mdx            |   47 +
 .../15_object_types_and_objects/index.mdx     |   29 +
 .../images/definer's_rights_package.png       |    3 +
 .../images/definers_rights_package.png        |    3 +
 .../images/invokers_rights_programs.png       |    3 +
 .../epas_compat_spl/index.mdx                 |   21 +
 .../01_oracle_compat_summary.mdx              |   14 +
 .../01_interval_range_partitioning.mdx        |   31 +
 .../02_automatic_list_partitioning.mdx        |   21 +
 .../02_selecting_a_partition_type/index.mdx   |   50 +
 .../01_example_partition_pruning.mdx          |  123 ++
 .../03_using_partition_pruning/index.mdx      |  145 ++
 .../defining_a_default_partition.mdx          |  206 +++
 .../defining_a_maxvalue_partition.mdx         |   83 ++
 .../index.mdx                                 |   17 +
 ...ning_keys_in_a_range_partitioned_table.mdx |   55 +
 .../index.mdx                                 |   52 +
 .../epas_compat_table_partitioning/index.mdx  |   17 +
 .../epas/16/application_programming/index.mdx |    6 +
 .../01_default_optimization_modes.mdx         |   86 ++
 .../02_access_method_hints.mdx                |  278 ++++
 .../03_specifying_a_join_order.mdx            |   37 +
 .../04_joining_relations_hints.mdx            |  140 ++
 .../05_optimizer_hints/05_global_hints.mdx    |  150 ++
 .../06_using_the_append_optimizer_hint.mdx    |   42 +
 .../07_parallelism_hints.mdx                  |  210 +++
 .../08_conflicting_hints.mdx                  |   25 +
 .../about_optimizer_hints.mdx                 |   52 +
 .../05_optimizer_hints/index.mdx              |   32 +
 .../optimizing_code/index.mdx                 |    9 +
 .../optimizing_code/optimizing_code.mdx       |    8 +
 .../01_setting_new_parameters.mdx             |  174 +++
 .../01_shared_buffers.mdx                     |   27 +
 .../02_work_mem.mdx                           |   27 +
 .../03_maintenance_work_mem.mdx               |   25 +
 .../04_wal_buffers.mdx                        |   25 +
 .../05_checkpoint_segments.mdx                |    9 +
 .../06_checkpoint_completion_target.mdx       |   23 +
 .../07_checkpoint_timeout.mdx                 |   25 +
 .../08_max_wal_size.mdx                       |   23 +
 .../09_min_wal_size.mdx                       |   21 +
 .../10_bgwriter_delay.mdx                     |   25 +
 .../11_seq_page_cost.mdx                      |   23 +
 .../12_random_page_cost.mdx                   |   27 +
 .../13_effective_cache_size.mdx               |   27 +
 .../14_synchronous_commit.mdx                 |   27 +
 .../15_edb_max_spins_per_delay.mdx            |   23 +
 .../16_pg_prewarm.autoprewarm.mdx             |   39 +
 .../17_pg_prewarm.autoprewarm_interval.mdx    |   23 +
 .../index.mdx                                 |   20 +
 .../02_resource_usage_memory.mdx              |   63 +
 ...03_resource_usage_edb_resource_manager.mdx |   45 +
 .../04_query_tuning.mdx                       |   29 +
 ...ry_tuning_planner_method_configuration.mdx |   33 +
 .../06_reporting_and_logging_what_to_log.mdx  |   75 +
 .../07_auditing_settings/01_edb_audit.mdx     |   21 +
 .../02_edb_audit_directory.mdx                |   21 +
 .../03_edb_audit_filename.mdx                 |   21 +
 .../04_edb_audit_rotation_day.mdx             |   21 +
 .../05_edb_audit_rotation_size.mdx            |   21 +
 .../06_edb_audit_rotation_seconds.mdx         |   21 +
 .../07_edb_audit_connect.mdx                  |   21 +
 .../08_edb_audit_disconnect.mdx               |   21 +
 .../09_edb_audit_statement.mdx                |   32 +
 .../07_auditing_settings/10_edb_audit_tag.mdx |   19 +
 .../11_edb_audit_destination.mdx              |   26 +
 .../12_edb_log_every_bulk_value.mdx           |    9 +
 .../07_auditing_settings/index.mdx            |   16 +
 .../08_ccd_locale_and_formatting.mdx          |   36 +
 .../09_ccd_statement_behaviour.mdx            |   57 +
 .../10_ccd_other_defaults.mdx                 |   65 +
 .../11_compatibility_options.mdx              |  375 +++++
 .../12_customized_options.mdx                 |  392 +++++
 .../13_ungrouped.mdx                          |  101 ++
 .../14_audit_archiver.mdx                     |  194 +++
 .../attribute_descriptions.mdx                |   15 +
 .../index.mdx                                 |   21 +
 .../01_configuration_parameters/index.mdx     |   25 +
 .../control_file_examples.mdx                 |  486 +++++++
 .../building_the_control_file/index.mdx       |  114 ++
 .../02_edb_loader/data_loading_methods.mdx    |   17 +
 .../edb_loader_overview_and_restrictions.mdx  |   32 +
 .../02_edb_loader/index.mdx                   |   53 +
 .../conventional_path_load.mdx                |  108 ++
 .../invoking_edb_loader/direct_path_load.mdx  |   45 +
 .../invoking_edb_loader/index.mdx             |   18 +
 .../parallel_direct_path_load.mdx             |  153 ++
 .../performing_remote_loading.mdx             |   41 +
 .../running_edb_loader.mdx                    |  292 ++++
 .../02_edb_loader/using_edb_loader.mdx        |   30 +
 .../cpu_usage_throttling.mdx                  |  325 +++++
 .../creating_resource_groups.mdx              |  278 ++++
 .../dirty_buffer_throttling.mdx               |  397 ++++++
 .../edb_resource_manager_key_concepts.mdx     |   20 +
 .../10_edb_resource_manager/index.mdx         |   32 +
 .../checking_the_status.mdx                   |   45 +
 .../copying_a_remote_schema.mdx               |  327 +++++
 .../14_edb_clone_schema/copying_a_schema.mdx  |  307 ++++
 .../edb_clone_schema_overview.mdx             |   80 ++
 .../14_edb_clone_schema/index.mdx             |   23 +
 .../performing_cleanup_tasks.mdx              |   68 +
 .../setting_up_edb_clone_schema.mdx           |  291 ++++
 .../epas/16/database_administration/index.mdx |   11 +
 .../epas/16/epas_platform_support/index.mdx   |   15 +
 .../epas_rel_notes/epas16_2_0_rel_notes.mdx   |   12 +
 .../epas_rel_notes/epas16_3_0_rel_notes.mdx   |   21 +
 .../epas_rel_notes/epas16_4_0_rel_notes.mdx   |   20 +
 .../epas_rel_notes/epas16_4_1_rel_notes.mdx   |   12 +
 .../epas_rel_notes/epas16_6_0_rel_notes.mdx   |   19 +
 .../16/epas_rel_notes/epas16_rel_notes.mdx    |   34 +
 .../docs/epas/16/epas_rel_notes/index.mdx     |   46 +
 .../01_sql_protect_overview.mdx               |   99 ++
 .../02_configuring_sql_protect.mdx            |  510 +++++++
 .../03_common_maintenance_operations.mdx      |  260 ++++
 .../04_backing_up_restoring_sql_protect.mdx   |  276 ++++
 .../index.mdx                                 |   27 +
 .../03_edb_wrap/edb_wrap_key_concepts.mdx     |   17 +
 .../epas_security_guide/03_edb_wrap/index.mdx |   21 +
 .../03_edb_wrap/obfuscating_source_code.mdx   |  211 +++
 .../03_virtual_private_database.mdx           |   33 +
 .../01_creating_a_password_function.mdx       |  135 ++
 .../01_creating_a_new_profile/index.mdx       |  124 ++
 .../02_altering_a_profile.mdx                 |   50 +
 .../03_dropping_a_profile.mdx                 |   47 +
 ...iating_a_profile_with_an_existing_role.mdx |   85 ++
 .../05_unlocking_a_locked_account.mdx         |   72 +
 ...g_a_new_role_associated_with_a_profile.mdx |   83 ++
 ...acking_up_profile_management_functions.mdx |   25 +
 .../04_profile_management/index.mdx           |   31 +
 .../profile_overview.mdx                      |   33 +
 .../16/epas_security_guide/04_sslutils.mdx    |  109 ++
 .../creating_a_data_redaction_policy.mdx      |  200 +++
 .../data_redaction_key_concepts.mdx           |   36 +
 .../data_redaction_system_catalogs.mdx        |   39 +
 .../05_data_redaction/index.mdx               |   15 +
 .../modifying_a_data_redaction_policy.mdx     |  130 ++
 .../removing_a_data_redaction_policy.mdx      |   55 +
 .../02_selecting_sql_statements_to_audit.mdx  |  702 +++++++++
 .../03_enabling_audit_logging.mdx             |  263 ++++
 ...using_error_codes_to_filter_audit_logs.mdx |   32 +
 ...sing_command_tags_to_filter_audit_logs.mdx |   82 ++
 ...07_redacting_passwords_from_audit_logs.mdx |   63 +
 .../08_audit_log_archiving.mdx                |  139 ++
 .../09_object_auditing.mdx                    |  258 ++++
 .../05_edb_audit_logging/index.mdx            |   24 +
 .../epas/16/epas_security_guide/index.mdx     |   16 +
 .../16/epas_security_guide/tde_feature.mdx    |   12 +
 .../epas_fundamentals/benefits_epas.mdx       |   23 +
 .../epas_compat_ora_dev_guide/index.mdx       |   32 +
 .../fundamentals/epas_fundamentals/index.mdx  |    7 +
 .../epas_fundamentals/terminology.mdx         |   19 +
 .../docs/epas/16/fundamentals/index.mdx       |    9 +
 ..._about_the_examples_used_in_this_guide.mdx |   54 +
 .../sql_fundamentals/02_conventions.mdx       |   20 +
 .../01_sample_database_installation.mdx       |   23 +
 .../02_sample_database_description.mdx        |  560 ++++++++
 .../01_sample_database/index.mdx              |   21 +
 .../02_creating_a_new_table.mdx               |   43 +
 .../03_populating_a_table_with_rows.mdx       |   36 +
 .../02_sql_tutorial/04_querying_a_table.mdx   |  125 ++
 .../05_joins_between_tables.mdx               |  171 +++
 .../06_aggregate_functions.mdx                |   88 ++
 .../02_sql_tutorial/07_updates.mdx            |   37 +
 .../02_sql_tutorial/08_deletions.mdx          |   64 +
 .../02_sql_tutorial/09_the_sql_language.mdx   |   20 +
 .../02_sql_tutorial/index.mdx                 |   25 +
 .../03_advanced_concepts/01_views.mdx         |   66 +
 .../03_advanced_concepts/02_foreign_keys.mdx  |   45 +
 .../03_the_rownum_pseudo_column.mdx           |   79 ++
 .../03_advanced_concepts/04_synonyms.mdx      |  160 +++
 ...defining_the_parent_child_relationship.mdx |   24 +
 .../02_selecting_the_root_nodes.mdx           |    9 +
 ...ization_tree_in_the_sample_application.mdx |   47 +
 .../05_hierarchical_queries/04_node_level.mdx |   44 +
 .../05_ordering_the_siblings.mdx              |   66 +
 ...ing_the_root_node_with_connect_by_root.mdx |  223 +++
 ...ieving_a_path_with_sys_connect_by_path.mdx |   63 +
 .../05_hierarchical_queries/index.mdx         |  219 +++
 .../01_rollup_extension.mdx                   |  158 +++
 .../02_cube_extension.mdx                     |  227 +++
 .../03_grouping_sets_extension.mdx            |  330 +++++
 .../04_grouping_function.mdx                  |  152 ++
 .../05_grouping_id_function.mdx               |  114 ++
 .../06_multidimensional_analysis/index.mdx    |  111 ++
 .../03_advanced_concepts/index.mdx            |   21 +
 .../sql_fundamentals/03_examples_used.mdx     |  503 +++++++
 .../fundamentals/sql_fundamentals/index.mdx   |    7 +
 .../images/accessing_configuration_files.png  |    3 +
 .../acknowledging_components_removed.png      |    3 +
 .../16/images/additional_configuration.png    |    3 +
 .../epas/16/images/additional_directories.png |    3 +
 .../16/images/advanced_server_dialect.png     |    3 +
 ...dvanced_server_installation_completion.png |    3 +
 .../advanced_server_installer_welcome.png     |    3 +
 .../16/images/advanced_server_services.png    |    3 +
 .../16/images/advanced_server_startup.png     |    3 +
 .../16/images/advanced_server_uninstaller.png |    3 +
 ...ced_server_to_use_trust_authentication.png |    3 +
 .../docs/epas/16/images/connecting_server.png |    3 +
 ...connecting_to_advanced_server_database.png |    3 +
 .../epas/16/images/connecting_to_server.png   |    3 +
 .../16/images/definer's_rights_package.png    |    3 +
 .../images/download-complete-confirmation.png |    3 +
 .../docs/epas/16/images/download_complete.png |    3 +
 ...tune_dynamic_tuning_server_utilization.png |    3 +
 ...natune_dynamic_tuning_workload_profile.png |    3 +
 .../docs/epas/16/images/ecpg_path.png         |    3 +
 .../employee_organization_hierarchy.png       |    3 +
 .../images/enterprisedb_license_agreement.png |    3 +
 .../16/images/epas_tools_utility_edb_wrap.png |    3 +
 .../epas/16/images/installation_directory.png |    3 +
 .../16/images/installing_advanced_server.png  |    3 +
 .../16/images/invokers_rights_programs.png    |    3 +
 .../epas/16/images/open_client_library.png    |    3 +
 .../docs/epas/16/images/parameters_tab.png    |    3 +
 .../docs/epas/16/images/password_window.png   |    3 +
 .../16/images/pgadmin4_client_dashboard.png   |    3 +
 .../16/images/pre_installation_summary.png    |    3 +
 .../docs/epas/16/images/program_body.png      |    3 +
 .../docs/epas/16/images/proxy_servers.png     |    3 +
 .../docs/epas/16/images/ready_to_install.png  |    3 +
 .../epas/16/images/sample_database_tables.png |    3 +
 .../docs/epas/16/images/select_components.png |    3 +
 .../selected-packages-summary-window.png      |    3 +
 ...lobal_breakpoint_from_left-hand_margin.png |    3 +
 .../docs/epas/16/images/setup_wizard.png      |    3 +
 .../docs/epas/16/images/stack_tab.png         |    3 +
 ...us-confirms-the-completed-installation.png |    3 +
 ...ackbuilder_plus_completed_installation.png |    3 +
 .../stackbuilder_plus_module_selection.png    |    3 +
 .../16/images/stackbuilder_plus_welcome.png   |    3 +
 ...ry-window-displaying-selected-packages.png |    3 +
 .../16/images/the-proxy-servers-dialog.png    |    3 +
 ...ckbuilder-plus-module-selection-window.png |    3 +
 .../images/the-stackbuilder-plus-welcome.png  |    3 +
 .../16/images/uninstallation_complete.png     |    3 +
 product_docs/docs/epas/16/index.mdx           |   44 +
 .../docs/epas/16/installing/index.mdx         |   66 +
 .../installing/linux_arm64/epas_debian_12.mdx |  129 ++
 .../epas/16/installing/linux_arm64/index.mdx  |   13 +
 .../component_locations.mdx                   |   57 +
 .../linux_install_details/index.mdx           |   14 +
 ...installing_epas_using_local_repository.mdx |   57 +
 .../configuring_a_package_installation.mdx    |   61 +
 .../connecting_to_epas.mdx                    |   28 +
 .../index.mdx                                 |   12 +
 .../modifying_the_data_directory_location.mdx |  114 ++
 .../specifying_cluster_options.mdx            |   95 ++
 .../starting_and_stopping_services.mdx        |  117 ++
 .../starting_multiple_postmasters.mdx         |   41 +
 .../linux_install_details/rpm_packages.mdx    |  152 ++
 .../updating_an_rpm_installation.mdx          |   23 +
 .../installing/linux_ppc64le/epas_rhel_8.mdx  |  159 +++
 .../installing/linux_ppc64le/epas_rhel_9.mdx  |  159 +++
 .../installing/linux_ppc64le/epas_sles_15.mdx |  147 ++
 .../16/installing/linux_ppc64le/index.mdx     |   30 +
 .../linux_x86_64/epas_debian_11.mdx           |  129 ++
 .../linux_x86_64/epas_debian_12.mdx           |  129 ++
 .../linux_x86_64/epas_other_linux_8.mdx       |  150 ++
 .../linux_x86_64/epas_other_linux_9.mdx       |  150 ++
 .../installing/linux_x86_64/epas_rhel_8.mdx   |  157 ++
 .../installing/linux_x86_64/epas_rhel_9.mdx   |  157 ++
 .../installing/linux_x86_64/epas_sles_15.mdx  |  147 ++
 .../linux_x86_64/epas_ubuntu_20.mdx           |  129 ++
 .../linux_x86_64/epas_ubuntu_22.mdx           |  129 ++
 .../epas/16/installing/linux_x86_64/index.mdx |   58 +
 .../16/installing/troubleshooting/index.mdx   |   11 +
 .../enabling_core_dump.mdx                    |  232 +++
 .../linux_troubleshooting/index.mdx           |   17 +
 .../installation_troubleshooting_linux.mdx    |   44 +
 .../windows_troubleshooting.mdx               |   29 +
 .../epas/16/installing/uninstalling/index.mdx |   10 +
 .../uninstalling/linux_uninstall.mdx          |   62 +
 .../uninstalling/windows_uninstall.mdx        |   41 +
 .../docs/epas/16/installing/windows/index.mdx |   16 +
 .../index.mdx                                 |   30 +
 .../index.mdx                                 |   29 +
 ...n_installation_with_limited_privileges.mdx |   64 +
 .../performing_an_unattended_installation.mdx |   31 +
 .../reference_command_line_options.mdx        |  172 +++
 ...ng_a_graphical_installation_on_windows.mdx |  200 +++
 .../setting_cluster_preferences.mdx           |   27 +
 .../using_stackbuilder_plus.mdx               |   52 +
 .../configuring_epas.mdx                      |   99 ++
 ...ing_server_startup_behavior_on_windows.mdx |   17 +
 .../index.mdx                                 |   23 +
 .../starting_and_stopping_epas.mdx            |   16 +
 ...sing_pg_ctl_to_control_advanced_server.mdx |   28 +
 .../using_the_windows_services_applet.mdx     |   19 +
 .../managing_performance/03_sql_profiler.mdx  |   33 +
 .../index.mdx                                 |   38 +
 .../performance_tuning_recommendations.mdx    |  105 ++
 .../simulating_statspack_reports.mdx          |  941 ++++++++++++
 .../taking_a_snapshot.mdx                     |   44 +
 .../using_drita_functions.mdx                 |  479 +++++++
 .../evaluating_wait_states.mdx                |   12 +
 .../epas/16/managing_performance/index.mdx    |   12 +
 .../16/managing_performance/query_advisor.mdx |    6 +
 .../managing_performance/using_dynatune.mdx   |   53 +
 .../epas/16/planning/configuration_mode.mdx   |   18 +
 .../16/planning/deployment_options/index.mdx  |   14 +
 product_docs/docs/epas/16/planning/index.mdx  |    6 +
 .../epas_limitations/index.mdx                |   11 +
 .../epas_requirements/index.mdx               |   56 +
 .../planning/planning_prerequisites/index.mdx |    7 +
 .../01_all_part_tables.mdx                    |   39 +
 .../02_all_tab_partitions.mdx                 |   47 +
 .../03_all_tab_subpartitions.mdx              |   46 +
 .../04_all_part_key_columns.mdx               |   18 +
 .../05_all_subpart_key_columns.mdx            |   18 +
 .../index.mdx                                 |   21 +
 .../03_system_catalog_tables.mdx              |  135 ++
 .../c_preprocessor_directives.mdx             |  129 ++
 .../07_reference/ecpgplus_statements.mdx      | 1257 +++++++++++++++++
 .../07_reference/index.mdx                    |   75 +
 .../07_reference/sqlda_structure.mdx          |  120 ++
 .../07_reference/supported_c_data_types.mdx   |   36 +
 .../07_reference/type_codes.mdx               |   40 +
 .../index.mdx                                 |    7 +
 .../02_case_sensitivity.mdx                   |   26 +
 .../01_basic_spl_elements/03_identifiers.mdx  |   21 +
 .../01_basic_spl_elements/04_qualifiers.mdx   |   45 +
 .../01_basic_spl_elements/05_constants.mdx    |   17 +
 .../06_user_defined_pl_sql_subtypes.mdx       |  118 ++
 .../01_basic_spl_elements/07_character.mdx    |   19 +
 .../01_basic_spl_elements/index.mdx           |   15 +
 .../04_basic_statements/01_assignment.mdx     |   43 +
 .../04_basic_statements/02_delete.mdx         |   47 +
 .../04_basic_statements/03_insert.mdx         |   84 ++
 .../04_basic_statements/04_null.mdx           |   40 +
 .../05_using_the_returning_into_clause.mdx    |  138 ++
 .../04_basic_statements/06_select_into.mdx    |  107 ++
 .../04_basic_statements/07_update.mdx         |   54 +
 .../08_obtaining_the_result_status.mdx        |   48 +
 .../04_basic_statements/index.mdx             |   21 +
 .../01_if_statement/01_if_then.mdx            |   57 +
 .../01_if_statement/02_if_then_else.mdx       |   72 +
 .../01_if_statement/03_if_then_else_if.mdx    |   92 ++
 .../04_if_then_elseif_else.mdx                |   77 +
 .../01_if_statement/index.mdx                 |   22 +
 .../02_return_statement.mdx                   |   45 +
 .../03_goto_statement.mdx                     |  101 ++
 .../01_selector_case_expression.mdx           |   86 ++
 .../02_searched_case_expression.mdx           |   85 ++
 .../04_case_expression/index.mdx              |   23 +
 .../01_selector_case_statement.mdx            |   95 ++
 .../02_searched_case_statement.mdx            |   92 ++
 .../05_case_statement/index.mdx               |   23 +
 .../06_loops/01_loop.mdx                      |   16 +
 .../06_loops/02_exit.mdx                      |   53 +
 .../06_loops/03_continue.mdx                  |   43 +
 .../06_loops/04_while.mdx                     |   53 +
 .../06_loops/05_for_integer_variant.mdx       |   65 +
 .../05_control_structures/06_loops/index.mdx  |   21 +
 .../07_exception_handling.mdx                 |   70 +
 .../08_user_defined_exceptions.mdx            |   87 ++
 .../09_pragma_exception_init.mdx              |  110 ++
 .../10_raise_application_error.mdx            |   75 +
 .../05_control_structures/index.mdx           |   21 +
 .../11_collection_methods/01_count.mdx        |   47 +
 .../11_collection_methods/02_deletes.mdx      |   75 +
 .../11_collection_methods/03_exists.mdx       |   47 +
 .../11_collection_methods/04_extend.mdx       |  137 ++
 .../11_collection_methods/05_first.mdx        |   40 +
 .../11_collection_methods/06_last.mdx         |   40 +
 .../11_collection_methods/07_limit.mdx        |   20 +
 .../11_collection_methods/08_next.mdx         |   42 +
 .../11_collection_methods/09_prior.mdx        |   41 +
 .../11_collection_methods/10_trim.mdx         |   72 +
 .../11_collection_methods/index.mdx           |   22 +
 .../17_advanced_server_keywords.mdx           |   93 ++
 .../index.mdx                                 |    8 +
 ...audit_logging_configuration_parameters.mdx |  126 ++
 .../01_index_advisor_components.mdx           |   42 +
 .../01_introduction/01_edb_redwood_date.mdx   |   17 +
 .../02_edb_redwood_raw_names.mdx              |   74 +
 .../03_edb_redwood_strings.mdx                |   69 +
 .../01_introduction/04_edb_stmt_level_tx.mdx  |   64 +
 .../01_introduction/05_oracle_home.mdx        |   30 +
 .../01_introduction/index.mdx                 |   27 +
 ...02_summary_of_configuration_parameters.mdx |  363 +++++
 .../04_audit_log_file.mdx                     |  278 ++++
 .../edb_loader_control_file_parameters.mdx    |  311 ++++
 .../edb_resource_manager_system_catalogs.mdx  |   34 +
 .../index.mdx                                 |    7 +
 product_docs/docs/epas/16/reference/index.mdx |    9 +
 .../01_dblink_ora_connect.mdx                 |   53 +
 .../02_dblink_ora_status.mdx                  |   20 +
 .../03_dblink_ora_disconnect.mdx              |   20 +
 .../04_dblink_ora_record.mdx                  |   22 +
 .../05_dblink_ora_call.mdx                    |   24 +
 .../06_dblink_ora_exec.mdx                    |   22 +
 .../07_dblink_ora_copy.mdx                    |   29 +
 .../index.mdx                                 |   22 +
 .../01_example_partition_by_list.mdx          |   47 +
 .../02_example_automatic_list_partition.mdx   |   60 +
 .../03_example_partition_by_range.mdx         |   54 +
 .../04_example_interval_range_partition.mdx   |   58 +
 .../05_example_partition_by_hash.mdx          |   73 +
 .../06_example_partitions_number.mdx          |  444 ++++++
 ...artition_by_range_subpartition_by_list.mdx |   82 ++
 .../08_example_creating_unique_index.mdx      |   82 ++
 .../09_example_subpartition_template.mdx      |  190 +++
 .../01_create_table_partition_by/index.mdx    |  234 +++
 ..._partition_to_a_list_partitioned_table.mdx |   60 +
 ...partition_to_a_range_partitioned_table.mdx |   67 +
 ..._a_partition_with_subpartitions_number.mdx |  190 +++
 .../02_alter_table_add_partition/index.mdx    |  114 ++
 ...tion_to_a_list_range_partitioned_table.mdx |   89 ++
 ...tion_to_a_range_list_partitioned_table.mdx |   67 +
 .../03_alter_table_add_subpartition/index.mdx |   85 ++
 .../01_example_splitting_a_list_partition.mdx |  111 ++
 ...02_example_splitting_a_range_partition.mdx |  120 ++
 ...ample_splitting_a_range_list_partition.mdx |  228 +++
 .../04_alter_table_split_partition/index.mdx  |  110 ++
 ..._example_splitting_a_list_subpartition.mdx |  139 ++
 ...example_splitting_a_range_subpartition.mdx |  170 +++
 .../index.mdx                                 |   92 ++
 ...ple_exchanging_a_table_for_a_partition.mdx |  135 ++
 .../index.mdx                                 |   76 +
 ..._a_partition_to_a_different_tablespace.mdx |   66 +
 .../07_alter_table_move_partition/index.mdx   |   62 +
 .../01_example_renaming_a_partition.mdx       |   59 +
 .../08_alter_table_rename_partition/index.mdx |   62 +
 ...le_setting_an_interval_range_partition.mdx |   65 +
 .../09_alter_table_set_interval/index.mdx     |   41 +
 ...le_setting_an_automatic_list_partition.mdx |   65 +
 .../index.mdx                                 |   37 +
 ...xample_setting_a_subpartition_template.mdx |  469 ++++++
 .../index.mdx                                 |   59 +
 .../12_drop_table.mdx                         |   43 +
 .../01_example_deleting_a_partition.mdx       |   59 +
 .../13_alter_table_drop_partition/index.mdx   |   40 +
 .../01_example_deleting_a_subpartition.mdx    |   66 +
 .../index.mdx                                 |   38 +
 .../01_example_emptying_a_table.mdx           |   96 ++
 .../15_truncate_table/index.mdx               |   36 +
 .../01_example_emptying_a_partition.mdx       |  116 ++
 .../index.mdx                                 |   45 +
 .../01_example_emptying_a_subpartition.mdx    |  126 ++
 .../index.mdx                                 |   46 +
 .../18_accessing_partition_table/index.mdx    |  257 ++++
 .../index.mdx                                 |   21 +
 .../limitations.mdx                           |   39 +
 .../03_built-in_packages/01_dbms_alert.mdx    |  398 ++++++
 .../02_dbms_aq/01_enqueue.mdx                 |  118 ++
 .../02_dbms_aq/02_dequeue.mdx                 |  130 ++
 .../02_dbms_aq/03_register.mdx                |   61 +
 .../02_dbms_aq/04_unregister.mdx              |   62 +
 .../03_built-in_packages/02_dbms_aq/index.mdx |   74 +
 .../03_dbms_aqadm/01_alter_queue.mdx          |   50 +
 .../03_dbms_aqadm/02_alter_queue_table.mdx    |   45 +
 .../03_dbms_aqadm/03_create_queue.mdx         |   73 +
 .../03_dbms_aqadm/04_create_queue_table.mdx   |  115 ++
 .../03_dbms_aqadm/05_drop_queue.mdx           |   33 +
 .../03_dbms_aqadm/06_drop_queue_table.mdx     |   41 +
 .../03_dbms_aqadm/07_purge_queue_table.mdx    |   46 +
 .../03_dbms_aqadm/08_start_queue.mdx          |   39 +
 .../03_dbms_aqadm/09_stop_queue.mdx           |   46 +
 .../03_dbms_aqadm/index.mdx                   |   52 +
 .../04_dbms_crypto/01_decrypt.mdx             |   98 ++
 .../04_dbms_crypto/02_encrypt.mdx             |   95 ++
 .../04_dbms_crypto/03_hash.mdx                |   46 +
 .../04_dbms_crypto/04_mac.mdx                 |   52 +
 .../04_dbms_crypto/05_randombytes.mdx         |   30 +
 .../04_dbms_crypto/06_randominteger.mdx       |   24 +
 .../04_dbms_crypto/07_randomnumber.mdx        |   24 +
 .../04_dbms_crypto/index.mdx                  |   47 +
 .../05_dbms_job/01_broken.mdx                 |   43 +
 .../05_dbms_job/02_change.mdx                 |   49 +
 .../05_dbms_job/03_interval.mdx               |   31 +
 .../05_dbms_job/04_next_date.mdx              |   31 +
 .../05_dbms_job/05_remove.mdx                 |   27 +
 .../05_dbms_job/06_run.mdx                    |   27 +
 .../05_dbms_job/07_submit.mdx                 |   68 +
 .../05_dbms_job/08_what.mdx                   |   31 +
 .../05_dbms_job/index.mdx                     |   53 +
 .../06_dbms_lob/01_append.mdx                 |   21 +
 .../06_dbms_lob/02_compare.mdx                |   39 +
 .../06_dbms_lob/03_converttoblob.mdx          |   60 +
 .../06_dbms_lob/04_converttoclob.mdx          |   60 +
 .../06_dbms_lob/05_copy.mdx                   |   36 +
 .../06_dbms_lob/06_erase.mdx                  |   30 +
 .../06_dbms_lob/07_get_storage_limit.mdx      |   23 +
 .../06_dbms_lob/08_getlength.mdx              |   23 +
 .../06_dbms_lob/09_instr.mdx                  |   34 +
 .../06_dbms_lob/10_read.mdx                   |   34 +
 .../06_dbms_lob/11_substr.mdx                 |   30 +
 .../06_dbms_lob/12_trim.mdx                   |   21 +
 .../06_dbms_lob/13_write.mdx                  |   31 +
 .../06_dbms_lob/14_writeappend.mdx            |   26 +
 .../06_dbms_lob/index.mdx                     |   60 +
 .../03_built-in_packages/07_dbms_lock.mdx     |   32 +
 .../08_dbms_mview/01_get_mv_dependencies.mdx  |   36 +
 .../08_dbms_mview/02_refresh.mdx              |   91 ++
 .../08_dbms_mview/03_refresh_all_mviews.mdx   |   52 +
 .../08_dbms_mview/04_refresh_dependent.mdx    |   82 ++
 .../08_dbms_mview/index.mdx                   |   29 +
 .../03_built-in_packages/09_dbms_output.mdx   |  431 ++++++
 .../10_dbms_pipe/01_create_pipe.mdx           |   56 +
 .../10_dbms_pipe/02_next_item_pipe.mdx        |  116 ++
 .../10_dbms_pipe/03_pack_message.mdx          |   19 +
 .../10_dbms_pipe/04_purge.mdx                 |   77 +
 .../10_dbms_pipe/05_receive_message.mdx       |   34 +
 .../10_dbms_pipe/06_remove_pipe.mdx           |   90 ++
 .../10_dbms_pipe/07_reset_buffer.mdx          |   52 +
 .../10_dbms_pipe/08_send_message.mdx          |   38 +
 .../10_dbms_pipe/09_unique_session_name.mdx   |   32 +
 .../10_dbms_pipe/10_unpack_message.mdx        |   17 +
 .../10_dbms_pipe/11_comprehensive_example.mdx |  160 +++
 .../10_dbms_pipe/index.mdx                    |   45 +
 .../10_dbms_privilege_capture.mdx             |  462 ++++++
 .../03_built-in_packages/11_dbms_profiler.mdx |  853 +++++++++++
 .../03_built-in_packages/12_dbms_random.mdx   |  238 ++++
 .../03_built-in_packages/13_dbms_redact.mdx   |  711 ++++++++++
 .../03_built-in_packages/14_dbms_rls.mdx      |  509 +++++++
 ...syntax_to_specify_a_repeating_interval.mdx |   34 +
 .../15_dbms_scheduler/02_create_job.mdx       |  113 ++
 .../15_dbms_scheduler/03_create_program.mdx   |   69 +
 .../15_dbms_scheduler/04_create_schedule.mdx  |   59 +
 .../05_define_program_argument.mdx            |   76 +
 .../06_dbms_scheduler_disable.mdx             |   40 +
 .../15_dbms_scheduler/07_drop_job.mdx         |   43 +
 .../15_dbms_scheduler/08_drop_program.mdx     |   37 +
 .../09_drop_program_argument.mdx              |   49 +
 .../15_dbms_scheduler/10_drop_schedule.mdx    |   36 +
 .../11_dbms_scheduler_enable.mdx              |   37 +
 .../12_evaluate_calendar_string.mdx           |   61 +
 .../15_dbms_scheduler/13_run_job.mdx          |   33 +
 .../14_set_job_argument_value.mdx             |   57 +
 .../15_dbms_scheduler/index.mdx               |   45 +
 .../03_built-in_packages/16_dbms_session.mdx  |   44 +
 .../17_dbms_sql/001_bind_array.mdx            |   94 ++
 .../17_dbms_sql/01_bind_variable.mdx          |   77 +
 .../17_dbms_sql/02_bind_variable_char.mdx     |   30 +
 .../17_dbms_sql/03_bind_variable_raw.mdx      |   30 +
 .../17_dbms_sql/04_close_cursor.mdx           |   41 +
 .../17_dbms_sql/05_column_value.mdx           |   77 +
 .../17_dbms_sql/06_column_value_char.mdx      |   34 +
 .../17_dbms_sql/07_column_value_raw.mdx       |   71 +
 .../17_dbms_sql/07a_column_value_long.mdx     |  103 ++
 .../17_dbms_sql/07b_column_value_rowid.mdx    |   75 +
 .../17_dbms_sql/07c_define_array.mdx          |  103 ++
 .../17_dbms_sql/08_define_column.mdx          |  109 ++
 .../17_dbms_sql/09_define_column_char.mdx     |   30 +
 .../17_dbms_sql/10_define_column_raw.mdx      |   76 +
 .../17_dbms_sql/10a_define_column_long.mdx    |   87 ++
 .../17_dbms_sql/10b_define_column_rowid.mdx   |   73 +
 .../17_dbms_sql/11_describe_columns.mdx       |   40 +
 .../17_dbms_sql/11a_describe_columns2.mdx     |   77 +
 .../17_dbms_sql/11b_describe_columns3.mdx     |   74 +
 .../17_dbms_sql/12_execute.mdx                |   40 +
 .../17_dbms_sql/13_execute_and_fetch.mdx      |   96 ++
 .../17_dbms_sql/14_fetch_rows.mdx             |   84 ++
 .../17_dbms_sql/15_is_open.mdx                |   21 +
 .../17_dbms_sql/16_last_row_count.mdx         |  111 ++
 .../17_dbms_sql/17_open_cursor.mdx            |   36 +
 .../17_dbms_sql/18_parse.mdx                  |   83 ++
 .../17_dbms_sql/19_to_cursor_number.mdx       |   47 +
 .../17_dbms_sql/20_to_refcursor.mdx           |   87 ++
 .../17_dbms_sql/index.mdx                     |   64 +
 .../03_built-in_packages/18_dbms_utility.mdx  |  867 ++++++++++++
 .../19_utl_encode/01_base64_decode.mdx        |   50 +
 .../19_utl_encode/02_base64_encode.mdx        |   58 +
 .../19_utl_encode/03_mimeheader_decode.mdx    |   41 +
 .../19_utl_encode/04_mimeheader_encode.mdx    |   53 +
 .../05_quoted_printable_decode.mdx            |   50 +
 .../06_quoted_printable_encode.mdx            |   48 +
 .../19_utl_encode/07_text_decode.mdx          |   54 +
 .../19_utl_encode/08_text_encode.mdx          |   54 +
 .../19_utl_encode/09_uudecode.mdx             |   58 +
 .../19_utl_encode/10_uuencode.mdx             |   72 +
 .../19_utl_encode/index.mdx                   |   32 +
 .../03_built-in_packages/20_utl_file.mdx      | 1213 ++++++++++++++++
 .../03_built-in_packages/21_utl_http.mdx      | 1025 ++++++++++++++
 .../03_built-in_packages/22_utl_mail.mdx      |  219 +++
 .../03_built-in_packages/23_utl_raw.mdx       |  280 ++++
 .../03_built-in_packages/24_utl_smtp.mdx      |  462 ++++++
 .../03_built-in_packages/25_utl_url.mdx       |  158 +++
 .../htp_and_htf/address.mdx                   |   34 +
 .../htp_and_htf/anchor.mdx                    |   44 +
 .../htp_and_htf/applet.mdx                    |   38 +
 .../03_built-in_packages/htp_and_htf/area.mdx |   38 +
 .../03_built-in_packages/htp_and_htf/base.mdx |   28 +
 .../htp_and_htf/basefont.mdx                  |   27 +
 .../htp_and_htf/bgsound.mdx                   |   32 +
 .../03_built-in_packages/htp_and_htf/big.mdx  |   30 +
 .../htp_and_htf/blockquote.mdx                |   36 +
 .../03_built-in_packages/htp_and_htf/body.mdx |   34 +
 .../03_built-in_packages/htp_and_htf/bold.mdx |   31 +
 .../htp_and_htf/br_and_nl.mdx                 |   36 +
 .../htp_and_htf/caption.mdx                   |   32 +
 .../htp_and_htf/center.mdx                    |   27 +
 .../centeropen_and_centerclose.mdx            |   25 +
 .../03_built-in_packages/htp_and_htf/cite.mdx |   30 +
 .../03_built-in_packages/htp_and_htf/code.mdx |   30 +
 .../htp_and_htf/comment.mdx                   |   27 +
 .../03_built-in_packages/htp_and_htf/dfn.mdx  |   29 +
 .../htp_and_htf/dirlist.mdx                   |   25 +
 .../03_built-in_packages/htp_and_htf/div.mdx  |   30 +
 .../htp_and_htf/dlistdef.mdx                  |   32 +
 .../htp_and_htf/dlistopen_and_dlistclose.mdx  |   34 +
 .../htp_and_htf/dlistterm.mdx                 |   32 +
 .../htp_and_htf/em_and_emphasis.mdx           |   36 +
 .../htp_and_htf/escape_sc.mdx                 |   32 +
 .../03_built-in_packages/htp_and_htf/font.mdx |   38 +
 .../htp_and_htf/formcheckbox.mdx              |   34 +
 .../htp_and_htf/formfile.mdx                  |   32 +
 .../htp_and_htf/formhidden.mdx                |   32 +
 .../htp_and_htf/formimage.mdx                 |   34 +
 .../htp_and_htf/formopen_and_formclose.mdx    |   40 +
 .../htp_and_htf/formpassword.mdx              |   36 +
 .../htp_and_htf/formradio.mdx                 |   34 +
 .../htp_and_htf/formreset.mdx                 |   30 +
 .../formselectopen_and_formselectclose.mdx    |   38 +
 .../htp_and_htf/formselectoption.mdx          |   32 +
 .../htp_and_htf/formsubmit.mdx                |   32 +
 .../htp_and_htf/formtext.mdx                  |   36 +
 .../htp_and_htf/formtextarea.mdx              |   50 +
 .../formtextarea_and_formtextarea2.mdx        |   47 +
 .../htp_and_htf/frame.mdx                     |   40 +
 .../framesetopen_and_framsetclose.mdx         |   36 +
 .../htp_and_htf/header.mdx                    |   38 +
 .../htp_and_htf/headopen_and_headclose.mdx    |   25 +
 .../03_built-in_packages/htp_and_htf/hr.mdx   |   37 +
 .../htp_and_htf/htmlopen_and_htmlclose.mdx    |   25 +
 .../03_built-in_packages/htp_and_htf/img.mdx  |   46 +
 .../htp_and_htf/index.mdx                     |   18 +
 .../htp_and_htf/isindex.mdx                   |   30 +
 .../htp_and_htf/italic.mdx                    |   30 +
 .../htp_and_htf/kbd_and_keyboard.mdx          |   36 +
 .../htp_and_htf/linkrel.mdx                   |   32 +
 .../htp_and_htf/linkrev.mdx                   |   32 +
 .../htp_and_htf/listheader.mdx                |   30 +
 .../listingopen_and_listingclose.mdx          |   25 +
 .../htp_and_htf/listitem.mdx                  |   36 +
 .../htp_and_htf/mailto.mdx                    |   34 +
 .../htp_and_htf/mapopen_and_mapclose.mdx      |   34 +
 .../menulistopen_and_menulistclose.mdx        |   25 +
 .../03_built-in_packages/htp_and_htf/meta.mdx |   32 +
 .../03_built-in_packages/htp_and_htf/nobr.mdx |   27 +
 .../noframesopen_and_noframesclose.mdx        |   25 +
 .../htp_and_htf/olistopen_and_olistclose.mdx  |   36 +
 .../htp_and_htf/para_and_paragraph.mdx        |   38 +
 .../htp_and_htf/param.mdx                     |   30 +
 .../htp_and_htf/plaintext.mdx                 |   30 +
 .../htp_and_htf/preopen_and_preclose.mdx      |   36 +
 .../htp_and_htf/print_and_prn.mdx             |   31 +
 .../htp_and_htf/prints_and_ps.mdx             |   30 +
 .../03_built-in_packages/htp_and_htf/s.mdx    |   30 +
 .../htp_and_htf/sample.mdx                    |   30 +
 .../htp_and_htf/small.mdx                     |   30 +
 .../htp_and_htf/strike.mdx                    |   30 +
 .../htp_and_htf/strong.mdx                    |   30 +
 .../htp_and_htf/style.mdx                     |   27 +
 .../03_built-in_packages/htp_and_htf/sub.mdx  |   32 +
 .../03_built-in_packages/htp_and_htf/sup.mdx  |   32 +
 .../htp_and_htf/tabledata.mdx                 |   40 +
 .../htp_and_htf/tableheader.mdx               |   40 +
 .../htp_and_htf/tableopen_and_tableclose.mdx  |   40 +
 .../htp_and_htf/tablerow.mdx                  |   40 +
 .../htp_and_htf/teletype.mdx                  |   30 +
 .../htp_and_htf/title.mdx                     |   27 +
 .../htp_and_htf/ulist.mdx                     |   40 +
 .../htp_and_htf/underline.mdx                 |   30 +
 .../htp_and_htf/variable.mdx                  |   30 +
 .../03_built-in_packages/htp_and_htf/wbr.mdx  |   21 +
 .../03_built-in_packages/index.mdx            |   25 +
 .../epas_compat_bip_guide/index.mdx           |   14 +
 .../epas_compat_cat_views/index.mdx           |   17 +
 .../02_all_all_tables.mdx                     |   24 +
 .../03_all_cons_columns.mdx                   |   24 +
 .../04_all_constraints.mdx                    |   31 +
 .../05_all_col_privs.mdx                      |   25 +
 .../06_all_db_links.mdx                       |   22 +
 .../07_all_dependencies.mdx                   |   22 +
 .../08_all_directories.mdx                    |   18 +
 .../09_all_ind_columns.mdx                    |   28 +
 .../10_all_indexes.mdx                        |   35 +
 .../oracle_compatible_views/11_all_jobs.mdx   |   35 +
 .../12_all_objects.mdx                        |   25 +
 .../13_all_part_key_columns.mdx               |   23 +
 .../14_all_part_tables.mdx                    |   44 +
 .../15_all_policies.mdx                       |   35 +
 .../oracle_compatible_views/16_all_queues.mdx |   28 +
 .../17_all_queue_tables.mdx                   |   28 +
 .../18_all_sequences.mdx                      |   27 +
 .../oracle_compatible_views/19_all_source.mdx |   24 +
 .../20_all_subpart_key_columns.mdx            |   23 +
 .../21_all_synonyms.mdx                       |   24 +
 .../22_all_tab_columns.mdx                    |   29 +
 .../23_all_tab_partitions.mdx                 |   52 +
 .../24_all_tab_subpartitions.mdx              |   51 +
 .../25_all_tab_privs.mdx                      |   27 +
 .../oracle_compatible_views/26_all_tables.mdx |   24 +
 .../27_all_triggers.mdx                       |   30 +
 .../oracle_compatible_views/28_all_types.mdx  |   23 +
 .../oracle_compatible_views/29_all_users.mdx  |   21 +
 .../30_all_view_columns.mdx                   |   28 +
 .../oracle_compatible_views/31_all_views.mdx  |   21 +
 .../32_dba_all_tables.mdx                     |   24 +
 .../33_dba_cons_columns.mdx                   |   24 +
 .../34_dba_constraints.mdx                    |   31 +
 .../35_dba_col_privs.mdx                      |   22 +
 .../36_dba_db_links.mdx                       |   22 +
 .../37_dba_directories.mdx                    |   19 +
 .../38_dba_dependencies.mdx                   |   22 +
 .../39_dba_ind_columns.mdx                    |   27 +
 .../40_dba_indexes.mdx                        |   35 +
 .../oracle_compatible_views/41_dba_jobs.mdx   |   35 +
 .../42_dba_objects.mdx                        |   25 +
 .../43_dba_part_key_columns.mdx               |   24 +
 .../44_dba_part_tables.mdx                    |   44 +
 .../45_dba_policies.mdx                       |   35 +
 .../45a_dba_privs_capture.mdx                 |   18 +
 .../46_dba_profiles.mdx                       |   22 +
 .../oracle_compatible_views/47_dba_queues.mdx |   28 +
 .../48_dba_queue_tables.mdx                   |   28 +
 .../49_dba_role_privs.mdx                     |   21 +
 .../oracle_compatible_views/50_dba_roles.mdx  |   19 +
 .../51_dba_sequences.mdx                      |   27 +
 .../oracle_compatible_views/52_dba_source.mdx |   23 +
 .../53_dba_subpart_key_columns.mdx            |   23 +
 .../54_dba_synonyms.mdx                       |   24 +
 .../55_dba_tab_columns.mdx                    |   28 +
 .../56_dba_tab_partitions.mdx                 |   52 +
 .../57_dba_tab_subpartitions.mdx              |   51 +
 .../58_dba_tab_privs.mdx                      |   23 +
 .../oracle_compatible_views/59_dba_tables.mdx |   24 +
 .../60_dba_triggers.mdx                       |   30 +
 .../oracle_compatible_views/61_dba_types.mdx  |   23 +
 .../oracle_compatible_views/62_dba_users.mdx  |   30 +
 .../62a_dba_used_privs.mdx                    |   19 +
 .../62b_dba_unused_privs.mdx                  |   19 +
 .../63_dba_view_columns.mdx                   |   28 +
 .../oracle_compatible_views/64_dba_views.mdx  |   21 +
 .../65_user_all_tables.mdx                    |   23 +
 .../66_user_cons_columns.mdx                  |   24 +
 .../67_user_constraints.mdx                   |   31 +
 .../68_user_col_privs.mdx                     |   22 +
 .../69_user_db_links.mdx                      |   22 +
 .../70_user_dependencies.mdx                  |   22 +
 .../71_user_indexes.mdx                       |   34 +
 .../oracle_compatible_views/72_user_jobs.mdx  |   36 +
 .../73_user_objects.mdx                       |   24 +
 .../74_user_part_tables.mdx                   |   42 +
 .../75_user_policies.mdx                      |   34 +
 .../76_user_queues.mdx                        |   27 +
 .../77_user_queue_tables.mdx                  |   27 +
 .../78_user_role_privs.mdx                    |   22 +
 .../79_user_sequences.mdx                     |   26 +
 .../80_user_source.mdx                        |   22 +
 .../81_user_subpart_key_columns.mdx           |   22 +
 .../82_user_synonyms.mdx                      |   24 +
 .../83_user_tab_columns.mdx                   |   27 +
 .../84_user_tab_partitions.mdx                |   52 +
 .../85_user_tab_subpartitions.mdx             |   50 +
 .../86_user_tab_privs.mdx                     |   23 +
 .../87_user_tables.mdx                        |   23 +
 .../88_user_triggers.mdx                      |   29 +
 .../oracle_compatible_views/89_user_types.mdx |   22 +
 .../oracle_compatible_views/90_user_users.mdx |   28 +
 .../91_user_view_columns.mdx                  |   27 +
 .../oracle_compatible_views/92_user_views.mdx |   20 +
 .../oracle_compatible_views/93_v_version.mdx  |   18 +
 .../94_product_component_version.mdx          |   15 +
 .../oracle_compatible_views/index.mdx         |    9 +
 .../epas_compat_cat_views/pg_views/index.mdx  |   10 +
 .../pg_views/pg_attribute.mdx                 |   11 +
 .../pg_views/pg_authid.mdx                    |   16 +
 .../pg_views/pg_class.mdx                     |   13 +
 .../pg_views/pg_collation.mdx                 |   12 +
 .../pg_views/pg_database.mdx                  |   13 +
 .../pg_views/pg_namespace.mdx                 |   18 +
 .../pg_views/pg_partitioned_table.mdx         |   13 +
 .../pg_views/pg_proc.mdx                      |   15 +
 .../pg_views/pg_subscription.mdx              |   12 +
 .../pg_views/pg_synonym.mdx                   |   15 +
 .../pg_views/pg_trigger.mdx                   |   12 +
 .../pg_views/pg_type.mdx                      |   12 +
 .../pg_views/pg_user.mdx                      |   13 +
 .../01_alter_capture_privilege.mdx            |   67 +
 .../epas_compat_sql/02_alter_directory.mdx    |   64 +
 .../epas_compat_sql/03_alter_index.mdx        |   93 ++
 .../epas_compat_sql/04_alter_procedure.mdx    |   55 +
 .../epas_compat_sql/05_alter_profile.mdx      |  124 ++
 .../epas_compat_sql/06_alter_queue.mdx        |  149 ++
 .../epas_compat_sql/07_alter_queue_table.mdx  |   50 +
 .../08_alter_role_identified_by.mdx           |   52 +
 ..._database_link_and_dbms_rls_privileges.mdx |  117 ++
 .../epas_compat_sql/10_alter_sequence.mdx     |   71 +
 .../epas_compat_sql/11_alter_session.mdx      |   77 +
 .../epas_compat_sql/11a_alter_synonym.mdx     |   67 +
 .../epas_compat_sql/12_alter_table.mdx        |  205 +++
 .../epas_compat_sql/13_alter_trigger.mdx      |  111 ++
 .../epas_compat_sql/14_alter_tablespace.mdx   |   47 +
 .../15_alter_user_identified_by.mdx           |   55 +
 ...r_user_role_profile_management_clauses.mdx |   95 ++
 .../epas_compat_sql/17_call.mdx               |   43 +
 .../epas_compat_sql/18_comment.mdx            |   64 +
 .../epas_compat_sql/19_commit.mdx             |   46 +
 .../19a_create_capture_privilege.mdx          |   61 +
 .../epas_compat_sql/20_create_database.mdx    |   49 +
 .../21_create_public_database_link.mdx        |  613 ++++++++
 .../epas_compat_sql/22_create_directory.mdx   |   95 ++
 .../epas_compat_sql/23_create_function.mdx    |  259 ++++
 .../epas_compat_sql/24_create_index.mdx       |  123 ++
 .../25_create_materialized_view.mdx           |   79 ++
 .../epas_compat_sql/26_create_package.mdx     |  117 ++
 .../27_create_package_body.mdx                |  279 ++++
 .../epas_compat_sql/28_create_procedure.mdx   |  272 ++++
 .../epas_compat_sql/29_create_profile.mdx     |  141 ++
 .../epas_compat_sql/30_create_queue.mdx       |   74 +
 .../epas_compat_sql/31_create_queue_table.mdx |  107 ++
 .../epas_compat_sql/32_create_role.mdx        |   60 +
 .../epas_compat_sql/33_create_schema.mdx      |   58 +
 .../epas_compat_sql/34_create_sequence.mdx    |  116 ++
 .../epas_compat_sql/35_create_synonym.mdx     |   91 ++
 .../epas_compat_sql/36_create_table.mdx       |  372 +++++
 .../epas_compat_sql/37_create_table_as.mdx    |   49 +
 .../epas_compat_sql/38_create_trigger.mdx     |  509 +++++++
 .../epas_compat_sql/39_create_type.mdx        |  357 +++++
 .../epas_compat_sql/40_create_type_body.mdx   |  156 ++
 .../epas_compat_sql/41_create_user.mdx        |   53 +
 ...e_user_role_profile_management_clauses.mdx |   91 ++
 .../epas_compat_sql/43_create_view.mdx        |   62 +
 .../epas_compat_sql/44_delete.mdx             |   88 ++
 .../44a_drop_capture_privilege.mdx            |   40 +
 .../45_drop_public_database_link.mdx          |   53 +
 .../epas_compat_sql/46_drop_directory.mdx     |   45 +
 .../epas_compat_sql/47_drop_function.mdx      |   83 ++
 .../epas_compat_sql/48_drop_index.mdx         |   43 +
 .../epas_compat_sql/49_drop_package.mdx       |   43 +
 .../epas_compat_sql/50_drop_procedure.mdx     |   84 ++
 .../epas_compat_sql/51_drop_profile.mdx       |   51 +
 .../epas_compat_sql/52_drop_queue.mdx         |   50 +
 .../epas_compat_sql/53_drop_queue_table.mdx   |   59 +
 .../epas_compat_sql/54_drop_synonym.mdx       |   55 +
 .../epas_compat_sql/55_drop_role.mdx          |   53 +
 .../epas_compat_sql/56_drop_sequence.mdx      |   43 +
 .../epas_compat_sql/57_drop_table.mdx         |   73 +
 .../epas_compat_sql/58_drop_tablespace.mdx    |   45 +
 .../epas_compat_sql/59_drop_trigger.mdx       |   43 +
 .../epas_compat_sql/60_drop_type.mdx          |   53 +
 .../epas_compat_sql/61_drop_user.mdx          |   59 +
 .../epas_compat_sql/62_drop_view.mdx          |   45 +
 .../epas_compat_sql/63_exec.mdx               |   45 +
 .../epas_compat_sql/64_grant.mdx              |  273 ++++
 .../epas_compat_sql/65_insert.mdx             |  130 ++
 .../epas_compat_sql/65a_merge.mdx             |  142 ++
 .../epas_compat_sql/66_lock.mdx               |   67 +
 .../epas_compat_sql/67_revoke.mdx             |  142 ++
 .../epas_compat_sql/68_rollback.mdx           |   48 +
 .../69_rollback_to_savepoint.mdx              |   56 +
 .../epas_compat_sql/70_savepoint.mdx          |   62 +
 .../epas_compat_sql/71_select.mdx             |  464 ++++++
 .../epas_compat_sql/72_set_constraints.mdx    |   37 +
 .../epas_compat_sql/73_set_role.mdx           |   43 +
 .../epas_compat_sql/74_set_transaction.mdx    |   51 +
 .../epas_compat_sql/75_truncate.mdx           |   51 +
 .../epas_compat_sql/76_update.mdx             |  131 ++
 .../epas_compat_sql/index.mdx                 |   16 +
 .../oracle_compatibility_reference/index.mdx  |    7 +
 .../summary_oracle_config_parameters.mdx      |   14 +
 .../01_sql_syntax/01_lexical_structure.mdx    |   35 +
 .../02_identifiers_and_key_words.mdx          |   45 +
 .../01_sql_syntax/03_constants.mdx            |  116 ++
 .../01_sql_syntax/04_comments.mdx             |   25 +
 .../sql_reference/01_sql_syntax/index.mdx     |   22 +
 .../02_data_types/01_numeric_types.mdx        |  167 +++
 .../02_data_types/02_character_types.mdx      |   95 ++
 .../02_data_types/03_binary_data.mdx          |   86 ++
 .../02_data_types/04_date_time_types.mdx      |  327 +++++
 .../02_data_types/05_boolean_type.mdx         |   41 +
 .../02_data_types/06_xml_type.mdx             |  115 ++
 .../02_data_types/array_types.mdx             |  457 ++++++
 .../02_data_types/composite_types.mdx         |  300 ++++
 .../02_data_types/enumerated_types.mdx        |   32 +
 .../02_data_types/geometric_types.mdx         |   20 +
 .../sql_reference/02_data_types/index.mdx     |   31 +
 .../02_data_types/monetary_types.mdx          |   32 +
 .../02_data_types/network_address_types.mdx   |   18 +
 .../02_data_types/object_identifier_types.mdx |   63 +
 .../02_data_types/pseudo_types.mdx            |   31 +
 .../02_data_types/range_types.mdx             |  223 +++
 .../01_logical_operators.mdx                  |   32 +
 .../02_comparison_operators.mdx               |   54 +
 ...3_mathematical_functions_and_operators.mdx |  129 ++
 .../04_string_functions_and_operators.mdx     |  194 +++
 .../05_pattern_matching_string_functions.mdx  |  218 +++
 ...ttern_matching_using_the_like_operator.mdx |   40 +
 .../07_data_type_formatting_functions.mdx     |  424 ++++++
 .../08_date_time_functions_and_operators.mdx  |  853 +++++++++++
 .../09_sequence_manipulation_functions.mdx    |   34 +
 .../10_conditional_expressions.mdx            |  291 ++++
 .../11_aggregate_functions.mdx                |  417 ++++++
 .../12_subquery_expressions.mdx               |   91 ++
 .../13_identifier_functions.mdx               |  200 +++
 .../14_bitwise_functions.mdx                  |   95 ++
 .../dump_function.mdx                         |   66 +
 .../03_functions_and_operators/index.mdx      |   22 +
 .../to_multi_byte.mdx                         |   65 +
 .../to_single_byte.mdx                        |   74 +
 .../epas/16/reference/sql_reference/index.mdx |   24 +
 .../06_unicode_collation_algorithm.mdx        |  330 +++++
 .../10_ecpgplus.mdx                           |   25 +
 .../11_libpq_c_library.mdx                    |  500 +++++++
 .../application_developer_tools/index.mdx     |    9 +
 .../connectivity_tools/connectors.mdx         |   22 +
 .../connectivity_tools/data_sources.mdx       |   18 +
 .../connectivity_tools/index.mdx              |    9 +
 .../managing_connections.mdx                  |   18 +
 .../09_tools_and_utilities.mdx                |   18 +
 .../edb_clone_schema_overview.mdx             |   14 +
 .../edb_loader_overview.mdx                   |    8 +
 .../edb_resource_manager_overview.mdx         |   10 +
 .../database_administration_tools/index.mdx   |    9 +
 .../epas_compat_tools_guide/index.mdx         |   33 +
 .../tools_utilities_and_components/index.mdx  |    6 +
 product_docs/docs/epas/16/upgrading/index.mdx |   13 +
 .../01_linking_versus_copying.mdx             |   15 +
 .../01_performing_an_upgrade/index.mdx        |   38 +
 .../01_command_line_options_reference.mdx     |   93 ++
 .../02_invoking_pg_upgrade/index.mdx          |   56 +
 .../major_upgrade/03_limitations.mdx          |   25 +
 .../03_upgrading_to_advanced_server.mdx       |  292 ++++
 .../04_upgrading_a_pgAgent_installation.mdx   |   13 +
 .../05_pg_upgrade_troubleshooting.mdx         |   34 +
 .../06_reverting_to_the_old_cluster.mdx       |   15 +
 .../major_upgrade/how_pg_upgrade_works.mdx    |   30 +
 .../epas/16/upgrading/major_upgrade/index.mdx |   32 +
 ..._version_update_of_an_rpm_installation.mdx |   61 +
 ...plus_to_perform_a_minor_version_update.mdx |   50 +
 .../epas/16/upgrading/minor_upgrade/index.mdx |   18 +
 ...nor_version_update_of_deb_installation.mdx |   68 +
 .../02_enhanced_compatibility_features.mdx    |  204 +++
 .../02_calling_dblink_ora_functions.mdx       |   59 +
 .../06_dblink_ora/connecting_to_oracle.mdx    |   46 +
 .../06_dblink_ora/index.mdx                   |   14 +
 .../07_open_client_library.mdx                |   23 +
 .../embedded_sql_commands.mdx                 |    9 +
 .../16/working_with_oracle_data/index.mdx     |    6 +
 .../loading_bulk_data.mdx                     |    9 +
 .../proprietary_source_code.mdx               |   10 +
 1079 files changed, 83764 insertions(+)
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/01_package_components.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/01a_display_packages.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/02_creating_packages.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/03_referencing_a_package.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/04_using_packages_with_user_defined_types.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/05_dropping_a_package.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/02_packages/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/12_debugger/configuring_debugger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/12_debugger/debugger_interface.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/12_debugger/debugging_a_program.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/12_debugger/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/12_debugger/starting_debugger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/comment_command.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/logical_decoding.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/obtaining_version_information.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/02_overview.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/04_using_descriptors.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/06_error_handling.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/ecpgplus_guide/installing_ecpgplus.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/01_commit.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/02_rollback.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/07_dynamic_sql.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/01_declaring_a_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/02_opening_a_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/03_fetching_rows_from_a_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/04_closing_a_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/05_using__rowtype_with_cursors.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/01_isopen.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/02_found.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/03_notfound.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/04_rowcount.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/05_summary_of_cursor_states_and_attributes.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/08_parameterized_cursors.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/01_ref_cursor_overview.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/01_declaring_a_sys_refcursor_cursor_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/02_declaring_a_user_defined_ref_cursor_type_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/03_opening_a_cursor_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/04_fetching_rows_from_a_cursor_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/05_closing_a_cursor_variable.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/06_usage_restrictions.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/01_returning_a_ref_cursor_from_a_function.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/02_modularizing_cursor_operations.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/08_dynamic_queries_with_ref_cursors.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/03_varrays.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/about_collections.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/01_table.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/02_using_the_multiset_union_operator.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/02_fetch_bulk_collect.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/03_execute_immediate_bulk_collect.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/01_overview.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/03_creating_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/04_trigger_variables.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/05_transactions_and_exceptions.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/06_compound_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/01_before_statement_level_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/02_after_statement_level_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/03_before_row_level_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/04_after_row_level_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/05_instead_of_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/14_packages.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/01_attributes.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/03_overloading_methods.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/01_member_methods.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/02_static_methods.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/04_creating_object_instances.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/05_referencing_an_object.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/06_dropping_an_object_type.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/index.mdx
 create mode 100755 product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definer's_rights_package.png
 create mode 100755 product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definers_rights_package.png
 create mode 100755 product_docs/docs/epas/16/application_programming/epas_compat_spl/images/invokers_rights_programs.png
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_spl/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/01_oracle_compat_summary.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/01_example_partition_pruning.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_default_partition.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_maxvalue_partition.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/01_default_optimization_modes.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/02_access_method_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/03_specifying_a_join_order.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/04_joining_relations_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/05_global_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/06_using_the_append_optimizer_hint.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/07_parallelism_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/08_conflicting_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/index.mdx
 create mode 100644 product_docs/docs/epas/16/application_programming/optimizing_code/optimizing_code.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/01_shared_buffers.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/02_work_mem.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/03_maintenance_work_mem.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/04_wal_buffers.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/05_checkpoint_segments.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/06_checkpoint_completion_target.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/07_checkpoint_timeout.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/09_min_wal_size.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/10_bgwriter_delay.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/11_seq_page_cost.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/12_random_page_cost.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/13_effective_cache_size.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/14_synchronous_commit.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/15_edb_max_spins_per_delay.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/16_pg_prewarm.autoprewarm.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/17_pg_prewarm.autoprewarm_interval.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/02_resource_usage_memory.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/03_resource_usage_edb_resource_manager.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/04_query_tuning.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/05_query_tuning_planner_method_configuration.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/01_edb_audit.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/02_edb_audit_directory.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/03_edb_audit_filename.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/04_edb_audit_rotation_day.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/05_edb_audit_rotation_size.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/06_edb_audit_rotation_seconds.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/07_edb_audit_connect.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/08_edb_audit_disconnect.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/09_edb_audit_statement.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/10_edb_audit_tag.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/11_edb_audit_destination.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/12_edb_log_every_bulk_value.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/08_ccd_locale_and_formatting.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/09_ccd_statement_behaviour.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/10_ccd_other_defaults.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/13_ungrouped.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/01_configuration_parameters/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/control_file_examples.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/data_loading_methods.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/conventional_path_load.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/02_edb_loader/using_edb_loader.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/10_edb_resource_manager/cpu_usage_throttling.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/10_edb_resource_manager/creating_resource_groups.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/10_edb_resource_manager/edb_resource_manager_key_concepts.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/10_edb_resource_manager/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/checking_the_status.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_schema.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/index.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/performing_cleanup_tasks.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx
 create mode 100644 product_docs/docs/epas/16/database_administration/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_platform_support/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_3_0_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_4_0_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_4_1_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/epas16_rel_notes.mdx
 create mode 100644 product_docs/docs/epas/16/epas_rel_notes/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/01_sql_protect_overview.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/02_configuring_sql_protect.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/03_common_maintenance_operations.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/04_backing_up_restoring_sql_protect.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/edb_wrap_key_concepts.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/obfuscating_source_code.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/03_virtual_private_database.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/01_creating_a_password_function.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/02_altering_a_profile.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/03_dropping_a_profile.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/04_associating_a_profile_with_an_existing_role.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/05_unlocking_a_locked_account.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/06_creating_a_new_role_associated_with_a_profile.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/07_backing_up_profile_management_functions.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_profile_management/profile_overview.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/04_sslutils.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/creating_a_data_redaction_policy.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_key_concepts.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_system_catalogs.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/modifying_a_data_redaction_policy.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_data_redaction/removing_a_data_redaction_policy.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/03_enabling_audit_logging.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/05_using_error_codes_to_filter_audit_logs.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/06_using_command_tags_to_filter_audit_logs.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/07_redacting_passwords_from_audit_logs.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/09_object_auditing.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/index.mdx
 create mode 100644 product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/epas_fundamentals/benefits_epas.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/epas_fundamentals/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/epas_fundamentals/terminology.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_about_the_examples_used_in_this_guide.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_conventions.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/01_sample_database_installation.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/02_sample_database_description.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/02_creating_a_new_table.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/03_populating_a_table_with_rows.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/04_querying_a_table.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/05_joins_between_tables.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/06_aggregate_functions.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/07_updates.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/08_deletions.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/01_views.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/02_foreign_keys.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/03_the_rownum_pseudo_column.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/04_synonyms.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/01_defining_the_parent_child_relationship.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/02_selecting_the_root_nodes.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/03_organization_tree_in_the_sample_application.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/04_node_level.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/05_ordering_the_siblings.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/07_retrieving_a_path_with_sys_connect_by_path.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/01_rollup_extension.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/02_cube_extension.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/03_grouping_sets_extension.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/04_grouping_function.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/05_grouping_id_function.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/index.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_examples_used.mdx
 create mode 100644 product_docs/docs/epas/16/fundamentals/sql_fundamentals/index.mdx
 create mode 100644 product_docs/docs/epas/16/images/accessing_configuration_files.png
 create mode 100755 product_docs/docs/epas/16/images/acknowledging_components_removed.png
 create mode 100644 product_docs/docs/epas/16/images/additional_configuration.png
 create mode 100644 product_docs/docs/epas/16/images/additional_directories.png
 create mode 100644 product_docs/docs/epas/16/images/advanced_server_dialect.png
 create mode 100755 product_docs/docs/epas/16/images/advanced_server_installation_completion.png
 create mode 100644 product_docs/docs/epas/16/images/advanced_server_installer_welcome.png
 create mode 100644 product_docs/docs/epas/16/images/advanced_server_services.png
 create mode 100644 product_docs/docs/epas/16/images/advanced_server_startup.png
 create mode 100755 product_docs/docs/epas/16/images/advanced_server_uninstaller.png
 create mode 100644 product_docs/docs/epas/16/images/configuring_advanced_server_to_use_trust_authentication.png
 create mode 100644 product_docs/docs/epas/16/images/connecting_server.png
 create mode 100644 product_docs/docs/epas/16/images/connecting_to_advanced_server_database.png
 create mode 100644 product_docs/docs/epas/16/images/connecting_to_server.png
 create mode 100755 product_docs/docs/epas/16/images/definer's_rights_package.png
 create mode 100644 product_docs/docs/epas/16/images/download-complete-confirmation.png
 create mode 100644 product_docs/docs/epas/16/images/download_complete.png
 create mode 100644 product_docs/docs/epas/16/images/dynatune_dynamic_tuning_server_utilization.png
 create mode 100644 product_docs/docs/epas/16/images/dynatune_dynamic_tuning_workload_profile.png
 create mode 100755 product_docs/docs/epas/16/images/ecpg_path.png
 create mode 100755 product_docs/docs/epas/16/images/employee_organization_hierarchy.png
 create mode 100644 product_docs/docs/epas/16/images/enterprisedb_license_agreement.png
 create mode 100755 product_docs/docs/epas/16/images/epas_tools_utility_edb_wrap.png
 create mode 100644 product_docs/docs/epas/16/images/installation_directory.png
 create mode 100644 product_docs/docs/epas/16/images/installing_advanced_server.png
 create mode 100755 product_docs/docs/epas/16/images/invokers_rights_programs.png
 create mode 100755 product_docs/docs/epas/16/images/open_client_library.png
 create mode 100755 product_docs/docs/epas/16/images/parameters_tab.png
 create mode 100644 product_docs/docs/epas/16/images/password_window.png
 create mode 100755 product_docs/docs/epas/16/images/pgadmin4_client_dashboard.png
 create mode 100644 product_docs/docs/epas/16/images/pre_installation_summary.png
 create mode 100755 product_docs/docs/epas/16/images/program_body.png
 create mode 100755 product_docs/docs/epas/16/images/proxy_servers.png
 create mode 100644 product_docs/docs/epas/16/images/ready_to_install.png
 create mode 100755 product_docs/docs/epas/16/images/sample_database_tables.png
 create mode 100644 product_docs/docs/epas/16/images/select_components.png
 create mode 100644 product_docs/docs/epas/16/images/selected-packages-summary-window.png
 create mode 100755 product_docs/docs/epas/16/images/setting_global_breakpoint_from_left-hand_margin.png
 create mode 100644 product_docs/docs/epas/16/images/setup_wizard.png
 create mode 100755 product_docs/docs/epas/16/images/stack_tab.png
 create mode 100644 product_docs/docs/epas/16/images/stackbuilder-plus-confirms-the-completed-installation.png
 create mode 100644 product_docs/docs/epas/16/images/stackbuilder_plus_completed_installation.png
 create mode 100644 product_docs/docs/epas/16/images/stackbuilder_plus_module_selection.png
 create mode 100644 product_docs/docs/epas/16/images/stackbuilder_plus_welcome.png
 create mode 100644 product_docs/docs/epas/16/images/summary-window-displaying-selected-packages.png
 create mode 100755 product_docs/docs/epas/16/images/the-proxy-servers-dialog.png
 create mode 100644 product_docs/docs/epas/16/images/the-stackbuilder-plus-module-selection-window.png
 create mode 100644 product_docs/docs/epas/16/images/the-stackbuilder-plus-welcome.png
 create mode 100755 product_docs/docs/epas/16/images/uninstallation_complete.png
 create mode 100644 product_docs/docs/epas/16/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_arm64/epas_debian_12.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_arm64/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/connecting_to_epas.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_8.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_15.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_11.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_12.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_8.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_9.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_8.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_15.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_20.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_22.mdx
 create mode 100644 product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/troubleshooting/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
 create mode 100644 product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
 create mode 100644 product_docs/docs/epas/16/installing/troubleshooting/windows_troubleshooting.mdx
 create mode 100644 product_docs/docs/epas/16/installing/uninstalling/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
 create mode 100644 product_docs/docs/epas/16/installing/uninstalling/windows_uninstall.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_installation_with_limited_privileges.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_unattended_installation.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/setting_cluster_preferences.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/controlling_server_startup_behavior_on_windows.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/index.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/starting_and_stopping_epas.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_pg_ctl_to_control_advanced_server.mdx
 create mode 100644 product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_the_windows_services_applet.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/03_sql_profiler.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/index.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/performance_tuning_recommendations.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/simulating_statspack_reports.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/taking_a_snapshot.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/using_drita_functions.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/evaluating_wait_states.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/index.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/query_advisor.mdx
 create mode 100644 product_docs/docs/epas/16/managing_performance/using_dynatune.mdx
 create mode 100644 product_docs/docs/epas/16/planning/configuration_mode.mdx
 create mode 100644 product_docs/docs/epas/16/planning/deployment_options/index.mdx
 create mode 100644 product_docs/docs/epas/16/planning/index.mdx
 create mode 100644 product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
 create mode 100644 product_docs/docs/epas/16/planning/planning_prerequisites/epas_requirements/index.mdx
 create mode 100644 product_docs/docs/epas/16/planning/planning_prerequisites/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/01_all_part_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/02_all_tab_partitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/03_all_tab_subpartitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/04_all_part_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/05_all_subpart_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/03_system_catalog_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/c_preprocessor_directives.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/sqlda_structure.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/supported_c_data_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/type_codes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx
 create mode 100644 product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_index_advisor_components.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/01_edb_redwood_date.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/02_edb_redwood_raw_names.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/03_edb_redwood_strings.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/04_edb_stmt_level_tx.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/05_oracle_home.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/04_audit_log_file.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/database_administrator_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/01_example_partition_by_list.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/02_example_automatic_list_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/03_example_partition_by_range.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/04_example_interval_range_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/05_example_partition_by_hash.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/06_example_partitions_number.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/07_example_partition_by_range_subpartition_by_list.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/08_example_creating_unique_index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/09_example_subpartition_template.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/01_example_adding_a_partition_to_a_list_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/02_example_adding_a_partition_to_a_range_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/03_example_adding_a_partition_with_subpartitions_number.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/01_example_adding_a_subpartition_to_a_list_range_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/02_example_adding_a_subpartition_to_a_range_list_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/01_example_splitting_a_list_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/02_example_splitting_a_range_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/03_example_splitting_a_range_list_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/01_example_splitting_a_list_subpartition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/02_example_splitting_a_range_subpartition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/01_example_exchanging_a_table_for_a_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/01_example_moving_a_partition_to_a_different_tablespace.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/01_example_renaming_a_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/01_example_setting_an_interval_range_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/01_example_setting_an_automatic_list_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/12_drop_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/01_example_deleting_a_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/01_example_deleting_a_subpartition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/01_example_emptying_a_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/01_example_emptying_a_partition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/01_example_emptying_a_subpartition.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/18_accessing_partition_table/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/limitations.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/01_alter_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/02_alter_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/03_create_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/04_create_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/05_drop_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/06_drop_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/07_purge_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/08_start_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/09_stop_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/03_hash.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/04_mac.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/05_randombytes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/06_randominteger.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/07_randomnumber.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/01_broken.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/02_change.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/03_interval.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/04_next_date.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/05_remove.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/06_run.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/07_submit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/08_what.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/01_append.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/02_compare.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/03_converttoblob.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/04_converttoclob.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/05_copy.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/06_erase.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/07_get_storage_limit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/08_getlength.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/09_instr.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/10_read.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/12_trim.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/13_write.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/14_writeappend.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/07_dbms_lock.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/01_get_mv_dependencies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/02_refresh.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/03_refresh_all_mviews.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/04_refresh_dependent.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/01_create_pipe.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/02_next_item_pipe.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/03_pack_message.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/04_purge.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/05_receive_message.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/06_remove_pipe.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/07_reset_buffer.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/08_send_message.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/09_unique_session_name.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/10_unpack_message.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/11_comprehensive_example.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_privilege_capture.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/11_dbms_profiler.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/13_dbms_redact.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/01_using_calendar_syntax_to_specify_a_repeating_interval.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/02_create_job.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/03_create_program.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/04_create_schedule.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/05_define_program_argument.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/06_dbms_scheduler_disable.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/07_drop_job.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/08_drop_program.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/09_drop_program_argument.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/10_drop_schedule.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/11_dbms_scheduler_enable.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/12_evaluate_calendar_string.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/13_run_job.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/14_set_job_argument_value.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/16_dbms_session.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/001_bind_array.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/01_bind_variable.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/02_bind_variable_char.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/03_bind_variable_raw.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/04_close_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/05_column_value.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/06_column_value_char.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07_column_value_raw.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07a_column_value_long.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07b_column_value_rowid.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07c_define_array.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/08_define_column.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/09_define_column_char.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10_define_column_raw.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10a_define_column_long.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10b_define_column_rowid.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11_describe_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11a_describe_columns2.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11b_describe_columns3.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/12_execute.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/13_execute_and_fetch.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/14_fetch_rows.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/15_is_open.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/16_last_row_count.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/18_parse.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/19_to_cursor_number.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_utility.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/01_base64_decode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/02_base64_encode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/03_mimeheader_decode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/04_mimeheader_encode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/05_quoted_printable_decode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/06_quoted_printable_encode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/07_text_decode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/08_text_encode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/09_uudecode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/10_uuencode.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/20_utl_file.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/21_utl_http.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/22_utl_mail.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/23_utl_raw.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/24_utl_smtp.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/25_utl_url.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/address.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/anchor.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/applet.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/area.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/base.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/basefont.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bgsound.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/big.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/blockquote.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/body.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bold.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/br_and_nl.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/caption.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/center.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/centeropen_and_centerclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/cite.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/code.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/comment.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dfn.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dirlist.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/div.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistdef.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistopen_and_dlistclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistterm.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/em_and_emphasis.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/escape_sc.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/font.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formcheckbox.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formfile.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formhidden.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formimage.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formopen_and_formclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formpassword.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formradio.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formreset.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectopen_and_formselectclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectoption.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formsubmit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtext.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea_and_formtextarea2.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/frame.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/framesetopen_and_framsetclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/header.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/headopen_and_headclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/hr.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/htmlopen_and_htmlclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/img.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/isindex.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/italic.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/kbd_and_keyboard.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrel.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrev.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listheader.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listingopen_and_listingclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listitem.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mailto.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mapopen_and_mapclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/menulistopen_and_menulistclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/meta.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/nobr.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/noframesopen_and_noframesclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/olistopen_and_olistclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/para_and_paragraph.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/param.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/plaintext.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/preopen_and_preclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/print_and_prn.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/prints_and_ps.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/s.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sample.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/small.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strike.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strong.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/style.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sub.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sup.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tabledata.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableheader.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableopen_and_tableclose.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tablerow.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/teletype.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/title.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ulist.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/underline.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/variable.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/wbr.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/02_all_all_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/03_all_cons_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/04_all_constraints.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/05_all_col_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/06_all_db_links.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/07_all_dependencies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/08_all_directories.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/10_all_indexes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/11_all_jobs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/12_all_objects.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/13_all_part_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/14_all_part_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/15_all_policies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/16_all_queues.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/17_all_queue_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/18_all_sequences.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/20_all_subpart_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/21_all_synonyms.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/23_all_tab_partitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/24_all_tab_subpartitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/26_all_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/27_all_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/28_all_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/29_all_users.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/30_all_view_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/31_all_views.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/32_dba_all_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/33_dba_cons_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/34_dba_constraints.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/35_dba_col_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/36_dba_db_links.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/38_dba_dependencies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/39_dba_ind_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/40_dba_indexes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/41_dba_jobs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/42_dba_objects.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/43_dba_part_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/44_dba_part_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45_dba_policies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45a_dba_privs_capture.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/46_dba_profiles.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/47_dba_queues.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/48_dba_queue_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/49_dba_role_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/50_dba_roles.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/51_dba_sequences.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/52_dba_source.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/53_dba_subpart_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/54_dba_synonyms.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/55_dba_tab_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/56_dba_tab_partitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/57_dba_tab_subpartitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/58_dba_tab_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/59_dba_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/60_dba_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/61_dba_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62_dba_users.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62a_dba_used_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62b_dba_unused_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/63_dba_view_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/64_dba_views.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/65_user_all_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/66_user_cons_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/67_user_constraints.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/68_user_col_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/69_user_db_links.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/70_user_dependencies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/71_user_indexes.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/73_user_objects.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/74_user_part_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/75_user_policies.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/76_user_queues.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/77_user_queue_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/78_user_role_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/79_user_sequences.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/80_user_source.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/81_user_subpart_key_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/83_user_tab_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/85_user_tab_subpartitions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/86_user_tab_privs.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/87_user_tables.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/88_user_triggers.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/89_user_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/90_user_users.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/91_user_view_columns.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/92_user_views.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/93_v_version.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/94_product_component_version.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_attribute.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_authid.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_class.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_collation.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_database.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_namespace.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_partitioned_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_proc.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_subscription.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_synonym.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_type.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_user.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/01_alter_capture_privilege.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/02_alter_directory.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/03_alter_index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/04_alter_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/05_alter_profile.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/06_alter_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/07_alter_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/08_alter_role_identified_by.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/09_alter_role_managing_database_link_and_dbms_rls_privileges.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/10_alter_sequence.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11_alter_session.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11a_alter_synonym.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/12_alter_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/13_alter_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/14_alter_tablespace.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/15_alter_user_identified_by.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/16_alter_user_role_profile_management_clauses.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/17_call.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/18_comment.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19_commit.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19a_create_capture_privilege.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/20_create_database.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/22_create_directory.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/23_create_function.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/24_create_index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/25_create_materialized_view.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/26_create_package.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/27_create_package_body.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/28_create_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/30_create_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/32_create_role.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/33_create_schema.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/35_create_synonym.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/38_create_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/39_create_type.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/40_create_type_body.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/41_create_user.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/42_create_user_role_profile_management_clauses.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44_delete.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44a_drop_capture_privilege.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/45_drop_public_database_link.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/46_drop_directory.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/47_drop_function.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/48_drop_index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/49_drop_package.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/50_drop_procedure.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/51_drop_profile.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/52_drop_queue.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/53_drop_queue_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/54_drop_synonym.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/55_drop_role.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/56_drop_sequence.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/57_drop_table.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/58_drop_tablespace.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/59_drop_trigger.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/60_drop_type.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/61_drop_user.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/62_drop_view.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/63_exec.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/64_grant.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65_insert.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/66_lock.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/67_revoke.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/68_rollback.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/69_rollback_to_savepoint.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/70_savepoint.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/71_select.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/72_set_constraints.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/73_set_role.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/74_set_transaction.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/75_truncate.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/76_update.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/oracle_compatibility_reference/summary_oracle_config_parameters.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/02_identifiers_and_key_words.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/03_constants.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/04_comments.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/01_numeric_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/02_character_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/03_binary_data.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/04_date_time_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/05_boolean_type.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/06_xml_type.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/array_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/composite_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/enumerated_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/geometric_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/monetary_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/network_address_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/object_identifier_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/pseudo_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/02_data_types/range_types.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/01_logical_operators.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/02_comparison_operators.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/03_mathematical_functions_and_operators.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/04_string_functions_and_operators.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/05_pattern_matching_string_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/06_pattern_matching_using_the_like_operator.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/07_data_type_formatting_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/08_date_time_functions_and_operators.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/09_sequence_manipulation_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/10_conditional_expressions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/11_aggregate_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/12_subquery_expressions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/13_identifier_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/14_bitwise_functions.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/dump_function.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/index.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_multi_byte.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_single_byte.mdx
 create mode 100644 product_docs/docs/epas/16/reference/sql_reference/index.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/10_ecpgplus.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/11_libpq_c_library.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/index.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/connectors.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/data_sources.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/index.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/managing_connections.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_clone_schema_overview.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_resource_manager_overview.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/index.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/epas_compat_tools_guide/index.mdx
 create mode 100644 product_docs/docs/epas/16/tools_utilities_and_components/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx
 create mode 100644 product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_deb_installation.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/02_enhanced_compatibility_features.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/02_calling_dblink_ora_functions.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/connecting_to_oracle.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/index.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/07_open_client_library.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/embedded_sql_commands.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/index.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/loading_bulk_data.mdx
 create mode 100644 product_docs/docs/epas/16/working_with_oracle_data/proprietary_source_code.mdx

diff --git a/product_docs/docs/epas/16/application_programming/02_packages/01_package_components.mdx b/product_docs/docs/epas/16/application_programming/02_packages/01_package_components.mdx
new file mode 100644
index 00000000000..118cc946633
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/01_package_components.mdx
@@ -0,0 +1,385 @@
+---
+title: "Package components"
+description: "Describes the two main components of packages"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.06.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.184.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/01_package_components/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Packages consist of two main components:
+
+-   The *package specification*, which is the public interface. You can reference these elements outside the package. Declare all database objects that are a part of a package in the specification.
+-   The *package body*, which contains the actual implementation of all the database objects declared in the package specification.
+
+  The package body implements the specifications in the package specification. It contains implementation details and private declarations that are invisible to the application. You can debug, enhance, or replace a package body without changing the specifications. Similarly, you can change the body without recompiling the calling programs because the implementation details are invisible to the application.
+
+## Package specification syntax
+
+The package specification defines the user interface for a package (the API). The specification lists the functions, procedures, types, exceptions, and cursors that are visible to a user of the package.
+
+The syntax used to define the interface for a package is:
+
+```sql
+CREATE [ OR REPLACE ] PACKAGE <package_name>
+  [ <authorization_clause> ]
+  { IS | AS }
+  [ <declaration>; ] ...
+  [ <procedure_or_function_declaration> ] ...
+END [ <package_name> ] ;
+```
+
+Where `authorization_clause` :=
+
+```sql
+{ AUTHID DEFINER } | { AUTHID CURRENT_USER }
+```
+
+Where `procedure_or_function_declaration` :=
+
+```text
+procedure_declaration | function_declaration
+```
+
+Where `procedure_declaration` :=
+
+```sql
+PROCEDURE proc_name [ argument_list ];
+[ restriction_pragma; ]
+```
+
+Where `function_declaration` :=
+
+```sql
+FUNCTION func_name [ argument_list ]
+  RETURN rettype [ DETERMINISTIC ];
+[ restriction_pragma; ]
+```
+
+Where `argument_list` :=
+
+```text
+( argument_declaration [, ...] )
+```
+
+Where `argument_declaration` :=
+
+```text
+argname [ IN | IN OUT | OUT ] argtype [ DEFAULT value ]
+```
+
+Where `restriction_pragma` :=
+
+```sql
+PRAGMA RESTRICT_REFERENCES(name, restrictions)
+```
+
+Where `restrictions` :=
+
+```text
+restriction [, ... ]
+```
+
+### Parameters
+
+`package_name`
+
+ `package_name` is an identifier assigned to the package. Each package must have a unique name in the schema.
+
+`AUTHID DEFINER`
+
+ If you omit the `AUTHID` clause or specify `AUTHID DEFINER`, the privileges of the package owner are used to determine access privileges to database objects.
+
+`AUTHID CURRENT_USER`
+
+ If you specify `AUTHID CURRENT_USER`, the privileges of the current user executing a program in the package are used to determine access privileges.
+
+`declaration`
+
+ `declaration` is an identifier of a public variable. You can access a public variable from outside the package using the syntax `package_name.variable`. There can be zero, one, or more public variables. Public variable definitions must come before procedure or function declarations.
+
+ `declaration` can be any of the following:
+
+-   Variable declaration
+-   Record declaration
+-   Collection declaration
+-   `REF CURSOR` and cursor variable declaration
+-   `TYPE` definitions for records, ollections, and `REF CURSOR`
+-   Exception
+-   Object variable declaration
+
+`proc_name`
+
+ The name of a public procedure.
+
+`argname`
+
+ The name of an argument. The argument is referenced by this name in the function or procedure body.
+
+`IN` | `IN OUT` | `OUT`
+
+ The argument mode. `IN` (the default) declares the argument for input only. `IN OUT` allows the argument to receive a value as well as return a value. `OUT` specifies the argument is for output only.
+
+`argtype`
+
+ The data types of an argument. An argument type can be a base data type, a copy of the type of an existing column using `%TYPE`, or a user-defined type such as a nested table or an object type. Don't specify a length for any base type. For example, specify `VARCHAR2`, not `VARCHAR2(10)`.
+
+ Reference the type of a column by writing `tablename.columnname %TYPE`. Using this nomenclature can sometimes help make a procedure independent from changes to the definition of a table.
+
+`DEFAULT value`
+
+ The `DEFAULT` clause supplies a default value for an input argument if you don't supply one in the invocation. You can't specify `DEFAULT` for arguments with modes `IN OUT` or `OUT`.
+
+`func_name`
+
+ The name of a public function.
+
+`rettype`
+
+ The return data type.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` function can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the function with all-constant arguments can be immediately replaced with the function value.
+
+`restriction`
+
+ The following keywords are accepted for compatibility and ignored:
+
+ `RNDS`
+
+ `RNPS`
+
+ `TRUST`
+
+ `WNDS`
+
+ `WNPS`
+
+## Package body syntax
+
+Package implementation details reside in the package body. The package body can contain objects that aren't visible to the package user. EDB Postgres Advanced Server supports the following syntax for the package body:
+
+```sql
+CREATE [ OR REPLACE ] PACKAGE BODY <package_name>
+  { IS | AS }
+  [ <private_declaration>; ] ...
+  [ <procedure_or_function_definition> ] ...
+  [ <package_initializer> ]
+END [ <package_name> ] ;
+```
+
+Where `procedure_or_function_definition` :=
+
+```text
+procedure_definition | function_definition
+```
+
+Where `procedure_definition` :=
+
+```sql
+PROCEDURE proc_name[ argument_list ]
+  [ options_list ]
+  { IS | AS }
+    procedure_body
+  END [ proc_name ] ;
+```
+
+Where `procedure_body` :=
+
+```sql
+[ PRAGMA AUTONOMOUS_TRANSACTION; ]
+[ declaration; ] [, ...]
+BEGIN
+  statement; [...]
+[ EXCEPTION
+   { WHEN exception [OR exception] [...]] THEN statement; }
+   [...]
+]
+```
+
+Where `function_definition` :=
+
+```sql
+FUNCTION func_name [ argument_list ]
+  RETURN rettype [ DETERMINISTIC ]
+  [ options_list ]
+  { IS | AS }
+    function_body
+  END [ func_name ] ;
+```
+
+Where `function_body` :=
+
+```sql
+[ PRAGMA AUTONOMOUS_TRANSACTION; ]
+[ declaration; ] [, ...]
+BEGIN
+  statement; [...]
+[ EXCEPTION
+  { WHEN exception [ OR exception ] [...] THEN statement; }
+  [...]
+]
+```
+
+Where `argument_list` :=
+
+```text
+( argument_declaration [, ...] )
+```
+
+Where `argument_declaration` :=
+
+```text
+argname [ IN | IN OUT | OUT ] argtype [ DEFAULT value ]
+```
+
+Where `options_list` :=
+
+```text
+option [ ... ]
+```
+
+Where `option` :=
+
+```sql
+STRICT
+LEAKPROOF
+PARALLEL { UNSAFE | RESTRICTED | SAFE }
+COST execution_cost
+ROWS result_rows
+SET config_param { TO value | = value | FROM CURRENT }
+```
+
+Where `package_initializer` :=
+
+```sql
+BEGIN
+ statement; [...]
+END;
+```
+
+### Parameters
+
+`package_name`
+
+ `package_name` is the name of the package for which this is the package body. An package specification with this name must already exist.
+
+`private_declaration`
+
+ `private_declaration` is an identifier of a private variable that any procedure or function can access in the package. There can be zero, one, or more private variables. `private_declaration` can be any of the following:
+
+-   Variable declaration
+-   Record declaration
+-   Collection declaration
+-   `REF CURSOR` and cursor variable declaration
+-   `TYPE` definitions for records, collections, and `REF CURSORs`
+-   Exception
+-   Object variable declaration
+
+`proc_name`
+
+ The name of the procedure being created.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the procedure as an autonomous transaction.
+
+`declaration`
+
+ A variable, type, `REF CURSOR`, or subprogram declaration. If you include subprogram declarations, declare them after all other variable, type, and `REF CURSOR` declarations.
+
+`statement`
+
+ An SPL program statement. A `DECLARE - BEGIN - END` block is considered an SPL statement unto itself. Thus, the function body can contain nested blocks.
+
+`exception`
+
+ An exception condition name such as `NO_DATA_FOUND, OTHERS`.
+
+`func_name`
+
+ The name of the function being created.
+
+`rettype`
+
+ The return data type, which can be any of the types listed for `argtype`. As for `argtype`, don't specify a length for `rettype`.
+
+`DETERMINISTIC`
+
+ Include `DETERMINISTIC` to specify for the function to always return the same result when given the same argument values. A `DETERMINISTIC` function must not modify the database.
+
+ !!! Note
+   The `DETERMINISTIC` keyword is equivalent to the PostgreSQL `IMMUTABLE` option.
+
+ !!!Note
+  If `DETERMINISTIC` is specified for a public function in the package body, you must also specify it for the function declaration in the package specification. For private functions, there's no function declaration in the package specification.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the function as an autonomous transaction.
+
+`argname`
+
+ The name of a formal argument. The argument is referenced by this name in the procedure body.
+
+`IN` | `IN OUT` | `OUT`
+
+ The argument mode. `IN` (the default) declares the argument for input only. `IN OUT` allows the argument to receive a value as well as return a value. `OUT` specifies the argument is for output only.
+
+`argtype`
+
+ The data types of an argument. An argument type can be a base data type, a copy of the type of an existing column using `%TYPE`, or a user-defined type such as a nested table or an object type. Don't specify a length for any base type. For example, specify `VARCHAR2`, not `VARCHAR2(10)`.
+
+ Reference the type of a column by writing `tablename.columnname%TYPE`. Using this nomenclature can sometimes help make a procedure independent from changes to the definition of a table.
+
+`DEFAULT value`
+
+ The `DEFAULT` clause supplies a default value for an input argument if you don't supply one in the procedure call. Don't specify `DEFAULT` for arguments with modes `IN OUT` or `OUT`.
+
+The following options aren't compatible with Oracle databases. They're extensions to Oracle package syntax provided only by EDB Postgres Advanced Server.
+
+`STRICT`
+
+ The `STRICT` keyword specifies for the function not to execute if called with a `NULL` argument. Instead the function returns `NULL`.
+
+`LEAKPROOF`
+
+ The `LEAKPROOF` keyword specifies for the function not to reveal any information about arguments other than through a return value.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query in contrast to a serial sequential scan.
+
+ When set to `UNSAFE`, the procedure or function can't be executed in parallel mode. The presence of such a procedure or function forces a serial execution plan. This is the default setting if you omit the `PARALLEL` clause.
+
+ When set to `RESTRICTED`, the procedure or function can be executed in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that is parallel restricted, that relation won't be chosen for parallelism.
+
+ When set to `SAFE`, the procedure or function can be executed in parallel mode without restriction.
+
+`execution_cost`
+
+ `execution_cost` specifies a positive number giving the estimated execution cost for the function, in units of `cpu_operator_cost`. If the function returns a set, this is the cost per returned row. The default is `0.0025`.
+
+`result_rows`
+
+ `result_rows` is the estimated number of rows for the query planner to expect the function to return. The default is `1000`.
+
+`SET`
+
+ Use the `SET` clause to specify a parameter value for the duration of the function:
+
+ `config_param` specifies the parameter name.
+
+ `value` specifies the parameter value.
+
+ `FROM CURRENT` guarantees that the parameter value is restored when the function ends.
+
+`package_initializer`
+
+ The statements in the `package_initializer` are executed once per user session when the package is first referenced.
+
+!!! Note
+    The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server. Oracle doesn't support them.
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/01a_display_packages.mdx b/product_docs/docs/epas/16/application_programming/02_packages/01a_display_packages.mdx
new file mode 100644
index 00000000000..4395b146967
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/01a_display_packages.mdx
@@ -0,0 +1,141 @@
+---
+title: "Viewing packages and package body definition"
+description: "Describes how to view the package specification and package body definition"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/01a_display_packages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+You can view the package specification and package body definition using the psql meta-commands `\sps` and `\spb`, respectively.
+
+## Synopsis
+
+```sql
+\sps[+] [<schema_name>].<package_name>
+\spb[+] [<schema_name>].<package_name>
+```
+
+## Creating and viewing a package and a package body
+
+Create a package and a package body `test_pkg` in the `public` schema:
+
+```sql
+edb=# CREATE OR REPLACE PACKAGE public.test_pkg IS
+edb$# emp_name character varying(10);
+edb$# PROCEDURE get_name(IN p_empno numeric);
+edb$# FUNCTION display_counter() RETURN integer;
+edb$# END;
+CREATE PACKAGE
+edb=#
+edb=# CREATE OR REPLACE PACKAGE BODY public.test_pkg IS
+edb$# v_counter integer;
+edb$# 
+edb$# PROCEDURE get_name(IN p_empno numeric) IS
+edb$# BEGIN
+edb$# SELECT ename INTO emp_name FROM emp WHERE empno = p_empno;
+edb$# v_counter := v_counter + 1;
+edb$# END;
+edb$# 
+edb$# FUNCTION display_counter() RETURN integer IS
+edb$# BEGIN
+edb$# RETURN v_counter;
+edb$# END;
+edb$# BEGIN
+edb$# v_counter := 0;
+edb$# DBMS_OUTPUT.PUT_LINE('Initialized counter');
+edb$# END;
+CREATE PACKAGE BODY
+edb=#
+```
+
+Use `\sps` and `\spb` commands to view the definition of package and package body:
+
+``` sql
+edb=# \sps test_pkg
+CREATE OR REPLACE PACKAGE public.test_pkg IS
+emp_name character varying(10);
+PROCEDURE get_name(IN p_empno numeric);
+FUNCTION display_counter() RETURN integer;
+END
+edb=#
+edb=# \sps+ test_pkg
+1       CREATE OR REPLACE PACKAGE public.test_pkg IS
+2       emp_name character varying(10);
+3       PROCEDURE get_name(INOUT p_empno numeric);
+4       FUNCTION display_counter(OUT p1 numeric, OUT p2 numeric) RETURN integer;
+5       END
+
+edb=# \sps public.test_pkg
+CREATE OR REPLACE PACKAGE public.test_pkg IS
+emp_name character varying(10);
+PROCEDURE get_name(INOUT p_empno numeric);
+FUNCTION display_counter(OUT p1 numeric, OUT p2 numeric) RETURN integer;
+END
+
+edb=# \sps+ public.test_pkg
+1       CREATE OR REPLACE PACKAGE public.test_pkg IS
+2       emp_name character varying(10);
+3       PROCEDURE get_name(INOUT p_empno numeric);
+4       FUNCTION display_counter(OUT p1 numeric, OUT p2 numeric) RETURN integer;
+5       END
+
+edb=# \spb test_pkg
+CREATE OR REPLACE PACKAGE BODY public.test_pkg IS
+v_counter integer;
+
+PROCEDURE get_name(IN p_empno numeric) IS
+BEGIN
+SELECT ename INTO emp_name FROM emp WHERE empno = p_empno;
+v_counter := v_counter + 1;
+END;
+
+FUNCTION display_counter() RETURN integer IS
+BEGIN
+RETURN v_counter;
+END;
+BEGIN
+v_counter := 0;
+DBMS_OUTPUT.PUT_LINE('Initialized counter');
+END
+edb=# 
+```
+
+## Viewing function and procedure definitions
+
+You can also view the definition of individual functions and procedures using the `\sf` command.
+
+Create the function and procedure:
+
+```sql
+edb=# CREATE OR REPLACE FUNCTION public.func1()
+edb-#  RETURNS integer
+edb-#  LANGUAGE edbspl
+edb-#  SECURITY DEFINER
+edb-# AS $function$ begin return 10; end$function$;
+CREATE FUNCTION
+edb=#
+edb=# CREATE OR REPLACE PROCEDURE public.proc1()
+edb-#  SECURITY DEFINER
+edb-# AS $procedure$ begin null; end$procedure$
+edb-#  LANGUAGE edbspl;
+CREATE PROCEDURE
+edb=#
+```
+
+Use the `\sf <function_name/procedure_name>` command to view the definition:
+
+```sql
+edb=# \sf func1
+CREATE OR REPLACE FUNCTION public.func1()
+ RETURNS integer
+ LANGUAGE edbspl
+ SECURITY DEFINER
+AS $function$ begin return 10; end$function$
+edb=# 
+edb=# \sf proc1
+CREATE OR REPLACE PROCEDURE public.proc1()
+ SECURITY DEFINER
+AS $procedure$ begin null; end$procedure$
+ LANGUAGE edbspl
+edb=# 
+```
+
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/02_creating_packages.mdx b/product_docs/docs/epas/16/application_programming/02_packages/02_creating_packages.mdx
new file mode 100644
index 00000000000..8505522b14e
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/02_creating_packages.mdx
@@ -0,0 +1,139 @@
+---
+title: "Creating packages"
+description: "Describes how to create the package specification"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.07.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.185.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/02_creating_packages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+A package isn't an executable piece of code but a repository of code. When you use a package, you execute or make reference to an element within a package.
+
+## Creating the package specification
+
+The package specification contains the definition of all the elements in the package that you can reference from outside of the package. These are called the *public elements* of the package, and they act as the package interface. The following code sample is a package specification:
+
+```sql
+--
+-- Package specification for the 'emp_admin' package.
+--
+CREATE OR REPLACE PACKAGE emp_admin
+IS
+   FUNCTION get_dept_name (
+      p_deptno NUMBER DEFAULT 10
+   )
+   RETURN VARCHAR2;
+   FUNCTION update_emp_sal (
+      p_empno NUMBER,
+      p_raise NUMBER
+   )
+   RETURN NUMBER;
+   PROCEDURE hire_emp (
+      p_empno           NUMBER,
+      p_ename           VARCHAR2,
+      p_job             VARCHAR2,
+      p_sal             NUMBER,
+      p_hiredate        DATE      DEFAULT   sysdate,
+      p_comm            NUMBER    DEFAULT   0,
+      p_mgr             NUMBER,
+      p_deptno          NUMBER    DEFAULT   10
+   );
+   PROCEDURE fire_emp (
+      p_empno NUMBER
+   );
+END emp_admin;
+```
+
+This code sample creates the `emp_admin` package specification. This package specification consists of two functions and two stored procedures. You can also add the `OR REPLACE` clause to the `CREATE PACKAGE` statement for convenience.
+
+## Creating the package body
+
+The body of the package contains the actual implementation behind the package specification. For the `emp_admin` package specification in the example, this code now create a package body that implements the specifications. The body contains the implementation of the functions and stored procedures in the specification.
+
+```sql
+--
+--  Package body for the 'emp_admin' package.
+--
+CREATE OR REPLACE PACKAGE BODY emp_admin
+IS
+   --
+   --  Function that queries the 'dept' table based on the department
+   --  number and returns the corresponding department name.
+   --
+   FUNCTION get_dept_name (
+      p_deptno        IN NUMBER DEFAULT 10
+   )
+   RETURN VARCHAR2
+   IS
+      v_dname         VARCHAR2(14);
+   BEGIN
+      SELECT dname INTO v_dname FROM dept WHERE deptno = p_deptno;
+      RETURN v_dname;
+   EXCEPTION
+      WHEN NO_DATA_FOUND THEN
+         DBMS_OUTPUT.PUT_LINE('Invalid department number ' || p_deptno);
+         RETURN '';
+   END;
+   --
+   --  Function that updates an employee's salary based on the
+   --  employee number and salary increment/decrement passed
+   --  as IN parameters.  Upon successful completion the function
+   --  returns the new updated salary.
+   --
+   FUNCTION update_emp_sal (
+      p_empno         IN NUMBER,
+      p_raise         IN NUMBER
+   )
+   RETURN NUMBER
+   IS
+      v_sal           NUMBER := 0;
+   BEGIN
+      SELECT sal INTO v_sal FROM emp WHERE empno = p_empno;
+      v_sal := v_sal + p_raise;
+      UPDATE emp SET sal = v_sal WHERE empno = p_empno;
+      RETURN v_sal;
+   EXCEPTION
+      WHEN NO_DATA_FOUND THEN
+         DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno || ' not found');
+         RETURN -1;
+      WHEN OTHERS THEN
+         DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+         DBMS_OUTPUT.PUT_LINE(SQLERRM);
+         DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+         DBMS_OUTPUT.PUT_LINE(SQLCODE);
+         RETURN -1;
+   END;
+   --
+   --  Procedure that inserts a new employee record into the 'emp' table.
+   --
+   PROCEDURE hire_emp (
+      p_empno         NUMBER,
+      p_ename         VARCHAR2,
+      p_job           VARCHAR2,
+      p_sal           NUMBER,
+      p_hiredate      DATE    DEFAULT sysdate,
+      p_comm          NUMBER  DEFAULT 0,
+      p_mgr           NUMBER,
+      p_deptno        NUMBER  DEFAULT 10
+   )
+   AS
+   BEGIN
+      INSERT INTO emp(empno, ename, job, sal, hiredate, comm, mgr, deptno)
+         VALUES(p_empno, p_ename, p_job, p_sal,
+                p_hiredate, p_comm, p_mgr, p_deptno);
+   END;
+   --
+   --  Procedure that deletes an employee record from the 'emp' table based
+   --  on the employee number.
+   --
+   PROCEDURE fire_emp (
+      p_empno         NUMBER
+   )
+   AS
+   BEGIN
+      DELETE FROM emp WHERE empno = p_empno;
+   END;
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/03_referencing_a_package.mdx b/product_docs/docs/epas/16/application_programming/02_packages/03_referencing_a_package.mdx
new file mode 100644
index 00000000000..30881b98fb5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/03_referencing_a_package.mdx
@@ -0,0 +1,26 @@
+---
+title: "Referencing a package"
+description: "Describes how to reference the types, items, and subprograms that are declared in a package specification"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.08.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.186.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/03_referencing_a_package/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+To reference the types, items, and subprograms that are declared in a package specification, use the dot notation. For example:
+
+`package_name.type_name`
+
+`package_name.item_name`
+
+`package_name.subprogram_name`
+
+To invoke a function from the `emp_admin` package specification, execute the following SQL command:
+
+```sql
+SELECT emp_admin.get_dept_name(10) FROM DUAL;
+```
+
+This example invokes the `get_dept_name` function declared in the package `emp_admin`. It passes the department number as an argument to the function, which returns the name of the department. The value returned is `ACCOUNTING`, which corresponds to department number `10`.
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/04_using_packages_with_user_defined_types.mdx b/product_docs/docs/epas/16/application_programming/02_packages/04_using_packages_with_user_defined_types.mdx
new file mode 100644
index 00000000000..6312a2077e5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/04_using_packages_with_user_defined_types.mdx
@@ -0,0 +1,192 @@
+---
+title: "Using packages with user-defined types"
+description: "Provides an example that incorporates various user-defined types in the context of a package"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.09.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.187.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/04_using_packages_with_user_defined_types/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This example incorporates various user-defined types in the context of a package.
+
+## Package specification
+
+The package specification of `emp_rpt` shows the declaration of a record type `emprec_typ` and a weakly typed `REF CURSOR, emp_refcur` as publicly accessible. It also shows two functions and two procedures. The function, `open_emp_by_dept`, returns the `REF CURSOR` type `EMP_REFCUR`. Procedures `fetch_emp` and `close_refcur` both declare a weakly typed `REF CURSOR` as a formal parameter.
+
+```sql
+CREATE OR REPLACE PACKAGE emp_rpt
+IS
+    TYPE emprec_typ IS RECORD (
+        empno       NUMBER(4),
+        ename       VARCHAR(10)
+    );
+    TYPE emp_refcur IS REF CURSOR;
+
+    FUNCTION get_dept_name (
+        p_deptno    IN NUMBER
+    ) RETURN VARCHAR2;
+    FUNCTION open_emp_by_dept (
+        p_deptno    IN emp.deptno%TYPE
+    ) RETURN EMP_REFCUR;
+    PROCEDURE fetch_emp (
+        p_refcur    IN OUT SYS_REFCURSOR
+    );
+    PROCEDURE close_refcur (
+        p_refcur    IN OUT SYS_REFCURSOR
+    );
+END emp_rpt;
+```
+
+## Package body
+
+The package body shows the declaration of several private variables: a static cursor `dept_cur`, a table type `depttab_typ`, a table variable `t_dept`, an integer variable `t_dept_max`, and a record variable `r_emp`.
+
+```sql
+CREATE OR REPLACE PACKAGE BODY emp_rpt
+IS
+    CURSOR dept_cur IS SELECT * FROM dept;
+    TYPE depttab_typ IS TABLE of dept%ROWTYPE
+        INDEX BY BINARY_INTEGER;
+    t_dept          DEPTTAB_TYP;
+    t_dept_max      INTEGER := 1;
+    r_emp           EMPREC_TYP;
+
+    FUNCTION get_dept_name (
+        p_deptno    IN NUMBER
+    ) RETURN VARCHAR2
+    IS
+    BEGIN
+        FOR i IN 1..t_dept_max LOOP
+            IF p_deptno = t_dept(i).deptno THEN
+                RETURN t_dept(i).dname;
+            END IF;
+        END LOOP;
+        RETURN 'Unknown';
+    END;
+
+    FUNCTION open_emp_by_dept(
+        p_deptno        IN emp.deptno%TYPE
+    ) RETURN EMP_REFCUR
+    IS
+        emp_by_dept EMP_REFCUR;
+    BEGIN
+        OPEN emp_by_dept FOR SELECT empno, ename FROM emp
+            WHERE deptno = p_deptno;
+        RETURN emp_by_dept;
+    END;
+
+    PROCEDURE fetch_emp (
+        p_refcur      IN OUT SYS_REFCURSOR
+    )
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('EMPNO ENAME');
+        DBMS_OUTPUT.PUT_LINE('----- -------');
+        LOOP
+            FETCH p_refcur INTO r_emp;
+            EXIT WHEN p_refcur%NOTFOUND;
+            DBMS_OUTPUT.PUT_LINE(r_emp.empno || ' ' || r_emp.ename);
+        END LOOP;
+    END;
+
+    PROCEDURE close_refcur (
+        p_refcur      IN OUT SYS_REFCURSOR
+    )
+    IS
+    BEGIN
+        CLOSE p_refcur;
+    END;
+BEGIN
+    OPEN dept_cur;
+    LOOP
+        FETCH dept_cur INTO t_dept(t_dept_max);
+        EXIT WHEN dept_cur%NOTFOUND;
+        t_dept_max := t_dept_max + 1;
+    END LOOP;
+    CLOSE dept_cur;
+    t_dept_max := t_dept_max - 1;
+END emp_rpt;
+```
+
+This package contains an initialization section that loads the private table variable `t_dept` using the private static cursor `dept_cur.t_dept`. `dept_cur.t_dept` serves as a department name lookup table in the function `get_dept_name`.
+
+The function `open_emp_by_dept` returns a `REF CURSOR` variable for a result set of employee numbers and names for a given department. This `REF CURSOR` variable can then be passed to the procedure `fetch_emp` to retrieve and list the individual rows of the result set. Finally, the procedure `close_refcur` can be used to close the `REF CURSOR` variable associated with this result set.
+
+## Using anonymous blocks
+The following anonymous block runs the package function and procedures. In the anonymous block's declaration section, note the declaration of cursor variable `v_emp_cur` using the package’s public `REF CURSOR` type, `EMP_REFCUR. v_emp_cur` contains the pointer to the result set that's passed between the package function and procedures.
+
+```sql
+DECLARE
+    v_deptno dept.deptno%TYPE DEFAULT 30;
+    v_emp_cur emp_rpt.EMP_REFCUR;
+BEGIN
+    v_emp_cur := emp_rpt.open_emp_by_dept(v_deptno);
+    DBMS_OUTPUT.PUT_LINE('EMPLOYEES IN DEPT #' || v_deptno ||
+        ': ' || emp_rpt.get_dept_name(v_deptno));
+    emp_rpt.fetch_emp(v_emp_cur);
+    DBMS_OUTPUT.PUT_LINE('**********************');
+    DBMS_OUTPUT.PUT_LINE(v_emp_cur%ROWCOUNT || ' rows were retrieved');
+    emp_rpt.close_refcur(v_emp_cur);
+END;
+```
+
+The following is the result of this anonymous block:
+
+```sql
+__OUTPUT__
+EMPLOYEES IN DEPT #30: SALES
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7521     WARD
+7654     MARTIN
+7698     BLAKE
+7844     TURNER
+7900     JAMES
+**********************
+6 rows were retrieved
+```
+
+The following anonymous block shows another way to achieve the same result. Instead of using the package procedures `fetch_emp` and `close_refcur`, the logic of these programs is coded directly into the anonymous block. In the anonymous block’s declaration section, note the addition of record variable `r_emp`, declared using the package’s public record type, `EMPREC_TYP`.
+
+```sql
+DECLARE
+    v_deptno     dept.deptno%TYPE DEFAULT 30;
+    v_emp_cur    emp_rpt.EMP_REFCUR;
+    r_emp        emp_rpt.EMPREC_TYP;
+BEGIN
+    v_emp_cur := emp_rpt.open_emp_by_dept(v_deptno);
+    DBMS_OUTPUT.PUT_LINE('EMPLOYEES IN DEPT #' || v_deptno ||
+        ': ' || emp_rpt.get_dept_name(v_deptno));
+    DBMS_OUTPUT.PUT_LINE('EMPNO ENAME');
+    DBMS_OUTPUT.PUT_LINE('----- -------');
+    LOOP
+        FETCH v_emp_cur INTO r_emp;
+        EXIT WHEN v_emp_cur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(r_emp.empno || ' ' ||
+            r_emp.ename);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('**********************');
+    DBMS_OUTPUT.PUT_LINE(v_emp_cur%ROWCOUNT || ' rows were retrieved');
+    CLOSE v_emp_cur;
+END;
+```
+
+The following is the result of this anonymous block.
+
+```sql
+__OUTPUT__
+EMPLOYEES IN DEPT #30: SALES
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7521     WARD
+7654     MARTIN
+7698     BLAKE
+7844     TURNER
+7900     JAMES
+**********************
+6 rows were retrieved
+```
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/05_dropping_a_package.mdx b/product_docs/docs/epas/16/application_programming/02_packages/05_dropping_a_package.mdx
new file mode 100644
index 00000000000..e5e1ba93397
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/05_dropping_a_package.mdx
@@ -0,0 +1,30 @@
+---
+title: "Dropping a package"
+description: "Defines the syntax for dropping a package"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.10.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.188.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/05_dropping_a_package/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The syntax for deleting an entire package or the package body is:
+
+```sql
+DROP PACKAGE [ BODY ] package_name;
+```
+
+If you omit the keyword `BODY`, both the package specification and the package body are deleted, that is, the entire package is dropped. If you specify the keyword `BODY`, then only the package body is dropped. The package specification remains intact. `package_name` is the identifier of the package to drop.
+
+The following statement destroys only the package body of `emp_admin`:
+
+```sql
+DROP PACKAGE BODY emp_admin;
+```
+
+The following statement drops the entire `emp_admin` package:
+
+```sql
+DROP PACKAGE emp_admin;
+```
diff --git a/product_docs/docs/epas/16/application_programming/02_packages/index.mdx b/product_docs/docs/epas/16/application_programming/02_packages/index.mdx
new file mode 100644
index 00000000000..b8e8764ed36
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/02_packages/index.mdx
@@ -0,0 +1,24 @@
+---
+navTitle: Working with packages
+title: "Working with packages"
+indexCards: simple
+description: "How to use packages to encapsulate logically related types, items, and subprograms"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.05.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/02_packages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+A *package* is a named collection of functions, procedures, variables, cursors, user-defined record types, and records that are referenced using a common qualifier: the package identifier. Packages have the following characteristics:
+
+-   They provide a convenient means of organizing the functions and procedures that perform a related purpose. Permission to use the package functions and procedures depends on one privilege granted to the entire package. You must reference all of the package programs with a common name.
+-   You can declare certain functions, procedures, variables, types, and so on in the package as *public*. Public entities are visible and other programs that are given `EXECUTE` privilege on the package can reference them. For public functions and procedures, only their signatures are visible: the program names, parameters, if any, and return types of functions. The SPL code of these functions and procedures isn't accessible to others. Therefore applications that use a package depend on only the information available in the signature and not in the procedural logic itself.
+-   You can declare other functions, procedures, variables, types, and so on in the package as *private*. Private entities can be referenced and used by function and procedures in the package but not by other external applications. Private entities are for use only by programs in the package.
+-   Function and procedure names can be overloaded in a package. You can define one or more functions/procedures with the same name but with different signatures. This capability enables you to create identically named programs that perform the same job but on different types of input.
+
+<div class="toctree" maxdepth="5">
+
+package_components creating_packages referencing_a_package using_packages_with_user_defined_types dropping_a_package
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/12_debugger/configuring_debugger.mdx b/product_docs/docs/epas/16/application_programming/12_debugger/configuring_debugger.mdx
new file mode 100644
index 00000000000..0096dae2dde
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/12_debugger/configuring_debugger.mdx
@@ -0,0 +1,38 @@
+---
+title: "Configuring the debugger"
+description: "Describes how to configure the debugger program prior to use"
+---
+
+The debugger is integrated with pgAdmin 4 and EDB Postgres Enterprise Manager. If you installed EDB Postgres Advanced Server on a Windows host, pgAdmin 4 is automatically installed. The pgAdmin 4 icon is in the Windows Start menu. 
+
+You can use the debugger in two basic ways to test programs:
+
+-   **Standalone debugging** &mdash; Use the debugger to start the program to test. Supply any input parameter values required by the program. You can immediately observe and step through the code of the program. Standalone debugging is the typical method used for new programs and for initial problem investigation.
+-   **In-context debugging** &mdash; In-context debugging is useful if it's difficult to reproduce a problem using standalone debugging due to complex interaction with the calling application. Using this approach, the program to test is started by an application other than the debugger. You set a *global breakpoint* on the program to test. The application that makes the first call to the program encounters the global breakpoint. Then the application suspends execution. At that point, the debugger takes control of the called program. You can then observe and step through the code of the called program as it runs in the context of the calling application. 
+
+  After you have completely stepped through the code of the called program in the debugger, the suspended application resumes executing.
+
+The debugging tools and operations are the same whether using standalone or in-context debugging. The difference is in how to invoke the program being debugged.
+
+If your EDB Postgres Advanced Server host is on a CentOS or Linux system, you can use `yum` to install pgAdmin4. Open a command line, assume superuser privileges, and enter:
+
+```shell
+yum install edb-pgadmin4*
+```
+
+On Linux, you must also install the `edb-as<xx>-server-pldebugger` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number. Information about pgAdmin 4 is available at the [pgAdmin website](https://www.pgadmin.org/).
+
+The RPM installation adds the pgAdmin4 icon to your Applications menu.
+
+Before using the debugger, edit the `postgresql.conf` file (located in the `data` subdirectory of your EDB Postgres Advanced Server home directory). Add `$libdir/plugin_debugger` to the libraries listed in the `shared_preload_libraries` configuration parameter:
+
+```ini
+shared_preload_libraries = '$libdir/dbms_pipe,$libdir/edb_gen,$libdir/plugin_debugger'
+```
+
+-   On Linux, the `postgresql.conf` file is located in: `/var/lib/edb/as<xx>/data`
+-   On Windows, the `postgresql.conf` file is located in: `C:\Program Files\edb\as<xx>\data`
+
+Where `<xx>` is the version of EDB Postgres Advanced Server.
+
+After modifying the `shared_preload_libraries` parameter, restart the database server.
diff --git a/product_docs/docs/epas/16/application_programming/12_debugger/debugger_interface.mdx b/product_docs/docs/epas/16/application_programming/12_debugger/debugger_interface.mdx
new file mode 100644
index 00000000000..6ee1511d447
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/12_debugger/debugger_interface.mdx
@@ -0,0 +1,52 @@
+---
+title: "Debugger interface overview"
+description: "Provides an overview of the main window of the debugger program"
+---
+
+The main debugger window contains two panels:
+
+-   The top Program Body panel displays the program source code.
+-   The bottom Tabs panel provides a set of tabs for different information.
+
+Use the tool bar icons located at the top panel to access debugging functions.
+
+## The Program Body panel
+
+The Program Body panel displays the source code of the program that's being debugged. The figure shows that the debugger is about to execute the `SELECT` statement. The blue indicator in the program body highlights the next statement to execute.
+
+![The Program Body](../../images/program_body.png)
+
+## The Tabs panel
+
+You can use the bottom Tabs panel to view or modify parameter values or local variables or to view messages generated by `RAISE INFO` and function results.
+
+The following is the information displayed by the tabs in the panel:
+
+-   The **Parameters** tab displays the current parameter values.
+-   The **Local variables** tab displays the value of any variables declared in the program.
+-   The **Messages** tab displays any results returned by the program as it executes.
+-   The **Results** tab displays any program results, such as the value from the `RETURN` statement of a function.
+-   The **Stack** tab displays the call stack.
+
+## The Stack tab
+
+<div id="stack_tab" class="registered_link"></div>
+
+The **Stack** tab displays a list of programs that are currently on the call stack, that is, programs that were invoked but that haven't yet completed. When a program is called, the name of the program is added to the top of the list displayed in the **Stack** tab. When the program ends, its name is removed from the list.
+
+The **Stack** tab also displays information about program calls. The information includes:
+
+-   The location of the call in the program
+-   The call arguments
+-   The name of the program being called
+
+Reviewing the call stack can help you trace the course of execution through a series of nested programs. 
+The figure shows that `emp_query_caller` is about to call a subprogram named `emp_query`. `emp_query_caller` is currently at the top of the call stack.
+
+![A debugged program calling a subprogram](../../images/stack_tab.png)
+
+After the call to `emp_query` executes, `emp_query` is displayed at the top of the **Stack** tab, and its code is displayed in the Program Body panel.
+
+![Debugging the called subprogram](../../images/stack_tab.png)
+
+After completing execution of the subprogram, control returns to the calling program (`emp_query_caller`), now displayed at the top of the **Stack** tab.
diff --git a/product_docs/docs/epas/16/application_programming/12_debugger/debugging_a_program.mdx b/product_docs/docs/epas/16/application_programming/12_debugger/debugging_a_program.mdx
new file mode 100644
index 00000000000..d61537fb661
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/12_debugger/debugging_a_program.mdx
@@ -0,0 +1,115 @@
+---
+title: "Running the debugger"
+description: "Describes the operations you can perform to debug a program"
+---
+
+You can perform the following operations to debug a program:
+
+-   Step through the program one line at a time.
+-   Execute the program until you reach a breakpoint.
+-   View and change local variable values within the program.
+
+## Considerations when using the program
+
+- These instructions use the standalone debugging method. To start the debugger for in-context debugging, see [Setting global breakpoint for in-context debugging](#setting_global_breakpoint_for_in_context_debugging).
+
+- You can't debug triggers using standalone debugging. You must use in-context debugging. See [Setting global breakpoint for in-context debugging](#setting_global_breakpoint_for_in_context_debugging) for information.
+
+
+## Stepping through the code
+
+Use the tool bar icons to step through a program with the debugger. The icons serve the following purposes:
+
+-   **Step into.** Execute the currently highlighted line of code.
+-   **Step over.** Execute a line of code, stepping over any subfunctions invoked by the code. The subfunction executes but is debugged only if it contains a breakpoint.
+-   **Continue/Start.** Execute the highlighted code and continue until the program encounters a breakpoint or completes.
+-   **Stop.** Halt a program.
+
+## Using breakpoints
+
+As the debugger executes a program, it pauses when it reaches a breakpoint. When the debugger pauses, you can observe or change local variables or navigate to an entry in the call stack to observe variables or set other breakpoints. The next step into, step over, or continue operation forces the debugger to resume executing with the next line of code following the breakpoint. 
+
+These are the two types of breakpoints:
+
+-  **Local breakpoint** &mdash; You can set a local breakpoint at any executable line of code in a program. The debugger pauses execution when it reaches a line where a local breakpoint was set.
+
+-  **Global breakpoint** &mdash; A global breakpoint triggers when any session reaches that breakpoint. Set a global breakpoint if you want to perform in-context debugging of a program. When you set a global breakpoint on a program, the debugging session that set the global breakpoint waits until that program is invoked in another session. Only a superuser can set a global breakpoint.
+
+### Setting a local breakpoint
+
+To create a local breakpoint, select the grey shaded margin to the left of the line of code where you want the local breakpoint set. The spot you select must be close to the right side of the margin as in the spot where the breakpoint dot is shown on source code line 12. When the breakpoint is created, the debugger displays a dark dot in the margin, indicating a breakpoint was set at the selected line of code.
+
+![Set a breakpoint by clicking in left-hand margin](../../images/setting_global_breakpoint_from_left-hand_margin.png)
+
+You can set as many local breakpoints as you want. Local breakpoints remain in effect for the rest of a debugging session until you remove them.
+
+### Removing a local breakpoint
+
+To remove a local breakpoint, select the breakpoint dot. The dot disappears.
+
+To remove all of the breakpoints from the program that currently appears in the Program Body frame,  select the **Clear all breakpoints** icon.
+
+!!! Note
+    When you perform any of these actions, only the breakpoints in the program that currently appears in the Program Body panel are removed. Breakpoints in called subprograms or breakpoints in programs that call the program currently appearing in the Program Body panel aren't removed.
+
+### Setting a global breakpoint for in-context debugging
+
+<div id="setting_global_breakpoint_for_in_context_debugging" class="registered_link"></div>
+
+To set a global breakpoint for in-context debugging:
+
+1. In the Browser panel, select the stored procedure, function, or trigger on which you want to set the breakpoint. 
+
+1. Select **Object > Debugging > Set Breakpoint**.
+
+To set a global breakpoint on a trigger:
+
+1. Expand the table node that contains the trigger.
+
+1. Select the specific trigger you want to debug.
+
+1. Select **Object > Debugging > Set Breakpoint**.
+
+To set a global breakpoint in a package:
+
+1. Select the specific procedure or function under the package node of the package you want to debug.
+
+1. Select **Object > Debugging > Set Breakpoint**.
+
+After you select **Set Breakpoint**, the Debugger window opens and waits for an application to call the program to debug.
+
+The PSQL client invokes the `select_emp` function on which a global breakpoint was set.
+
+```sql
+$ psql edb enterprisedb
+psql.bin (16.1.0, server 16.1.0)
+Type "help" for help.
+
+edb=# SELECT select_emp(7900);
+```
+
+The `select_emp` function doesn't finish until you step through the program in the debugger.
+
+![Program on which a global breakpoint was set](../../images/parameters_tab.png)
+
+You can now debug the program using the operations like step into, step over, and continue. Or you can set local breakpoints. After you step through executing the program, the calling application (PSQL) regains control, the `select_emp` function finishes executing, and its output is displayed.
+
+```sql
+$ psql edb enterprisedb
+psql.bin (16.1.0, server 16.1.0)
+Type "help" for help.
+
+edb=# SELECT select_emp(7900);
+__OUTPUT__
+INFO: Number    : 7900
+INFO: Name      : JAMES
+INFO: Hire Date : 12/03/1981
+INFO: Salary    : 950.00
+INFO: Commission: 0.00
+INFO: Department: SALES
+ select_emp
+------------
+(1 row)
+```
+
+At this point, you can end the debugger session. If you don't end the debugger session, the next application that invokes the program encounters the global breakpoint, and the debugging cycle begins again.
diff --git a/product_docs/docs/epas/16/application_programming/12_debugger/index.mdx b/product_docs/docs/epas/16/application_programming/12_debugger/index.mdx
new file mode 100644
index 00000000000..0f77c9e76aa
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/12_debugger/index.mdx
@@ -0,0 +1,30 @@
+---
+title: "Debugging programs"
+description: "How to use the debugger to identify ways to make your program run faster, more efficiently, and more reliably"
+indexCards: simple
+navigation:
+  - configuring_debugger
+  - starting_debugger
+  - debugger_interface
+  - debugging_a_program
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.41.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.42.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.40.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.110.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.112.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.111.html"
+---
+
+<div id="debugger" class="registered_link"></div>
+
+The debugger gives developers and DBAs the ability to test and debug server-side programs using a graphical, dynamic environment. The types of programs that you can debug are:
+- SPL stored procedures
+- functions
+- triggers
+- packages
+- PL/pgSQL functions and triggers.
+
+
+
diff --git a/product_docs/docs/epas/16/application_programming/12_debugger/starting_debugger.mdx b/product_docs/docs/epas/16/application_programming/12_debugger/starting_debugger.mdx
new file mode 100644
index 00000000000..7443ef2a04c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/12_debugger/starting_debugger.mdx
@@ -0,0 +1,31 @@
+---
+title: "Starting the debugger"
+description: "Describes how to open the debugger program"
+---
+
+Use pgAdmin 4 to access the debugger for standalone debugging. To open the debugger: 
+
+1.  Select the name of the stored procedure or function you want to debug in the pgAdmin 4 **Browser** panel. Or, to debug a package, select the specific procedure or function under the package node of the package you want to debug.
+
+1.  Select **Object > Debugging > Debug**.
+
+You can use the Debugger window to pass parameter values when you are standalone debugging a program that expects parameters. When you start the debugger, the Debugger window opens to display any `IN` or `IN OUT` parameters the program expects. If the program declares no `IN` or `IN OUT` parameters, the Debugger window doesn't open.
+
+Use the fields on the Debugger window to provide a value for each parameter:
+
+-   The **Name** field contains the formal parameter name.
+-   The **Type** field contains the parameter data type.
+-   Select the **Null?** check box to indicate that the parameter is a `NULL` value.
+-   Select the **Expression?** check box if the `Value` field contains an expression.
+-   The **Value** field contains the parameter value that's passed to the program.
+-   Select the **Use Default?** check box to indicate for the program to use the value in the **Default Value** field.
+-   The **Default Value** field contains the default value of the parameter.
+
+If you're debugging a procedure or function that's a member of a package that has an initialization section, select the **Debug Package Initializer** check box to step into the package initialization section, This setting allows you to debug the initialization section code before debugging the procedure or function. If you don't select the check box, the debugger executes the package initialization section without allowing you to see or step through the individual lines of code as they execute.
+
+After entering the desired parameter values, select **Debug** to start the debugging process.
+
+!!! Note
+    The Debugger window doesn't open during in-context debugging. Instead, the application calling the program to debug must supply any required input parameter values.
+
+After you complete a full debugging cycle by stepping through the program code, the Debugger window reopens. You can enter new parameter values and repeat the debugging cycle or end the debugging session.
diff --git a/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/comment_command.mdx b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/comment_command.mdx
new file mode 100644
index 00000000000..d9746991c2c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/comment_command.mdx
@@ -0,0 +1,164 @@
+---
+title: "Using the COMMENT command"
+description: "Describes how to add comments to objects"
+redirects:
+  - /epas/latest/epas_guide/15_enhanced_sql_and_other_misc_features/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+In addition to allowing comments on objects supported by the PostgreSQL `COMMENT` command, EDB Postgres Advanced Server supports comments on other object types. The complete supported syntax is:
+
+```sql
+COMMENT ON
+{
+  AGGREGATE <aggregate_name> ( <aggregate_signature> ) |
+  CAST (<source_type> AS <target_type>) |
+  COLLATION <object_name> |
+  COLUMN <relation_name>.<column_name> |
+  CONSTRAINT <constraint_name> ON <table_name> |
+  CONSTRAINT <constraint_name> ON DOMAIN <domain_name> |
+  CONVERSION <object_name> |
+  DATABASE <object_name> |
+  DOMAIN <object_name> |
+  EXTENSION <object_name> |
+  EVENT TRIGGER <object_name> |
+  FOREIGN DATA WRAPPER <object_name> |
+  FOREIGN TABLE <object_name> |
+  FUNCTION <func_name> ([[<argmode>] [<argname>] <argtype> [,...]])|
+  INDEX <object_name> |
+  LARGE OBJECT <large_object_oid> |
+  MATERIALIZED VIEW <object_name> |
+  OPERATOR <operator_name> (left_type, right_type) |
+  OPERATOR CLASS <object_name> USING <index_method> |
+  OPERATOR FAMILY <object_name> USING <index_method> |
+  PACKAGE <object_name>
+  POLICY <policy_name> ON <table_name> |
+  [ PROCEDURAL ] LANGUAGE <object_name> |
+  PROCEDURE <proc_name> [([[<argmode>] [<argname>] <argtype> [, ...]])]
+  PUBLIC SYNONYM <object_name>
+  ROLE <object_name> |
+  RULE <rule_name> ON <table_name> |
+  SCHEMA <object_name> |
+  SEQUENCE <object_name> |
+  SERVER <object_name> |
+  TABLE <object_name> |
+  TABLESPACE <object_name> |
+  TEXT SEARCH CONFIGURATION <object_name> |
+  TEXT SEARCH DICTIONARY <object_name> |
+  TEXT SEARCH PARSER <object_name> |
+  TEXT SEARCH TEMPLATE <object_name> |
+  TRANSFORM FOR <type_name> LANGUAGE <lang_name> |
+  TRIGGER <trigger_name> ON <table_name> |
+  TYPE <object_name> |
+  VIEW <object_name>
+} IS <'text'>
+```
+
+Where `aggregate_signature` is:
+
+```sql
+* |
+[ <argmode> ] [ <argname> ] <argtype> [ , ... ] |
+[ [ <argmode> ] [ <argname> ] <argtype> [ , ... ] ]
+ORDER BY [ <argmode> ] [ <argname> ] <argtype> [ , ... ]
+```
+
+## Parameters
+
+`object_name`
+
+The name of the object on which you're commenting.
+
+`AGGREGATE aggregate_name (aggregate_signature)`
+
+Include the `AGGREGATE` clause to create a comment about an aggregate. `aggregate_name` specifies the name of an aggregate. `aggregate_signature` specifies the associated signature in one of the following forms:
+
+```sql
+* |
+[ <argmode> ] [ <argname> ] <argtype> [ , ... ] |
+[ [ <argmode> ] [ <argname> ] <argtype> [ , ... ] ]
+ORDER BY [ <argmode> ] [ <argname> ] <argtype> [ , ... ]
+```
+
+Where `argmode` is the mode of a function, procedure, or aggregate argument. `argmode` can be `IN`, `OUT`, `INOUT`, or `VARIADIC`. The default is `IN`.
+
+`argname` is the name of an aggregate argument.
+
+`argtype` is the data type of an aggregate argument.
+
+`CAST (source_type AS target_type)`
+
+Include the `CAST` clause to create a comment about a cast. When creating a comment about a cast, `source_type` specifies the source data type of the cast, and `target_type` specifies the target data type of the cast.
+
+`COLUMN relation_name.column_name`
+
+Include the `COLUMN` clause to create a comment about a column. `column_name` specifies the name of the column to which the comment applies. `relation_name` is the table, view, composite type, or foreign table in which a column resides.
+
+`CONSTRAINT constraint_name ON table_name`
+
+`CONSTRAINT constraint_name ON DOMAIN domain_name`
+
+Include the `CONSTRAINT` clause to add a comment about a constraint. When you're creating a comment about a constraint, `constraint_name` specifies the name of the constraint. `table_name` or `domain_name` specifies the name of the table or domain on which the constraint is defined.
+
+`FUNCTION func_name ([[argmode] [argname] argtype [, ...]])`
+
+Include the `FUNCTION` clause to add a comment about a function. `func_name` specifies the name of the function. `argmode` specifies the mode of the function. `argmode` can be `IN`, `OUT`, `INOUT`, or `VARIADIC`. The default is `IN`.
+
+`argname` specifies the name of a function, procedure, or aggregate argument. `argtype` specifies the data type of a function, procedure, or aggregate argument.
+
+`large_object_oid`
+
+`large_object_oid` is the system-assigned OID of the large object about which you're commenting.
+
+`OPERATOR operator_name (left_type, right_type)`
+
+Include the `OPERATOR` clause to add a comment about an operator. `operator_name` specifies the optionally schema-qualified name of an operator on which you're commenting. `left_type` and `right_type` are the optionally schema-qualified data types of the operator's arguments.
+
+`OPERATOR CLASS object_name USING index_method`
+
+Include the `OPERATOR CLASS` clause to add a comment about an operator class. `object_name` specifies the optionally schema-qualified name of an operator on which you're commenting. `index_method` specifies the associated index method of the operator class.
+
+`OPERATOR FAMILY object_name USING index_method`
+
+Include the `OPERATOR FAMILY` clause to add a comment about an operator family. `object_name` specifies the optionally schema-qualified name of an operator family on which you're commenting. `index_method` specifies the associated index method of the operator family.
+
+`POLICY policy_name ON table_name`
+
+Include the `POLICY` clause to add a comment about a policy. `policy_name` specifies the name of the policy. `table_name` specifies the table that the policy is associated with.
+
+`PROCEDURE proc_name [([[argmode] [argname] argtype [, ...]])]`
+
+Include the `PROCEDURE` clause to add a comment about a procedure. `proc_name` specifies the name of the procedure. `argmode` specifies the mode of the procedure. `argmode` can be `IN`, `OUT`, `INOUT`, or `VARIADIC`. The default is `IN`.
+
+`argname` specifies the name of a function, procedure, or aggregate argument. `argtype` specifies the data type of a function, procedure, or aggregate argument.
+
+`RULE rule_name ON table_name`
+
+Include the `RULE` clause to specify a comment on a rule. `rule_name` specifies the name of the rule. `table_name` specifies the name of the table on which the rule is defined.
+
+`TRANSFORM FOR type_name LANGUAGE lang_name`
+
+Include the `TRANSFORM FOR` clause to specify a comment on a `TRANSFORM`.
+
+`type_name` specifies the name of the data type of the transform. `lang_name` specifies the name of the language of the transform.
+
+`TRIGGER trigger_name ON table_name`
+
+Include the `TRIGGER` clause to specify a comment on a trigger. `trigger_name` specifies the name of the trigger. `table_name` specifies the name of the table on which the trigger is defined.
+
+`text`
+
+The comment, written as a string literal, or `NULL` to drop the comment.
+
+!!! Note
+    Names of tables, aggregates, collations, conversions, domains, foreign tables, functions, indexes, operators, operator classes, operator families, packages, procedures, sequences, text search objects, types, and views can be schema qualified.
+
+## Example
+
+This example adds a comment to a table named `new_emp`:
+
+```sql
+COMMENT ON TABLE new_emp IS 'This table contains information about new
+employees.';
+```
+
+For more information about using the `COMMENT` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-comment.html).
diff --git a/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/index.mdx b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/index.mdx
new file mode 100644
index 00000000000..f1664dcd109
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Using enhanced SQL and other miscellaneous features"
+description: "How to use the enhanced SQL functionality and additional productivity features included in EDB Postgres Advanced Server"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.60.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.032.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.062.html"
+---
+
+<div id="enhanced_sql_and_other_misc_features" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes enhanced SQL functionality and other features that add flexibility and convenience. 
+
+
diff --git a/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/logical_decoding.mdx b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/logical_decoding.mdx
new file mode 100644
index 00000000000..c739ab937e1
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/logical_decoding.mdx
@@ -0,0 +1,17 @@
+---
+title: "Configuring logical decoding on standby"
+description: "Describes how to create a logical replication slot on a standby server"
+---
+
+Logical decoding on a standby server allows you to create a logical replication slot on a standby server that can respond to API operations such as `get`, `peek`, and `advance`.
+
+For more information about logical decoding, refer to the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/logicaldecoding-explanation.html).
+
+For a logical slot on a standby server to work, you must set the `hot_standby_feedback` parameter to `ON` on the standby. The `hot_standby_feedback` parameter prevents `VACCUM` from removing recently dead rows that are required by an existing logical replication slot on the standby server. If a slot conflict occurs on the standby, the slots are dropped.
+
+For logical decoding on a standby to work, you must set `wal_level` to `logical` on both the primary and standby servers. If you set `wal_level` to a value other than `logical`, then slots aren't created. If you set `wal_level` to a value other than `logical` on primary, and if existing logical slots are on standby, such slots are dropped. You can't create new slots.
+
+When transactions are written to the primary server, the activity triggers the creation of a logical slot on the standby server. If a primary server is idle, creating a logical slot on a standby server might take noticeable time.
+
+For more information about functions that support replication, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-REPLICATION). See also this [logical decoding example](https://www.postgresql.org/docs/current/logicaldecoding-example.html).
+
diff --git a/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/obtaining_version_information.mdx b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/obtaining_version_information.mdx
new file mode 100644
index 00000000000..490a838995e
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/15_enhanced_sql_and_other_misc_features/obtaining_version_information.mdx
@@ -0,0 +1,39 @@
+---
+title: "Obtaining version information"
+description: "Describes how to display the product name, version, and the host system on which it was installed."
+---
+
+The text string output of the `version()` function displays the name of the product, its version, and the host system on which it was installed.
+
+For EDB Postgres Advanced Server, the `version()` output is in a format similar to the PostgreSQL community version. The first text word is *PostgreSQL* instead of *EnterpriseDB* as in EDB Postgres Advanced Server version 10 and earlier.
+
+The general format of the `version()` output is:
+
+```text
+PostgreSQL $PG_VERSION_EXT (EnterpriseDB EDB Postgres Advanced Server $PG_VERSION) on $host
+```
+
+So for the current EDB Postgres Advanced Server, the version string appears as follows:
+
+```sql
+edb@45032=#select version();
+__OUTPUT__
+version
+-----------------------------------------------------------------------------------------------
+------------------------------------------------
+PostgreSQL 16.1 (EnterpriseDB Advanced Server 16.1.0 (Debian 16.1.0-1.bullseye)) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
+(1 row)
+```
+
+In contrast, for EDB Postgres Advanced Server 10, the version string was the following:
+
+```sql
+edb=# select version();
+__OUTPUT__
+                                                version
+------------------------------------------------------------------------------------------
+-------------------
+EnterpriseDB 10.4.9 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 
+4.4.7-18), 64-bit
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/02_overview.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/02_overview.mdx
new file mode 100644
index 00000000000..05d4ede4740
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/02_overview.mdx
@@ -0,0 +1,126 @@
+---
+title: "ECPGPlus overview"
+description: "Provides an overview of the ECPGPlus precompiler capabilities"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.07.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.04.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.06.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.05.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/02_overview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="overview" class="registered_link"></div>
+
+EDB enhanced ECPG (the PostgreSQL precompiler) to create ECPGPlus. ECPGPlus is a Pro\*C-compatible version of the PostgreSQL C precompiler. ECPGPlus translates a program that combines C code and embedded SQL statements into an equivalent C program. As it performs the translation, ECPGPlus verifies that the syntax of each SQL construct is correct.
+
+## About ECPGPlus
+
+The following diagram charts the path of a program containing embedded SQL statements as it's compiled into an executable:
+
+![Compilation of a program containing embedded SQL statements](../../images/ecpg_path.png)
+
+Compilation of a program containing embedded SQL statements
+
+To produce an executable from a C program that contains embedded SQL statements:
+
+1.  Pass the program (`my_program.pgc` in the diagram) to the ECPGPlus precompiler. ECPGPlus translates each SQL statement in `my_program.pgc` into C code that calls the `ecpglib` API and produces a C program (`my_program.c`). 
+1. Pass the C program to a C compiler. The C compiler generates an object file (`my_program.o`). 
+1. Pass the object file (`my_program.o`) as well as the `ecpglib` library file and any other required libraries to the linker, which in turn produces the executable (`my_program`).
+
+While the ECPGPlus preprocessor validates the syntax of each SQL statement, it can't validate the semantics. For example, the preprocessor confirms that an `INSERT` statement is syntactically correct, but it can't confirm that the table mentioned in the `INSERT` statement exists.
+
+## Behind the scenes
+
+A client application contains a mix of C code and SQL code made up of the following elements:
+
+-   C preprocessor directives
+-   C declarations (variables, types, functions, ...)
+-   C definitions (variables, types, functions, ...)
+-   SQL preprocessor directives
+-   SQL statements
+
+For example:
+
+```c 
+1 #include <stdio.h>
+2 EXEC SQL INCLUDE sqlca;
+3
+4 extern void printInt(char *label, int val);
+5 extern void printStr(char *label, char *val);
+6 extern void printFloat(char *label, float val);
+7
+8 void displayCustomer(int custNumber)
+9 {
+10  EXEC SQL BEGIN DECLARE SECTION;
+11    VARCHAR custName[50];
+12    float custBalance;
+13    int custID = custNumber;
+14  EXEC SQL END DECLARE SECTION;
+15
+16  EXEC SQL SELECT name, balance
+17    INTO :custName, :custBalance
+18    FROM customer
+19    WHERE id = :custID;
+20
+21  printInt("ID", custID);
+22  printStr("Name", custName);
+23  printFloat("Balance", custBalance);
+24 }
+```
+
+In this code fragment:
+
+-   Line 1 specifies a directive to the C preprocessor.
+
+    C preprocessor directives can be interpreted or ignored. The option is controlled by a command line option (`-C PROC`) entered when you invoke ECPGPlus. In either case, ECPGPlus copies each C preprocessor directive to the output file (4) without change. Any C preprocessor directive found in the source file appears in the output file.
+
+-   Line 2 specifies a directive to the SQL preprocessor.
+
+    SQL preprocessor directives are interpreted by the ECPGPlus preprocessor and aren't copied to the output file.
+
+-   Lines 4 through 6 contain C declarations.
+
+    C declarations are copied to the output file without change, except that each `VARCHAR` declaration is translated into an equivalent `struct` declaration.
+
+-   Lines 10 through 14 contain an embedded-SQL declaration section.  
+
+    C variables that you refer to in SQL code are known as *host variables*. If you invoke the ECPGPlus preprocessor in Pro\*C mode (`-C PROC`), you can refer to any C variable in a SQL statement. Otherwise you must declare each host variable in a `BEGIN/END DECLARATION SECTION` pair.
+
+-   Lines 16 through 19 contain a SQL statement.
+
+    SQL statements are translated into calls to the ECPGPlus runtime library.
+
+-   Lines 21 through 23 contain C code.
+
+    C code is copied to the output file without change.
+
+Prefix any SQL statement with `EXEC SQL`. The SQL statement extends to the next (unquoted) semicolon. For example:
+
+```sql
+printf(“Updating employee salaries\n”);
+
+EXEC SQL UPDATE emp SET sal = sal * 1.25;
+EXEC SQL COMMIT;
+
+printf(“Employee salaries updated\n”);
+```
+
+When the preprocessor encounters this code fragment, it passes the C code (the first line and the last line) to the output file without translation and converts each `EXEC SQL` statement into a call to an `ecpglib` function. The result is similar to the following:
+
+```c
+printf("Updating employee salaries\n");
+
+{
+  ECPGdo( __LINE__, 0, 1, NULL, 0, ECPGst_normal,
+         "update emp set sal = sal * 1.25",
+         ECPGt_EOIT, ECPGt_EORT);
+}
+
+{
+  ECPGtrans(__LINE__, NULL, "commit");
+}
+
+printf(“Employee salaries updated\n”);
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx
new file mode 100644
index 00000000000..eb6b5564d4a
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/03_using_embedded_sql.mdx
@@ -0,0 +1,374 @@
+---
+title: "Using embedded SQL"
+description: "Provides examples for making a query and for using a cursor to process a result set"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.11.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.09.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.08.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.12.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.10.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/03_using_embedded_sql/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_embedded_sql" class="registered_link"></div>
+
+These two examples show how to use embedded SQL with EDB Postgres Advanced Server.
+
+## Example: A simple query
+
+The first code sample shows how to execute a `SELECT` statement that returns a single row, storing the results in a group of host variables. After declaring host variables, it connects to the `edb` sample database using a hard-coded role name and the associated password and queries the `emp` table. The query returns the values into the declared host variables. After checking the value of the `NULL` indicator variable, it prints a simple result set onscreen and closes the connection.
+
+```c
+/************************************************************
+ * print_emp.pgc
+ *
+ */
+#include <stdio.h>
+
+int main(void)
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    int v_empno;
+    char v_ename[40];
+    double v_sal;
+    double v_comm;
+    short v_comm_ind;
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL WHENEVER SQLERROR sqlprint;
+
+  EXEC SQL CONNECT TO edb
+    USER 'alice' IDENTIFIED BY '1safepwd';
+
+  EXEC SQL
+     SELECT
+      empno, ename, sal, comm
+     INTO
+      :v_empno, :v_ename, :v_sal, :v_comm INDICATOR:v_comm_ind
+     FROM
+      emp
+    WHERE
+      empno = 7369;
+
+  if (v_comm_ind)
+    printf("empno(%d), ename(%s), sal(%.2f) comm(NULL)\n",
+            v_empno, v_ename, v_sal);
+  else
+    printf("empno(%d), ename(%s), sal(%.2f) comm(%.2f)\n",
+            v_empno, v_ename, v_sal, v_comm);
+  EXEC SQL DISCONNECT;
+}
+/***********************************************************\*
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio` library and then declares the `main` function:
+
+```c
+#include <stdio.h>
+
+int main(void)
+{
+```
+
+Next, the application declares a set of host variables used to interact with the database server:
+
+```c
+EXEC SQL BEGIN DECLARE SECTION;
+  int v_empno;
+  char v_ename[40];
+  double v_sal;
+  double v_comm;
+  short v_comm_ind;
+EXEC SQL END DECLARE SECTION;
+```
+
+If you plan to precompile the code in `PROC` mode, you can omit the `BEGIN DECLARE…END DECLARE` section. For more information about declaring host variables, see [Declaring host variables](#declaring-host-variables).
+
+The data type associated with each variable in the declaration section is a C data type. Data passed between the server and the client application must share a compatible data type. For more information about data types, see the [Supported C data types](/epas/latest/reference/application_programmer_reference/07_reference/).
+
+The next statement tells the server how to handle an error:
+
+```sql
+EXEC SQL WHENEVER SQLERROR sqlprint;
+```
+
+If the client application encounters an error in the SQL code, the server prints an error message to `stderr` (standard error), using the `sqlprint()` function supplied with `ecpglib`. The next `EXEC SQL` statement establishes a connection with EDB Postgres Advanced Server:
+
+```sql
+EXEC SQL CONNECT TO edb
+  USER 'alice' IDENTIFIED BY '1safepwd';
+```
+
+In this example, the client application connects to the `edb` database using a role named alice with a password of `1safepwd`.
+
+The code then performs a query against the `emp` table:
+
+```sql
+EXEC SQL
+   SELECT
+     empno, ename, sal, comm
+   INTO
+     :v_empno, :v_ename, :v_sal, :v_comm INDICATOR :v_comm_ind
+   FROM
+     emp
+  WHERE
+     empno = 7369;
+```
+
+The query returns information about employee number 7369.
+
+The `SELECT` statement uses an `INTO` clause to assign the retrieved values (from the `empno`, `ename`, `sal`, and `comm` columns) into the `:v_empno`, `:v_ename`, `:v_sal`, and `:v_comm` host variables (and the `:v_comm_ind` null indicator). The first value retrieved is assigned to the first variable listed in the `INTO` clause, the second value is assigned to the second variable, and so on.
+
+The `comm` column contains the commission values earned by an employee and can potentially contain a `NULL` value. The statement includes the `INDICATOR` keyword and a host variable to hold a null indicator.
+
+The code checks the null indicator and displays the appropriate results:
+
+```C
+if (v_comm_ind)
+  printf("empno(%d), ename(%s), sal(%.2f) comm(NULL)\n",
+          v_empno, v_ename, v_sal);
+else
+  printf("empno(%d), ename(%s), sal(%.2f) comm(%.2f)\n",
+          v_empno, v_ename, v_sal, v_comm);
+```
+
+If the null indicator is `0` (that is, `false`), the `comm` column contains a meaningful value, and the `printf` function displays the commission. If the null indicator contains a non-zero value, `comm` is `NULL`, and `printf` displays a value of `NULL`. A host variable (other than a null indicator) contains no meaningful value if you fetch a `NULL` into that host variable. You must use null indicators to identify any value that might be `NULL`.
+
+The final statement in the code sample closes the connection to the server:
+
+```sql
+EXEC SQL DISCONNECT;
+}
+```
+
+### Using indicator variables
+
+The previous example included an *indicator variable* that identifies any row in which the value of the `comm` column (when returned by the server) was `NULL`. An indicator variable is an extra host variable that denotes if the content of the preceding variable is `NULL` or truncated. The indicator variable is populated when the contents of a row are stored. An indicator variable can contain the following values:
+
+| Indicator value                               | Denotes                                                                          |
+| --------------------------------------------- | -------------------------------------------------------------------------------- |
+| If an indicator variable is less than `0`.    | The value returned by the server was `NULL`.                                     |
+| If an indicator variable is equal to `0`.     | The value returned by the server was not `NULL`, and was not truncated.          |
+| If an indicator variable is greater than `0`. | The value returned by the server was truncated when stored in the host variable. |
+
+When including an indicator variable in an `INTO` clause, you don't need to include the optional `INDICATOR` keyword.
+
+You can omit an indicator variable if you're certain that a query never returns a `NULL` value into the corresponding host variable. If you omit an indicator variable and a query returns a `NULL` value, `ecpglib` raises a runtime error.
+
+<div id="declaring_host_variables" class="registered_link"></div>
+
+### Declaring host variables
+
+You can use a *host variable* in a SQL statement at any point that a value can appear in that statement. A host variable is a C variable that you can use to pass data values from the client application to the server and return data from the server to the client application. A host variable can be:
+
+-   An array
+-   A `typedef`
+-   A pointer
+-   A `struct`
+-   Any scalar C data type
+
+The code fragments that follow show using host variables in code compiled in `PROC` mode and in non-`PROC` mode. The SQL statement adds a row to the `dept` table, inserting the values returned by the variables `v_deptno`, `v_dname`, and `v_loc` into the `deptno` column, the `dname` column, and the `loc` column, respectively.
+
+If you're compiling in `PROC` mode, you can omit the `EXEC SQL BEGIN DECLARE SECTION` and `EXEC SQL END DECLARE SECTION` directives. `PROC` mode permits you to use C function parameters as host variables:
+
+```c
+void addDept(int v_deptno, char v_dname, char v_loc)
+{
+  EXEC SQL INSERT INTO dept VALUES( :v_deptno, :v_dname, :v_loc);
+}
+```
+
+If you aren't compiling in `PROC` mode, you must wrap embedded variable declarations with the `EXEC SQL BEGIN DECLARE SECTION` and the `EXEC SQL END DECLARE SECTION` directives:
+
+```c
+void addDept(int v_deptno, char v_dname, char v_loc)
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    int v_deptno_copy = v_deptno;
+    char v_dname_copy[14+1] = v_dname;
+    char v_loc_copy[13+1] = v_loc;
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL INSERT INTO dept VALUES( :v_deptno, :v_dname, :v_loc);
+}
+```
+
+You can also include the `INTO` clause in a `SELECT` statement to use the host variables to retrieve information:
+
+```sql
+EXEC SQL SELECT deptno, dname, loc
+  INTO :v_deptno, :v_dname, v_loc FROM dept;
+```
+
+Each column returned by the `SELECT` statement must have a type-compatible target variable in the `INTO` clause. This is a simple example that retrieves a single row. To retrieve more than one row, you must define a cursor, as shown in the next example.
+
+## Example: Using a cursor to process a result set
+
+The code sample that follows shows using a cursor to process a result set. Four basic steps are involved in creating and using a cursor:
+
+1.  Use the `DECLARE CURSOR` statement to define a cursor.
+2.  Use the `OPEN CURSOR` statement to open the cursor.
+3.  Use the `FETCH` statement to retrieve data from a cursor.
+4.  Use the `CLOSE CURSOR` statement to close the cursor.
+
+After declaring host variables, the example connects to the `edb` database using a user-supplied role name and password and queries the `emp` table. The query returns the values into a cursor named `employees`. The code sample then opens the cursor and loops through the result set a row at a time, printing the result set. When the sample detects the end of the result set, it closes the connection.
+
+```c
+/************************************************************
+ * print_emps.pgc
+ *
+ */
+#include <stdio.h>
+
+int main(int argc, char *argv[])
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    char *username = argv[1];
+    char *password = argv[2];
+    int v_empno;
+    char v_ename[40];
+    double v_sal;
+    double v_comm;
+    short v_comm_ind;
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL WHENEVER SQLERROR sqlprint;
+
+  EXEC SQL CONNECT TO edb USER :username IDENTIFIED BY :password;
+
+  EXEC SQL DECLARE employees CURSOR FOR
+    SELECT
+      empno, ename, sal, comm 
+    FROM 
+      emp;
+
+  EXEC SQL OPEN employees;
+
+  EXEC SQL WHENEVER NOT FOUND DO break;
+
+  for (;;)
+  {
+    EXEC SQL FETCH NEXT FROM employees 
+      INTO
+       :v_empno, :v_ename, :v_sal, :v_comm INDICATOR :v_comm_ind;
+
+    if (v_comm_ind)
+      printf("empno(%d), ename(%s), sal(%.2f) comm(NULL)\n",
+              v_empno, v_ename, v_sal);
+    else
+      printf("empno(%d), ename(%s), sal(%.2f) comm(%.2f)\n",
+              v_empno, v_ename, v_sal, v_comm);
+  }
+  EXEC SQL CLOSE employees;
+  EXEC SQL DISCONNECT;
+}
+/************************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio` library and then declares the `main` function:
+
+```c
+#include <stdio.h>
+
+int main(int argc, char *argv[])
+{
+```
+### DECLARE
+
+Next, the application declares a set of host variables used to interact with the database server:
+
+```sql
+EXEC SQL BEGIN DECLARE SECTION;
+  char *username = argv[1];
+  char *password = argv[2];
+  int v_empno;
+  char v_ename[40];
+  double v_sal;
+  double v_comm;
+  short v_comm_ind;
+EXEC SQL END DECLARE SECTION;
+```
+
+`argv[]` is an array that contains the command line arguments entered when the user runs the client application. `argv[1]` contains the first command line argument (in this case, a `username`), and `argv[2]` contains the second command line argument (a `password`). The example omits the error-checking code you would normally include a real-world application. The declaration initializes the values of `username` and `password`, setting them to the values entered when the user invoked the client application.
+
+You might think that you can refer to `argv[1]` and `argv[2]` in a SQL statement instead of creating a separate copy of each variable. However, that doesn't work. All host variables must be declared in a `BEGIN/END DECLARE SECTION`, unless you're compiling in `PROC` mode. Since `argv` is a function *parameter* (not an automatic variable), you can't declare it in a `BEGIN/END DECLARE SECTION`. If you're compiling in `PROC` mode, you can refer to any C variable in a SQL statement.
+
+The next statement tells the server to respond to an SQL error by printing the text of the error message returned by ECPGPlus or the database server:
+
+```sql
+EXEC SQL WHENEVER SQLERROR sqlprint;
+```
+
+Then, the client application establishes a connection with EDB Postgres Advanced Server:
+
+```sql
+EXEC SQL CONNECT TO edb USER :username IDENTIFIED BY :password;
+```
+
+The `CONNECT` statement creates a connection to the `edb` database, using the values found in the `:username` and `:password` host variables to authenticate the application to the server when connecting.
+
+The next statement declares a cursor named `employees`:
+
+```sql
+EXEC SQL DECLARE employees CURSOR FOR
+  SELECT
+    empno, ename, sal, comm 
+  FROM 
+    emp;
+```
+
+`employees` contains the result set of a `SELECT` statement on the `emp` table. The query returns employee information from the following columns: `empno`, `ename`, `sal`, and `comm`. Notice that when you declare a cursor, you don't include an `INTO` clause. Instead, you specify the target variables (or descriptors) when you `FETCH` from the cursor.
+
+### OPEN 
+
+Before fetching rows from the cursor, the client application must `OPEN` the cursor:
+
+```sql
+EXEC SQL OPEN employees;
+```
+
+In the subsequent `FETCH` section, the client application loops through the contents of the cursor. The client application includes a `WHENEVER` statement that instructs the server to `break` (that is, terminate the loop) when it reaches the end of the cursor:
+
+```sql
+EXEC SQL WHENEVER NOT FOUND DO break;
+```
+### FETCH
+
+The client application then uses a `FETCH` statement to retrieve each row from the cursor `INTO` the previously declared host variables:
+
+```c
+for (;;)
+{
+  EXEC SQL FETCH NEXT FROM employees
+    INTO
+     :v_empno, :v_ename, :v_sal, :v_comm INDICATOR :v_comm_ind;
+```
+
+The `FETCH` statement uses an `INTO` clause to assign the retrieved values into the `:v_empno`, `:v_ename`, `:v_sal`, and `:v_comm` host variables (and the `:v_comm_ind` null indicator). The first value in the cursor is assigned to the first variable listed in the `INTO` clause, the second value is assigned to the second variable, and so on.
+
+The `FETCH` statement also includes the `INDICATOR` keyword and a host variable to hold a null indicator. If the `comm` column for the retrieved record contains a `NULL` value, `v_comm_ind` is set to a non-zero value, indicating that the column is `NULL`.
+
+The code then checks the null indicator and displays the appropriate results:
+
+```c
+if (v_comm_ind)
+  printf("empno(%d), ename(%s), sal(%.2f) comm(NULL)\n",
+          v_empno, v_ename, v_sal);
+else
+  printf("empno(%d), ename(%s), sal(%.2f) comm(%.2f)\n",
+          v_empno, v_ename, v_sal, v_comm);
+}
+```
+
+If the null indicator is `0` (that is, `false`), `v_comm` contains a meaningful value, and the `printf` function displays the commission. If the null indicator contains a non-zero value, `comm` is `NULL`, and `printf` displays the string `'NULL'`. A host variable (other than a null indicator) contains no meaningful value if you fetch a `NULL` into that host variable. You must use null indicators for any value which may be `NULL`.
+
+### CLOSE 
+
+The final statements in the code sample close the cursor `(employees)` and the connection to the server:
+
+```sql
+EXEC SQL CLOSE employees;
+EXEC SQL DISCONNECT;
+```
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/04_using_descriptors.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/04_using_descriptors.mdx
new file mode 100644
index 00000000000..d4fee0c21d4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/04_using_descriptors.mdx
@@ -0,0 +1,570 @@
+---
+title: "Using descriptors"
+description: "Describes the process for executing SQL statements that are composed at runtime"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.13.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.14.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/04_using_descriptors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_descriptors" class="registered_link"></div>
+
+Dynamic SQL allows a client application to execute SQL statements that are composed at runtime. This ability is useful when you don't know the content or form for a statement when you're writing a client application. ECPGPlus doesn't allow you to use a host variable in place of an identifier (such as a table name, column name, or index name). Instead, use dynamic SQL statements to build a string that includes the information, and then execute that string. The string is passed between the client and the server in the form of a *descriptor*. A descriptor is a data structure that contains both the data and the information about the shape of the data.
+
+## Overview of the client application flow
+
+A client application must use a `GET DESCRIPTOR` statement to retrieve information from a descriptor. The basic flow of a client application using dynamic SQL is:
+
+1.  Use an `ALLOCATE DESCRIPTOR` statement to allocate a descriptor for the result set (select list).
+2.  Use an `ALLOCATE DESCRIPTOR` statement to allocate a descriptor for the input parameters (bind variables).
+3.  Obtain, assemble, or compute the text of an SQL statement.
+4.  Use a `PREPARE` statement to parse and check the syntax of the SQL statement.
+5.  Use a `DESCRIBE` statement to describe the select list into the select-list descriptor.
+6.  Use a `DESCRIBE` statement to describe the input parameters into the bind-variables descriptor.
+7.  Prompt the user (if required) for a value for each input parameter. Use a `SET DESCRIPTOR` statement to assign the values into a descriptor.
+8.  Use a `DECLARE CURSOR` statement to define a cursor for the statement.
+9.  Use an `OPEN CURSOR` statement to open a cursor for the statement.
+10. Use a `FETCH` statement to fetch each row from the cursor, storing each row in select-list descriptor.
+11. Use a `GET DESCRIPTOR` command to interrogate the select-list descriptor to find the value of each column in the current row.
+12. Use a `CLOSE CURSOR` statement to close the cursor and free any cursor resources.
+
+## Descriptor attributes
+
+A descriptor can contain these attributes.
+
+| Field                     | Type  | Attribute description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ----------------------------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `CARDINALITY`                 | `integer` | The number of rows in the result set.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `DATA`                        | N/A       | The data value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `DATETIME_INTERVAL_CODE`      | `integer` | If `TYPE` is `9`: <br />  <br /> `1 - DATE`   <br />   <br />   `2 - TIME`   <br />   <br />   `3 - TIMESTAMP`   <br />   <br />   `4 - TIME WITH TIMEZONE`   <br />   <br />   `5 - TIMESTAMP WITH TIMEZONE`                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `DATETIME_INTERVAL_PRECISION` | `integer` | Unused.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `INDICATOR`                   | `integer` | Indicates a `NULL` or truncated value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `KEY_MEMBER`                  | `integer` | Unused (returns `FALSE`).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `LENGTH`                      | `integer` | The data length (as stored on server).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `NAME`                        | `string`  | The name of the column in which the data resides.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| `NULLABLE`                    | `integer` | Unused (returns `TRUE`).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `OCTET_LENGTH`                | `integer` | The data length (in bytes) as stored on server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `PRECISION`                   | `integer` | The data precision (if the data is of `numeric` type).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `RETURNED_LENGTH`             | `integer` | Actual length of data item.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `RETURNED_OCTET_LENGTH`       | `integer` | Actual length of data item.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `SCALE`                       | `integer` | The data scale (if the data is of `numeric` type).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `TYPE`                        | `integer` | A numeric code that represents the data type of the column: <br />  <br /> `1 - SQL3_CHARACTER`  <br />  <br />  `2 - SQL3_NUMERIC`  <br />  <br />  `3 - SQL3_DECIMAL`  <br />  <br />  `4 - SQL3_INTEGER`  <br />  <br />  `5 - SQL3_SMALLINT`  <br />  <br />  `6 - SQL3_FLOAT`  <br />  <br />  `7 - SQL3_REAL`  <br />  <br />  `8 - SQL3_DOUBLE_PRECISION`  <br />  <br />  `9 - SQL3_DATE_TIME_TIMESTAMP`  <br />  <br />  `10 - SQL3_INTERVAL`  <br />  <br />  `12 - SQL3_CHARACTER_VARYING`  <br />  <br />  `13 - SQL3_ENUMERATED`  <br />  <br />  `14 - SQL3_BIT`  <br />  <br />  `15 - SQL3_BIT_VARYING`  <br />  <br />  `16 - SQL3_BOOLEAN` |
+
+## Example: Using a descriptor to return data
+
+The following simple application executes an SQL statement entered by an end user. The code sample shows:
+
+-   How to use a SQL descriptor to execute a `SELECT` statement.
+-   How to find the data and metadata returned by the statement.
+
+The application accepts an SQL statement from an end user, tests the statement to see if it includes the `SELECT` keyword, and executes the statement.
+
+### Using a SQL descriptor to execute a `SELECT` statement
+
+When invoking the application, an end user must provide the name of the database on which to perform the SQL statement and a string that contains the text of the query.
+
+For example, a user might invoke the sample with the following command:
+
+```
+./exec_stmt edb "SELECT * FROM emp"
+```
+
+Sample Program:
+```c
+/************************************************************
+ * exec_stmt.pgc
+ *
+ */
+
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql3types.h>
+#include <sqlca.h>
+
+EXEC SQL WHENEVER SQLERROR SQLPRINT;
+static void print_meta_data( char * desc_name );
+
+char *md1 = "col field                data              ret";
+char *md2 = "num name                 type              len";
+char *md3 = "--- -------------------- ----------------- ---";
+
+int main( int argc, char *argv[] )
+{
+
+  EXEC SQL BEGIN DECLARE SECTION;
+    char  *db   = argv[1];
+    char  *stmt = argv[2];
+    int    col_count;
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL CONNECT TO :db;
+
+  EXEC SQL ALLOCATE DESCRIPTOR parse_desc;
+  EXEC SQL PREPARE query FROM :stmt;
+  EXEC SQL DESCRIBE query INTO SQL DESCRIPTOR parse_desc;
+  EXEC SQL GET DESCRIPTOR parse_desc :col_count = COUNT;
+
+if( col_count == 0 )
+{
+    EXEC SQL EXECUTE IMMEDIATE :stmt;
+
+    if( sqlca.sqlcode >= 0 )
+      EXEC SQL COMMIT;
+}
+else
+{
+    int row;
+
+    EXEC SQL ALLOCATE DESCRIPTOR row_desc;
+    EXEC SQL DECLARE my_cursor CURSOR FOR query;
+    EXEC SQL OPEN my_cursor;
+
+    for( row = 0; ; row++ )
+    {
+       EXEC SQL BEGIN DECLARE SECTION;
+         int     col;
+       EXEC SQL END DECLARE SECTION;
+       EXEC SQL FETCH IN my_cursor
+         INTO SQL DESCRIPTOR row_desc;
+
+       if( sqlca.sqlcode != 0 )
+          break;
+
+       if( row == 0 )
+          print_meta_data( "row_desc" );
+
+       printf("[RECORD %d]\n", row+1);
+
+       for( col = 1; col <= col_count; col++ )
+       {
+           EXEC SQL BEGIN DECLARE SECTION;
+             short   ind;
+             varchar val[40+1];
+             varchar name[20+1];
+           EXEC SQL END DECLARE SECTION;
+
+           EXEC SQL GET DESCRIPTOR row_desc
+             VALUE :col
+             :val = DATA, :ind = INDICATOR, :name = NAME;
+
+           if( ind == -1 )
+             printf( "  %-20s : <null>\n", name.arr );
+           else if( ind > 0 )
+             printf( "  %-20s : <truncated>\n", name.arr );
+           else
+             printf( "  %-20s : %s\n", name.arr, val.arr );
+       }
+
+       printf( "\n" );
+
+    }
+    printf( "%d rows\n", row );
+}
+
+exit( 0 );
+}
+
+static void print_meta_data( char *desc_name )
+{
+   EXEC SQL BEGIN DECLARE SECTION;
+     char  *desc = desc_name;
+     int    col_count;
+     int    col;
+   EXEC SQL END DECLARE SECTION;
+
+static char *types[] =
+{
+  "unused           ",
+  "CHARACTER        ",
+  "NUMERIC          ",
+  "DECIMAL          ",
+  "INTEGER          ",
+  "SMALLINT         ",
+  "FLOAT            ",
+  "REAL             ",
+  "DOUBLE           ",
+  "DATE_TIME        ",
+  "INTERVAL         ",
+  "unused           ",
+  "CHARACTER_VARYING",
+  "ENUMERATED       ",
+  "BIT              ",
+  "BIT_VARYING      ",
+  "BOOLEAN          ",
+  "abstract         "
+};
+
+EXEC SQL GET DESCRIPTOR :desc :col_count = count;
+
+
+printf( "%s\n", md1 );
+printf( "%s\n", md2 );
+printf( "%s\n", md3 );
+
+for( col = 1; col <= col_count; col++ )
+{
+
+   EXEC SQL BEGIN DECLARE SECTION;
+     int     type;
+     int     ret_len;
+     varchar name[21];
+   EXEC SQL END DECLARE SECTION;
+   char *type_name;
+
+   EXEC SQL GET DESCRIPTOR :desc
+     VALUE :col
+     :name = NAME,
+     :type = TYPE,
+     :ret_len = RETURNED_OCTET_LENGTH;
+
+   if( type > 0 && type < SQL3_abstract )
+     type_name = types[type];
+   else
+     type_name = "unknown";
+
+   printf( "%02d: %-20s %-17s %04d\n",
+     col, name.arr, type_name, ret_len );
+}
+printf( "\n" );
+}
+
+/************************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio` and `stdlib` libraries, SQL data type symbols, and the `SQLCA` (SQL communications area) structure:
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include <sql3types.h>
+#include <sqlca.h>
+```
+
+The sample provides minimal error handling. When the application encounters a SQL error, it prints the error message to screen:
+
+```sql
+EXEC SQL WHENEVER SQLERROR SQLPRINT;
+```
+
+### Finding the data and metadata returned by the statement
+
+The application includes a forward-declaration for a function named `print_meta_data()` that prints the metadata found in a descriptor:
+
+```c
+static void print_meta_data( char * desc_name );
+```
+
+The following code specifies the column header information that the application uses when printing the metadata:
+
+```c
+char *md1 = "col field data ret";
+char *md2 = "num name type len";
+char *md3 = "--- -------------------- ----------------- ---";
+
+int main( int argc, char *argv[] )
+{
+```
+
+The following declaration section identifies the host variables to contain the name of the database the application connects to, the content of the SQL statement, and a host variable for the number of columns in the result set (if any).
+
+```sql
+EXEC SQL BEGIN DECLARE SECTION;
+  char *db = argv[1];
+  char *stmt = argv[2];
+  int col_count;
+EXEC SQL END DECLARE SECTION;
+```
+
+The application connects to the database using the default credentials:
+
+```sql
+EXEC SQL CONNECT TO :db;
+```
+
+Next, the application allocates a SQL descriptor to hold the metadata for a statement:
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR parse_desc;
+```
+
+The application uses a `PREPARE` statement to check the syntax of the string provided by the user:
+
+```sql
+EXEC SQL PREPARE query FROM :stmt;
+```
+
+It also uses a `DESCRIBE` statement to move the metadata for the query into the SQL descriptor.
+
+```sql
+EXEC SQL DESCRIBE query INTO SQL DESCRIPTOR parse_desc;
+```
+
+Then, the application interrogates the descriptor to discover the number of columns in the result set and stores that in the host variable `col_count`.
+
+```sql
+EXEC SQL GET DESCRIPTOR parse_desc :col_count = COUNT;
+```
+
+If the column count is zero, the end user didn't enter a `SELECT` statement. The application uses an `EXECUTE IMMEDIATE` statement to process the contents of the statement:
+
+```c
+if( col_count == 0 )
+{
+   EXEC SQL EXECUTE IMMEDIATE :stmt;
+```
+
+If the statement executes successfully, the application performs a `COMMIT`:
+
+```c
+if( sqlca.sqlcode >= 0 )
+  EXEC SQL COMMIT;
+}
+else
+{
+```
+
+If the statement entered by the user is a `SELECT` statement (which we know because the column count is non-zero), the application declares a variable named `row`:
+
+```c
+int row;
+```
+
+Then, the application allocates another descriptor that holds the description and the values of a specific row in the result set:
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR row_desc;
+```
+
+The application declares and opens a cursor for the prepared statement:
+
+```sql
+EXEC SQL DECLARE my_cursor CURSOR FOR query;
+EXEC SQL OPEN my_cursor;
+```
+
+It loops through the rows in the result set:
+
+```c
+for( row = 0; ; row++ )
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    int col;
+  EXEC SQL END DECLARE SECTION;
+```
+
+Then, it uses a `FETCH` to retrieve the next row from the cursor into the descriptor:
+
+```sql
+EXEC SQL FETCH IN my_cursor INTO SQL DESCRIPTOR row_desc;
+```
+
+The application confirms that the `FETCH` didn't fail. If the `FETCH` fails, the application reached the end of the result set and breaks the loop:
+
+```c
+if( sqlca.sqlcode != 0 )
+   break;
+```
+
+The application checks to see if this is the first row of the cursor. If it is, the application prints the metadata for the row:
+
+```c
+if( row == 0 )
+   print_meta_data( "row_desc" );
+```
+
+Next, it prints a record header containing the row number:
+
+```c
+printf("[RECORD %d]\n", row+1);
+```
+
+Then, it loops through each column in the row:
+
+```c
+for( col = 1; col <= col_count; col++ )
+{
+   EXEC SQL BEGIN DECLARE SECTION;
+     short ind;
+     varchar val[40+1];
+     varchar name[20+1];
+   EXEC SQL END DECLARE SECTION;
+```
+
+The application interrogates the row descriptor `(row_desc)` to copy the column value `:val`, null indicator `:ind`, and column name `:name` into the host variables declared earlier. You can retrieve multiple items from a descriptor using a comma-separated list:
+
+```sql
+EXEC SQL GET DESCRIPTOR row_desc
+  VALUE :col
+  :val = DATA, :ind = INDICATOR, :name = NAME;
+```
+
+If the null indicator (`ind`) is negative, the column value is `NULL`. If the null indicator is greater than `0`, the column value is too long to fit into the val host variable, so we print `<truncated>`. Otherwise, the null indicator is `0`, meaning `NOT NULL`, so we print the value. In each case, we prefix the value (or `<null>` or `<truncated>`) with the name of the column.
+
+```c
+if( ind == -1 )
+  printf( " %-20s : <null>\n", name.arr );
+else if( ind > 0 )
+  printf( " %-20s : <truncated>\n", name.arr );
+else
+  printf( " %-20s : %s\n", name.arr, val.arr );
+}
+
+printf( "\n" );
+}
+```
+
+When the loop terminates, the application prints the number of rows fetched and exits:
+
+```c
+   printf( "%d rows\n", row );
+  }
+
+exit( 0 );
+}
+```
+
+The `print_meta_data()` function extracts the metadata from a descriptor and prints the name, data type, and length of each column:
+
+```c
+static void print_meta_data( char *desc_name )
+{
+```
+
+The application declares host variables:
+
+```sql
+EXEC SQL BEGIN DECLARE SECTION;
+  char *desc = desc_name;
+  int col_count;
+  int col;
+EXEC SQL END DECLARE SECTION;
+```
+
+The application then defines an array of character strings that map data type values (`numeric`) into data type names. We use the numeric value found in the descriptor to index into this array. For example, if we find that a given column is of type `2`, we can find the name of that type (`NUMERIC`) by writing `types[2]`.
+
+```c
+static char *types[] =
+{
+  "unused ",
+  "CHARACTER ",
+  "NUMERIC ",
+  "DECIMAL ",
+  "INTEGER ",
+  "SMALLINT ",
+  "FLOAT ",
+  "REAL ",
+  "DOUBLE ",
+  "DATE_TIME ",
+  "INTERVAL ",
+  "unused ",
+  "CHARACTER_VARYING",
+  "ENUMERATED ",
+  "BIT ",
+  "BIT_VARYING ",
+  "BOOLEAN ",
+  "abstract "
+};
+```
+
+The application retrieves the column count from the descriptor. The program refers to the descriptor using a host variable (`desc`) that contains the name of the descriptor. In most scenarios, you use an identifier to refer to a descriptor. In this case, the caller provided the descriptor name, so we can use a host variable to refer to the descriptor.
+
+```sql
+EXEC SQL GET DESCRIPTOR :desc :col_count = count;
+```
+
+The application prints the column headers defined at the beginning of this application:
+
+```c
+printf( "%s\n", md1 );
+printf( "%s\n", md2 );
+printf( "%s\n", md3 );
+```
+
+Then, it loops through each column found in the descriptor and prints the name, type, and length of each column.
+
+```c
+for( col = 1; col <= col_count; col++ )
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    int type;
+    int ret_len;
+    varchar name[21];
+  EXEC SQL END DECLARE SECTION;
+  char *type_name;
+```
+
+It retrieves the name, type code, and length of the current column:
+
+```sql
+EXEC SQL GET DESCRIPTOR :desc
+ VALUE :col
+ :name = NAME,
+ :type = TYPE,
+ :ret_len = RETURNED_OCTET_LENGTH;
+```
+
+If the numeric type code matches a 'known' type code (that is, a type code found in the `types[]` array), it sets `type_name` to the name of the corresponding type. Otherwise, it sets `type_name` to `"unknown"`:
+
+```c
+if( type > 0 && type < SQL3_abstract )
+  type_name = types[type];
+else
+  type_name = "unknown";
+```
+
+It then prints the column number, name, type name, and length:
+
+```c
+   printf( "%02d: %-20s %-17s %04d\n",
+     col, name.arr, type_name, ret_len );
+  }
+  printf( "\n" );
+}
+```
+
+Invoke the sample application with the following command:
+
+```c
+./exec_stmt test "SELECT * FROM emp WHERE empno IN(7902, 7934)"
+```
+
+The application returns:
+
+```sql
+__OUTPUT__
+col field                data              ret
+num name                 type              len
+--- -------------------- ----------------- ---
+01: empno                NUMERIC           0004
+02: ename                CHARACTER_VARYING 0004
+03: job                  CHARACTER_VARYING 0007
+04: mgr                  NUMERIC           0004
+05: hiredate             DATE_TIME         0018
+06: sal                  NUMERIC           0007
+07: comm                 NUMERIC           0000
+08: deptno               NUMERIC           0002
+
+[RECORD 1]
+  empno                : 7902
+  ename                : FORD
+  job                  : ANALYST
+  mgr                  : 7566
+  hiredate             : 03-DEC-81 00:00:00
+  sal                  : 3000.00
+  comm                 : <null>
+  deptno               : 20
+
+[RECORD 2]
+  empno                : 7934
+  ename                : MILLER
+  job                  : CLERK
+  mgr                  : 7782
+  hiredate             : 23-JAN-82 00:00:00
+  sal                  : 1300.00
+  comm                 : <null>
+  deptno               : 10
+
+2 rows
+```
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx
new file mode 100644
index 00000000000..2866085e93d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements.mdx
@@ -0,0 +1,812 @@
+---
+title: "Building and executing dynamic SQL statements"
+description: "Outlines four techniques for building and executing dynamic SQL statements"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.18.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.15.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.17.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.16.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.19.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/05_building_executing_dynamic_sql_statements/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="building_executing_dynamic_sql_statements" class="registered_link"></div>
+
+The following examples show four techniques for building and executing dynamic SQL statements. Each example shows processing a different combination of statement and input types:
+
+-   The [first example](#executing_a_nonquery_statement_without_parameters) shows processing and executing a SQL statement that doesn't contain a `SELECT` statement and doesn't require input variables. This example corresponds to the techniques used by Oracle Dynamic SQL Method 1.
+-   The [second example](#executing_a_nonquery_statement_with_a_specified_number_of_placeholders) shows processing and executing a SQL statement that doesn't contain a `SELECT` statement and contains a known number of input variables. This example corresponds to the techniques used by Oracle Dynamic SQL Method 2.
+-   The [third example](#executing_a_query_statement_with_known_number_of_placeholders) shows processing and executing a SQL statement that might contain a `SELECT` statement and includes a known number of input variables. This example corresponds to the techniques used by Oracle Dynamic SQL Method 3.
+-   The [fourth example](#executing_query_with_unknown_number_of_variables) shows processing and executing a SQL statement that might contain a `SELECT` statement and includes an unknown number of input variables. This example corresponds to the techniques used by Oracle Dynamic SQL Method 4.
+
+<div id="executing_a_nonquery_statement_without_parameters" class="registered_link"></div>
+
+## Example: Executing a nonquery statement without parameters
+
+This example shows how to use the `EXECUTE IMMEDIATE` command to execute a SQL statement, where the text of the statement isn't known until you run the application. You can't use `EXECUTE IMMEDIATE` to execute a statement that returns a result set. You can't use `EXECUTE IMMEDIATE` to execute a statement that contains parameter placeholders.
+
+The `EXECUTE IMMEDIATE` statement parses and plans the SQL statement each time it executes, which can have a negative impact on the performance of your application. If you plan to execute the same statement repeatedly, consider using the `PREPARE/EXECUTE` technique described in [Example: Executing a nonquery statement with a specified number of placeholders](#example-executing-a-nonquery-statement-with-a-specified-number-of-placeholders).
+
+```c
+/***********************************************************/
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+
+static void handle_error(void);
+
+int main(int argc, char *argv[])
+{
+  char    *insertStmt;
+
+  EXEC SQL WHENEVER SQLERROR DO handle_error();
+
+  EXEC SQL CONNECT :argv[1];
+
+  insertStmt = "INSERT INTO dept VALUES(50, 'ACCTG', 'SEATTLE')";
+
+  EXEC SQL EXECUTE IMMEDIATE :insertStmt;
+
+  fprintf(stderr, "ok\n");
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+
+
+static void handle_error(void)
+{
+  fprintf(stderr, "%s\n", sqlca.sqlerrm.sqlerrmc);
+
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+
+  exit(EXIT_FAILURE);
+}
+
+/***********************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio`, `string`, and `stdlib` libraries and providing basic infrastructure for the program:
+
+```c
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+
+static void handle_error(void);
+int main(int argc, char *argv[])
+{
+  char *insertStmt;
+```
+
+The example then sets up an error handler. ECPGPlus calls the `handle_error()` function whenever a SQL error occurs:
+
+```sql
+EXEC SQL WHENEVER SQLERROR DO handle_error();
+```
+
+Then, the example connects to the database using the credentials specified on the command line:
+
+```sql
+EXEC SQL CONNECT :argv[1];
+```
+
+Next, the program uses an `EXECUTE IMMEDIATE` statement to execute a SQL statement, adding a row to the `dept` table:
+
+```c
+insertStmt = "INSERT INTO dept VALUES(50, 'ACCTG', 'SEATTLE')";
+
+EXEC SQL EXECUTE IMMEDIATE :insertStmt;
+```
+
+If the `EXECUTE IMMEDIATE` command fails, ECPGPlus invokes the `handle_error()` function, which terminates the application after displaying an error message to the user. If the `EXECUTE IMMEDIATE` command succeeds, the application displays a message (`ok`) to the user, commits the changes, disconnects from the server, and terminates the application:
+
+```c
+  fprintf(stderr, "ok\n");
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+```
+
+ECPGPlus calls the `handle_error()` function whenever it encounters a SQL error. The `handle_error()` function prints the content of the error message, resets the error handler, rolls back any changes, disconnects from the database, and terminates the application:
+
+```c
+static void handle_error(void)
+{
+  fprintf(stderr, "%s\n", sqlca.sqlerrm.sqlerrmc);
+
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+
+  exit(EXIT_FAILURE);
+}
+```
+
+<div id="executing_a_nonquery_statement_with_a_specified_number_of_placeholders" class="registered_link"></div>
+
+## Example: Executing a nonquery statement with a specified number of placeholders
+
+To execute a nonquery command that includes a known number of parameter placeholders, you must first `PREPARE` the statement (providing a *statement handle*) and then `EXECUTE` the statement using the statement handle. When the application executes the statement, it must provide a value for each placeholder found in the statement.
+
+When an application uses the `PREPARE/EXECUTE` mechanism, each SQL statement is parsed and planned once but might execute many times, providing different values each time.
+
+ECPGPlus converts each parameter value to the type required by the SQL statement, if possible. Otherwise, ECPGPlus reports an error.
+
+```c
+/***********************************************************/
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+#include <sqlca.h>
+
+static void handle_error(void);
+
+int main(int argc, char *argv[])
+{
+  char *stmtText;
+
+  EXEC SQL WHENEVER SQLERROR DO handle_error();
+
+  EXEC SQL CONNECT :argv[1];
+
+  stmtText = "INSERT INTO dept VALUES(?, ?, ?)";
+
+  EXEC SQL PREPARE stmtHandle FROM :stmtText;
+
+  EXEC SQL EXECUTE stmtHandle USING :argv[2], :argv[3], :argv[4];
+
+  fprintf(stderr, "ok\n");
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+
+static void handle_error(void)
+{
+  printf("%s\n", sqlca.sqlerrm.sqlerrmc);
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+
+  exit(EXIT_FAILURE);
+}
+/***********************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio`, `string`, `stdlib`, and `sqlca` libraries and providing basic infrastructure for the program:
+
+```c
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+#include <sqlca.h>
+
+static void handle_error(void);
+
+int main(int argc, char *argv[])
+{
+  char *stmtText;
+```
+
+The example then sets up an error handler. ECPGPlus calls the `handle_error()` function whenever a SQL error occurs.
+
+```sql
+EXEC SQL WHENEVER SQLERROR DO handle_error();
+```
+
+Then, the example connects to the database using the credentials specified on the command line:
+
+```sql
+EXEC SQL CONNECT :argv[1];
+```
+
+Next, the program uses a `PREPARE` statement to parse and plan a statement that includes three parameter markers. If the `PREPARE` statement succeeds, it creates a statement handle that you can use to execute the statement. (In this example, the statement handle is named `stmtHandle`.) You can execute a given statement multiple times using the same statement handle.
+
+```sql
+stmtText = "INSERT INTO dept VALUES(?, ?, ?)";
+
+EXEC SQL PREPARE stmtHandle FROM :stmtText;
+```
+
+After parsing and planning the statement, the application uses the `EXECUTE` statement to execute the statement associated with the statement handle, substituting user-provided values for the parameter markers:
+
+```sql
+EXEC SQL EXECUTE stmtHandle USING :argv[2], :argv[3], :argv[4];
+```
+
+If the `EXECUTE` command fails, ECPGPlus invokes the `handle_error()` function, which terminates the application after displaying an error message to the user. If the `EXECUTE` command succeeds, the application displays a message (`ok`) to the user, commits the changes, disconnects from the server, and terminates the application:
+
+```c
+  fprintf(stderr, "ok\n");
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+```
+
+ECPGPlus calls the `handle_error()` function whenever it encounters a SQL error. The `handle_error()` function prints the content of the error message, resets the error handler, rolls back any changes, disconnects from the database, and terminates the application:
+
+```c
+static void handle_error(void)
+{
+  printf("%s\n", sqlca.sqlerrm.sqlerrmc);
+
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+  exit(EXIT_FAILURE);
+}
+```
+<div id="executing_a_query_statement_with_known_number_of_placeholders" class="registered_link"></div>
+
+## Example: Executing a query with a known number of placeholders
+
+This example shows how to execute a query with a known number of input parameters and with a known number of columns in the result set. This method uses the `PREPARE` statement to parse and plan a query and then opens a cursor and iterates through the result set.
+
+```c
+/***********************************************************/
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+#include <stdbool.h>
+#include <sqlca.h>
+
+static void handle_error(void);
+
+int main(int argc, char *argv[])
+{
+  VARCHAR  empno[10];
+  VARCHAR  ename[20];
+
+  EXEC SQL WHENEVER SQLERROR DO handle_error();
+
+  EXEC SQL CONNECT :argv[1];
+
+  EXEC SQL PREPARE queryHandle
+    FROM "SELECT empno, ename FROM emp WHERE deptno = ?";
+
+  EXEC SQL DECLARE empCursor CURSOR FOR queryHandle;
+
+  EXEC SQL OPEN empCursor USING :argv[2];
+
+  EXEC SQL WHENEVER NOT FOUND DO break;
+
+  while(true)
+  {
+
+    EXEC SQL FETCH empCursor INTO :empno, :ename;
+
+    printf("%-10s %s\n", empno.arr, ename.arr);
+  }
+
+  EXEC SQL CLOSE empCursor;
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+
+static void handle_error(void)
+{
+  printf("%s\n", sqlca.sqlerrm.sqlerrmc);
+
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+
+  exit(EXIT_FAILURE);
+}
+
+/***********************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio`, `string`, `stdlib`, `stdbool`, and `sqlca` libraries and providing basic infrastructure for the program:
+
+```c
+#include <stdio.h>
+#include <string.h>
+#include <stdlib.h>
+#include <stdbool.h>
+#include <sqlca.h>
+
+static void handle_error(void);
+
+int main(int argc, char *argv[])
+{
+  VARCHAR empno[10];
+  VARCHAR ename[20];
+```
+
+The example then sets up an error handler. ECPGPlus calls the `handle_error()` function whenever a SQL error occurs:
+
+```sql
+EXEC SQL WHENEVER SQLERROR DO handle_error();
+```
+
+Then, the example connects to the database using the credentials specified on the command line:
+
+```sql
+EXEC SQL CONNECT :argv[1];
+```
+
+Next, the program uses a `PREPARE` statement to parse and plan a query that includes a single parameter marker. If the `PREPARE` statement succeeds, it creates a statement handle that you can use to execute the statement. (In this example, the statement handle is named `stmtHandle`.) You can execute a given statement multiple times using the same statement handle.
+
+```sql
+EXEC SQL PREPARE stmtHandle
+  FROM "SELECT empno, ename FROM emp WHERE deptno = ?";
+```
+
+The program then declares and opens the cursor `empCursor`, substituting a user-provided value for the parameter marker in the prepared `SELECT` statement. The `OPEN` statement includes a `USING` clause, which must provide a value for each placeholder found in the query:
+
+```sql
+EXEC SQL DECLARE empCursor CURSOR FOR stmtHandle;
+
+EXEC SQL OPEN empCursor USING :argv[2];
+
+EXEC SQL WHENEVER NOT FOUND DO break;
+
+while(true)
+{
+```
+
+The program iterates through the cursor and prints the employee number and name of each employee in the selected department:
+
+```sql
+  EXEC SQL FETCH empCursor INTO :empno, :ename;
+
+  printf("%-10s %s\n", empno.arr, ename.arr);
+}
+```
+
+The program then closes the cursor, commits any changes, disconnects from the server, and terminates the application:
+
+```sql
+  EXEC SQL CLOSE empCursor;
+
+  EXEC SQL COMMIT RELEASE;
+
+  exit(EXIT_SUCCESS);
+}
+```
+
+The application calls the `handle_error()` function whenever it encounters a SQL error. The `handle_error()` function prints the content of the error message, resets the error handler, rolls back any changes, disconnects from the database, and terminates the application:
+
+```c
+static void handle_error(void)
+{
+  printf("%s\n", sqlca.sqlerrm.sqlerrmc);
+
+  EXEC SQL WHENEVER SQLERROR CONTINUE;
+  EXEC SQL ROLLBACK RELEASE;
+
+  exit(EXIT_FAILURE);
+}
+```
+
+<div id="executing_query_with_unknown_number_of_variables" class="registered_link"></div>
+
+## Example: Executing a query with an unknown number of variables
+
+This example shows executing a query with an unknown number of input parameters or columns in the result set. This type of query might occur when you prompt the user for the text of the query or when a query is assembled from a form on which the user chooses from a number of conditions (i.e., a filter).
+
+```c
+/***********************************************************/
+#include <stdio.h>
+#include <stdlib.h>
+#include <sqlda.h>
+#include <sqlcpr.h>
+
+SQLDA *params;
+SQLDA *results;
+
+static void allocateDescriptors(int count,
+                                int varNameLength,
+                                int indNameLenth);
+static void bindParams(void);
+static void displayResultSet(void);
+
+int main(int argc, char *argv[])
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    char   *username = argv[1];
+    char   *password = argv[2];
+    char   *stmtText = argv[3];
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL WHENEVER SQLERROR sqlprint;
+
+  EXEC SQL CONNECT TO test
+    USER :username
+    IDENTIFIED BY :password;
+
+  params  = sqlald(20, 64, 64);
+  results = sqlald(20, 64, 64);
+
+  EXEC SQL PREPARE stmt FROM :stmtText;
+
+  EXEC SQL DECLARE dynCursor CURSOR FOR stmt;
+
+  bindParams();
+
+  EXEC SQL OPEN dynCursor USING DESCRIPTOR params;
+
+  displayResultSet(20);
+}
+
+static void bindParams(void)
+{
+  EXEC SQL DESCRIBE BIND VARIABLES FOR stmt INTO params;
+
+  if (params->F < 0)
+     fprintf(stderr, "Too many parameters required\n");
+  else
+  {
+     int i;
+
+     params->N = params->F;
+
+     for (i = 0; i < params->F; i++)
+     {
+       char *paramName = params->S[i];
+       int   nameLen   = params->C[i];
+       char  paramValue[255];
+
+       printf("Enter value for parameter %.*s: ",
+               nameLen, paramName);
+
+       fgets(paramValue, sizeof(paramValue), stdin);
+
+       params->T[i] = 1;     /* Data type = Character (1) */
+       params->L[i] = strlen(paramValue) - 1;
+       params->V[i] = strdup(paramValue);
+     }
+  }
+}
+
+static void displayResultSet(void)
+{
+  EXEC SQL DESCRIBE SELECT LIST FOR stmt INTO results;
+
+  if (results->F < 0)
+     fprintf(stderr, "Too many columns returned by query\n");
+  else if (results->F == 0)
+     return;
+  else
+  {
+     int col;
+
+     results->N = results->F;
+
+     for (col = 0; col < results->F; col++)
+     {
+       int null_permitted, length;
+
+       sqlnul(&results->T[col],
+              &results->T[col],
+              &null_permitted);
+
+       switch (results->T[col])
+       {
+          case 2:        /* NUMERIC */
+          {
+            int precision, scale;
+
+            sqlprc(&results->L[col], &precision, &scale);
+
+            if (precision == 0)
+               precision = 38;
+
+            length = precision + 3;
+            break;
+           }
+
+          case 12:   /* DATE */
+          {
+            length = 30;
+            break;
+          }
+
+          default:   /* Others */
+          {
+            length = results->L[col] + 1;
+            break;
+          }
+       }
+
+       results->V[col] = realloc(results->V[col], length);
+       results->L[col] = length;
+       results->T[col] = 1;
+     }
+
+     EXEC SQL WHENEVER NOT FOUND DO break;
+
+     while (1)
+     {
+       const char *delimiter = "";
+
+       EXEC SQL FETCH dynCursor USING DESCRIPTOR results;
+
+       for (col = 0; col < results->F; col++)
+       {
+          if (*results->I[col] == -1)
+            printf("%s%s", delimiter, "<null>");
+          else
+            printf("%s%s", delimiter, results->V[col]);
+          delimiter = ", ";
+       }
+
+
+ printf("\n");
+      }
+  }
+}
+/***********************************************************/
+```
+
+The code sample begins by including the prototypes and type definitions for the C `stdio` and `stdlib` libraries. In addition, the program includes the `sqlda.h` and `sqlcpr.h` header files. `sqlda.h` defines the SQLDA structure used throughout this example. `sqlcpr.h` defines a small set of functions used to interrogate the metadata found in an SQLDA structure.
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include <sqlda.h>
+#include <sqlcpr.h>
+```
+
+Next, the program declares pointers to two SQLDA structures. The first SQLDA structure (`params`) is used to describe the metadata for any parameter markers found in the dynamic query text. The second SQLDA structure (`results`) contains both the metadata and the result set obtained by executing the dynamic query.
+
+```sql
+SQLDA *params;
+SQLDA *results;
+```
+
+The program then declares two helper functions, which are defined near the end of the code sample:
+
+```c
+static void bindParams(void);
+static void displayResultSet(void);
+```
+
+Next, the program declares three host variables. The first two (`username` and `password`) are used to connect to the database server. The third host variable (`stmtTxt`) is a NULL-terminated C string containing the text of the query to execute. The values for these three host variables are derived from the command-line arguments. When the program begins to execute, it sets up an error handler and then connects to the database server:
+
+```c
+int main(int argc, char *argv[])
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    char *username = argv[1];
+    char *password = argv[2];
+    char *stmtText = argv[3];
+  EXEC SQL END DECLARE SECTION;
+
+  EXEC SQL WHENEVER SQLERROR sqlprint;
+  EXEC SQL CONNECT TO test
+    USER :username
+    IDENTIFIED BY :password;
+```
+
+Next, the program calls the `sqlald()` function to allocate the memory required for each descriptor. Each descriptor contains pointers to arrays of:
+
+-   Column names
+-   Indicator names
+-   Data types
+-   Lengths
+-   Data values
+
+When you allocate an `SQLDA` descriptor, you specify the maximum number of columns you expect to find in the result set (for `SELECT`-list descriptors) or the maximum number of parameters you expect to find the dynamic query text (for bind-variable descriptors). In this case, we specify that we expect no more than 20 columns and 20 parameters. You must also specify a maximum length for each column or parameter name and each indicator variable name. In this case, we expect names to be no more than 64 bytes long.
+
+See [SQLDA structure](/epas/latest/reference/application_programmer_reference/07_reference/) for a complete description of the `SQLDA` structure.
+
+```c
+params = sqlald(20, 64, 64);
+results = sqlald(20, 64, 64);
+```
+
+After allocating the `SELECT`-list and bind descriptors, the program prepares the dynamic statement and declares a cursor over the result set.
+
+```sql
+EXEC SQL PREPARE stmt FROM :stmtText;
+
+EXEC SQL DECLARE dynCursor CURSOR FOR stmt;
+```
+
+Next, the program calls the `bindParams()` function. The `bindParams()` function examines the bind descriptor `(params)` and prompts the user for a value to substitute in place of each parameter marker found in the dynamic query.
+
+```c
+bindParams();
+```
+
+Finally, the program opens the cursor (using any parameter values supplied by the user) and calls the `displayResultSet()` function to print the result set produced by the query:
+
+```sql
+EXEC SQL OPEN dynCursor USING DESCRIPTOR params;
+
+displayResultSet();
+}
+```
+
+The `bindParams()` function determines whether the dynamic query contains any parameter markers. If so, it prompts the user for a value for each parameter and then binds that value to the corresponding marker. The `DESCRIBE BIND VARIABLE` statement populates the `params` SQLDA structure with information describing each parameter marker:
+
+```c
+static void bindParams(void)
+{
+  EXEC SQL DESCRIBE BIND VARIABLES FOR stmt INTO params;
+```
+
+If the statement contains no parameter markers, `params->F` contains 0. If the statement contains more parameters than fit into the descriptor, `params->F` contains a negative number. In this case, the absolute value of `params->F` indicates the number of parameter markers found in the statement. If `params->F` contains a positive number, that number indicates how many parameter markers were found in the statement.
+
+```c
+if (params->F < 0)
+   fprintf(stderr, "Too many parameters required\n");
+else
+{
+   int i;
+
+   params->N = params->F;
+```
+
+Next, the program executes a loop that prompts the user for a value, iterating once for each parameter marker found in the statement:
+
+```c
+for (i = 0; i < params->F; i++)
+{
+  char *paramName = params->S[i];
+  int nameLen = params->C[i];
+  char paramValue[255];
+
+  printf("Enter value for parameter %.*s: ",
+          nameLen, paramName);
+
+  fgets(paramValue, sizeof(paramValue), stdin);
+```
+
+After prompting the user for a value for a given parameter, the program binds that value to the parameter by setting:
+
+-  `params->T[i]` to indicate the data type of the value
+-  `params->L[i]` to the length of the value (we subtract one to trim off the trailing new-line character added by `fgets()`)
+-  `params->V[i]` to point to a copy of the NULL-terminated string provided by the user
+
+```c
+     params->T[i] = 1;        /* Data type = Character (1) */
+     params->L[i] = strlen(paramValue) + 1;
+     params->V[i] = strdup(paramValue);
+    }
+  }
+}
+```
+
+The `displayResultSet()` function loops through each row in the result set and prints the value found in each column. `displayResultSet()` starts by executing a `DESCRIBE SELECT LIST` statement. This statement populates an SQLDA descriptor (`results`) with a description of each column in the result set.
+
+```c
+static void displayResultSet(void)
+{
+  EXEC SQL DESCRIBE SELECT LIST FOR stmt INTO results;
+```
+
+If the dynamic statement returns no columns (that is, the dynamic statement is not a `SELECT` statement), `results->F` contains 0. If the statement returns more columns than fit into the descriptor, `results->F` contains a negative number. In this case, the absolute value of `results->F` indicates the number of columns returned by the statement. If `results->F` contains a positive number, that number indicates how many columns were returned by the query.
+
+```c
+if (results->F < 0)
+   fprintf(stderr, "Too many columns returned by query\n");
+else if (results->F == 0)
+   return;
+else
+{
+   int col;
+
+   results->N = results->F;
+```
+
+Next, the program enters a loop, iterating once for each column in the result set:
+
+```c
+for (col = 0; col < results->F; col++)
+{
+  int null_permitted, length;
+```
+
+To decode the type code found in `results->T`, the program invokes the `sqlnul()` function (see the description of the `T` member of the SQLDA structure in the [The SQLDA structure](/epas/latest/reference/application_programmer_reference/07_reference/)). This call to `sqlnul()` modifies `results->T[col]` to contain only the type code (the nullability flag is copied to `null_permitted`). This step is needed because the `DESCRIBE SELECT LIST` statement encodes the type of each column and the nullability of each column into the `T` array.
+
+```c
+sqlnul(&results->T[col],
+       &results->T[col],
+       &null_permitted);
+```
+
+After decoding the actual data type of the column, the program modifies the results descriptor to tell ECPGPlus to return each value in the form of a NULL-terminated string. Before modifying the descriptor, the program must compute the amount of space required to hold each value. To make this computation, the program examines the maximum length of each column `(results->V[col])` and the data type of each column `(results->T[col])`.
+
+For numeric values (where `results->T[col] = 2`), the program calls the `sqlprc()` function to extract the precision and scale from the column length. To compute the number of bytes required to hold a numeric value in string form, `displayResultSet()` starts with the precision (that is, the maximum number of digits) and adds three bytes for a sign character, a decimal point, and a NULL terminator.
+
+```c
+switch (results->T[col])
+{
+   case 2:          /* NUMERIC */
+   {
+     int precision, scale;
+
+     sqlprc(&results->L[col], &precision, &scale);
+
+     if (precision == 0)
+        precision = 38;
+     length = precision + 3;
+     break;
+   }
+```
+
+For date values, the program uses a hard-coded length of 30. In a real-world application, you might want to more carefully compute the amount of space required.
+
+```c
+case 12:     /* DATE */
+{
+  length = 30;
+  break;
+}
+```
+
+For a value of any type other than date or numeric, `displayResultSet()` starts with the maximum column width reported by `DESCRIBE SELECT LIST` and adds one extra byte for the NULL terminator. Again, in a real-world application you might want to include more careful calculations for other data types:
+
+```c
+default:    /* Others */
+{
+  length = results->L[col] + 1;
+  break;
+}
+}
+```
+
+After computing the amount of space required to hold a given column, the program:
+
+-  Allocates enough memory to hold the value
+-  Sets `results->L[col]` to indicate the number of bytes found at `results->V[col]`
+-  Sets the type code for the column `(results->T[col])` to `1` to instruct the upcoming `FETCH` statement to return the value in the form of a NULL-terminated string
+
+```c
+  results->V[col] = malloc(length);
+  results->L[col] = length;
+  results->T[col] = 1;
+}
+```
+
+At this point, the results descriptor is configured such that a `FETCH` statement can copy each value into an appropriately sized buffer in the form of a NULL-terminated string.
+
+Next, the program defines a new error handler to break out of the upcoming loop when the cursor is exhausted.
+
+```sql
+EXEC SQL WHENEVER NOT FOUND DO break;
+
+while (1)
+{
+  const char *delimiter = "";
+```
+
+The program executes a `FETCH` statement to fetch the next row in the cursor into the `results` descriptor. If the `FETCH` statement fails (because the cursor is exhausted), control transfers to the end of the loop because of the `EXEC SQL WHENEVER` directive found before the top of the loop.
+
+ `EXEC SQL FETCH dynCursor USING DESCRIPTOR results;`
+
+The `FETCH` statement populates the following members of the results descriptor:
+
+-   `*results->I[col]` indicates whether the column contains a NULL value `(-1)` or a non-NULL value `(0)`. If the value is non-NULL but too large to fit into the space provided, the value is truncated, and `*results->I[col]` contains a positive value.
+-   `results->V[col]` contains the value fetched for the given column (unless `*results->I[col]` indicates that the column value is NULL).
+-   `results->L[col]` contains the length of the value fetched for the given column.
+
+Finally, `displayResultSet()` iterates through each column in the result set, examines the corresponding NULL indicator, and prints the value. The result set isn't aligned. Instead, each value is separated from the previous value by a comma.
+
+```c
+for (col = 0; col < results->F; col++)
+{
+   if (*results->I[col] == -1)
+     printf("%s%s", delimiter, "<null>");
+   else
+     printf("%s%s", delimiter, results->V[col]);
+   delimiter = ", ";
+}
+
+printf("\n");
+}
+}
+}
+/***********************************************************/
+```
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/06_error_handling.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/06_error_handling.mdx
new file mode 100644
index 00000000000..b4fa22842b3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/06_error_handling.mdx
@@ -0,0 +1,198 @@
+---
+title: "Error handling"
+description: "Outlines the methods for detecting and handling errors in embedded SQL code"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.20.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.21.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.22.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/06_error_handling/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="error_handling" class="registered_link"></div>
+
+ECPGPlus provides two methods to detect and handle errors in embedded SQL code. A client application can:
+
+-   Examine the `sqlca` data structure for error messages and supply customized error handling for your client application.
+-   Include `EXEC SQL WHENEVER` directives to instruct the ECPGPlus compiler to add error-handling code.
+
+## Error handling with sqlca
+
+The SQL communications area (`sqlca`) is a global variable used by `ecpglib` to communicate information from the server to the client application. After executing a SQL statement such as an `INSERT` or `SELECT` statement, you can inspect the contents of `sqlca` to determine if the statement completed successfully or if the statement failed.
+
+`sqlca` has the following structure:
+
+```c
+struct
+{
+    char sqlcaid[8];
+    long sqlabc;
+    long sqlcode;
+    struct
+    {
+        int sqlerrml;
+        char sqlerrmc[SQLERRMC_LEN];
+    } sqlerrm;
+    char sqlerrp[8];
+    long sqlerrd[6];
+    char sqlwarn[8];
+    char sqlstate[5];
+
+} sqlca;
+```
+
+Use the following directive to implement `sqlca` functionality:
+
+```sql
+EXEC SQL INCLUDE sqlca;
+```
+
+If you include the `ecpg` directive, you don't need to `#include` the `sqlca.h` file in the client application's header declaration.
+
+The EDB Postgres Advanced Server `sqlca` structure contains the following members:
+
+-  `sqlcaid` &mdash; Contains the string: `"SQLCA"`.
+
+-  `sqlabc` &mdash; `sqlabc` contains the size of the `sqlca` structure.
+
+-  `sqlcode` &mdash; The `sqlcode` member was deprecated with SQL 92. EDB Postgres Advanced Server supports `sqlcode` for backward compatibility. Use the `sqlstate` member when writing new code.
+
+    `sqlcode` is an integer value. A positive `sqlcode` value indicates that the client application encountered a harmless processing condition. A negative value indicates a warning or error.
+
+    If a statement processes without error, `sqlcode` contains a value of `0`. If the client application encounters an error or warning during a statement's execution, `sqlcode` contains the last code returned.
+
+    The SQL standard defines only a positive value of 100, which indicates that the most recent SQL statement processed returned or affected no rows. Since the SQL standard doesn't define other `sqlcode` values, be aware that the values assigned to each condition can vary from database to database.
+
+`sqlerrm` is a structure embedded in `sqlca`, composed of two members:
+
+-  `sqlerrml` &mdash; Contains the length of the error message currently stored in `sqlerrmc`.
+
+-  `sqlerrmc` &mdash; Contains the null-terminated message text associated with the code stored in `sqlstate`. If a message exceeds 149 characters, `ecpglib` truncates the error message.
+
+-  `sqlerrp` &mdash; Contains the string `"NOT SET"`.
+
+`sqlerrd` is an array that contains six elements:
+
+-   `sqlerrd[1]` &mdash; Contains the OID of the processed row (if applicable).
+
+-   `sqlerrd[2]` &mdash; Contains the number of processed or returned rows.
+
+-   `sqlerrd[0]`, `sqlerrd[3]`, `sqlerrd[4]` and `sqlerrd[5]` are unused.
+
+`sqlwarn` is an array that contains 8 characters:
+
+-   `sqlwarn[0]` &mdash; Contains a value of `'W'` if any other element in `sqlwarn` is set to `'W'`.
+
+-   `sqlwarn[1]` &mdash; Contains a value of `'W'` if a data value was truncated when it was stored in a host variable.
+
+-   `sqlwarn[2]` &mdash; Contains a value of `'W'` if the client application encounters a nonfatal warning.
+
+-   `sqlwarn[3]`, `sqlwarn[4]`, `sqlwarn[5]`, `sqlwarn[6]`, and `sqlwarn[7]` are unused.
+
+`sqlstate` is a five-character array that contains a SQL-compliant status code after the execution of a statement from the client application. If a statement processes without error, `sqlstate` contains a value of `00000`. `sqlstate` isn't a null-terminated string.
+
+`sqlstate` codes are assigned in a hierarchical scheme:
+
+-   The first two characters of `sqlstate` indicate the general class of the condition.
+-   The last three characters of `sqlstate` indicate a specific status within the class.
+
+If the client application encounters multiple errors (or warnings) during an SQL statement's execution, `sqlstate` contains the last code returned.
+
+## List of sqlstate and sqlcode values
+
+The following table lists the `sqlstate` and `sqlcode` values, as well as the symbolic name and error description for the related condition.
+
+| sqlstate            | sqlcode (deprecated) | Symbolic name                   | Description                                                                                                                                                                                                                         |
+| ------------------- | -------------------- | ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `YE001`             | `-12`                | `ECPG_OUT_OF_MEMORY`            | Virtual memory is exhausted.                                                                                                                                                                                                        |
+| `YE002`             | `-200`               | `ECPG_UNSUPPORTED`              | The preprocessor generated an unrecognized item. Might indicate incompatibility between the preprocessor and the library.                                                                                                       |
+| `07001`, or `07002` | `-201`               | `ECPG_TOO_MANY_ARGUMENTS`       | The program specifies more variables than the command expects.                                                                                                                                                                      |
+| `07001`, or `07002` | `-202`               | `ECPG_TOO_FEW_ARGUMENTS`        | The program specified fewer variables than the command expects.                                                                                                                                                                     |
+| `21000`             | `-203`               | `ECPG_TOO_MANY_MATCHES`         | The SQL command returned multiple rows, but the statement was prepared to receive a single row.                                                                                                                                 |
+| `42804`             | `-204`               | `ECPG_INT_FORMAT`               | The host variable (defined in the C code) is of type INT, and the selected data is of a type that can't be converted into an INT. `ecpglib` uses the `strtol()` function to convert string values into numeric form.               |
+| `42804`             | `-205`               | `ECPG_UINT_FORMAT`              | The host variable (defined in the C code) is an unsigned INT, and the selected data is of a type that can't be converted into an unsigned INT. `ecpglib` uses the `strtoul()` function to convert string values into numeric form. |
+| `42804`             | `-206`               | `ECPG_FLOAT_FORMAT`             | The host variable (defined in the C code) is of type FLOAT, and the selected data is of a type that can't be converted into a FLOAT. `ecpglib` uses the `strtod()` function to convert string values into numeric form.           |
+| `42804`             | `-211`               | `ECPG_CONVERT_BOOL`             | The host variable (defined in the C code) is of type BOOL, and the selected data can't be stored in a BOOL.                                                                                                                        |
+| `YE002`             | `-2-1`               | `ECPG_EMPTY`                    | The statement sent to the server was empty.                                                                                                                                                                                         |
+| `22002`             | `-213`               | `ECPG_MISSING_INDICATOR`        | A NULL indicator variable wasn't supplied for the NULL value returned by the server. (The client application received an unexpected NULL value.).                                                                           |
+| `42804`             | `-214`               | `ECPG_NO_ARRAY`                 | The server returned an array, and the corresponding host variable can't store an array.                                                                                                                           |
+| `42804`             | `-215`               | `ECPG_DATA_NOT_ARRAY`           | The server returned a value that isn't an array into a host variable that expects an array value.                                                                                                                              |
+| `08003`             | `-220`               | `ECPG_NO_CONN`                  | The client application attempted to use a nonexistent connection.                                                                                                                                                              |
+| `YE002`             | `-221`               | `ECPG_NOT_CONN`                 | The client application attempted to use an allocated but closed connection.                                                                                                                                                    |
+| `26000`             | `-230`               | `ECPG_INVALID_STMT`             | The statement wasn't prepared.                                                                                                                                                                                                |
+| `33000`             | `-240`               | `ECPG_UNKNOWN_DESCRIPTOR`       | The specified descriptor isn't found.                                                                                                                                                                                              |
+| `07009`             | `-241`               | `ECPG_INVALID_DESCRIPTOR_INDEX` | The descriptor index is out of range.                                                                                                                                                                                               |
+| `YE002`             | `-242`               | `ECPG_UNKNOWN_DESCRIPTOR_ITEM`  | The client application requested an invalid descriptor item (internal error).                                                                                                                                                   |
+| `07006`             | `-243`               | `ECPG_VAR_NOT_NUMERIC`          | A dynamic statement returned a numeric value for a non-numeric host variable.                                                                                                                                                   |
+| `07006`             | `-244`               | `ECPG_VAR_NOT_CHAR`             | A dynamic SQL statement returned a CHAR value, and the host variable isn't a CHAR.                                                                                                                                             |
+|                     | `-400`               | `ECPG_PGSQL`                    | The server returned an error message. The resulting message contains the error text.                                                                                                                                            |
+| `08007`             | `-401`               | `ECPG_TRANS`                    | The server can't start, commit, or roll back the specified transaction.                                                                                                                                                              |
+| `08001`             | `-402`               | `ECPG_CONNECT`                  | The client application's attempt to connect to the database failed.                                                                                                                                                             |
+| `02000`             | `100`                | `ECPG_NOT_FOUND`                | The last command retrieved or processed no rows, or you reached the end of a cursor.                                                                                                                                           |
+
+## Implementing simple error handling for client applications
+
+Use the `EXEC SQL WHENEVER` directive to implement simple error handling for client applications compiled with ECPGPlus. The syntax of the directive is:
+
+```sql
+EXEC SQL WHENEVER <condition> <action>;
+```
+
+This directive instructs the ECPG compiler to insert error-handling code into your program.
+
+The code instructs the client application to perform a specified action if the client application detects a given condition. The *condition* can be one of the following:
+
+`SQLERROR`
+
+ A `SQLERROR` condition exists when `sqlca.sqlcode` is less than zero.
+
+`SQLWARNING`
+
+ A `SQLWARNING` condition exists when `sqlca.sqlwarn[0]` contains a `'W'`.
+
+`NOT FOUND`
+
+ A `NOT FOUND` condition exists when `sqlca.sqlcode` is `ECPG_NOT_FOUND` (when a query returns no data).
+
+You can specify that the client application perform one of the following *actions* if it encounters one of the previous conditions:
+
+`CONTINUE`
+
+ Specify `CONTINUE` to instruct the client application to continue processing, ignoring the current `condition`. `CONTINUE` is the default action.
+
+`DO CONTINUE`
+
+ An action of `DO CONTINUE` generates a `CONTINUE` statement in the emitted C code. If it encounters the condition, it skips the rest of the code in the loop and continues with the next iteration. You can use it only in a loop.
+
+`GOTO label` or `GO TO label`
+
+ Use a C `goto` statement to jump to the specified `label`.
+
+`SQLPRINT`
+
+ Print an error message to `stderr` (standard error), using the `sqlprint()` function. The `sqlprint()` function prints `sql error` followed by the contents of `sqlca.sqlerrm.sqlerrmc`.
+
+`STOP`
+
+ Call `exit(1)` to signal an error and terminate the program.
+
+`DO BREAK`
+
+ Execute the C `break` statement. Use this action in loops or `switch` statements.
+
+`CALL name(args)` or `DO name(args)`
+
+ Invoke the C function specified by the name `parameter`, using the parameters specified in the `args` parameter.
+
+## Example
+
+The following code fragment prints a message if the client application encounters a warning and aborts the application if it encounters an error:
+
+```sql
+EXEC SQL WHENEVER SQLWARNING SQLPRINT;
+EXEC SQL WHENEVER SQLERROR STOP;
+```
+
+!!! Note
+    The ECPGPlus compiler processes your program from top to bottom, even though the client application might not execute from top to bottom. The compiler directive is applied to each line in order and remains in effect until the compiler encounters another directive. If the control of the flow in your program isn't top to bottom, consider adding error-handling directives to any parts of the program that might be missed during compiling.
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/index.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/index.mdx
new file mode 100644
index 00000000000..ffc3d72ba2f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/index.mdx
@@ -0,0 +1,36 @@
+---
+navTitle: Including embedded SQL commands
+title: "Including embedded SQL commands"
+indexCards: simple
+description: "How to use ECPGPlus to complie applications"
+navigation:
+  - 02_overview
+  - installing_ecpgplus
+  - 03_using_embedded_sql
+  - 04_using_descriptors
+  - 05_building_executing_dynamic_sql_statements
+  - 06_error_handling
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/toc.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB enhanced ECPG (the PostgreSQL precompiler) to create ECPGPlus. ECPGPlus allows you to include Pro\*C-compatible embedded SQL commands in C applications when connected to an EDB Postgres Advanced Server database. When you use ECPGPlus to compile an application, the SQL code syntax is checked and translated into C.
+
+ECPGPlus supports:
+
+-   Oracle Dynamic SQL – Method 4 (ODS-M4)
+-   Pro\*C-compatible anonymous blocks
+-   A `CALL` statement compatible with Oracle databases
+
+As part of ECPGPlus's Pro\*C compatibility, you don't need to include the `BEGIN DECLARE SECTION` and `END DECLARE SECTION` directives.
+
+While most ECPGPlus statements work with community PostgreSQL, the `CALL` statement and the `EXECUTE…END EXEC` statement work only when the client application is connected to EDB Postgres Advanced Server.
+
+<div class="toctree" maxdepth="4">
+
+introduction overview using_embedded_sql using_descriptors building_executing_dynamic_sql_statements error_handling reference conclusion
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/ecpgplus_guide/installing_ecpgplus.mdx b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/installing_ecpgplus.mdx
new file mode 100644
index 00000000000..29605d0a77d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/ecpgplus_guide/installing_ecpgplus.mdx
@@ -0,0 +1,145 @@
+---
+title: "Installing and configuring ECPGPlus"
+description: "Provides an overview of the ECPGPlus precompiler capabilities"
+---
+
+On Windows, ECPGPlus is installed by the EDB Postgres Advanced Server installation wizard as part of the Database Server component. On Linux, you install ECPGPlus by running an executable.
+
+## Installing ECPGPlus
+
+On Linux, install with the `edb-as<xx>-server-devel` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number. On Linux, the executable is located in:
+
+```text
+/usr/edb/as14/bin
+```
+
+On Windows, the executable is located in:
+
+```text
+C:\Program Files\edb\as14\bin
+```
+
+When invoking the ECPGPlus compiler, the executable must be in your search path (`%PATH%` on Windows, `$PATH` on Linux). For example, the following commands set the search path to include the directory that holds the ECPGPlus executable file `ecpg`.
+
+On Windows:
+
+```shell
+set EDB_PATH=C:\Program Files\edb\as14\bin
+set PATH=%EDB_PATH%;%PATH%
+```
+
+On Linux:
+
+```shell
+export EDB_PATH==/usr/edb/as14/bin
+export PATH=$EDB_PATH:$PATH
+```
+
+## Constructing a makefile
+
+A makefile contains a set of instructions that tell the make utility how to transform a program written in C that contains embedded SQL into a C program. To try the examples, you need:
+
+-   A C compiler and linker
+-   The make utility
+-   ECPGPlus preprocessor and library
+-   A makefile that contains instructions for ECPGPlus
+
+The following code is an example of a makefile for the samples included in this documentation. To use the sample code, save it in a file named `makefile` in the directory that contains the source code file.
+
+```c
+INCLUDES = -I$(shell pg_config --includedir)
+LIBPATH = -L $(shell pg_config --libdir)
+CFLAGS += $(INCLUDES) -g
+LDFLAGS += -g
+LDLIBS += $(LIBPATH) -lecpg -lpq
+
+.SUFFIXES: .pgc,.pc
+
+.pgc.c:
+     ecpg -c $(INCLUDES) $?
+
+.pc.c:
+     ecpg -C PROC -c $(INCLUDES) $?
+```
+
+The first two lines use the pg_config program to locate the necessary header files and library directories:
+
+```sql
+INCLUDES = -I$(shell pg_config --includedir)
+LIBPATH = -L $(shell pg_config --libdir)
+```
+
+The pg_config program is shipped with EDB Postgres Advanced Server.
+
+make knows to use the `CFLAGS` variable when running the C compiler and `LDFLAGS` and `LDLIBS` when invoking the linker. ECPG programs must be linked against the ECPG runtime library (`-lecpg`) and the libpq library (`-lpq`).
+
+```sql
+CFLAGS += $(INCLUDES) -g
+LDFLAGS += -g
+LDLIBS += $(LIBPATH) -lecpg -lpq
+```
+
+The sample makefile tells make how to translate a `.pgc` or a `.pc` file into a C program. Two lines in the makefile specify the mode in which the source file is compiled. The first compile option is:
+
+```c
+.pgc.c:
+      ecpg -c $(INCLUDES) $?
+```
+
+The first option tells make how to transform a file that ends in `.pgc` (presumably, an ECPG source file) into a file that ends in `.c` (a C program), using community ECPG, without the ECPGPlus enhancements. It invokes the ECPG precompiler with the `-c` flag, which instructs the compiler to convert SQL code into C, using the value of the `INCLUDES` variable and the name of the `.pgc` file.
+
+```c
+.pc.c:
+    ecpg -C PROC -c $(INCLUDES) $?
+```
+
+The second option tells make how to transform a file that ends in `.pg` (an ECPG source file) into a file that ends in `.c` (a C program) using the ECPGPlus extensions. It invokes the ECPG precompiler with the `-c` flag, which instructs the compiler to convert SQL code to C. It also uses the `-C PROC` flag, which instructs the compiler to use ECPGPlus in Pro\*C-compatibility mode, using the value of the `INCLUDES` variable and the name of the `.pgc` file.
+
+When you run make, pass the name of the ECPG source code file you want to compile. For example, to compile an ECPG source code file named `customer_list.pgc`, use the command:
+
+```shell
+make customer_list
+```
+
+The make utility:
+
+1.  Consults the makefile located in the current directory.
+1.  Discovers that the makefile contains a rule that compiles `customer_list.pgc` into a C program (`customer_list.c`).
+1.  Uses the rules built into `make` to compile `customer_list.c` into an executable program.
+
+## ECPGPlus command line options
+
+In the sample makefile, make includes the `-C` option when invoking ECPGPlus to invoke ECPGPlus in Pro\*C-compatible mode.
+
+If you include the `-C` `PROC` keywords at the command line, in addition to the ECPG syntax, you can use Pro\*C command line syntax. For example:
+
+```shell
+$ ecpg -C PROC INCLUDE=/usr/edb/as14/include acct_update.c
+```
+
+To display a complete list of the other ECPGPlus options available, in the ECPGPlus installation directory, enter:
+
+```shell
+./ecpg --help
+```
+
+The command line options are:
+
+| Option       | Description                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| -c           | Generate C code from embedded SQL code.                                                                                                                                                                                                                                                                                                                                                                                    |
+| -C &lt;mode>    | Specify a compatibility mode:<br /><br />`INFORMIX`<br /><br />`INFORMIX_SE`<br /><br />`PROC`                                                                                                                                                                                                                                                                                                                    |
+| -D &lt;symbol>  | Define a preprocessor symbol.<br /><br />The -D keyword isn't supported when compiling in `PROC` mode. Instead, use the Oracle-style `‘DEFINE=’` clause.                                                                                                                                                                                                                                                                            |
+| -h           | Parse a header file. This option includes option `'-c'`.                                                                                                                                                                                                                                                                                                                                                                                 |
+| -i           | Parse system. Include files as well.                                                                                                                                                                                                                                                                                                                                                                                                     |
+| -I &lt;directory> | Search &lt;directory> for `include` files.                                                                                                                                                                                                                                                                                                                                                                                                  |
+| -o &lt;outfile> | Write the result to &lt;outfile>.                                                                                                                                                                                                                                                                                                                                                                                                           |
+| -r &lt;option>  | Specify runtime behavior. The value of &lt;option> can be:<br /><br />`no_indicator` &mdash; Don't use indicators, but instead use special values to represent NULL values.<br /><br />`prepare` &mdash; Prepare all statements before using them.<br /><br />`questionmarks` &mdash; Allow use of a question mark as a placeholder.<br /><br />`usebulk` &mdash; Enable bulk processing for `INSERT`, `UPDATE`, and `DELETE` statements that operate on host variable arrays. |
+| --regression | Run in regression testing mode.                                                                                                                                                                                                                                                                                                                                                                                                          |
+| -t           | Turn on autocommit of transactions.                                                                                                                                                                                                                                                                                                                                                                                                    |
+| -l           | Disable `#line` directives.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| --help       | Display the help options.                                                                                                                                                                                                                                                                                                                                                                                                                |
+| --version    | Output version information.                                                                                                                                                                                                                                                                                                                                                                                                              |
+
+!!! Note
+    If you don't specify an output file name when invoking ECPGPlus, the output file name is created by removing the `.pgc` extension from the file name and appending `.c`.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx
new file mode 100644
index 00000000000..f9ffade6228
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/02_spl_block_structure.mdx
@@ -0,0 +1,96 @@
+---
+title: "SPL block structure overview"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.050.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.144.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/02_spl_block_structure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="spl_block_structure" class="registered_link"></div>
+
+Regardless of whether the program is a procedure, function, subprogram, or trigger, an SPL program has the same *block* structure. A block consists of up to three sections: an optional declaration section, a mandatory executable section, and an optional exception section. Minimally, a block has an executable section that consists of one or more SPL statements between the keywords `BEGIN` and `END`.
+
+Use the optional declaration section to declare variables, cursors, types, and subprograms that are used by the statements in the executable and exception sections. Declarations appear just before the `BEGIN` keyword of the executable section. Depending on the context of where the block is used, the declaration section can begin with the keyword `DECLARE`.
+
+You can include an exception section in the `BEGIN - END` block. The exception section begins with the keyword `EXCEPTION` and continues until the end of the block in which it appears. If an exception is thrown by a statement in the block, program control might go to the exception section where the thrown exception is handled, depending on the exception and the contents of the exception section.
+
+The following is the general structure of a block:
+
+```sql
+[ [ DECLARE ]
+      <pragmas>
+      <declarations> ]
+    BEGIN
+      <statements>
+  [ EXCEPTION
+      WHEN <exception_condition> THEN
+        <statements> [, ...] ]
+    END;
+```
+
+-  `pragmas` are the directives (`AUTONOMOUS_TRANSACTION` is the currently supported pragma). 
+-  `declarations` are one or more variable, cursor, type, or subprogram declarations that are local to the block. If subprogram declarations are included, you must declare them after all other variable, cursor, and type declarations. Terminate each declaration with a semicolon. The use of the keyword `DECLARE` depends on the context in which the block appears.
+- `statements` are one or more SPL statements. Terminate each statement with a semicolon. You must also terminate the end of the block denoted by the keyword `END` with a semicolon.
+-  If present, the keyword `EXCEPTION` marks the beginning of the exception section. `exception_condition` is a conditional expression testing for one or more types of exceptions. If an exception matches one of the exceptions in `exception_condition`, the `statements` following the `WHEN exception_condition` clause are executed. There can be one or more `WHEN exception_condition` clauses, each followed by `statements`.
+
+!!! Note
+    A `BEGIN/END` block is considered a statement, thus you can nest blocks. The exception section can also contain nested blocks.
+
+The following is the simplest possible block, consisting of the `NULL` statement in the executable section. The `NULL` statement is an executable statement that does nothing.
+
+```sql
+BEGIN
+   NULL;
+END;
+```
+
+The following block contains a declaration section as well as the executable section:
+
+```sql
+DECLARE
+    v_numerator     NUMBER(2);
+    v_denominator   NUMBER(2);
+    v_result        NUMBER(5,2);
+BEGIN
+   v_numerator := 75;
+   v_denominator := 14;
+   v_result := v_numerator / v_denominator;
+   DBMS_OUTPUT.PUT_LINE(v_numerator || ' divided by ' || v_denominator ||
+       ' is ' || v_result);
+END;
+```
+
+In this example, three numeric variables are declared of data type `NUMBER`. Values are assigned to two of the variables, and one number is divided by the other. Results are stored in a third variable and then displayed. The output is:
+
+```sql
+__OUTPUT__
+75 divided by 14 is 5.36
+```
+
+The following block consists of a declaration, an executable, and an exception:
+
+```sql
+DECLARE
+    v_numerator     NUMBER(2);
+    v_denominator   NUMBER(2);
+    v_result        NUMBER(5,2);
+BEGIN
+   v_numerator := 75;
+   v_denominator := 0;
+   v_result := v_numerator / v_denominator;
+   DBMS_OUTPUT.PUT_LINE(v_numerator || ' divided by ' || v_denominator ||
+       ' is ' || v_result);
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('An exception occurred');
+END;
+```
+
+The following output shows that the statement in the exception section is executed as a result of the division by zero:
+
+```sql
+__OUTPUT__
+An exception occurred
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx
new file mode 100644
index 00000000000..b5394b86a1f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/03_anonymous_blocks.mdx
@@ -0,0 +1,17 @@
+---
+title: "Anonymous blocks"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.051.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.145.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/03_anonymous_blocks/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="anonymous_blocks" class="registered_link"></div>
+
+You typically write blocks as part of a procedure, function, subprogram, or trigger. You name procedure, function, and trigger programs and store them in the database if you want to reuse them. 
+
+For quick, one-time execution such as testing, you can enter the block without providing a name or storing it in the database. A block without a name  and that isn't stored in the database is called an *anonymous block*. Once the block is executed and erased from the application buffer, you can't execute it again unless the block code you enter it into the application again.
+
+Typically, the same block of code executes many times. To run a block of code repeatedly without reentering the code each time, with some simple modifications, you can turn an anonymous block into a procedure or function. See [Procedures overview](04_procedures_overview) and [Functions overview](05_functions_overview).
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx
new file mode 100644
index 00000000000..6b3eb1053d3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure.mdx
@@ -0,0 +1,175 @@
+---
+title: "Creating a procedure"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/04_procedures_overview/01_creating_a_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_procedure" class="registered_link"></div>
+
+The `CREATE PROCEDURE` command defines and names a standalone procedure that's stored in the database.
+
+If you include a schema name, then the procedure is created in the specified schema. Otherwise it's created in the current schema. The name of the new procedure must not match any existing procedure with the same input argument types in the same schema. However, procedures of different input argument types can share a name. This is called *overloading*. 
+
+!!! Note
+    Overloading of procedures is an EDB Postgres Advanced Server feature. Overloading of stored, standalone procedures isn't compatible with Oracle databases.
+
+## Updating the definition of an existing procedure
+
+To update the definition of an existing procedure, use `CREATE OR REPLACE PROCEDURE`. You can't change the name or argument types of a procedure this way. Attempting to do so creates a new, distinct procedure. When using `OUT` parameters, you can't change the types of any `OUT` parameters except by dropping the procedure.
+
+```sql
+CREATE [OR REPLACE] PROCEDURE <name> [ (<parameters>) ]
+   [
+          IMMUTABLE
+        | STABLE
+        | VOLATILE
+        | DETERMINISTIC
+        | [ NOT ] LEAKPROOF
+        | CALLED ON NULL INPUT
+        | RETURNS NULL ON NULL INPUT
+        | STRICT
+        | [ EXTERNAL ] SECURITY INVOKER
+        | [ EXTERNAL ] SECURITY DEFINER
+        | AUTHID DEFINER
+        | AUTHID CURRENT_USER
+        | PARALLEL { UNSAFE | RESTRICTED | SAFE }
+        | COST <execution_cost>
+        | ROWS <result_rows>
+        | SET <configuration_parameter>
+          { TO <value> | = <value> | FROM CURRENT }
+   ...]
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+Where:
+
+`name`
+
+ `name` is the identifier of the procedure.
+
+`parameters`
+
+ `parameters` is a list of formal parameters.
+
+`declarations`
+
+ `declarations` are variable, cursor, type, or subprogram declarations. If you include subprogram declarations, you must declare them after all other variable, cursor, and type declarations.
+
+`statements`
+
+ `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+`IMMUTABLE`
+
+`STABLE`
+
+`VOLATILE`
+
+ These attributes inform the query optimizer about the behavior of the procedure. You can specify only one choice. `VOLATILE` is the default behavior.
+
+-   `IMMUTABLE` indicates that the procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups or otherwise use information not directly present in its argument list. If you include this clause, you can immediately replace any call of the procedure with all-constant arguments with the procedure value.
+
+-   `STABLE` indicates that the procedure can't modify the database. It also indicates that, in a single table scan, it consistently returns the same result for the same argument values but that its result might change across SQL statements. Use this selection for procedures that depend on database lookups, parameter variables (such as the current time zone), and so on.
+
+-   `VOLATILE` indicates that the procedure value can change even in a single table scan, so you can't make optimizations. You must classify any function that has side effects as volatile, even if its result is predictable, to prevent calls from being optimized away.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the procedure with all-constant arguments can be immediately replaced with the procedure value.
+
+`[ NOT ] LEAKPROOF`
+
+ A `LEAKPROOF` procedure has no side effects and reveals no information about the values used to call the procedure.
+
+`CALLED ON NULL INPUT`
+
+`RETURNS NULL ON NULL INPUT`
+
+`STRICT`
+
+-   `CALLED ON NULL INPUT` (the default) indicates that the procedure is called normally when some of its arguments are `NULL`. It's the author's responsibility to check for `NULL` values if necessary and respond appropriately.
+
+-   `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` when any of its arguments are `NULL`. If these clauses are specified, the procedure isn't executed when there are `NULL` arguments. Instead a `NULL` result is assumed automatically.
+
+`[ EXTERNAL ] SECURITY DEFINER`
+
+ `SECURITY DEFINER` specifies for the procedure to execute with the privileges of the user that created it. This is the default. The key word `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`[ EXTERNAL ] SECURITY INVOKER`
+
+ The `SECURITY INVOKER` clause indicates for the procedure to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`AUTHID DEFINER`
+
+`AUTHID CURRENT_USER`
+
+-   The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If you omit the `AUTHID` clause or specify `AUTHID DEFINER`, the rights of the procedure owner determine access privileges to database objects.
+
+-   The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If you specify `AUTHID CURRENT_USER`, the rights of the current user executing the procedure determine access privileges.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans, that is, parallel mode. A parallel sequential scan uses multiple workers to scan a relation in parallel during a query, in contrast to a serial sequential scan.
+
+-   When the value is set to `UNSAFE`, you can't execute the procedure in parallel mode. The presence of such a procedure forces a serial execution plan. This is the default setting.
+
+-   When the value is set to `RESTRICTED`, you can execute the procedure in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that's parallel restricted, that relation isn't chosen for parallelism.
+
+-   When the value is set to `SAFE`, you can execute the procedure in parallel mode without restriction.
+
+`COST execution_cost`
+
+ `execution_cost` is a positive number giving the estimated execution cost for the procedure, in units of `cpu_operator_cost`. If the procedure returns a set, this is the cost per returned row. Larger values cause the planner to try to avoid evaluating the function more often than necessary.
+
+`ROWS result_rows`
+
+ `result_rows` is a positive number giving the estimated number of rows for the planner to expect the procedure to return. This setting is allowed only when the procedure is declared to return a set. The default is 1000 rows.
+
+`SET configuration_parameter { TO value | = value | FROM CURRENT }`
+
+ The `SET` clause causes the specified configuration parameter to be set to the specified value when the procedure is entered and then restored to its prior value when the procedure exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the procedure is entered.
+
+ If a `SET` clause is attached to a procedure, then the effects of a `SET LOCAL` command executed inside the procedure for the same variable are restricted to the procedure. The configuration parameter's prior value is restored at procedure exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, much as it does for a previous `SET LOCAL` command. The effects of this command persist after procedure exit, unless the current transaction is rolled back.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the procedure as an autonomous transaction.
+
+!!! Note
+    -   The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle.
+
+    -   By default, stored procedures are created as `SECURITY DEFINERS`, but when written in plpgsql, the stored procedures are created as `SECURITY INVOKERS`.
+
+## Example
+
+This example shows a simple procedure that takes no parameters:
+
+```sql
+CREATE OR REPLACE PROCEDURE simple_procedure
+IS
+BEGIN
+   DBMS_OUTPUT.PUT_LINE('That''s all folks!');
+END simple_procedure;
+```
+
+Store the procedure in the database by entering the procedure code in EDB Postgres Advanced Server.
+
+This example shows using the `AUTHID DEFINER` and `SET` clauses in a procedure declaration. The `update_salary` procedure conveys the privileges of the role that defined the procedure to the role that's calling the procedure while the procedure executes.
+
+```sql
+CREATE OR REPLACE PROCEDURE update_salary(id INT, new_salary NUMBER)
+  SET SEARCH_PATH = 'public' SET WORK_MEM = '1MB'
+  AUTHID DEFINER IS
+BEGIN
+  UPDATE emp SET salary = new_salary WHERE emp_id = id;
+END;
+```
+
+Include the `SET` clause to set the procedure's search path to `public` and the work memory to `1MB`. These settings don't affect other procedures, functions, and objects.
+
+In the example, the `AUTHID DEFINER` clause temporarily grants privileges to a role that otherwise might not be allowed to execute the statements in the procedure. To instruct the server to use the privileges associated with the role invoking the procedure, replace the `AUTHID DEFINER` clause with the `AUTHID CURRENT_USER` clause.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx
new file mode 100644
index 00000000000..48425b9bdd0
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure.mdx
@@ -0,0 +1,37 @@
+---
+title: "Calling a procedure"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/04_procedures_overview/02_calling_a_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="calling_a_procedure" class="registered_link"></div>
+
+You can invoke a procedure from another SPL program by specifying the procedure name followed by any parameters and a semicolon:
+
+```text
+<name> [ ([ <parameters> ]) ];
+```
+
+Where:
+
+`name` is the identifier of the procedure.
+
+`parameters` is a list of parameters.
+
+!!! Note
+    -   If there are no parameters to pass, you can call the procedure with an empty parameter list, or you can omit the parentheses.
+
+    -   The syntax for calling a procedure is the same as in the preceding syntax diagram when executing it with the `EXEC` command in PSQL or EDB\*Plus. See [SQL reference](../../../../reference/oracle_compatibility_reference/epas_compat_sql/63_exec/) for information about the `EXEC` command.
+
+This example calls the procedure from an anonymous block:
+
+```sql
+BEGIN
+   simple_procedure;
+END;
+
+That's all folks!
+```
+
+!!! Note
+    Each application has its own way of calling a procedure. For example, a Java application uses the application programming interface JDBC.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx
new file mode 100644
index 00000000000..13a47cb22d4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure.mdx
@@ -0,0 +1,27 @@
+---
+title: "Deleting a procedure"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/04_procedures_overview/03_deleting_a_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="deleting_a_procedure" class="registered_link"></div>
+
+You can delete a procedure from the database using the `DROP PROCEDURE` command.
+
+```sql
+DROP PROCEDURE [ IF EXISTS ] <name> [ (<parameters>) ]
+    [ CASCADE | RESTRICT ];
+```
+
+Where `name` is the name of the procedure to drop.
+
+!!! Note
+    -   The specification of the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as in an overloaded procedure. Oracle requires that you always omit the parameter list.
+
+    -   Using `IF EXISTS`, `CASCADE`, or `RESTRICT` isn't compatible with Oracle databases. See [SQL reference](../../../../reference/oracle_compatibility_reference/epas_compat_sql/50_drop_procedure) for information on these options.
+
+This example drops the procedure `simple_procedure`:
+
+```sql
+DROP PROCEDURE simple_procedure;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx
new file mode 100644
index 00000000000..7e18a9f73c6
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/04_procedures_overview/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Procedures overview"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.052.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.146.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/04_procedures_overview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="procedures_overview" class="registered_link"></div>
+
+Procedures are standalone SPL programs that you invoke or call as an individual SPL program statement. When called, procedures can optionally receive values from the caller in the form of input parameters. They can optionally return values to the caller in the form of output parameters.
+
+<div class="toctree" maxdepth="3">
+
+creating_a_procedure calling_a_procedure deleting_a_procedure
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx
new file mode 100644
index 00000000000..f5d1ee54f19
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function.mdx
@@ -0,0 +1,180 @@
+---
+title: "Creating a function"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/05_functions_overview/01_creating_a_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_function" class="registered_link"></div>
+
+The `CREATE FUNCTION` command defines and names a standalone function to store in the database.
+
+If a schema name is included, then the function is created in the specified schema. Otherwise it's created in the current schema. The name of the new function must not match any existing function with the same input argument types in the same schema. However, functions of different input argument types can share a name. Sharing a name is called *overloading*. 
+
+!!! Note
+    Overloading functions is an EDB Postgres Advanced Server feature. **Overloading stored, standalone functions isn't compatible with Oracle databases.**
+
+## Updating the definition of an existing function
+
+To update the definition of an existing function, use `CREATE OR REPLACE FUNCTION`. You can't change the name or argument types of a function this way. If you try to, you instead create a new, distinct function. Also, `CREATE OR REPLACE FUNCTION` doesn't let you change the return type of an existing function. To do that, you must drop and recreate the function. When using `OUT` parameters, you can't change the types of any `OUT` parameters except by dropping the function.
+
+```sql
+CREATE [ OR REPLACE ] FUNCTION <name> [ (<parameters>) ]
+  RETURN <data_type>
+   [
+           IMMUTABLE
+        | STABLE
+        | VOLATILE
+        | DETERMINISTIC
+        | [ NOT ] LEAKPROOF
+        | CALLED ON NULL INPUT
+        | RETURNS NULL ON NULL INPUT
+        | STRICT
+        | [ EXTERNAL ] SECURITY INVOKER
+        | [ EXTERNAL ] SECURITY DEFINER
+        | AUTHID DEFINER
+        | AUTHID CURRENT_USER
+        | PARALLEL { UNSAFE | RESTRICTED | SAFE }
+        | COST <execution_cost>
+        | ROWS <result_rows>
+        | SET <configuration_parameter>
+          { TO <value> | = <value> | FROM CURRENT }
+   ...]
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+Where:
+
+ `name` is the identifier of the function.
+
+ `parameters` is a list of formal parameters.
+
+ `data_type` is the data type of the value returned by the function’s `RETURN` statement.
+
+ `declarations` are variable, cursor, type, or subprogram declarations. If you include subprogram declarations, you must declare them after all other variable, cursor, and type declarations.
+
+ `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+`IMMUTABLE`
+
+`STABLE`
+
+`VOLATILE`
+
+ These attributes inform the query optimizer about the behavior of the function. You can specify only one. `VOLATILE` is the default behavior.
+
+-   `IMMUTABLE` indicates that the function can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, any call of the function with all-constant arguments can be immediately replaced with the function value.
+
+-   `STABLE` indicates that the function can't modify the database. It also indicates that, in a single table scan, it consistently returns the same result for the same argument values but that its result might change across SQL statements. Select this attribute for functions that depend on database lookups, parameter variables (such as the current time zone), and so on.
+
+-   `VOLATILE` indicates that the function value can change even in a single table scan, so no optimizations can be made. Classify any function that has side effects as volatile, even if its result is predictable, to prevent calls from being optimized away.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` function can't modify the database and always reaches the same result when given the same argument values. It doesn't do database lookups or otherwise use information not directly present in its argument list. If you include this clause, you can replace any call of the function with all-constant arguments with the function value.
+
+`[ NOT ] LEAKPROOF`
+
+ A `LEAKPROOF` function has no side effects and reveals no information about the values used to call the function.
+
+`CALLED ON NULL INPUT`
+
+`RETURNS NULL ON NULL INPUT`
+
+`STRICT`
+
+-   `CALLED ON NULL INPUT` (the default) indicates for the procedure to be called normally when some of its arguments are `NULL`. It is the author's responsibility to check for `NULL` values if necessary and respond appropriately.
+
+-   `RETURNS NULL ON NULL INPUT` or `STRICT` indicates that the procedure always returns `NULL` when any of its arguments are `NULL`. If you specify these clauses, the procedure isn't executed when there are `NULL` arguments. Instead, a `NULL` result is assumed automatically.
+
+`[ EXTERNAL ] SECURITY DEFINER`
+
+ `SECURITY DEFINER` (the default) specifies for the function to execute with the privileges of the user that created it. The key word `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`[ EXTERNAL ] SECURITY INVOKER`
+
+ The `SECURITY INVOKER` clause indicates for the function to execute with the privileges of the user that calls it. The key word `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`AUTHID DEFINER`
+
+`AUTHID CURRENT_USER`
+
+-   The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If the `AUTHID` clause is omitted or if `AUTHID DEFINER` is specified, the rights of the function owner determine access privileges to database objects.
+
+-   The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If `AUTHID CURRENT_USER` is specified, the rights of the current user executing the function determine access privileges.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans, that is, parallel mode. A parallel sequential scan uses multiple workers to scan a relation in parallel during a query in contrast to a serial sequential scan.
+
+-   When this value is set to `UNSAFE`, you can't execute the function in parallel mode. The presence of such a function in a SQL statement forces a serial execution plan. This is the default setting.
+
+-   When this value is set to `RESTRICTED`, you can execute the function in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that's parallel restricted, that relation isn't chosen for parallelism.
+
+-   When this value is set to `SAFE`, you can execute the function in parallel mode with no restriction.
+
+`COST execution_cost`
+
+ `execution_cost` is a positive number giving the estimated execution cost for the function, in units of `cpu_operator_cost`. If the function returns a set, this is the cost per returned row. Larger values cause the planner to try to avoid evaluating the function more often than necessary.
+
+`ROWS result_rows`
+
+ `result_rows` is a positive number giving the estimated number of rows for the planner to expect the function to return. This is allowed only when the function is declared to return a set. The default assumption is 1000 rows.
+
+`SET configuration_parameter { TO value | = value | FROM CURRENT }`
+
+ The `SET` clause causes the specified configuration parameter to be set to the specified value when the function is entered and then restored to its prior value when the function exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the function is entered.
+
+ If a `SET` clause is attached to a function, then the effects of a `SET LOCAL` command executed inside the function for the same variable are restricted to the function. The configuration parameter's prior value is restored at function exit. A `SET` command without `LOCAL` overrides the `SET` clause, much as it does for a previous `SET LOCAL` command. The effects of such a command persist after procedure exit, unless the current transaction is rolled back.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the function as an autonomous transaction.
+
+!!! Note
+    The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle.
+
+## Examples
+
+This example shows a simple function that takes no parameters:
+
+```sql
+CREATE OR REPLACE FUNCTION simple_function
+    RETURN VARCHAR2
+IS
+BEGIN
+    RETURN 'That''s All Folks!';
+END simple_function;
+```
+
+This function takes two input parameters: 
+
+```sql
+CREATE OR REPLACE FUNCTION emp_comp (
+    p_sal           NUMBER,
+    p_comm          NUMBER
+) RETURN NUMBER
+IS
+BEGIN
+    RETURN (p_sal + NVL(p_comm, 0)) * 24;
+END emp_comp;
+```
+
+This example uses the `AUTHID CURRENT_USER` clause and `STRICT` keyword in a function declaration:
+
+```sql
+CREATE OR REPLACE FUNCTION dept_salaries(dept_id int) RETURN NUMBER
+  STRICT
+  AUTHID CURRENT_USER
+BEGIN
+  RETURN QUERY (SELECT sum(salary) FROM emp WHERE deptno = id);
+END;
+```
+
+Include the `STRICT` keyword to instruct the server to return `NULL` if any input parameter passed is `NULL`. If a `NULL` value is passed, the function doesn't execute.
+
+The `dept_salaries` function executes with the privileges of the role that's calling the function. If the current user doesn't have the privileges to perform the `SELECT` statement querying the `emp` table (to display employee salaries), the function reports an error. To instruct the server to use the privileges associated with the role that defined the function, replace the `AUTHID CURRENT_USER` clause with the `AUTHID DEFINER` clause.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx
new file mode 100644
index 00000000000..d734c7dcbb2
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function.mdx
@@ -0,0 +1,55 @@
+---
+title: "Calling a function"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/05_functions_overview/02_calling_a_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="calling_a_function" class="registered_link"></div>
+
+You can use a function anywhere an expression can appear in an SPL statement. Invoke a function by specifying its name followed by any parameters enclosed in parentheses.
+
+```text
+<name> [ ([ <parameters> ]) ]
+```
+
+`name` is the name of the function. 
+
+`parameters` is a list of parameters.
+
+!!! Note
+    If there are no parameters to pass, you can call the function with an empty parameter list, or you can omit the parentheses.
+
+This example shows how to call the function from another SPL program:
+
+```sql
+BEGIN
+    DBMS_OUTPUT.PUT_LINE(simple_function);
+END;
+
+That's All Folks!
+```
+
+You typically use a function in a SQL statement, as this example shows:
+
+```sql
+SELECT empno "EMPNO", ename "ENAME", sal "SAL", comm "COMM",
+    emp_comp(sal, comm) "YEARLY COMPENSATION" FROM emp;
+__OUTPUT__
+ EMPNO | ENAME  |   SAL   |  COMM   | YEARLY COMPENSATION
+-------+--------+---------+---------+---------------------
+  7369 | SMITH  |  800.00 |         |            19200.00
+  7499 | ALLEN  | 1600.00 |  300.00 |            45600.00
+  7521 | WARD   | 1250.00 |  500.00 |            42000.00
+  7566 | JONES  | 2975.00 |         |            71400.00
+  7654 | MARTIN | 1250.00 | 1400.00 |            63600.00
+  7698 | BLAKE  | 2850.00 |         |            68400.00
+  7782 | CLARK  | 2450.00 |         |            58800.00
+  7788 | SCOTT  | 3000.00 |         |            72000.00
+  7839 | KING   | 5000.00 |         |           120000.00
+  7844 | TURNER | 1500.00 |    0.00 |            36000.00
+  7876 | ADAMS  | 1100.00 |         |            26400.00
+  7900 | JAMES  |  950.00 |         |            22800.00
+  7902 | FORD   | 3000.00 |         |            72000.00
+  7934 | MILLER | 1300.00 |         |            31200.00
+(14 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx
new file mode 100644
index 00000000000..b3db08d5710
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function.mdx
@@ -0,0 +1,27 @@
+---
+title: "Deleting a function"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/05_functions_overview/03_deleting_a_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="deleting_a_function" class="registered_link"></div>
+
+You can delete a function from the database using `DROP FUNCTION`.
+
+```sql
+DROP FUNCTION [ IF EXISTS ] <name> [ (<parameters>) ]
+    [ CASCADE | RESTRICT ];
+```
+
+Where `name` is the name of the function to drop.
+
+!!! Note
+    -   Specifying the parameter list is required in EDB Postgres Advanced Server under certain circumstances such as in an overloaded function. Oracle requires that you always omit the parameter list.
+
+    -   Use of `IF EXISTS`, `CASCADE`, or `RESTRICT` isn't compatible with Oracle databases. See the [SQL reference](../../../../reference/oracle_compatibility_reference/epas_compat_sql/47_drop_function) for information on these options.
+
+This example drops the function `simple_function`:
+
+```sql
+DROP FUNCTION simple_function;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx
new file mode 100644
index 00000000000..d1e9bfdc7b2
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/05_functions_overview/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "Functions overview"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.053.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.147.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/05_functions_overview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="functions_overview" class="registered_link"></div>
+
+Functions are standalone SPL programs that are invoked as expressions. When evaluated, a function returns a value that's substituted in the expression in which the function is embedded. Functions can optionally take values from the calling program in the form of input parameters. 
+
+In addition to the fact that the function returns a value, a function can also optionally return values to the caller in the form of output parameters. However, we don't encourage the use of output parameters in functions.
+
+<div class="toctree" maxdepth="3">
+
+creating_a_function calling_a_function deleting_a_function
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx
new file mode 100644
index 00000000000..e41d8fcf33a
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation.mdx
@@ -0,0 +1,106 @@
+---
+title: "Positional versus named parameter notation"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/01_positional_vs_named_parameter_notation/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="positional_vs_named_parameter_notation" class="registered_link"></div>
+
+You can use either *positional* or *named* parameter notation when passing parameters to a function or procedure. 
+
+- If you specify parameters using *positional notation*, you must list the parameters in the order that they are declared. If you specify parameters with named notation, the order of the parameters doesn't matter.
+
+- If you specify parameters using *named notation*, list the name of each parameter followed by an arrow (`=>`) and the parameter value. Named notation is more verbose but makes your code easier to read and maintain.
+
+This example uses positional and named parameter notation:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_info (
+    p_deptno        IN     NUMBER,
+    p_empno         IN OUT NUMBER,
+    p_ename         IN OUT VARCHAR2,
+)
+IS
+BEGIN
+    dbms_output.put_line('Department Number =' || p_deptno);
+    dbms_output.put_line('Employee Number =' || p_empno);
+    dbms_output.put_line('Employee Name =' || p_ename;
+END;
+```
+
+To call the procedure using positional notation, pass the following:
+
+```sql
+emp_info(30, 7455, 'Clark');
+```
+
+To call the procedure using named notation, pass the following:
+
+```sql
+emp_info(p_ename =>'Clark', p_empno=>7455, p_deptno=>30);
+```
+
+If you used named notation, you don't need to rearrange a procedure’s parameter list if the parameter list changes, the parameters are reordered, or an optional parameter is added.
+
+When an argument has a default value and the argument isn't a trailing argument, you must use named notation to call the procedure or function. This example shows a procedure with two leading default arguments:
+
+```sql
+CREATE OR REPLACE PROCEDURE check_balance (
+    p_customerID  IN NUMBER DEFAULT NULL,
+    p_balance     IN NUMBER DEFAULT NULL,
+    p_amount      IN NUMBER
+)
+IS
+DECLARE
+    balance NUMBER;
+BEGIN
+   IF (p_balance IS NULL AND p_customerID IS NULL) THEN
+      RAISE_APPLICATION_ERROR
+          (-20010, 'Must provide balance or customer');
+   ELSEIF (p_balance IS NOT NULL AND p_customerID IS NOT NULL) THEN
+      RAISE_APPLICATION_ERROR
+          (-20020,'Must provide balance or customer, not both');
+   ELSEIF (p_balance IS NULL) THEN
+      balance := getCustomerBalance(p_customerID);
+   ELSE
+      balance := p_balance;
+   END IF;
+
+   IF (amount > balance) THEN
+      RAISE_APPLICATION_ERROR
+        (-20030, 'Balance insufficient');
+   END IF;
+END;
+```
+
+You can omit nontrailing argument values when you call this procedure only by using named notation. When using positional notation, only trailing arguments are allowed to default. You can call this procedure with the following arguments:
+
+```sql
+check_balance(p_customerID => 10, p_amount = 500.00)
+
+check_balance(p_balance => 1000.00, p_amount = 500.00)
+```
+
+You can use a combination of positional and named notation, referred to as *mixed* notation, to specify parameters. This example shows using mixed parameter notation:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_info (
+    p_deptno        IN     NUMBER,
+    p_empno         IN OUT NUMBER,
+    p_ename         IN OUT VARCHAR2,
+)
+IS
+BEGIN
+    dbms_output.put_line('Department Number =' || p_deptno);
+    dbms_output.put_line('Employee Number =' || p_empno);
+    dbms_output.put_line('Employee Name =' || p_ename;
+END;
+```
+
+You can call the procedure using mixed notation:
+
+```sql
+emp_info(30, p_ename =>'Clark', p_empno=>7455);
+```
+
+When using mixed notation, named arguments can't precede positional arguments.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx
new file mode 100644
index 00000000000..80fa19364bd
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes.mdx
@@ -0,0 +1,32 @@
+---
+title: "Parameter modes"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/02_parameter_modes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="parameter_modes" class="registered_link"></div>
+
+A parameter has one of three possible modes: `IN`, `OUT`, or `IN OUT`. The following characteristics of a formal parameter depend on its mode:
+
+-   Its initial value when the procedure or function is called
+-   Whether the called procedure or function can modify the formal parameter
+-   How the actual parameter value is passed from the calling program to the called program
+-   What happens to the formal parameter value when an unhandled exception occurs in the called program
+
+The following table summarizes the behavior of parameters according to their mode.
+
+| Mode property                                                                   | IN                                                | IN OUT                                            | OUT                                               |
+| ------------------------------------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------- | ------------------------------------------------- |
+| Formal parameter initialized to:                                                | Actual parameter value                            | Actual parameter value                            | Actual parameter value                            |
+| Formal parameter modifiable by the called program?                              | No                                                | Yes                                               | Yes                                               |
+| Actual parameter contains: (after normal called program termination)            | Original actual parameter value prior to the call | Last value of the formal parameter                | Last value of the formal parameter                |
+| Actual parameter contains: (after a handled exception in the called program)    | Original actual parameter value prior to the call | Last value of the formal parameter                | Last value of the formal parameter                |
+| Actual parameter contains: (after an unhandled exception in the called program) | Original actual parameter value prior to the call | Original actual parameter value prior to the call | Original actual parameter value prior to the call |
+
+As shown by the table:
+
+- The `IN` formal parameter is initialized to the actual parameter with which it's called unless it was explicitly initialized with a default value. You can reference the `IN` parameter in the called program. However, the called program can't assign a new value to the `IN` parameter. After control returns to the calling program, the actual parameter always contains the same value that it had prior to the call.
+
+- Like an `IN` parameter, an `IN OUT` formal parameter is initialized to the actual parameter with which it's called. Like an `OUT` parameter, an `IN OUT` formal parameter can be modifiwed by the called program. The last value in the formal parameter is passed to the calling program’s actual parameter if the called program ends without an exception. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call.
+
+- The `OUT` formal parameter is initialized to the actual parameter with which it's called. The called program can reference and assign new values to the formal parameter. If the called program ends without an exception, the actual parameter takes on the value last set in the formal parameter. If a handled exception occurs, the value of the actual parameter takes on the last value assigned to the formal parameter. If an unhandled exception occurs, the value of the actual parameter remains as it was prior to the call.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx
new file mode 100644
index 00000000000..3351c854b72
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters.mdx
@@ -0,0 +1,75 @@
+---
+title: "Using default values in parameters"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/03_using_default_values_in_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_default_values_in_parameters" class="registered_link"></div>
+
+You can set a default value of a formal parameter by including the `DEFAULT` clause or using the assignment operator (`:=`) in the `CREATE PROCEDURE` or `CREATE FUNCTION` statement.
+
+## Syntax
+
+The general form of a formal parameter declaration is:
+
+```text
+(<name> [ IN|OUT|IN OUT ] <data_type> [{DEFAULT | := } <expr> ])
+```
+
+`name` is an identifier assigned to the parameter.
+
+`IN|OUT|IN OUT` specifies the parameter mode.
+
+`data_type` is the data type assigned to the variable.
+
+`expr` is the default value assigned to the parameter. If you don't include a `DEFAULT` clause, the caller must provide a value for the parameter.
+
+The default value is evaluated every time you invoke the function or procedure. For example, assigning `SYSDATE` to a parameter of type `DATE` causes the parameter to have the time of the current invocation, not the time when the procedure or function was created.
+
+## Example 
+
+This example uses the assignment operator to set a default value of `SYSDATE` into the parameter `hiredate:`
+
+```sql
+CREATE OR REPLACE PROCEDURE hire_emp (
+    p_empno         NUMBER,
+    p_ename         VARCHAR2,
+    p_hiredate      DATE := SYSDATE
+)
+IS
+BEGIN
+    INSERT INTO emp(empno, ename, hiredate)
+                   VALUES(p_empno, p_ename, p_hiredate);
+
+    DBMS_OUTPUT.PUT_LINE('Hired!');
+END hire_emp;
+```
+
+If the parameter declaration includes a default value, you can omit the parameter from the actual parameter list when you call the procedure. Calls to the sample procedure `(hire_emp)` must include two arguments: the employee number `(p_empno)` and employee name `(p_empno)`. The third parameter `(p_hiredate)` defaults to the value of `SYSDATE:`
+
+```sql
+hire_emp (7575, Clark)
+```
+
+If you do include a value for the actual parameter when you call the procedure, that value takes precedence over the default value. This command adds an employee with a hiredate of `February 15, 2010`, regardless of the current value of `SYSDATE`.
+
+```sql
+hire_emp (7575, Clark, 15-FEB-2010)
+```
+
+You can write the same procedure by substituting the `DEFAULT` keyword for the assignment operator:
+
+```sql
+CREATE OR REPLACE PROCEDURE hire_emp (
+    p_empno         NUMBER,
+    p_ename         VARCHAR2,
+    p_hiredate      DATE DEFAULT SYSDATE
+)
+IS
+BEGIN
+    INSERT INTO emp(empno, ename, hiredate)
+                   VALUES(p_empno, p_ename, p_hiredate);
+
+    DBMS_OUTPUT.PUT_LINE('Hired!');
+END hire_emp;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx
new file mode 100644
index 00000000000..a84ced4e434
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/declaring_parameters.mdx
@@ -0,0 +1,87 @@
+---
+title: "Declaring parameters"
+---
+
+Declare parameters in the procedure or function definition, and enclose them in parentheses following the procedure or function name. Parameters declared in the procedure or function definition are known as *formal parameters*. When you invoke the procedure or function, the calling program supplies the actual data to use in the called program’s processing as well as the variables that receive the results of the called program’s processing. The data and variables supplied by the calling program when the procedure or function is called are referred to as the *actual parameters*.
+
+The following is the general format of a formal parameter declaration:
+
+```text
+(<name> [ IN | OUT | IN OUT ] <data_type> [ DEFAULT <value> ])
+```
+
+-  `name` is an identifier assigned to the formal parameter. 
+-  Whether a parameter is `IN`, `OUT`, or `IN OUT` is referred to as the parameter’s *mode*. If specified, `IN` defines the parameter for receiving input data into the procedure or function. An `IN` parameter can also be initialized to a default value. If specified, `OUT` defines the parameter for returning data from the procedure or function. If specified, `IN OUT` allows the parameter to be used for both input and output. If all of `IN`, `OUT`, and `IN OUT` are omitted, then the parameter acts as if it were defined as `IN` by default.  
+-  `data_type` defines the data type of the parameter. 
+-  `value` is a default value assigned to an `IN` parameter in the called program if you don't specify an actual parameter in the call.
+
+This example shows a procedure that takes parameters:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_query (
+    p_deptno        IN     NUMBER,
+    p_empno         IN OUT NUMBER,
+    p_ename         IN OUT VARCHAR2,
+    p_job           OUT    VARCHAR2,
+    p_hiredate      OUT    DATE,
+    p_sal           OUT    NUMBER
+)
+IS
+BEGIN
+    SELECT empno, ename, job, hiredate, sal
+        INTO p_empno, p_ename, p_job, p_hiredate, p_sal
+        FROM emp
+        WHERE deptno = p_deptno
+          AND (empno = p_empno
+           OR  ename = UPPER(p_ename));
+END;
+```
+
+In this example, `p_deptno` is an `IN` formal parameter, `p_empno` and `p_ename` are `IN OUT` formal parameters, and `p_job, p_hiredate` and `p_sal` are `OUT` formal parameters.
+
+!!! Note
+    In the example, no maximum length was specified on the `VARCHAR2` parameters, and no precision and scale were specified on the `NUMBER` parameters. It's illegal to specify a length, precision, scale, or other constraints on parameter declarations. These constraints are inherited from the actual parameters that are used when the procedure or function is called.
+
+The `emp_query` procedure can be called by another program, passing it the actual parameters. This example is another SPL program that calls `emp_query`:
+
+```sql
+DECLARE
+    v_deptno        NUMBER(2);
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_job           VARCHAR2(9);
+    v_hiredate      DATE;
+    v_sal           NUMBER;
+BEGIN
+    v_deptno := 30;
+    v_empno  := 7900;
+    v_ename  := '';
+    emp_query(v_deptno, v_empno, v_ename, v_job, v_hiredate, v_sal);
+    DBMS_OUTPUT.PUT_LINE('Department : ' || v_deptno);
+    DBMS_OUTPUT.PUT_LINE('Employee No: ' || v_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+END;
+```
+
+In this example, `v_deptno`, `v_empno`, `v_ename`, `v_job`, `v_hiredate`, and `v_sal` are the actual parameters.
+
+The output from the example is:
+
+```sql
+__OUTPUT__
+Department : 30
+Employee No: 7900
+Name       : JAMES
+Job        : CLERK
+Hire Date  : 03-DEC-81
+Salary     : 950
+```
+
+<div class="toctree" maxdepth="3">
+
+positional_vs_named_parameter_notation parameter_modes using_default_values_in_parameters
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx
new file mode 100644
index 00000000000..ff33188fd88
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Procedure and function parameters"
+indexCards: simple
+navigation:
+- declaring_parameters
+- 01_positional_vs_named_parameter_notation
+- 02_parameter_modes
+- 03_using_default_values_in_parameters
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.054.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.148.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/06_procedure_and_function_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="procedure_and_function_parameters" class="registered_link"></div>
+
+An important aspect of using procedures and functions is the capability to pass data from the calling program to the procedure or function and to receive data back from the procedure or function. You do this by using *parameters*.
+
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx
new file mode 100644
index 00000000000..52099985964
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure.mdx
@@ -0,0 +1,128 @@
+---
+title: "Creating a subprocedure"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/01_creating_a_subprocedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_subprocedure" class="registered_link"></div>
+
+The `PROCEDURE` clause specified in the declaration section defines and names a subprocedure local to that block.
+
+- The term *block* refers to the SPL block structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks are the structures for standalone procedures and functions, anonymous blocks, subprograms, triggers, packages, and object type methods.
+
+- The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block. Therefore, the SPL code can access it in the executable section and optional exception section of that block.
+
+## Declaring subprocedures
+
+You can declare subprocedures only after all the other variable, cursor, and type declarations included in the declaration section. Subprograms must be the last set of declarations.
+
+```sql
+PROCEDURE <name> [ (<parameters>) ]
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+Where:
+
+- `name` is the identifier of the subprocedure.
+
+- `parameters` is a list of formal parameters.
+
+- `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subprocedure as an autonomous transaction.
+
+- `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, you must declare them after all other variable, cursor, and type declarations.
+
+- `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+## Example: Subprocedure in an anonymous block
+
+This example is a subprocedure in an anonymous block:
+
+```sql
+DECLARE
+    PROCEDURE list_emp
+    IS
+        v_empno     NUMBER(4);
+        v_ename     VARCHAR2(10);
+        CURSOR emp_cur IS
+            SELECT empno, ename FROM emp ORDER BY empno;
+    BEGIN
+        OPEN emp_cur;
+        DBMS_OUTPUT.PUT_LINE('Subprocedure list_emp:');
+        DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+        DBMS_OUTPUT.PUT_LINE('-----    -------');
+        LOOP
+            FETCH emp_cur INTO v_empno, v_ename;
+            EXIT WHEN emp_cur%NOTFOUND;
+            DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+        END LOOP;
+        CLOSE emp_cur;
+    END;
+BEGIN
+    list_emp;
+END;
+```
+
+Invoking this anonymous block produces the following output:
+
+```sql
+__OUTPUT__
+Subprocedure list_emp:
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+```
+
+## Example: Subprocedure in a trigger
+
+This example is a subprocedure in a trigger:
+
+```sql
+CREATE OR REPLACE TRIGGER dept_audit_trig
+    AFTER INSERT OR UPDATE OR DELETE ON dept
+DECLARE
+    v_action        VARCHAR2(24);
+    PROCEDURE display_action (
+        p_action    IN  VARCHAR2
+    )
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('User ' || USER || ' ' || p_action ||
+            ' dept on ' || TO_CHAR(SYSDATE,'YYYY-MM-DD'));
+    END display_action;
+BEGIN
+    IF INSERTING THEN
+        v_action := 'added';
+    ELSIF UPDATING THEN
+        v_action := 'updated';
+    ELSIF DELETING THEN
+        v_action := 'deleted';
+    END IF;
+    display_action(v_action);
+END;
+```
+
+Invoking this trigger produces the following output:
+
+```sql
+INSERT INTO dept VALUES (50,'HR','DENVER');
+__OUTPUT__
+User enterprisedb added dept on 2016-07-26
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx
new file mode 100644
index 00000000000..0f2a0b069bd
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction.mdx
@@ -0,0 +1,75 @@
+---
+title: "Creating a subfunction"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/02_creating_a_subfunction/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_subfunction" class="registered_link"></div>
+
+The `FUNCTION` clause specified in the declaration section defines and names a subfunction local to that block.
+
+- The term *block* refers to the SPL block structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks are the structures for standalone procedures and functions, anonymous blocks, subprograms, triggers, packages, and object type methods.
+
+- The phrase *the identifier is local to the block* means that the identifier (that is, a variable, cursor, type, or subprogram) is declared in the declaration section of that block and is therefore accessible by the SPL code in the executable section and optional exception section of that block.
+
+## Declaring a subfunction
+
+```sql
+FUNCTION <name> [ (<parameters>) ]
+RETURN <data_type>
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+Where:
+
+-  `name` is the identifier of the subfunction.
+
+-  `parameters` is a list of formal parameters.
+
+-  `data_type` is the data type of the value returned by the function’s `RETURN` statement.
+
+-  `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the subfunction as an autonomous transaction.
+
+-  `declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations.
+
+-  `statements` are SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+## Example: Recursive subfunction
+
+This example shows the use of a recursive subfunction:
+
+```sql
+DECLARE
+    FUNCTION factorial (
+        n           BINARY_INTEGER
+    ) RETURN BINARY_INTEGER
+    IS
+    BEGIN
+        IF n = 1 THEN
+            RETURN n;
+        ELSE
+            RETURN n * factorial(n-1);
+        END IF;
+    END factorial;
+BEGIN
+    FOR i IN 1..5 LOOP
+        DBMS_OUTPUT.PUT_LINE(i || '! = ' || factorial(i));
+    END LOOP;
+END;
+```
+
+The following is the output:
+
+```sql
+__OUTPUT__
+1! = 1
+2! = 2
+3! = 6
+4! = 24
+5! = 120
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx
new file mode 100644
index 00000000000..6ba631fead5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships.mdx
@@ -0,0 +1,81 @@
+---
+title: "Declaring block relationships"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/03_block_relationships/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="block_relationships" class="registered_link"></div>
+
+You can declare the relationship between blocks in an SPL program. The ability to invoke subprograms and access identifiers declared in a block depends on this relationship.
+
+## About block relationships
+
+The following are the basic terms:
+
+-   A *block* is the basic SPL structure consisting of an optional declaration section, a mandatory executable section, and an optional exception section. Blocks implement standalone procedure and function programs, anonymous blocks, triggers, packages, and subprocedures and subfunctions.
+-   An identifier (variable, cursor, type, or subprogram) *local to a block* means that it's declared in the declaration section of the given block. You can access such local identifiers from the executable section and optional exception section of the block.
+-   The *parent block* contains the declaration of another block, that is, the *child block*.
+-   *Descendent blocks* are the set of blocks forming the child relationship starting from a given parent block.
+-   *Ancestor blocks* are the set of blocks forming the parental relationship starting from a given child block.
+-   The set of descendent (ancestor) blocks form a *hierarchy*.
+-   The *level* is an ordinal number of a given block from the highest ancestor block. For example, given a standalone procedure, the subprograms declared in the declaration section of this procedure are all at the same level, such as level 1. Additional subprograms in the declaration section of the subprograms declared in the standalone procedure are at the next level, that is, level 2.
+-   The *sibling blocks* are the set of blocks that have the same parent block, that is, they are all locally declared in the same block. Sibling blocks are at the same level relative to each other.
+
+## Example 
+
+The following schematic of a set of procedure declaration sections provides an example of a set of blocks and their relationships to their surrounding blocks.
+
+The two vertical lines on the left-hand side of the blocks indicate there are two pairs of sibling blocks. `block_1a` and `block_1b` is one pair, and `block_2a` and `block_2b` is the second pair.
+
+The relationship of each block with its ancestors is shown on the right-hand side of the blocks. Three hierarchical paths are formed when progressing up the hierarchy from the lowest-level child blocks. The first consists of `block_0`, `block_1a`, `block_2a`, and `block_3`. The second is `block_0`, `block_1a`, and `block_2b`. The third is `block_0`, `block_1b`, and `block_2b`.
+
+```sql
+CREATE PROCEDURE block_0
+IS
+        .
+    +---- PROCEDURE block_1a    ------- Local to block_0
+    |     IS
+    |         .                          |
+    |         .                          |
+    |         .                          |
+    |     +-- PROCEDURE block_2a   ---- Local to block_1a and descendant
+    |     |   IS                          of block_0
+    |     |       .                      |
+    |     |       .                      |
+    |     |       .                      |
+    |     |      PROCEDURE block_3   -- Local to block_2a and descendant
+    |     |      IS                       of block_1a, and block_0
+    | Siblings        .                  |
+    |     |           .                  |
+    |     |           .                  |
+    |     |       END block_3;           |
+    |     |   END block_2a;              |
+    |     +-- PROCEDURE block_2b   ---- Local to block_1a and descendant
+    |     |   IS                          of block_0
+ Siblings |       ,                      |
+    |     |       .                      |
+    |     |       .                      |
+    |     +-- END block_2b;              |
+    |                                    |
+    |      END block_1a;        ---------+
+    +----  PROCEDURE block_1b;   ------- Local to block_0
+    |      IS
+    |          .                         |
+    |          .                         |
+    |          .                         |
+    |          PROCEDURE block_2b   ---- Local to block_1b and descendant
+    |          IS                          of block_0
+    |              .                     |
+    |              .                     |
+    |              .                     |
+    |          END block_2b;             |
+    |                                    |
+    +----  END block_1b;        ---------+
+BEGIN
+      .
+      .
+      .
+END block_0;
+```
+
+The rules for invoking subprograms based on block location are described starting with [Invoking subprograms](04_invoking_subprograms/#invoking_subprograms). The rules for accessing variables based on block location are described in [Accessing subprogram variables](07_accessing_subprogram_variables/#accessing_subprogram_variables).
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx
new file mode 100644
index 00000000000..eb240543652
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms.mdx
@@ -0,0 +1,355 @@
+---
+title: "Invoking subprograms"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/04_invoking_subprograms/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="invoking_subprograms" class="registered_link"></div>
+
+Invoke a subprogram in the same manner as a standalone procedure or function by specifying its name and any actual parameters.
+
+You can invoke the subprogram with zero, one, or more qualifiers. Qualifiers are the names of the parent subprograms or labeled anonymous blocks forming the ancestor hierarchy from which the subprogram was declared.
+
+## Overview of subprograms
+
+Invoke the subprogram using a dot-separated list of qualifiers ending with the subprogram name and any of its arguments:
+
+```text
+[[<qualifier_1>.][...]<qualifier_n>.]<subprog> [(<arguments>)]
+```
+### Specifying qualifiers
+
+If specified, `qualifier_n` is the subprogram in which `subprog` was declared in its declaration section. The preceding list of qualifiers must reside in a continuous path up the hierarchy from `qualifier_n` to `qualifier_1`. `qualifier_1` can be any ancestor subprogram in the path as well as any of the following:
+
+-   Standalone procedure name containing the subprogram
+-   Standalone function name containing the subprogram
+-   Package name containing the subprogram
+-   Object type name containing the subprogram in an object type method
+-   An anonymous block label included prior to the `DECLARE` keyword if a declaration section exists, or prior to the `BEGIN` keyword if there is no declaration section
+
+!!! Note
+    `qualifier_1` can't be a schema name. If it is, an error is thrown when invoking the subprogram. This EDB Postgres Advanced Server restriction isn't compatible with Oracle databases, which allow the use of the schema name as a qualifier.
+
+`arguments` is the list of actual parameters to pass to the subprocedure or subfunction.
+
+### Searching for subprograms
+
+When you invoke the subprogram, the search for the subprogram occurs as follows:
+
+-   The invoked subprogram name of its type (that is, subprocedure or subfunction) along with any qualifiers in the specified order (referred to as the invocation list) is used to find a matching set of blocks residing in the same hierarchical order. The search begins in the block hierarchy where the lowest level is the block from where the subprogram is invoked. The declaration of the subprogram must be in the SPL code prior to the code line where it's invoked when the code is observed from top to bottom. (You can achieve an exception to this requirement using a forward declaration. See [Using forward declarations](05_using_forward_declarations/#using_forward_declarations).)
+-   If the invocation list doesn't match the hierarchy of blocks starting from the block where the subprogram is invoked, a comparison is made by matching the invocation list starting with the parent of the previous starting block. In other words, the comparison progresses up the hierarchy.
+-   If there are sibling blocks of the ancestors, the invocation list comparison also includes the hierarchy of the sibling blocks but always comparing in an upward level. It doesn't compare the descendants of the sibling blocks.
+-   This comparison process continues up the hierarchies until the first complete match is found, in which case the located subprogram is invoked. The formal parameter list of the matched subprogram must comply with the actual parameter list specified for the invoked subprogram. Otherwise an error occurs when invoking the subprogram.
+-   If no match is found after searching up to the standalone program, then an error is thrown when invoking the subprogram.
+
+!!! Note
+    The EDB Postgres Advanced Server search algorithm for subprogram invocation isn't completely compatible with Oracle databases. For Oracle, the search looks for the first match of the first qualifier (that is, `qualifier_1`). When such a match is found, all remaining qualifiers, the subprogram name, subprogram type, and arguments of the invocation must match the hierarchy content where the matching first qualifier is found. Otherwise an error is thrown. For EDB Postgres Advanced Server, a match isn't found unless all qualifiers, the subprogram name, and the subprogram type of the invocation match the hierarchy content. If such an exact match isn't initially found, EDB Postgres Advanced Server continues the search progressing up the hierarchy.
+
+You can access the location of subprograms relative to the block from where the invocation is made as follows:
+
+-   You can invoke subprograms declared in the local block from the executable section or the exception section of the same block.
+-   You can invoke subprograms declared in the parent or other ancestor blocks from the child block of the parent or other ancestors.
+-   You can call subprograms declared in sibling blocks from a sibling block or from any descendent block of the sibling.
+
+However, you can't access the following locations of subprograms relative to the block from where the invocation is made:
+
+-   Subprograms declared in blocks that are descendants of the block from where the invocation is attempted
+-   Subprograms declared in blocks that are descendants of a sibling block from where the invocation is attempted
+
+## Invoking locally declared subprograms
+
+This example contains a single hierarchy of blocks contained in the standalone procedure `level_0`. In the executable section of the procedure `level_1a`, the means of invoking the local procedure `level_2a` are shown, with and without qualifiers.
+
+Access to the descendant of the local procedure `level_2a`, which is the procedure `level_3a`, isn't permitted, with or without qualifiers. These calls are commented out in the example.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    PROCEDURE level_1a
+    IS
+        PROCEDURE level_2a
+        IS
+            PROCEDURE level_3a
+            IS
+            BEGIN
+                DBMS_OUTPUT.PUT_LINE('........ BLOCK level_3a');
+                DBMS_OUTPUT.PUT_LINE('........ END BLOCK level_3a');
+            END level_3a;
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END level_2a;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        level_2a;                              -- Local block called
+        level_1a.level_2a;                     -- Qualified local block called
+        level_0.level_1a.level_2a;             -- Double qualified local block called
+--        level_3a;                            -- Error - Descendant of local block
+--        level_2a.level_3a;                   -- Error - Descendant of local block
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    level_1a;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+When the standalone procedure is invoked, the output is the following. This output indicates that the procedure `level_2a` is successfully invoked from the calls in the executable section of the procedure `level_1a`:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. BLOCK level_1a
+...... BLOCK level_2a
+...... END BLOCK level_2a
+...... BLOCK level_2a
+...... END BLOCK level_2a
+...... BLOCK level_2a
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+END BLOCK level_0
+```
+
+If you try to run the procedure `level_0` with any of the calls to the descendent block uncommented, then an error occurs.
+
+## Invoking subprograms declared in ancestor blocks
+
+This example shows how to invoke subprograms that are declared in parent and other ancestor blocks relative to the block where the invocation is made.
+
+In this example, the executable section of procedure `level_3a` invokes the procedure `level_2a`, which is its parent block. `v_cnt` is used to avoid an infinite loop.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+  v_cnt           NUMBER(2) := 0;
+  PROCEDURE level_1a
+  IS
+      PROCEDURE level_2a
+      IS
+          PROCEDURE level_3a
+          IS
+          BEGIN
+              DBMS_OUTPUT.PUT_LINE('........ BLOCK level_3a');
+              v_cnt := v_cnt + 1;
+              IF v_cnt < 2 THEN
+                  level_2a;                  -- Parent block called
+              END IF;
+              DBMS_OUTPUT.PUT_LINE('........ END BLOCK level_3a');
+          END level_3a;
+      BEGIN
+          DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+          level_3a;                          -- Local block called
+          DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+      END level_2a;
+  BEGIN
+      DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+      level_2a;                              -- Local block called
+      DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+  END level_1a;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    level_1a;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. BLOCK level_1a
+...... BLOCK level_2a
+........ BLOCK level_3a
+...... BLOCK level_2a
+........ BLOCK level_3a
+........ END BLOCK level_3a
+...... END BLOCK level_2a
+........ END BLOCK level_3a
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+END BLOCK level_0
+```
+
+In a similar example, the executable section of the procedure `level_3a` invokes the procedure `level_1a`, which is further up the ancestor hierarchy. `v_cnt` is again used to avoid an infinite loop.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    v_cnt           NUMBER(2) := 0;
+    PROCEDURE level_1a
+    IS
+        PROCEDURE level_2a
+        IS
+            PROCEDURE level_3a
+            IS
+            BEGIN
+                DBMS_OUTPUT.PUT_LINE('........ BLOCK level_3a');
+                v_cnt := v_cnt + 1;
+                IF v_cnt < 2 THEN
+                    level_1a;                  -- Ancestor block called
+                END IF;
+                DBMS_OUTPUT.PUT_LINE('........ END BLOCK level_3a');
+            END level_3a;
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            level_3a;                          -- Local block called
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END level_2a;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        level_2a;                              -- Local block called
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    level_1a;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. BLOCK level_1a
+...... BLOCK level_2a
+........ BLOCK level_3a
+.. BLOCK level_1a
+...... BLOCK level_2a
+........ BLOCK level_3a
+........ END BLOCK level_3a
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+........ END BLOCK level_3a
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+END BLOCK level_0
+```
+
+## Invoking subprograms declared in sibling blocks
+
+These examples show how you can invoke subprograms that are declared in a sibling block relative to the local, parent, or other ancestor blocks from where the invocation of the subprogram is made.
+
+In this example, the executable section of the procedure `level_1b` invokes the procedure `level_1a`, which is its sibling block. Both are local to the standalone procedure `level_0`.
+
+Invoking `level_2a` or, equivalently, `level_1a.level_2a` from the procedure `level_1b` is commented out as this call results in an error. Invoking a descendent subprogram (`level_2a`) of a sibling block (`level_1a`) isn't permitted.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    v_cnt     NUMBER(2) := 0;
+    PROCEDURE level_1a
+    IS
+        PROCEDURE level_2a
+        IS
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END level_2a;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+    PROCEDURE level_1b
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1b');
+        level_1a;                              -- Sibling block called
+--      level_2a;                              -- Error – Descendant of sibling block
+--      level_1a.level_2a;                     -- Error - Descendant of sibling block
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1b');
+    END level_1b;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    level_1b;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. BLOCK level_1b
+.. BLOCK level_1a
+.. END BLOCK level_1a
+.. END BLOCK level_1b
+END BLOCK level_0
+```
+
+In this example, the procedure `level_1a` is successfully invoked. It's the sibling of the procedure `level_1b`, which is an ancestor of the procedure `level_3b`.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    PROCEDURE level_1a
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+    PROCEDURE level_1b
+    IS
+        PROCEDURE level_2b
+        IS
+            PROCEDURE level_3b
+            IS
+            BEGIN
+                DBMS_OUTPUT.PUT_LINE('........ BLOCK level_3b');
+                level_1a;                      -- Ancestor's sibling block called
+                level_0.level_1a;              -- Qualified ancestor's sibling block
+                DBMS_OUTPUT.PUT_LINE('........ END BLOCK level_3b');
+            END level_3b;
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2b');
+            level_3b;                          -- Local block called
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2b');
+        END level_2b;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1b');
+        level_2b;                              -- Local block called
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1b');
+    END level_1b;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    level_1b;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. BLOCK level_1b
+...... BLOCK level_2b
+........ BLOCK level_3b
+.. BLOCK level_1a
+.. END BLOCK level_1a
+.. BLOCK level_1a
+.. END BLOCK level_1a
+........ END BLOCK level_3b
+...... END BLOCK level_2b
+.. END BLOCK level_1b
+END BLOCK level_0
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx
new file mode 100644
index 00000000000..b594c2db4b9
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations.mdx
@@ -0,0 +1,57 @@
+---
+title: "Using forward declarations"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/05_using_forward_declarations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_forward_declarations" class="registered_link"></div>
+
+When you want to invoke a subprogram, you must declare it in the hierarchy of blocks in the standalone program prior to where you invoke it. In other words, when scanning the SPL code from beginning to end, the subprogram declaration must appear before its invocation.
+
+However, you can construct the SPL code so that the full declaration of the subprogram appears in the SPL code after the point in the code where it's invoked. (The full declaration includes its optional declaration section, its mandatory executable section, and optional exception section.) 
+
+You can do this by inserting a *forward declaration* in the SPL code prior to its invocation. The forward declaration is the specification of a subprocedure or subfunction name, formal parameters, and return type if it's a subfunction.
+
+You must specify the full subprogram consisting of the optional declaration section, the executable section, and the optional exception section in the same declaration section as the forward declaration. However it can appear following other subprogram declarations that invoke this subprogram with the forward declaration.
+
+Typical use of a forward declaration is when two subprograms invoke each other:
+
+```sql
+DECLARE
+    FUNCTION add_one (
+        p_add       IN NUMBER
+    ) RETURN NUMBER;
+    FUNCTION test_max (
+        p_test      IN NUMBER)
+    RETURN NUMBER
+    IS
+    BEGIN
+        IF p_test < 5 THEN
+            RETURN add_one(p_test);
+        END IF;
+        DBMS_OUTPUT.PUT('Final value is ');
+        RETURN p_test;
+    END;
+    FUNCTION add_one (
+        p_add       IN NUMBER)
+    RETURN NUMBER
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Increase by 1');
+        RETURN test_max(p_add + 1);
+    END;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE(test_max(3));
+END;
+```
+
+Subfunction `test_max` invokes subfunction `add_one`, which also invokes subfunction `test_max`. A forward declaration is required for one of the subprograms, which is implemented for `add_one` at the beginning of the anonymous block declaration section.
+
+The resulting output from the anonymous block is as follows:
+
+```sql
+__OUTPUT__
+Increase by 1
+Increase by 1
+Final value is 5
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx
new file mode 100644
index 00000000000..9d629226023
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms.mdx
@@ -0,0 +1,165 @@
+---
+title: "Overloading subprograms"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/06_overloading_subprograms/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="overloading_subprograms" class="registered_link"></div>
+
+Generally, subprograms of the same type (subprocedure or subfunction) with the same name and same formal parameter specification can appear multiple times in the same standalone program as long as they aren't sibling blocks (that is, the subprograms aren't declared in the same local block).
+
+You can invoke each subprogram individually depending on the use of qualifiers and the location where the subprogram invocation is made.
+
+However, it's possible to declare subprograms, even as siblings, that are of the same subprogram type and name as long as certain aspects of the formal parameters differ. These characteristics (subprogram type, name, and formal parameter specification) are generally known as a program’s *signature*.
+
+The declaration of multiple subprograms where the signatures are identical except for certain aspects of the formal parameter specification is referred to as subprogram *overloading*.
+
+## Requirements
+
+The particular overloaded subprogram to invoke is determined by a match of the actual parameters specified by the subprogram invocation and the formal parameter lists of the overloaded subprograms.
+
+Any of the following differences permit overloaded subprograms:
+
+-   The number of formal parameters are different.
+-   At least one pair of data types of the corresponding formal parameters (that is, compared according to the same order of appearance in the formal parameter list) are different but aren't aliases. 
+
+The following differences alone don't permit overloaded subprograms:
+
+-   Different formal parameter names
+-   Different parameter modes (`IN`, `IN OUT`, `OUT`) for the corresponding formal parameters
+-   For subfunctions, different data types in the `RETURN` clause
+
+One of the differences allowing overloaded subprograms is different data types.
+
+## Using aliases
+
+Certain data types have alternative names referred to as *aliases*, which can be used for the table definition.
+
+For example, you can specify fixed-length character data types as `CHAR` or `CHARACTER`. You can specify variable-length character data types as `CHAR VARYING`, `CHARACTER VARYING`, `VARCHAR`, or `VARCHAR2`. For integers, there are `BINARY_INTEGER`, `PLS_INTEGER`, and `INTEGER` data types. For numbers, there are `NUMBER`, `NUMERIC`, `DEC`, and `DECIMAL` data types.
+
+For detailed information about the data types supported by EDB Postgres Advanced Server, see [Data types](../../../../reference/sql_reference/02_data_types/).
+
+Thus, when attempting to create overloaded subprograms, the formal parameter data types aren't considered different if the specified data types are aliases of each other.
+
+You can determine if certain data types are aliases of other types by displaying the table definition containing the data types.
+
+## Example: Data types and aliases
+
+The following table definition contains some data types and their aliases:
+
+```sql
+CREATE TABLE data_type_aliases (
+    dt_BLOB             BLOB,
+    dt_LONG_RAW         LONG RAW,
+    dt_RAW              RAW(4),
+    dt_BYTEA            BYTEA,
+    dt_INTEGER          INTEGER,
+    dt_BINARY_INTEGER   BINARY_INTEGER,
+    dt_PLS_INTEGER      PLS_INTEGER,
+    dt_REAL             REAL,
+    dt_DOUBLE_PRECISION DOUBLE PRECISION,
+    dt_FLOAT            FLOAT,
+    dt_NUMBER           NUMBER,
+    dt_DECIMAL          DECIMAL,
+    dt_NUMERIC          NUMERIC,
+    dt_CHAR             CHAR,
+    dt_CHARACTER        CHARACTER,
+    dt_VARCHAR2         VARCHAR2(4),
+    dt_CHAR_VARYING     CHAR VARYING(4),
+    dt_VARCHAR          VARCHAR(4)
+);
+```
+
+Using the PSQL `\d` command to display the table definition, the Type column displays the data type internally assigned to each column based on its data type in the table definition.
+
+```sql
+\d data_type_aliases
+       Column        |         Type         | Modifiers
+---------------------+----------------------+-----------
+ dt_blob             | bytea                |
+ dt_long_raw         | bytea                |
+ dt_raw              | bytea(4)             |
+ dt_bytea            | bytea                |
+ dt_integer          | integer              |
+ dt_binary_integer   | integer              |
+ dt_pls_integer      | integer              |
+ dt_real             | real                 |
+ dt_double_precision | double precision     |
+ dt_float            | double precision     |
+ dt_number           | numeric              |
+ dt_decimal          | numeric              |
+ dt_numeric          | numeric              |
+ dt_char             | character(1)         |
+ dt_character        | character(1)         |
+ dt_varchar2         | character varying(4) |
+ dt_char_varying     | character varying(4) |
+ dt_varchar          | character varying(4) |
+```
+
+In the example, the base set of data types are `bytea`, `integer`, `real`, `double precision`, `numeric`, `character`, and `character varying`.
+
+When attempting to declare overloaded subprograms, a pair of formal parameter data types that are aliases aren't enough to allow subprogram overloading. Thus, parameters with data types `INTEGER` and `PLS_INTEGER` can't overload a pair of subprograms. However, data types `INTEGER` and `REAL`, `INTEGER` and `FLOAT`, or `INTEGER` and `NUMBER` can overload the subprograms.
+
+!!! Note
+    The overloading rules based on formal parameter data types aren't compatible with Oracle databases. Generally, the EDB Postgres Advanced Server rules are more flexible, and certain combinations are allowed in EDB Postgres Advanced Server that result in an error when attempting to create the procedure or function in Oracle databases.
+
+For certain pairs of data types used for overloading, you might need to cast the arguments specified by the subprogram invocation to avoid an error encountered during runtime of the subprogram. Invoking a subprogram must include the actual parameter list that can specifically identify the data types. Certain pairs of overloaded data types might require the `CAST` function to explicitly identify data types. For example, pairs of overloaded data types that might require casting during the invocation are `CHAR` and `VARCHAR2`, or `NUMBER` and `REAL`.
+
+## Example: Overloaded subfunctions
+
+This example shows a group of overloaded subfunctions invoked from an anonymous block. The executable section of the anonymous block contains the use of the `CAST` function to invoke overloaded functions with certain data types.
+
+```sql
+DECLARE
+    FUNCTION add_it (
+        p_add_1     IN BINARY_INTEGER,
+        p_add_2     IN BINARY_INTEGER
+    ) RETURN VARCHAR2
+    IS
+    BEGIN
+        RETURN 'add_it BINARY_INTEGER: ' || TO_CHAR(p_add_1 + p_add_2,9999.9999);
+    END add_it;
+    FUNCTION add_it (
+        p_add_1     IN NUMBER,
+        p_add_2     IN NUMBER
+    ) RETURN VARCHAR2
+    IS
+    BEGIN
+        RETURN 'add_it NUMBER: ' || TO_CHAR(p_add_1 + p_add_2,999.9999);
+    END add_it;
+    FUNCTION add_it (
+        p_add_1     IN REAL,
+        p_add_2     IN REAL
+    ) RETURN VARCHAR2
+    IS
+    BEGIN
+        RETURN 'add_it REAL: ' || TO_CHAR(p_add_1 + p_add_2,9999.9999);
+    END add_it;
+    FUNCTION add_it (
+        p_add_1     IN DOUBLE PRECISION,
+        p_add_2     IN DOUBLE PRECISION
+    ) RETURN VARCHAR2
+    IS
+    BEGIN
+        RETURN 'add_it DOUBLE PRECISION: ' || TO_CHAR(p_add_1 + p_add_2,9999.9999);
+    END add_it;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE(add_it (25, 50));
+    DBMS_OUTPUT.PUT_LINE(add_it (25.3333, 50.3333));
+    DBMS_OUTPUT.PUT_LINE(add_it (TO_NUMBER(25.3333), TO_NUMBER(50.3333)));
+    DBMS_OUTPUT.PUT_LINE(add_it (CAST('25.3333' AS REAL), CAST('50.3333' AS REAL)));
+    DBMS_OUTPUT.PUT_LINE(add_it (CAST('25.3333' AS DOUBLE PRECISION),
+        CAST('50.3333' AS DOUBLE PRECISION)));
+END;
+```
+
+The following is the output displayed from the anonymous block:
+
+```sql
+__OUTPUT__
+add_it BINARY_INTEGER:    75.0000
+add_it NUMBER:   75.6666
+add_it NUMBER:   75.6666
+add_it REAL:    75.6666
+add_it DOUBLE PRECISION:    75.6666
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx
new file mode 100644
index 00000000000..35712c77b2d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables.mdx
@@ -0,0 +1,411 @@
+---
+title: "Accessing subprogram variables"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/07_accessing_subprogram_variables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="accessing_subprogram_variables" class="registered_link"></div>
+
+You can access variables declared in blocks, such as subprograms or anonymous blocks, from the executable section or the exception section of other blocks depending on their relative location.
+
+Accessing a variable means being able to reference it in a SQL statement or an SPL statement as you can with any local variable.
+
+!!! Note
+    If the subprogram signature contains formal parameters, you can access these in the same way as local variables of the subprogram. All discussion related to variables of a subprogram also applies to formal parameters of the subprogram.
+
+Accessing variables includes not only those defined as a data type but also includes others such as record types, collection types, and cursors.
+
+At most one qualifier can access the variable. The qualifier is the name of the subprogram or labeled anonymous block in which the variable was locally declared.
+
+## Syntax 
+
+The syntax to reference a variable is:
+
+```text
+[<qualifier>.]<variable>
+```
+
+If specified, `qualifier` is the subprogram or labeled anonymous block in which `variable` was declared in its declaration section (that is, it's a local variable).
+
+!!! Note
+    In EDB Postgres Advanced Server, in only one circumstance are two qualifiers are permitted. This scenario is for accessing public variables of packages where you can specify the reference in the following format:
+
+```text
+schema_name.package_name.public_variable_name
+```
+
+For more information about supported package syntax, see [Built-in packages](../../../../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/).
+
+## Requirements 
+
+You can access variables in the following ways:
+
+-   Variables can be accessed as long as the block in which the variable was locally declared is in the ancestor hierarchical path starting from the block containing the reference to the variable. Such variables declared in ancestor blocks are referred to as *global variables*.
+-   If a reference to an unqualified variable is made, the first attempt is to locate a local variable of that name. If such a local variable doesn't exist, then the search for the variable is made in the parent of the current block, and so forth, proceeding up the ancestor hierarchy. If such a variable isn't found, then an error occurs when the subprogram is invoked.
+-   If a reference to a qualified variable is made, the same search process is performed but searching for the first match of the subprogram or labeled anonymous block that contains the local variable. The search proceeds up the ancestor hierarchy until a match is found. If such a match isn't found, then an error occurs when the subprogram is invoked.
+
+You can't access the following location of variables relative to the block from where the reference to the variable is made:
+
+-   Variables declared in a descendent block
+-   Variables declared in a sibling block, a sibling block of an ancestor block, or any descendants within the sibling block
+
+!!! Note
+    The EDB Postgres Advanced Server process for accessing variables isn't compatible with Oracle databases. For Oracle, you can specify any number of qualifiers, and the search is based on the first match of the first qualifier in a similar manner to the Oracle matching algorithm for invoking subprograms.
+
+## Accessing variables with the same name
+
+This example shows similar access attempts when all variables in all blocks have the same name:
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    v_common        VARCHAR2(20) := 'Value from level_0';
+    PROCEDURE level_1a
+    IS
+        v_common    VARCHAR2(20) := 'Value from level_1a';
+        PROCEDURE level_2a
+        IS
+            v_common    VARCHAR2(20) := 'Value from level_2a';
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            DBMS_OUTPUT.PUT_LINE('........ v_common: ' || v_common);
+            DBMS_OUTPUT.PUT_LINE('........ level_2a.v_common: ' || level_2a.v_common);
+            DBMS_OUTPUT.PUT_LINE('........ level_1a.v_common: ' || level_1a.v_common);
+            DBMS_OUTPUT.PUT_LINE('........ level_0.v_common: ' || level_0.v_common);
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END level_2a;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        DBMS_OUTPUT.PUT_LINE('.... v_common: ' || v_common);
+        DBMS_OUTPUT.PUT_LINE('.... level_0.v_common: ' || level_0.v_common);
+        level_2a;
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+    PROCEDURE level_1b
+    IS
+        v_common    VARCHAR2(20) := 'Value from level_1b';
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1b');
+        DBMS_OUTPUT.PUT_LINE('.... v_common: ' || v_common);
+        DBMS_OUTPUT.PUT_LINE('.... level_0.v_common : ' || level_0.v_common);
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1b');
+    END level_1b;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    DBMS_OUTPUT.PUT_LINE('.. v_common: ' || v_common);
+    level_1a;
+    level_1b;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output showing the content of each variable when the procedure is invoked:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. v_common: Value from level_0
+.. BLOCK level_1a
+.... v_common: Value from level_1a
+.... level_0.v_common: Value from level_0
+...... BLOCK level_2a
+........ v_common: Value from level_2a
+........ level_2a.v_common: Value from level_2a
+........ level_1a.v_common: Value from level_1a
+........ level_0.v_common: Value from level_0
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+.. BLOCK level_1b
+.... v_common: Value from level_1b
+.... level_0.v_common : Value from level_0
+.. END BLOCK level_1b
+END BLOCK level_0
+```
+
+## Using labels to qualify access to variables
+
+You can also use the labels on anonymous blocks to qualify access to variables. This example shows variable access in a set of nested anonymous blocks:
+
+```sql
+DECLARE
+    v_common        VARCHAR2(20) := 'Value from level_0';
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    DBMS_OUTPUT.PUT_LINE('.. v_common: ' || v_common);
+    <<level_1a>>
+    DECLARE
+        v_common    VARCHAR2(20) := 'Value from level_1a';
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        DBMS_OUTPUT.PUT_LINE('.... v_common: ' || v_common);
+        <<level_2a>>
+        DECLARE
+            v_common    VARCHAR2(20) := 'Value from level_2a';
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            DBMS_OUTPUT.PUT_LINE('........ v_common: ' || v_common);
+            DBMS_OUTPUT.PUT_LINE('........ level_1a.v_common: ' || level_1a.v_common);
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END;
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END;
+    <<level_1b>>
+    DECLARE
+        v_common    VARCHAR2(20) := 'Value from level_1b';
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1b');
+        DBMS_OUTPUT.PUT_LINE('.... v_common: ' || v_common);
+        DBMS_OUTPUT.PUT_LINE('.... level_1b.v_common: ' || level_1b.v_common);
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1b');
+    END;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END;
+```
+
+The following is the output showing the content of each variable when the anonymous block is invoked:
+
+```sql
+__OUTPUT__
+BLOCK level_0
+.. v_common: Value from level_0
+.. BLOCK level_1a
+.... v_common: Value from level_1a
+...... BLOCK level_2a
+........ v_common: Value from level_2a
+........ level_1a.v_common: Value from level_1a
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+.. BLOCK level_1b
+.... v_common: Value from level_1b
+.... level_1b.v_common: Value from level_1b
+.. END BLOCK level_1b
+END BLOCK level_0
+```
+## Examples
+
+### Example: Accessing record types in parent blocks
+
+This example is an object type whose object type method, `display_emp`, contains the record type `emp_typ` and the subprocedure `emp_sal_query`. The record variable `r_emp` declared locally to `emp_sal_query` can access the record type `emp_typ` declared in the parent block `display_emp`.
+
+```sql
+CREATE OR REPLACE TYPE emp_pay_obj_typ AS OBJECT
+(
+    empno           NUMBER(4),
+    MEMBER PROCEDURE display_emp(SELF IN OUT emp_pay_obj_typ)
+);
+
+CREATE OR REPLACE TYPE BODY emp_pay_obj_typ AS
+    MEMBER PROCEDURE display_emp (SELF IN OUT emp_pay_obj_typ)
+    IS
+        TYPE emp_typ IS RECORD (
+            ename           emp.ename%TYPE,
+            job             emp.job%TYPE,
+            hiredate        emp.hiredate%TYPE,
+            sal             emp.sal%TYPE,
+            deptno          emp.deptno%TYPE
+         );
+        PROCEDURE emp_sal_query (
+            p_empno         IN emp.empno%TYPE
+        )
+        IS
+            r_emp           emp_typ;
+            v_avgsal        emp.sal%TYPE;
+        BEGIN
+            SELECT ename, job, hiredate, sal, deptno
+                INTO r_emp.ename, r_emp.job, r_emp.hiredate, r_emp.sal, r_emp.deptno
+                FROM emp WHERE empno = p_empno;
+            DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+            DBMS_OUTPUT.PUT_LINE('Name       : ' || r_emp.ename);
+            DBMS_OUTPUT.PUT_LINE('Job        : ' || r_emp.job);
+            DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || r_emp.hiredate);
+            DBMS_OUTPUT.PUT_LINE('Salary     : ' || r_emp.sal);
+            DBMS_OUTPUT.PUT_LINE('Dept #     : ' || r_emp.deptno);
+
+            SELECT AVG(sal) INTO v_avgsal
+            FROM emp WHERE deptno = r_emp.deptno;
+            IF r_emp.sal > v_avgsal THEN
+                DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+                    || 'department average of ' || v_avgsal);
+            ELSE
+                DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+                    || 'department average of ' || v_avgsal);
+            END IF;
+        END;
+    BEGIN
+        emp_sal_query(SELF.empno);
+    END;
+END;
+```
+
+The following is the output displayed when an instance of the object type is created and the procedure `display_emp` is invoked:
+
+```sql
+DECLARE
+    v_emp          EMP_PAY_OBJ_TYP;
+BEGIN
+    v_emp := emp_pay_obj_typ(7900);
+    v_emp.display_emp;
+END;
+__OUTPUT__
+Employee # : 7900
+Name       : JAMES
+Job        : CLERK
+Hire Date  : 03-DEC-81 00:00:00
+Salary     : 950.00
+Dept #     : 30
+Employee's salary does not exceed the department average of 1566.67
+```
+### Example: Accessing an upper-level procedure
+
+This example is a package with three levels of subprocedures. A record type, collection type, and cursor type declared in the upper-level procedure can be accessed by the descendent subprocedure.
+
+```sql
+CREATE OR REPLACE PACKAGE emp_dept_pkg
+IS
+    PROCEDURE display_emp (
+        p_deptno        NUMBER
+    );
+END;
+
+CREATE OR REPLACE PACKAGE BODY emp_dept_pkg
+IS
+    PROCEDURE display_emp (
+        p_deptno        NUMBER
+    )
+    IS
+        TYPE emp_rec_typ IS RECORD (
+            empno           emp.empno%TYPE,
+            ename           emp.ename%TYPE
+        );
+        TYPE emp_arr_typ IS TABLE OF emp_rec_typ INDEX BY BINARY_INTEGER;
+        TYPE emp_cur_type IS REF CURSOR RETURN emp_rec_typ;
+        PROCEDURE emp_by_dept (
+            p_deptno        emp.deptno%TYPE
+        )
+        IS
+            emp_arr         emp_arr_typ;
+            emp_refcur      emp_cur_type;
+            i               BINARY_INTEGER := 0;
+            PROCEDURE display_emp_arr
+            IS
+            BEGIN
+                DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+                DBMS_OUTPUT.PUT_LINE('-----    -------');
+                FOR j IN emp_arr.FIRST .. emp_arr.LAST LOOP
+                    DBMS_OUTPUT.PUT_LINE(emp_arr(j).empno || '     ' ||
+                        emp_arr(j).ename);
+                END LOOP;
+            END display_emp_arr;
+        BEGIN
+            OPEN emp_refcur FOR SELECT empno, ename FROM emp WHERE deptno = p_deptno;
+            LOOP
+                i := i + 1;
+                FETCH emp_refcur INTO emp_arr(i).empno, emp_arr(i).ename;
+                EXIT WHEN emp_refcur%NOTFOUND;
+            END LOOP;
+            CLOSE emp_refcur;
+            display_emp_arr;
+        END emp_by_dept;
+    BEGIN
+        emp_by_dept(p_deptno);
+    END;
+END;
+```
+
+The following is the output displayed when the top-level package procedure is invoked:
+
+```sql
+BEGIN
+    emp_dept_pkg.display_emp(20);
+END;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7566     JONES
+7788     SCOTT
+7876     ADAMS
+7902     FORD
+```
+
+### Example: Accessing variables in blocks
+
+This example shows how variables in various blocks are accessed, with and without qualifiers. The lines that are commented out show attempts to access variables that result in an error.
+
+```sql
+CREATE OR REPLACE PROCEDURE level_0
+IS
+    v_level_0       VARCHAR2(20) := 'Value from level_0';
+    PROCEDURE level_1a
+    IS
+        v_level_1a  VARCHAR2(20) := 'Value from level_1a';
+        PROCEDURE level_2a
+        IS
+            v_level_2a      VARCHAR2(20) := 'Value from level_2a';
+        BEGIN
+            DBMS_OUTPUT.PUT_LINE('...... BLOCK level_2a');
+            DBMS_OUTPUT.PUT_LINE('........ v_level_2a: ' || v_level_2a);
+            DBMS_OUTPUT.PUT_LINE('........ v_level_1a: ' || v_level_1a);
+            DBMS_OUTPUT.PUT_LINE('........ level_1a.v_level_1a: ' || level_1a.v_level_1a);
+            DBMS_OUTPUT.PUT_LINE('........ v_level_0: ' || v_level_0);
+            DBMS_OUTPUT.PUT_LINE('........ level_0.v_level_0: ' || level_0.v_level_0);
+            DBMS_OUTPUT.PUT_LINE('...... END BLOCK level_2a');
+        END level_2a;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1a');
+        level_2a;
+--        DBMS_OUTPUT.PUT_LINE('.... v_level_2a: ' || v_level_2a);
+--                              Error - Descendent block ----^
+--        DBMS_OUTPUT.PUT_LINE('.... level_2a.v_level_2a: ' || level_2a.v_level_2a);
+--                              Error - Descendent block ---------------^
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1a');
+    END level_1a;
+    PROCEDURE level_1b
+    IS
+        v_level_1b  VARCHAR2(20) := 'Value from level_1b';
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('.. BLOCK level_1b');
+        DBMS_OUTPUT.PUT_LINE('.... v_level_1b: ' || v_level_1b);
+        DBMS_OUTPUT.PUT_LINE('.... v_level_0 : ' || v_level_0);
+--        DBMS_OUTPUT.PUT_LINE('.... level_1a.v_level_1a: ' || level_1a.v_level_1a);
+--                               Error - Sibling block -----------------^
+--        DBMS_OUTPUT.PUT_LINE('.... level_2a.v_level_2a: ' || level_2a.v_level_2a);
+--                               Error - Sibling block descendant ------^
+        DBMS_OUTPUT.PUT_LINE('.. END BLOCK level_1b');
+    END level_1b;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('BLOCK level_0');
+    DBMS_OUTPUT.PUT_LINE('.. v_level_0: ' || v_level_0);
+    level_1a;
+    level_1b;
+    DBMS_OUTPUT.PUT_LINE('END BLOCK level_0');
+END level_0;
+```
+
+The following is the output showing the content of each variable when the procedure is invoked:
+
+```sql
+BEGIN
+    level_0;
+END;
+__OUTPUT__
+BLOCK level_0
+.. v_level_0: Value from level_0
+.. BLOCK level_1a
+...... BLOCK level_2a
+........ v_level_2a: Value from level_2a
+........ v_level_1a: Value from level_1a
+........ level_1a.v_level_1a: Value from level_1a
+........ v_level_0: Value from level_0
+........ level_0.v_level_0: Value from level_0
+...... END BLOCK level_2a
+.. END BLOCK level_1a
+.. BLOCK level_1b
+.... v_level_1b: Value from level_1b
+.... v_level_0 : Value from level_0
+.. END BLOCK level_1b
+END BLOCK level_0
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx
new file mode 100644
index 00000000000..9e41462e83f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/index.mdx
@@ -0,0 +1,34 @@
+---
+title: "Subprograms: subprocedures and subfunctions"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/07_subprograms_subprocedures_and_subfunctions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="subprograms_subprocedures_and_subfunctions" class="registered_link"></div>
+
+You can use the capability and functionality of SPL procedure and function programs to your advantage to build well-structured and maintainable programs by organizing the SPL code into subprocedures and subfunctions.
+
+You can invoke the same SPL code multiple times from different locations in a relatively large SPL program by declaring subprocedures and subfunctions in the SPL program.
+
+Subprocedures and subfunctions have the following characteristics:
+
+-   The syntax, structure, and functionality of subprocedures and subfunctions are almost identical to standalone procedures and functions. The major difference is the use of the keyword `PROCEDURE` or `FUNCTION` instead of `CREATE PROCEDURE` or `CREATE FUNCTION` to declare the subprogram.
+-   Subprocedures and subfunctions provide isolation for the identifiers (that is, variables, cursors, types, and other subprograms) declared within itself. That is, you can't access or alter these identifiers from the upper, parent-level SPL programs or subprograms outside of the subprocedure or subfunction. This ensures that the subprocedure and subfunction results are reliable and predictable.
+-   The declaration section of subprocedures and subfunctions can include its own subprocedures and subfunctions. Thus, a multi-level hierarchy of subprograms can exist in the standalone program. In the hierarchy, a subprogram can access the identifiers of upper-level parent subprograms and also invoke upper-level parent subprograms. However, the same access to identifiers and invocation can't be done for lower-level child subprograms in the hierarchy.
+
+You can declare and invoke subprocedures and subfunctions from any of the following types of SPL programs:
+
+-   Standalone procedures and functions
+-   Anonymous blocks
+-   Triggers
+-   Packages
+-   Procedure and function methods of an object type body
+-   Subprocedures and subfunctions declared in any of the preceding programs
+
+
+<div class="toctree" maxdepth="3">
+
+creating_a_subprocedure creating_a_subfunction block_relationships invoking_subprograms using_forward_declarations overloading_subprograms accessing_subprogram_variables
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx
new file mode 100644
index 00000000000..7264839644d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions.mdx
@@ -0,0 +1,74 @@
+---
+title: "Compilation errors in procedures and functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.055.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.149.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/08_compilation_errors_in_procedures_and_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="compilation_errors_in_procedures_and_functions" class="registered_link"></div>
+
+When the EDB Postgres Advanced Server parsers compile a procedure or function, they confirm that both the `CREATE` statement and the program body (the portion of the program that follows the `AS` keyword) conform to the grammar rules for SPL and SQL constructs. By default, the server stops compiling if a parser detects an error. The parsers detect syntax errors in expressions, but they don't detect semantic errors. Semantic errors include an expression referencing a nonexistent column, table, or function, or a value of incorrect type.
+
+## Setting an error count compilation limit
+
+`spl.max_error_count` instructs the server to stop parsing if it encounters the specified number of errors in SPL code or when it encounters an error in SQL code. The default value of `spl.max_error_count` is `10`. The maximum value is `1000`. Setting `spl.max_error_count` to a value of `1` instructs the server to stop parsing when it encounters the first error in either SPL or SQL code.
+
+You can use the `SET` command to specify a value for `spl.max_error_count` for your current session. The syntax is:
+
+```sql
+SET spl.max_error_count = <number_of_errors>
+```
+
+Where `number_of_errors` specifies the number of SPL errors that can occur before the server stops compiling. For example:
+
+```sql
+SET spl.max_error_count = 6
+```
+## Example
+
+The example instructs the server to continue past the first five SPL errors it encounters. When the server encounters the sixth error, it stops validating and prints six detailed error messages and one error summary.
+
+To save time when developing new code or when importing code from another source, you might want to set the `spl.max_error_count` configuration parameter to a relatively high number of errors.
+
+If you instruct the server to continue parsing in spite of errors in the SPL code in a program body, and the parser encounters an error in a segment of SQL code, there can be more errors in any SPL or SQL code that follows the incorrect SQL code. For example, the following function results in two errors:
+
+```sql
+CREATE FUNCTION computeBonus(baseSalary number) RETURN number AS
+BEGIN
+
+    bonus := baseSalary * 1.10;
+    total := bonus + 100;
+
+    RETURN bonus;
+END;
+
+ERROR:  "bonus" is not a known variable
+LINE 4:     bonus := baseSalary * 1.10;
+            ^
+ERROR:  "total" is not a known variable
+LINE 5:     total := bonus + 100;
+            ^
+ERROR:  compilation of SPL function/procedure "computebonus" failed due to 2 errors
+```
+
+This example adds a `SELECT` statement to the example. The error in the `SELECT` statement masks the other errors that follow.
+
+```sql
+CREATE FUNCTION computeBonus(employeeName number) RETURN number AS
+BEGIN
+    SELECT salary INTO baseSalary FROM emp
+      WHERE ename = employeeName;
+
+    bonus := baseSalary * 1.10;
+    total := bonus + 100;
+
+    RETURN bonus;
+
+END;
+
+ERROR:  "basesalary" is not a known variable
+LINE 3:     SELECT salary INTO baseSalary FROM emp WHERE ename = emp...
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx
new file mode 100644
index 00000000000..0a39e05f954
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege.mdx
@@ -0,0 +1,41 @@
+---
+title: "EXECUTE privilege"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/01_execute_privilege/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="execute_privilege" class="registered_link"></div>
+
+An SPL program (function, procedure, or package) can begin execution only if any of the following are true:
+
+-   The current user is a superuser.
+-   The current user was granted `EXECUTE` privilege on the SPL program.
+-   The current user inherits `EXECUTE` privilege on the SPL program by virtue of being a member of a group that has this privilege.
+-   `EXECUTE` privilege was granted to the `PUBLIC` group.
+
+Whenever an SPL program is created in EDB Postgres Advanced Server, `EXECUTE` privilege is granted to the `PUBLIC` group by default. Therefore, any user can immediately execute the program.
+
+You can remove this default privilege by using the `REVOKE EXECUTE` command. For example:
+
+```sql
+REVOKE EXECUTE ON PROCEDURE list_emp FROM PUBLIC;
+```
+
+You can then grant explicit `EXECUTE` privilege on the program to individual users or groups.
+
+```sql
+GRANT EXECUTE ON PROCEDURE list_emp TO john;
+```
+
+Now, user `john` can execute the `list_emp` program. Other users who don't meet any of the required conditions can't.
+
+Once a program begins to execute, the next aspect of security is the privilege checks that occur if the program attempts to perform an action on any database object including:
+
+-   Reading or modifying table or view data
+-   Creating, modifying, or deleting a database object such as a table, view, index, or sequence
+-   Obtaining the current or next value from a sequence
+-   Calling another program (function, procedure, or package)
+
+Each such action can be protected by privileges on the database object either allowed or disallowed for the user.
+
+It's possible for a database to have more than one object of the same type with the same name, but each such object belongs to a different schema in the database. If this is the case, which object is being referenced by an SPL program? For more information, see [Database object name resolution](02_database_object_name_resolution).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx
new file mode 100644
index 00000000000..b705bb8e5e9
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution.mdx
@@ -0,0 +1,27 @@
+---
+title: "Database object name resolution"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/02_database_object_name_resolution/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="database_object_name_resolution" class="registered_link"></div>
+
+You can reference a database object inside an SPL program either by its qualified name or by an unqualified name. A qualified name is in the form of `schema.name`, where `schema` is the name of the schema under which the database object with identifier `name` exists. An unqualified name doesn't have the `schema.` portion. When a reference is made to a qualified name, there is no ambiguity as to which database object is intended. It either does or doesn't exist in the specified schema.
+
+Locating an object with an unqualified name, however, requires the use of the current user’s search path. When a user becomes the current user of a session, a default search path is always associated with that user. The search path consists of a list of schemas that are searched in left-to-right order for locating an unqualified database object reference. The object is considered nonexistent if it can’t be found in any of the schemas in the search path. You can display the default search path in PSQL using the `SHOW search_path` command:
+
+```sql
+edb=# SHOW search_path;
+__OUTPUT__
+   search_path
+-----------------
+ "$user", public
+(1 row)
+```
+
+`$user` in the search path is a generic placeholder that refers to the current user. So if the current user of this session is `enterprisedb`, an unqualified database object is searched for in the following schemas in this order: first in `enterprisedb`, and then in `public`.
+
+Once an unqualified name is resolved in the search path, you can determine if the current user has the appropriate privilege to perform the desired action on that specific object.
+
+!!! Note
+    The concept of the search path isn't compatible with Oracle databases. For an unqualified reference, Oracle looks in the schema of the current user for the named database object. Also, in Oracle, a user and their schema is the same entity. In EDB Postgres Advanced Server, a user and a schema are two distinct objects.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx
new file mode 100644
index 00000000000..683e24c2f78
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges.mdx
@@ -0,0 +1,9 @@
+---
+title: "Database object privileges"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/03_database_object_privileges/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="database_object_privileges" class="registered_link"></div>
+
+Once an SPL program begins execution, any attempt to access a database object from the program results in a check. This check ensures that the current user is authorized to perform the intended action against the referenced object. Privileges on database objects are added and removed using the `GRANT` and `REVOKE` commands. If the current user attempts unauthorized access on a database object, then the program throws an exception. See [Exception handling](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling/#exception_handling).
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx
new file mode 100644
index 00000000000..3f93904ddb3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights.mdx
@@ -0,0 +1,23 @@
+---
+title: "About definer and invoker rights"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/04_definers_vs_invokers_rights/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="definers_vs_invokers_rights" class="registered_link"></div>
+
+When an SPL program is about to begin executing, a determination is made as to the user to  associate with this process. This user is referred to as the *current user*. The current user’s database object privileges are used to determine whether access to database objects referenced in the program is permitted. The current prevailing search path in effect when the program is invoked is used to resolve any unqualified object references.
+
+The selection of the current user is influenced by whether the SPL program was created with definer’s right or invoker’s rights. The `AUTHID` clause determines that selection. Appearance of the clause `AUTHID DEFINER` gives the program definer’s rights. This is also the default if the `AUTHID` clause is omitted. Use of the clause `AUTHID CURRENT_USER` gives the program invoker’s rights. The difference between the two is summarized as follows:
+
+-   If a program has *definer’s rights*, then the owner of the program becomes the current user when program execution begins. The program owner’s database object privileges are used to determine if access to a referenced object is permitted. In a definer’s rights program, the user who actually invoked the program is irrelevant.
+-   If a program has *invoker’s rights*, then the current user at the time the program is called remains the current user while the program (but not necessarily the subprogram) is executing. When an invoker’s rights program is invoked, the current user is typically the user that started the session (made the database connection). You can change the current user after the session started using the `SET ROLE` command. In an invoker’s rights program, who actually owns the program is irrelevant.
+
+From the previous definitions, the following observations can be made:
+
+-   If a definer’s rights program calls a definer’s rights program, the current user changes from the owner of the calling program to the owner of the called program while the called program executes.
+-   If a definer’s rights program calls an invoker’s rights program, the owner of the calling program remains the current user whiile both the calling and called programs execute.
+-   If an invoker’s rights program calls an invoker’s rights program, the current user of the calling program remains the current user while the called program executes.
+-   If an invoker’s rights program calls a definer’s rights program, the current user switches to the owner of the definer’s rights program while the called program executes.
+
+The same principles apply if the called program in turn calls another program in these cases.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx
new file mode 100644
index 00000000000..6a11821ca7b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/05_security_example.mdx
@@ -0,0 +1,281 @@
+---
+title: "Security example"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/05_security_example/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+
+<div id="security_example" class="registered_link"></div>
+
+In this example, a new database is created along with two users: 
+-  `– hr_mgr`, who owns a copy of the entire sample application in schema `hr_mgr`
+-  `sales_mgr`, who owns a schema named `sales_mgr` that has a copy of only the `emp` table containing only the employees who work in sales
+
+The procedure `list_emp`, function `hire_clerk`, and package `emp_admin` are used in this example. All of the default privileges that are granted upon installation of the sample application are removed and then explicitly regranted so as to present a more secure environment.
+
+Programs `list_emp` and `hire_clerk` are changed from the default of definer’s rights to invoker’s rights. Then, when `sales_mgr` runs these programs, they act on the `emp` table in the `sales_mgr` schema since the `sales_mgr` search path and privileges are used for name resolution and authorization checking.
+
+Programs `get_dept_name` and `hire_emp` in the `emp_admin` package are then executed by `sales_mgr`. In this case, the `dept` table and `emp` table in the `hr_mgr` schema are accessed as `hr_mgr` is the owner of the `emp_admin` package which is using definer’s rights. Since the default search path is in effect with the `$user` placeholder, the schema matching the user (in this case, `hr_mgr`) is used to find the tables.
+
+## Step 1: Create database and users
+
+As user `enterprisedb`, create the `hr` database:
+
+```sql
+CREATE DATABASE hr;
+```
+
+Switch to the hr database and create the users:
+
+```sql
+\c hr enterprisedb
+CREATE USER hr_mgr IDENTIFIED BY password;
+CREATE USER sales_mgr IDENTIFIED BY password;
+```
+
+## Step 2: Create the sample application
+
+Create the entire sample application, owned by `hr_mgr`, in the `hr_mgr` schema.
+
+```sql
+\c - hr_mgr
+\i /usr/edb/as16/share/edb-sample.sql
+
+BEGIN
+CREATE TABLE
+CREATE TABLE
+CREATE TABLE
+CREATE VIEW
+CREATE SEQUENCE
+        .
+        .
+        .
+CREATE PACKAGE
+CREATE PACKAGE BODY
+COMMIT
+```
+
+## Step 3: Create the emp table in schema sales_mgr
+
+Create a subset of the `emp` table owned by `sales_mgr` in the `sales_mgr` schema.
+
+```sql
+\c – hr_mgr
+GRANT USAGE ON SCHEMA hr_mgr TO sales_mgr;
+\c – sales_mgr
+CREATE TABLE emp AS SELECT * FROM hr_mgr.emp WHERE job = 'SALESMAN';
+```
+
+The `GRANT USAGE ON SCHEMA` command allows `sales_mgr` access into the `hr_mgr`’s schema to make a copy of the `hr_mgr` `emp` table. This step is required in EDB Postgres Advanced Server and isn't compatible with Oracle databases. Oracle doesn't have the concept of a schema that's distinct from its user.
+
+## Step 4: Remove default privileges
+
+Remove all privileges to later illustrate the minimum required privileges needed.
+
+```sql
+\c – hr_mgr
+REVOKE USAGE ON SCHEMA hr_mgr FROM sales_mgr;
+REVOKE ALL ON dept FROM PUBLIC;
+REVOKE ALL ON emp FROM PUBLIC;
+REVOKE ALL ON next_empno FROM PUBLIC;
+REVOKE EXECUTE ON FUNCTION new_empno() FROM PUBLIC;
+REVOKE EXECUTE ON PROCEDURE list_emp FROM PUBLIC;
+REVOKE EXECUTE ON FUNCTION hire_clerk(VARCHAR2,NUMBER) FROM PUBLIC;
+REVOKE EXECUTE ON PACKAGE emp_admin FROM PUBLIC;
+```
+
+## Step 5: Change list_emp to invoker’s rights
+
+While connected as user `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `list_emp` program and resave it in EDB Postgres Advanced Server. When performing this step, be sure you're logged in as `hr_mgr`. Otherwise the modified program might end up in the `public` schema instead of in the `hr_mgr` schema.
+
+```sql
+CREATE OR REPLACE PROCEDURE list_emp
+AUTHID CURRENT_USER
+IS
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    CURSOR emp_cur IS
+        SELECT empno, ename FROM emp ORDER BY empno;
+BEGIN
+    OPEN emp_cur;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cur INTO v_empno, v_ename;
+        EXIT WHEN emp_cur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_cur;
+END;
+```
+
+## Step 6: Change hire_clerk to invoker’s rights and qualify call to new_empno
+
+While connected as user `hr_mgr`, add the `AUTHID CURRENT_USER` clause to the `hire_clerk` program.
+
+Also, after the `BEGIN` statement, fully qualify the reference `new_empno` to `hr_mgr.new_empno` to ensure the `hire_clerk` function call to the `new_empno` function resolves to the `hr_mgr` schema.
+
+When resaving the program, be sure you're logged in as `hr_mgr`. Otherwise the modified program might end up in the `public` schema instead of in the `hr_mgr` schema.
+
+```sql
+CREATE OR REPLACE FUNCTION hire_clerk (
+    p_ename         VARCHAR2,
+    p_deptno        NUMBER
+) RETURN NUMBER
+AUTHID CURRENT_USER
+IS
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_job           VARCHAR2(9);
+    v_mgr           NUMBER(4);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_comm          NUMBER(7,2);
+    v_deptno        NUMBER(2);
+BEGIN
+    v_empno := hr_mgr.new_empno;
+    INSERT INTO emp VALUES (v_empno, p_ename, 'CLERK', 7782,
+        TRUNC(SYSDATE), 950.00, NULL, p_deptno);
+    SELECT empno, ename, job, mgr, hiredate, sal, comm, deptno INTO
+        v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
+        FROM emp WHERE empno = v_empno;
+    DBMS_OUTPUT.PUT_LINE('Department : ' || v_deptno);
+    DBMS_OUTPUT.PUT_LINE('Employee No: ' || v_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+    DBMS_OUTPUT.PUT_LINE('Manager    : ' || v_mgr);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+    DBMS_OUTPUT.PUT_LINE('Commission : ' || v_comm);
+    RETURN v_empno;
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+        DBMS_OUTPUT.PUT_LINE(SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+        DBMS_OUTPUT.PUT_LINE(SQLCODE);
+        RETURN -1;
+END;
+```
+
+## Step 7: Grant required privileges
+
+While connected as user `hr_mgr`, grant the privileges needed so `sales_mgr` can execute the `list_emp` procedure, `hire_clerk` function, and `emp_admin` package. The only data object `sales_mgr` has access to is the `emp` table in the `sales_mgr` schema. `sales_mgr` has no privileges on any table in the `hr_mgr` schema.
+
+```sql
+GRANT USAGE ON SCHEMA hr_mgr TO sales_mgr;
+GRANT EXECUTE ON PROCEDURE list_emp TO sales_mgr;
+GRANT EXECUTE ON FUNCTION hire_clerk(VARCHAR2,NUMBER) TO sales_mgr;
+GRANT EXECUTE ON FUNCTION new_empno() TO sales_mgr;
+GRANT EXECUTE ON PACKAGE emp_admin TO sales_mgr;
+```
+
+## Step 8: Run programs list_emp and hire_clerk
+
+Connect as user `sales_mgr`, and run the following anonymous block:
+
+```sql
+\c – sales_mgr
+DECLARE
+    v_empno         NUMBER(4);
+BEGIN
+    hr_mgr.list_emp;
+    DBMS_OUTPUT.PUT_LINE('*** Adding new employee ***');
+    v_empno := hr_mgr.hire_clerk('JONES',40);
+    DBMS_OUTPUT.PUT_LINE('*** After new employee added ***');
+    hr_mgr.list_emp;
+END;
+
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7521     WARD
+7654     MARTIN
+7844     TURNER
+*** Adding new employee ***
+Department : 40
+Employee No: 8000
+Name       : JONES
+Job        : CLERK
+Manager    : 7782
+Hire Date  : 08-NOV-07 00:00:00
+Salary     : 950.00
+*** After new employee added ***
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7521     WARD
+7654     MARTIN
+7844     TURNER
+8000     JONES
+```
+
+The table and sequence accessed by the programs of the anonymous block are shown in the following diagram. The gray ovals represent the schemas of `sales_mgr` and `hr_mgr`. The current user during each program execution is shown in parenthesis in bold red font.
+
+![Invokers Rights Programs](../../images/invokers_rights_programs.png)
+
+<div style="text-align: center"> Fig. 1: Invokers Rights Programs </div>
+
+Selecting from the `sales_mgr` `emp` table shows that the update was made in this table.
+
+```sql
+SELECT empno, ename, hiredate, sal, deptno,
+hr_mgr.emp_admin.get_dept_name(deptno) FROM sales_mgr.emp;
+__OUTPUT__
+ empno | ename  |      hiredate      |   sal   | deptno | get_dept_name
+-------+--------+--------------------+---------+--------+---------------
+  7499 | ALLEN  | 20-FEB-81 00:00:00 | 1600.00 |     30 | SALES
+  7521 | WARD   | 22-FEB-81 00:00:00 | 1250.00 |     30 | SALES
+  7654 | MARTIN | 28-SEP-81 00:00:00 | 1250.00 |     30 | SALES
+  7844 | TURNER | 08-SEP-81 00:00:00 | 1500.00 |     30 | SALES
+  8000 | JONES  | 08-NOV-07 00:00:00 |  950.00 |     40 | OPERATIONS
+(5 rows)
+```
+
+The following diagram shows that the `SELECT` command references the `emp` table in the `sales_mgr` schema. However, the `dept` table referenced by the `get_dept_name` function in the `emp_admin` package is from the `hr_mgr` schema since the `emp_admin` package has definer’s rights and is owned by `hr_mgr`. The default search path setting with the `$user` placeholder resolves the access by user `hr_mgr` to the `dept` table in the `hr_mgr` schema.
+
+![Definer's Rights Package](../../images/definers_rights_package.png)
+
+<div style="text-align: center"> Fig. 2: Definer's Rights Package </div>
+
+## Step 9: Run program hire_emp in the emp_admin package
+
+While connected as user `sales_mgr`, run the `hire_emp` procedure in the `emp_admin` package.
+
+```sql
+EXEC hr_mgr.emp_admin.hire_emp(9001,
+'ALICE','SALESMAN',8000,TRUNC(SYSDATE),1000,7369,40);
+```
+
+This diagram shows that the `hire_emp` procedure in the `emp_admin` definer’s rights package updates the `emp` table belonging to `hr_mgr`. The object privileges of `hr_mgr` are used and the default search path setting with the `$user` placeholder resolves to the schema of `hr_mgr`.
+
+![Definer's Rights Package](../../images/definer's_rights_package.png)
+
+<div style="text-align: center"> Fig. 3: Definer's Rights Package </div>
+
+Now connect as user `hr_mgr`. The following `SELECT` command verifies that the new employee was added to the `hr_mgr` `emp` table since the `emp_admin` package has definer’s rights and `hr_mgr` is the `emp_admin` owner.
+
+```sql
+\c – hr_mgr
+SELECT empno, ename, hiredate, sal, deptno,
+hr_mgr.emp_admin.get_dept_name(deptno) FROM hr_mgr.emp;
+__OUTPUT__
+empno  | ename  |      hiredate      |   sal   | deptno | get_dept_name
+-------+--------+--------------------+---------+--------+---------------
+  7369 | SMITH  | 17-DEC-80 00:00:00 |  800.00 |     20 | RESEARCH
+  7499 | ALLEN  | 20-FEB-81 00:00:00 | 1600.00 |     30 | SALES
+  7521 | WARD   | 22-FEB-81 00:00:00 | 1250.00 |     30 | SALES
+  7566 | JONES  | 02-APR-81 00:00:00 | 2975.00 |     20 | RESEARCH
+  7654 | MARTIN | 28-SEP-81 00:00:00 | 1250.00 |     30 | SALES
+  7698 | BLAKE  | 01-MAY-81 00:00:00 | 2850.00 |     30 | SALES
+  7782 | CLARK  | 09-JUN-81 00:00:00 | 2450.00 |     10 | ACCOUNTING
+  7788 | SCOTT  | 19-APR-87 00:00:00 | 3000.00 |     20 | RESEARCH
+  7839 | KING   | 17-NOV-81 00:00:00 | 5000.00 |     10 | ACCOUNTING
+  7844 | TURNER | 08-SEP-81 00:00:00 | 1500.00 |     30 | SALES
+  7876 | ADAMS  | 23-MAY-87 00:00:00 | 1100.00 |     20 | RESEARCH
+  7900 | JAMES  | 03-DEC-81 00:00:00 |  950.00 |     30 | SALES
+  7902 | FORD   | 03-DEC-81 00:00:00 | 3000.00 |     20 | RESEARCH
+  7934 | MILLER | 23-JAN-82 00:00:00 | 1300.00 |     10 | ACCOUNTING
+  9001 | ALICE  | 08-NOV-07 00:00:00 | 8000.00 |     40 | OPERATIONS
+(15 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/index.mdx
new file mode 100644
index 00000000000..337591d753c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/09_program_security/index.mdx
@@ -0,0 +1,24 @@
+---
+title: "Program security"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.056.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.150.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/09_program_security/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="program_security" class="registered_link"></div>
+
+You can control the security over whether a user can execute an SPL program. You can also control the database objects an SPL program can access for any given user executing the program. These are controlled by the following:
+
+-   Privilege to execute a program
+-   Privileges granted on the database objects (including other SPL programs) that a program attempts to access
+-   Whether the program is defined with definer’s rights or invoker’s rights
+
+<div class="toctree" maxdepth="3">
+
+execute_privilege database_object_name_resolution database_object_privileges definers_vs_invokers_rights security_example
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/index.mdx
new file mode 100644
index 00000000000..dc41bbca5ff
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/02_spl_programs/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "Types of SPL programs"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.049.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.143.html"
+redirects:
+  - /epas/latest/epas_compat_spl/02_spl_programs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="spl_programs" class="registered_link"></div>
+
+SPL is a procedural, block-structured language. You can create four different types of programs using SPL: *procedures*, *functions*, *triggers*, and *packages*.
+
+In addition, you can use SPL to create subprograms. A *subprogram* refers to a *subprocedure* or a *subfunction*. These are nearly identical in appearance to procedures and functions. They differ in that procedures and functions are *standalone programs*. They are stored individually in the database, and you can invoke them from other SPL programs or from PSQL. You can invoke subprograms only from the standalone program where they were created.
+
+<div class="toctree" maxdepth="3">
+
+basic_spl_elements spl_block_structure anonymous_blocks procedures_overview functions_overview procedure_and_function_parameters subprograms_subprocedures_and_subfunctions compilation_errors_in_procedures_and_functions program_security
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx
new file mode 100644
index 00000000000..a5c1a3686fc
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/01_declaring_a_variable.mdx
@@ -0,0 +1,55 @@
+---
+title: "Declaring a variable"
+redirects:
+  - /epas/latest/epas_compat_spl/03_variable_declarations/01_declaring_a_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="declaring_a_variable" class="registered_link"></div>
+
+Generally, you must declare all variables used in a block in the declaration section of the block. A variable declaration consists of a name that's assigned to the variable and its data type. Optionally, you can initialize the variable to a default value in the variable declaration.
+
+## Syntax 
+
+The general syntax of a variable declaration is:
+
+```sql
+<name> <type> [ { := | DEFAULT } { <expression> | NULL } ];
+```
+
+`name` is an identifier assigned to the variable.
+
+`type` is the data type assigned to the variable.
+
+`[ := expression ]`, if given, specifies the initial value assigned to the variable when the block is entered. If the clause isn't given then the variable is initialized to the SQL `NULL` value.
+
+The default value is evaluated every time the block is entered. So, for example, assigning `SYSDATE` to a variable of type `DATE` causes the variable to have the time of the current invocation, not the time when the procedure or function was precompiled.
+
+## Example: Variable declarations that use defaults
+
+This procedure shows some variable declarations that use defaults consisting of string and numeric expressions:
+
+```sql
+CREATE OR REPLACE PROCEDURE dept_salary_rpt (
+    p_deptno        NUMBER
+)
+IS
+    todays_date     DATE := SYSDATE;
+    rpt_title       VARCHAR2(60) := 'Report For Department # ' || p_deptno
+                             || ' on ' || todays_date;
+    base_sal        INTEGER := 35525;
+    base_comm_rate  NUMBER := 1.33333;
+    base_annual     NUMBER := ROUND(base_sal * base_comm_rate, 2);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE(rpt_title);
+    DBMS_OUTPUT.PUT_LINE('Base Annual Salary: ' || base_annual);
+END;
+```
+
+The following output of the procedure shows that default values in the variable declarations are assigned to the variables:
+
+```sql
+EXEC dept_salary_rpt(20);
+__OUTPUT__
+Report For Department # 20 on 10-JUL-07 16:44:45
+Base Annual Salary: 47366.55
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx
new file mode 100644
index 00000000000..f319d7a4748
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations.mdx
@@ -0,0 +1,128 @@
+---
+title: "Using %TYPE in variable declarations"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.058.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.152.html"
+redirects:
+  - /epas/latest/epas_compat_spl/03_variable_declarations/02_using__type_in_variable_declarations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="[using]()%_type_in_variable_declarations" class="registered_link"></div>
+
+Often, variables are declared in SPL programs that are used to hold values from tables in the database. To ensure compatibility between the table columns and the SPL variables, make sure their data types are the same.
+
+However, often a change is made to the table definition. If the data type of the column is changed, you might need to make the corresponding change to the variable in the SPL program.
+
+Instead of coding the specific column data type into the variable declaration, you can use the column attribute `%TYPE`. Specify a qualified column name in dot notation or the name of a previously declared variable as a prefix to `%TYPE`. The data type of the column or variable prefixed to `%TYPE` is assigned to the variable being declared. If the data type of the given column or variable changes, the new data type is associated with the variable, and you don't need to modify the declaration code.
+
+!!! Note
+    You can use the `%TYPE` attribute with formal parameter declarations as well.
+
+## Syntax 
+
+```sql
+<name> { { <table> | <view> }.<column> | <variable> }%TYPE;
+```
+
+-  `name` is the identifier assigned to the variable or formal parameter that's being declared. 
+-  `column` is the name of a column in `table` or `view`. 
+-  `variable` is the name of a variable that was declared prior to the variable identified by `name`.
+
+!!! Note
+    The variable doesn't inherit any of the column’s other attributes that you specify on the column with the `NOT NULL` clause or the `DEFAULT` clause.
+
+## Example: Defining parameters using %TYPE
+
+In this example, a procedure:
+
+-  Queries the `emp` table using an employee number
+-  Displays the employee’s data
+-  Finds the average salary of all employees in the department to which the employee belongs
+-  Compares the chosen employee’s salary with the department average
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_sal_query (
+    p_empno         IN NUMBER
+)
+IS
+    v_ename         VARCHAR2(10);
+    v_job           VARCHAR2(9);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_deptno        NUMBER(2);
+    v_avgsal        NUMBER(7,2);
+BEGIN
+    SELECT ename, job, hiredate, sal, deptno
+        INTO v_ename, v_job, v_hiredate, v_sal, v_deptno
+        FROM emp WHERE empno = p_empno;
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || v_deptno);
+
+    SELECT AVG(sal) INTO v_avgsal
+        FROM emp WHERE deptno = v_deptno;
+    IF v_sal > v_avgsal THEN
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+            || 'department average of ' || v_avgsal);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+            || 'department average of ' || v_avgsal);
+    END IF;
+END;
+```
+
+Alternatively, you can write the procedure without explicitly coding the `emp` table data types into the declaration section of the procedure:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_sal_query (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_avgsal        v_sal%TYPE;
+BEGIN
+    SELECT ename, job, hiredate, sal, deptno
+        INTO v_ename, v_job, v_hiredate, v_sal, v_deptno
+        FROM emp WHERE empno = p_empno;
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || v_deptno);
+
+    SELECT AVG(sal) INTO v_avgsal
+        FROM emp WHERE deptno = v_deptno;
+    IF v_sal > v_avgsal THEN
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+            || 'department average of ' || v_avgsal);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+            || 'department average of ' || v_avgsal);
+    END IF;
+END;
+```
+
+`p_empno` shows an example of a formal parameter defined using `%TYPE`. `v_avgsal` shows the use of `%TYPE` referring to another variable instead of a table column.
+
+The following is sample output from executing this procedure:
+
+```sql
+EXEC emp_sal_query(7698);
+__OUTPUT__
+Employee # : 7698
+Name       : BLAKE
+Job        : MANAGER
+Hire Date  : 01-MAY-81 00:00:00
+Salary     : 2850.00
+Dept #     : 30
+Employee's salary is more than the department average of 1566.67
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx
new file mode 100644
index 00000000000..3133ce5a563
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations.mdx
@@ -0,0 +1,59 @@
+---
+title: "Using %ROWTYPE in record declarations"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.059.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.153.html"
+redirects:
+  - /epas/latest/epas_compat_spl/03_variable_declarations/03_using__row_type_in_record_declarations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="[using]()%_row_type_in_record_declarations" class="registered_link"></div>
+
+The `%TYPE` attribute provides an easy way to create a variable that depends on a column's data type. Using the `%ROWTYPE` attribute, you can define a record that contains fields that correspond to all columns of a given table. Each field takes on the data type of its corresponding column. The fields in the record don't inherit any of the columns' other attributes like those specified with the `NOT NULL` clause or the `DEFAULT` clause.
+
+A *record* is a named, ordered collection of fields. A *field* is similar to a variable. It has an identifier and data type but has the additional property of belonging to a record. You must refereence it using dot notation with the record name as its qualifier.
+
+## Syntax
+
+You can use the `%ROWTYPE` attribute to declare a record. The `%ROWTYPE` attribute is prefixed by a table name. Each column in the named table defines an identically named field in the record with the same data type as the column.
+
+```text
+<record> <table>%ROWTYPE;
+```
+
+-  `record` is an identifier assigned to the record. 
+-  `table` is the name of a table or view whose columns define the fields in the record. 
+
+## Example
+
+This example shows how you can modify the `emp_sal_query` procedure from [Using %TYPE in variable declarations](02_using__type_in_variable_declarations) to use `emp%ROWTYPE` to create a record named `r_emp` instead of declaring individual variables for the columns in `emp`:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_sal_query (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+    r_emp           emp%ROWTYPE;
+    v_avgsal        emp.sal%TYPE;
+BEGIN
+    SELECT ename, job, hiredate, sal, deptno
+        INTO r_emp.ename, r_emp.job, r_emp.hiredate, r_emp.sal, r_emp.deptno
+        FROM emp WHERE empno = p_empno;
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || r_emp.ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || r_emp.job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || r_emp.hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || r_emp.sal);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || r_emp.deptno);
+    SELECT AVG(sal) INTO v_avgsal
+        FROM emp WHERE deptno = r_emp.deptno;
+    IF r_emp.sal > v_avgsal THEN
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+            || 'department average of ' || v_avgsal);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+            || 'department average of ' || v_avgsal);
+    END IF;
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx
new file mode 100644
index 00000000000..55669da0581
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables.mdx
@@ -0,0 +1,111 @@
+---
+title: "User-defined record types and record variables"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.060.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.154.html"
+redirects:
+  - /epas/latest/epas_compat_spl/03_variable_declarations/04_user_defined_record_types_and_record_variables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_defined_record_types_and_record_variables" class="registered_link"></div>
+
+You can declare records based on a table definition using the `%ROWTYPE` attribute, as shown in [Using %ROWTYPE in record declarations](03_using__row_type_in_record_declarations). You can also define a new record structure that isn't tied to a particular table definition.
+
+You use the `TYPE IS RECORD` statement to create the definition of a record type. A *record type* is a definition of a record made up of one or more identifiers and their corresponding data types. You can't use a record type by itself to manipulate data.
+
+## Syntax
+
+The syntax for a `TYPE IS RECORD` statement is:
+
+```sql
+TYPE <rec_type> IS RECORD ( <fields> )
+```
+
+Where `fields` is a comma-separated list of one or more field definitions of the following form:
+
+```sql
+<field_name> <data_type> [NOT NULL][{:= | DEFAULT} <default_value>]
+```
+
+Where:
+
+-  `rec_type` is an identifier assigned to the record type.
+-  `field_name` is the identifier assigned to the field of the record type.
+-  `data_type` specifies the data type of `field_name`.
+-  The `DEFAULT` clause assigns a default data value for the corresponding field. The data type of the default expression must match the data type of the column. If you don't specify a default, then the default is `NULL`.
+
+A *record variable* or *record* is an instance of a record type. A record is declared from a record type. The properties of the record such as its field names and types are inherited from the record type.
+
+The following is the syntax for a record declaration:
+
+```text
+<record> <rectype>
+```
+
+`record` is an identifier assigned to the record variable. `rectype` is the identifier of a previously defined record type. Once declared, you can't then use a record to hold data.
+
+Use dot notation to reference the fields in the record:
+
+```text
+<record>.<field>
+```
+
+`record` is a previously declared record variable and `field` is the identifier of a field belonging to the record type from which `record` is defined.
+
+## Example 
+
+This `emp_sal_query` procedure uses a user-defined record type and record variable:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_sal_query (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+    TYPE emp_typ IS RECORD (
+        ename       emp.ename%TYPE,
+        job         emp.job%TYPE,
+        hiredate    emp.hiredate%TYPE,
+        sal         emp.sal%TYPE,
+        deptno      emp.deptno%TYPE
+    );
+    r_emp           emp_typ;
+    v_avgsal        emp.sal%TYPE;
+BEGIN
+    SELECT ename, job, hiredate, sal, deptno
+        INTO r_emp.ename, r_emp.job, r_emp.hiredate, r_emp.sal, r_emp.deptno
+        FROM emp WHERE empno = p_empno;
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || r_emp.ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || r_emp.job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || r_emp.hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || r_emp.sal);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || r_emp.deptno);
+
+    SELECT AVG(sal) INTO v_avgsal
+        FROM emp WHERE deptno = r_emp.deptno;
+    IF r_emp.sal > v_avgsal THEN
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+            || 'department average of ' || v_avgsal);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+            || 'department average of ' || v_avgsal);
+    END IF;
+END;
+```
+
+Instead of specifying data type names, you can use the `%TYPE` attribute for the field data types in the record type definition.
+
+The following is the output from executing this stored procedure:
+
+```sql
+EXEC emp_sal_query(7698);
+__OUTPUT__
+Employee # : 7698
+Name       : BLAKE
+Job        : MANAGER
+Hire Date  : 01-MAY-81 00:00:00
+Salary     : 2850.00
+Dept #     : 30
+Employee's salary is more than the department average of 1566.67
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/index.mdx
new file mode 100644
index 00000000000..4005c2a5b6f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/03_variable_declarations/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Using variable declarations"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.057.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.151.html"
+redirects:
+  - /epas/latest/epas_compat_spl/03_variable_declarations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="variable_declarations" class="registered_link"></div>
+
+SPL is a block-structured language. The first section that can appear in a block is the declaration. The declaration contains the definition of variables, cursors, and other types that you can use in SPL statements contained in the block.
+
+<div class="toctree" maxdepth="3">
+
+declaring_a_variable using\_%\_type_in_variable_declarations using\_%\_row_type_in_record_declarations user_defined_record_types_and_record_variables
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/01_commit.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/01_commit.mdx
new file mode 100644
index 00000000000..c9a78de11d4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/01_commit.mdx
@@ -0,0 +1,66 @@
+---
+title: "COMMIT"
+redirects:
+  - /epas/latest/epas_compat_spl/06_transaction_control/01_commit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="commit" class="registered_link"></div>
+
+The `COMMIT` command makes all database updates from the current transaction permanent and ends the current transaction.
+
+```sql
+COMMIT [ WORK ];
+```
+
+You can use the `COMMIT` command in anonymous blocks, stored procedures, or functions. In an SPL program, it can appear in the executable section and the exception section.
+
+In this example, the third `INSERT` command in the anonymous block results in an error. The effect of the first two `INSERT` commands is retained as shown by the first `SELECT` command. Even after issuing a `ROLLBACK` command, the two rows remain in the table, as shown by the second `SELECT` command verifying that they were indeed committed.
+
+!!! Note
+    You can set the `edb_stmt_level_tx` configuration parameter shown in the example for the entire database using the `ALTER DATABASE` command. Alternatively, you can set it for the entire database server by changing it in the `postgresql.conf` file.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO on;
+
+BEGIN
+    INSERT INTO dept VALUES (50, 'FINANCE', 'DALLAS');
+    INSERT INTO dept VALUES (60, 'MARKETING', 'CHICAGO');
+    COMMIT;
+    INSERT INTO dept VALUES (70, 'HUMAN RESOURCES', 'CHICAGO');
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+SQLERRM: value too long for type character varying(14)
+SQLCODE: 22001
+
+SELECT * FROM dept;
+__OUTPUT__
+deptno  |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     50 | FINANCE    | DALLAS
+     60 | MARKETING  | CHICAGO
+(6 rows)
+```
+```sql
+ROLLBACK;
+
+SELECT * FROM dept;
+__OUTPUT__
+deptno  |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     50 | FINANCE    | DALLAS
+     60 | MARKETING  | CHICAGO
+(6 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/02_rollback.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/02_rollback.mdx
new file mode 100644
index 00000000000..75dd37430c5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/02_rollback.mdx
@@ -0,0 +1,183 @@
+---
+title: "ROLLBACK"
+redirects:
+  - /epas/latest/epas_compat_spl/06_transaction_control/02_rollback/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="rollback" class="registered_link"></div>
+
+The `ROLLBACK` command undoes all database updates made during the current transaction and ends the current transaction.
+
+```sql
+ROLLBACK [ WORK ];
+```
+
+You can use the `ROLLBACK` command in anonymous blocks, stored procedures, or functions. In an SPL program, it can appear in the executable section and the exception section.
+
+In this example, the exception section contains a `ROLLBACK` command. Even though the first two `INSERT` commands execute successfully, the third causes an exception that results in the rollback of all the `INSERT` commands in the anonymous block.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO on;
+
+BEGIN
+    INSERT INTO dept VALUES (50, 'FINANCE', 'DALLAS');
+    INSERT INTO dept VALUES (60, 'MARKETING', 'CHICAGO');
+    INSERT INTO dept VALUES (70, 'HUMAN RESOURCES', 'CHICAGO');
+EXCEPTION
+    WHEN OTHERS THEN
+        ROLLBACK;
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+SQLERRM: value too long for type character varying(14)
+SQLCODE: 22001
+
+SELECT * FROM dept;
+__OUTPUT__
+deptno  |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+(4 rows)
+```
+
+This example uses both `COMMIT` and `ROLLBACK`. First, the following stored procedure is created. It inserts a new employee.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO on;
+
+CREATE OR REPLACE PROCEDURE emp_insert (
+    p_empno         IN emp.empno%TYPE,
+    p_ename         IN emp.ename%TYPE,
+    p_job           IN emp.job%TYPE,
+    p_mgr           IN emp.mgr%TYPE,
+    p_hiredate      IN emp.hiredate%TYPE,
+    p_sal           IN emp.sal%TYPE,
+    p_comm          IN emp.comm%TYPE,
+    p_deptno        IN emp.deptno%TYPE
+)
+IS
+BEGIN
+    INSERT INTO emp VALUES (
+        p_empno,
+        p_ename,
+        p_job,
+        p_mgr,
+        p_hiredate,
+        p_sal,
+        p_comm,
+        p_deptno);
+
+    DBMS_OUTPUT.PUT_LINE('Added employee...');
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || p_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || p_job);
+    DBMS_OUTPUT.PUT_LINE('Manager    : ' || p_mgr);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || p_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || p_sal);
+    DBMS_OUTPUT.PUT_LINE('Commission : ' || p_comm);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || p_deptno);
+    DBMS_OUTPUT.PUT_LINE('----------------------');
+END;
+```
+
+This procedure has no exception section. Any errors are propagated up to the calling program.
+
+Then the following anonymous block runs. The `COMMIT` command is used after all calls to the `emp_insert` procedure and the `ROLLBACK` command in the exception section.
+
+```sql
+BEGIN
+    emp_insert(9601,'FARRELL','ANALYST',7902,'03-MAR-08',5000,NULL,40);
+    emp_insert(9602,'TYLER','ANALYST',7900,'25-JAN-08',4800,NULL,40);
+    COMMIT;
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('An error occurred - roll back inserts');
+        ROLLBACK;
+END;
+__OUTPUT__
+Added employee...
+Employee # : 9601
+Name       : FARRELL
+Job        : ANALYST
+Manager    : 7902
+Hire Date  : 03-MAR-08 00:00:00
+Salary     : 5000
+Commission :
+Dept #     : 40
+----------------------
+Added employee...
+Employee # : 9602
+Name       : TYLER
+Job        : ANALYST
+Manager    : 7900
+Hire Date  : 25-JAN-08 00:00:00
+Salary     : 4800
+Commission :
+Dept #     : 40
+----------------------
+```
+
+The following `SELECT` command shows that employees Farrell and Tyler were successfully added:
+
+```sql
+SELECT * FROM emp WHERE empno > 9600;
+__OUTPUT__
+empno | ename  |  job   | mgr |     hiredate       |   sal   | comm | deptno
+------+--------+--------+-----+--------------------+---------+------+--------
+  9601| FARRELL| ANALYST|7902 | 03-MAR-08 00:00:00 | 5000.00 |      |   40
+  9602| TYLER  | ANALYST|7900 | 25-JAN-08 00:00:00 | 4800.00 |      |   40
+(2 rows)
+```
+
+Next, execute the following anonymous block:
+
+```sql
+BEGIN
+    emp_insert(9603,'HARRISON','SALESMAN',7902,'13-DEC-07',5000,3000,20);
+    emp_insert(9604,'JARVIS','SALESMAN',7902,'05-MAY-08',4800,4100,11);
+    COMMIT;
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('An error occurred - roll back inserts');
+        ROLLBACK;
+END;
+__OUTPUT__
+Added employee...
+Employee # : 9603
+Name       : HARRISON
+Job        : SALESMAN
+Manager    : 7902
+Hire Date  : 13-DEC-07 00:00:00
+Salary     : 5000
+Commission : 3000
+Dept #     : 20
+----------------------
+SQLERRM: insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+An error occurred - roll back inserts
+```
+
+A `SELECT` command run against the table produces the following:
+
+```sql
+SELECT * FROM emp WHERE empno > 9600;
+__OUTPUT__
+empno | ename  |  job   | mgr |     hiredate       |   sal   | comm | deptno
+------+--------+--------+-----+--------------------+---------+------+--------
+  9601| FARRELL| ANALYST|7902 | 03-MAR-08 00:00:00 | 5000.00 |      |   40
+  9602| TYLER  | ANALYST|7900 | 25-JAN-08 00:00:00 | 4800.00 |      |   40
+(2 rows)
+```
+
+The `ROLLBACK` command in the exception section successfully undoes the insert of employee Harrison. Employees Farrell and Tyler are still in the table as their inserts were made permanent by the `COMMIT` command in the first anonymous block.
+
+!!! Note
+    Executing a `COMMIT` or `ROLLBACK` in a plpgsql procedure throws an error if an Oracle-style SPL procedure is on the runtime stack.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction.mdx
new file mode 100644
index 00000000000..e26d2edddf1
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction.mdx
@@ -0,0 +1,419 @@
+---
+title: "PRAGMA AUTONOMOUS_TRANSACTION"
+redirects:
+  - /epas/latest/epas_compat_spl/06_transaction_control/03_pragma_autonomous_transaction/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="pragma_autonomous_transaction" class="registered_link"></div>
+
+A stored procedural language (SPL) program can be declared as an *autonomous transaction* by specifying the following directive in the declaration section of the SPL block. An autonomous transaction is an independent transaction started by a calling program. 
+
+```sql
+PRAGMA AUTONOMOUS_TRANSACTION;
+```
+
+A commit or rollback of SQL commands in the autonomous transaction has no effect on the commit or rollback in any transaction of the calling program. A commit or rollback in the calling program has no effect on the commit or rollback of SQL commands in the autonomous transaction.
+
+## Requirements and restrictions
+
+The following SPL programs can include `PRAGMA AUTONOMOUS_TRANSACTION`:
+
+-   Standalone procedures and functions
+-   Anonymous blocks
+-   Procedures and functions declared as subprograms in packages and other calling procedures, functions, and anonymous blocks
+-   Triggers
+-   Object type methods
+
+The following are issues and restrictions related to autonomous transactions:
+
+-   Each autonomous transaction consumes a connection slot for as long as it's in progress. In some cases, this might mean that you need to raise the `max_connections` parameter in the `postgresql.conf` file.
+-   In most respects, an autonomous transaction behaves as if it were a completely separate session, but GUCs (settings established with `SET`) are a deliberate exception. Autonomous transactions absorb the surrounding values and can propagate values they commit to the outer transaction.
+-   Autonomous transactions can be nested, but there is a limit of 16 levels of autonomous transactions in a single session.
+-   Parallel query isn't supported in autonomous transactions.
+-   The EDB Postgres Advanced Server implementation of autonomous transactions isn't entirely compatible with Oracle databases. The EDB Postgres Advanced Server autonomous transaction doesn't produce an error if there's an uncommitted transaction at the end of an SPL block.
+
+## About the examples 
+
+The following set of examples use autonomous transactions. This first set of scenarios shows the default behavior when there are no autonomous transactions.
+
+Before each scenario, the `dept` table is reset to the following initial values:
+
+```sql
+SELECT * FROM dept;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+(4 rows)
+```
+
+## Scenario 1a: No autonomous transactions with only a final COMMIT
+
+This first set of scenarios shows the insertion of three rows:
+
+-  Starting just after the initial `BEGIN` command of the transaction 
+-  From an anonymous block in the starting transactions
+-  From a stored procedure executed from  the anonymous block
+
+The stored procedure is the following:
+
+```sql
+CREATE OR REPLACE PROCEDURE insert_dept_70 IS
+BEGIN
+    INSERT INTO dept VALUES (70,'MARKETING','LOS ANGELES');
+END;
+```
+
+The PSQL session is the following:
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+END;
+COMMIT;
+```
+
+After the final commit, all three rows are inserted:
+
+```sql
+SELECT * FROM dept ORDER BY 1;
+__OUTPUT__
+ deptno |   dname    |     loc
+--------+------------+-------------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     50 | HR         | DENVER
+     60 | FINANCE    | CHICAGO
+     70 | MARKETING  | LOS ANGELES
+(7 rows)
+```
+
+## Scenario 1b: No autonomous transactions but a final ROLLBACK
+
+The next scenario shows that a final `ROLLBACK` command after all inserts results in the rollback of all three insertions:
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+END;
+ROLLBACK;
+
+SELECT * FROM dept ORDER BY 1;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+(4 rows)
+```
+
+## Scenario 1c: No autonomous transactions, but anonymous block ROLLBACK
+
+A `ROLLBACK` command given at the end of the anonymous block also eliminates all three prior insertions:
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+    ROLLBACK;
+END;
+COMMIT;
+
+SELECT * FROM dept ORDER BY 1;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+(4 rows)
+```
+
+The next set of scenarios shows the effect of using autonomous transactions with `PRAGMA AUTONOMOUS_TRANSACTION` in various locations.
+
+## Scenario 2a: Autonomous transaction of anonymous block with COMMIT
+
+The procedure remains as initially created:
+
+```sql
+CREATE OR REPLACE PROCEDURE insert_dept_70 IS
+BEGIN
+    INSERT INTO dept VALUES (70,'MARKETING','LOS ANGELES');
+END;
+```
+
+The `PRAGMA AUTONOMOUS_TRANSACTION` is given with the anonymous block along with the `COMMIT` command at the end of the anonymous block:
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+    COMMIT;
+END;
+ROLLBACK;
+```
+
+After the `ROLLBACK` at the end of the transaction, only the first row insertion at the beginning of the transaction is discarded. The other two row insertions in the anonymous block with `PRAGMA AUTONOMOUS_TRANSACTION` were independently committed.
+
+```sql
+SELECT * FROM dept ORDER BY 1;
+__OUTPUT__
+ deptno |   dname    |     loc
+--------+------------+-------------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     60 | FINANCE    | CHICAGO
+     70 | MARKETING  | LOS ANGELES
+(6 rows)
+```
+
+## Scenario 2b: Autonomous transaction anonymous block with COMMIT, including procedure with ROLLBACK but not an autonomous transaction procedure
+
+This procedure has the `ROLLBACK` command at the end. However, the `PRAGMA ANONYMOUS_TRANSACTION` isn't included in this procedure.
+
+```sql
+CREATE OR REPLACE PROCEDURE insert_dept_70 IS
+BEGIN
+    INSERT INTO dept VALUES (70,'MARKETING','LOS ANGELES');
+    ROLLBACK;
+END;
+```
+
+The rollback in the procedure removes the two rows inserted in the anonymous block (`deptno` 60 and 70) before the final `COMMIT` command in the anonymous block:
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+    COMMIT;
+END;
+COMMIT;
+```
+
+After the final commit at the end of the transaction, the only row inserted is the first one from the beginning of the transaction. Since the anonymous block is an autonomous transaction, the rollback in the enclosed procedure has no effect on the insertion that occurs before the anonymous block is executed.
+
+```sql
+SELECT * FROM dept ORDER by 1;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     50 | HR         | DENVER
+(5 rows)
+```
+
+## Scenario 2c: Autonomous transaction anonymous block with COMMIT, including procedure with ROLLBACK that is also an autonomous transaction procedure
+
+The procedure with the `ROLLBACK` command at the end also has `PRAGMA ANONYMOUS_TRANSACTION` included. This isolates the effect of the `ROLLBACK` command in the procedure.
+
+```sql
+CREATE OR REPLACE PROCEDURE insert_dept_70 IS
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    INSERT INTO dept VALUES (70,'MARKETING','LOS ANGELES');
+    ROLLBACK;
+END;
+```
+
+The rollback in the procedure removes the row inserted by the procedure but not the other row inserted in the anonymous block.
+
+```sql
+BEGIN;
+INSERT INTO dept VALUES (50,'HR','DENVER');
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+BEGIN
+    INSERT INTO dept VALUES (60,'FINANCE','CHICAGO');
+    insert_dept_70;
+    COMMIT;
+END;
+COMMIT;
+```
+
+After the final commit at the end of the transaction, the row inserted is the first one from the beginning of the transaction as well as the row inserted at the beginning of the anonymous block. The only insertion rolled back is the one in the procedure.
+
+```sql
+SELECT * FROM dept ORDER by 1;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     50 | HR         | DENVER
+     60 | FINANCE    | CHICAGO
+(6 rows)
+```
+
+The following examples show `PRAGMA AUTONOMOUS_TRANSACTION` in a couple of other SPL program types.
+
+## Autonomous transaction trigger
+
+This example shows the effect of declaring a trigger with `PRAGMA AUTONOMOUS_TRANSACTION`.
+
+The following table is created to log changes to the `emp` table:
+
+```sql
+CREATE TABLE empauditlog (
+    audit_date      DATE,
+    audit_user      VARCHAR2(20),
+    audit_desc      VARCHAR2(20)
+);
+```
+
+The trigger attached to the `emp` table that inserts these changes into the `empauditlog` table is the following. `PRAGMA AUTONOMOUS_TRANSACTION` is included in the declaration section.
+
+```sql
+CREATE OR REPLACE TRIGGER emp_audit_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+DECLARE
+    PRAGMA AUTONOMOUS_TRANSACTION;
+    v_action        VARCHAR2(20);
+BEGIN
+    IF INSERTING THEN
+        v_action := 'Added employee(s)';
+    ELSIF UPDATING THEN
+        v_action := 'Updated employee(s)';
+    ELSIF DELETING THEN
+        v_action := 'Deleted employee(s)';
+    END IF;
+    INSERT INTO empauditlog VALUES (SYSDATE, USER,
+        v_action);
+END;
+```
+
+The following two inserts are made into the `emp` table in a transaction started by the `BEGIN` command:
+
+```sql
+BEGIN;
+INSERT INTO emp VALUES (9001,'SMITH','ANALYST',7782,SYSDATE,NULL,NULL,10);
+INSERT INTO emp VALUES (9002,'JONES','CLERK',7782,SYSDATE,NULL,NULL,10);
+```
+
+The following shows the two new rows in the `emp` table as well as the two entries in the `empauditlog` table:
+
+```sql
+SELECT * FROM emp WHERE empno > 9000;
+__OUTPUT__
+ empno | ename |   job   | mgr  |      hiredate      | sal | comm | deptno
+-------+-------+---------+------+--------------------+-----+------+--------
+  9001 | SMITH | ANALYST | 7782 | 23-AUG-18 07:12:27 |     |      |     10
+  9002 | JONES | CLERK   | 7782 | 23-AUG-18 07:12:27 |     |      |     10
+(2 rows)
+```
+```sql
+SELECT TO_CHAR(AUDIT_DATE,'DD-MON-YY HH24:MI:SS') AS "audit date",
+ audit_user, audit_desc FROM empauditlog ORDER BY 1 ASC;
+__OUTPUT__
+  audit date        |  audit_user  |    audit_desc
+--------------------+--------------+-------------------
+ 23-AUG-18 07:12:27 | enterprisedb | Added employee(s)
+ 23-AUG-18 07:12:27 | enterprisedb | Added employee(s)
+(2 rows)
+```
+
+But then the `ROLLBACK` command is given during this session. The `emp` table no longer contains the two rows, but the `empauditlog` table still contains its two entries. The trigger implicitly performed a commit, and `PRAGMA AUTONOMOUS_TRANSACTION` commits those changes independent from the rollback given in the calling transaction.
+
+```sql
+ROLLBACK;
+
+SELECT * FROM emp WHERE empno > 9000;
+__OUTPUT__
+ empno | ename | job | mgr | hiredate | sal | comm | deptno
+-------+-------+-----+-----+----------+-----+------+--------
+(0 rows)
+```
+```sql
+SELECT TO_CHAR(AUDIT_DATE,'DD-MON-YY HH24:MI:SS') AS "audit date",
+    audit_user, audit_desc FROM empauditlog ORDER BY 1 ASC;
+__OUTPUT__
+     audit date     |  audit_user  |    audit_desc
+--------------------+--------------+-------------------
+ 23-AUG-18 07:12:27 | enterprisedb | Added employee(s)
+ 23-AUG-18 07:12:27 | enterprisedb | Added employee(s)
+(2 rows)
+```
+
+## Autonomous transaction object type method
+
+This example shows the effect of declaring an object method with `PRAGMA AUTONOMOUS_TRANSACTION`.
+
+The following object type and object type body are created. The member procedure in the object type body contains the `PRAGMA AUTONOMOUS_TRANSACTION` in the declaration section along with `COMMIT` at the end of the procedure.
+
+```sql
+CREATE OR REPLACE TYPE insert_dept_typ AS OBJECT (
+    deptno          NUMBER(2),
+    dname           VARCHAR2(14),
+    loc             VARCHAR2(13),
+    MEMBER PROCEDURE insert_dept
+);
+
+CREATE OR REPLACE TYPE BODY insert_dept_typ AS
+    MEMBER PROCEDURE insert_dept
+    IS
+        PRAGMA AUTONOMOUS_TRANSACTION;
+    BEGIN
+        INSERT INTO dept VALUES (SELF.deptno,SELF.dname,SELF.loc);
+        COMMIT;
+    END;
+END;
+```
+
+In the following anonymous block, an insert is performed into the `dept` table, followed by invoking the `insert_dept` method of the object and ending with a `ROLLBACK` command in the anonymous block.
+
+```sql
+BEGIN;
+DECLARE
+    v_dept          INSERT_DEPT_TYP :=
+                      insert_dept_typ(60,'FINANCE','CHICAGO');
+BEGIN
+    INSERT INTO dept VALUES (50,'HR','DENVER');
+    v_dept.insert_dept;
+    ROLLBACK;
+END;
+```
+
+Since `insert_dept` was declared as an autonomous transaction, its insert of department number 60 remains in the table, but the rollback removes the insertion of department 50:
+
+```sql
+SELECT * FROM dept ORDER BY 1;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+     60 | FINANCE    | CHICAGO
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx
new file mode 100644
index 00000000000..2469034108f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/about_transactions.mdx
@@ -0,0 +1,17 @@
+---
+title: "About transactions"
+---
+
+A transaction begins when the first SQL command is encountered in the SPL program. All subsequent SQL commands are included as part of that transaction. 
+
+The transaction ends when one of the following occurs:  
+
+-   An unhandled exception occurs. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted.
+-   A `COMMIT` command is encountered. In this case, the effect of all database updates made during the transaction become permanent.
+-   A `ROLLBACK` command is encountered. In this case, the effects of all database updates made during the transaction are rolled back, and the transaction is aborted. If a new SQL command is encountered, a new transaction begins.
+-   Control returns to the calling application, such as Java or PSQL. In this case, the action of the application determines whether the transaction is committed or rolled back. The exception is when the transaction is in a block in which `PRAGMA AUTONOMOUS_TRANSACTION` was declared. In this case, the commitment or rollback of the transaction occurs independently of the calling program.
+
+!!! Note
+    Unlike Oracle, DDL commands such as `CREATE TABLE` don't implicitly occur in their own transaction. Therefore, DDL commands don't cause an immediate database commit as in Oracle, and you can roll back DDL commands just like DML commands.
+
+A transaction can span one or more `BEGIN/END` blocks, or a single `BEGIN/END` block can contain one or more transactions.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/index.mdx
new file mode 100644
index 00000000000..404c31aa24d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/06_transaction_control/index.mdx
@@ -0,0 +1,34 @@
+---
+title: "Working with transactions"
+indexCards: simple
+navigation:
+  - about_transactions
+  - 01_commit
+  - 02_rollback
+  - 03_pragma_autonomous_transaction
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.072.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.166.html"
+redirects:
+  - /epas/latest/epas_compat_spl/06_transaction_control/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="transaction_control" class="registered_link"></div>
+
+There might be times when you want all updates to a database to occur successfully or for none to occur in case of any error. A set of database updates that occur successfully as a single unit or not at all is called a *transaction*.
+
+A common example in banking is a funds transfer between two accounts. The two parts of the transaction are the withdrawal of funds from one account and the deposit of the funds in another account. Both parts of this transaction must occur for the bank’s books to balance. The deposit and withdrawal are one transaction.
+
+You can create an SPL application that uses a style of transaction control compatible with Oracle databases if the following conditions are met:
+
+-   The `edb_stmt_level_tx` parameter is set to `TRUE`. This prevents the action of unconditionally rolling back all database updates in the `BEGIN/END` block if any exception occurs.
+-   The application isn't running in autocommit mode. If autocommit mode is on, each successful database update is immediately committed and can't be undone. The manner in which autocommit mode is turned on or off depends on the application.
+
+The three main transaction commands are COMMIT, ROLLBACK, and PRAGM_AUTONOMOUS_TRANSACTION.
+
+<div class="toctree" maxdepth="3">
+
+commit rollback pragma_autonomous_transaction
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/07_dynamic_sql.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/07_dynamic_sql.mdx
new file mode 100644
index 00000000000..07f98567f0a
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/07_dynamic_sql.mdx
@@ -0,0 +1,122 @@
+---
+title: "Using dynamic SQL"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.073.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.167.html"
+redirects:
+  - /epas/latest/epas_compat_spl/07_dynamic_sql/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dynamic_sql" class="registered_link"></div>
+
+*Dynamic SQL* is a technique that lets you execute SQL commands that aren't known until the commands are about to be executed. In static SQL commands, the full command (with the exception of variables) must be known and coded into the program before the program can begin to execute. Using dynamic SQL, the executed SQL can change during program runtime.
+
+In addition, dynamic SQL is the only method by which data definition commands, such as `CREATE TABLE`, can be executed from an SPL program.
+
+However, the runtime performance of dynamic SQL is slower than static SQL.
+
+## Syntax 
+
+The `EXECUTE IMMEDIATE` command is used to run SQL commands dynamically:
+
+```sql
+EXECUTE IMMEDIATE '<sql_expression>;'
+  [ INTO { <variable> [, ...] | <record> } ]
+  [ USING {[<bind_type>] <bind_argument>} [, ...]} ];
+```
+
+Where:
+
+- `sql_expression` is a string expression containing the SQL command to dynamically execute
+- `variable` receives the output of the result set, typically from a `SELECT` command, created as a result of executing the SQL command in `sql_expression`. The number, order, and type of variables must match the number and order and be type-compatible with the fields of the result set. 
+
+When using the `USING` clause, the value of `expression` is passed to a *placeholder*. Placeholders appear embedded in the SQL command in `sql_expression` where you can use variables. Placeholders are denoted by an identifier with a colon (:) prefix, for example, `:name`. The number and order of the evaluated expressions must match the number, order of the placeholders in `sql_expression`. The resulting data types must also be compatible with the placeholders. You don't declare placeholders in the SPL program. They appear only in `sql_expression`.
+
+Currently `bind_type` is ignored, and `bind_argument` is treated as `IN OUT`.
+
+Alternatively, a `record` can be specified as long as the record’s fields match the number and order and are type-compatible with the result set. 
+
+When using the `INTO` clause, exactly one row must be returned in the result set. Otherwise an exception occurs. When using the `USING` clause, the value of `expression` is passed to a *placeholder*. Placeholders appear embedded in the SQL command in `sql_expression` where variables can be used. Placeholders are denoted by an identifier with a colon (:) prefix, such as `:name`. The number, order, and resultant data types of the evaluated expressions must match the number and order and be type-compatible with the placeholders in `sql_expression`. 
+
+Placeholders aren't declared anywhere in the SPL program. They appear only in `sql_expression`.
+
+Currently all options for `bind_type` are ignored and `bind_argument` is treated as `IN OUT`.
+
+## Example: SQL commands as string literals
+
+This example shows basic dynamic SQL commands as string literals:
+
+```sql
+DECLARE
+    v_sql           VARCHAR2(50);
+BEGIN
+    EXECUTE IMMEDIATE 'CREATE TABLE job (jobno NUMBER(3),' ||
+        ' jname VARCHAR2(9))';
+    v_sql := 'INSERT INTO job VALUES (100, ''ANALYST'')';
+    EXECUTE IMMEDIATE v_sql;
+    v_sql := 'INSERT INTO job VALUES (200, ''CLERK'')';
+    EXECUTE IMMEDIATE v_sql;
+END;
+```
+
+This example uses the `USING` clause to pass values to placeholders in the SQL string:
+
+```sql
+DECLARE
+    v_sql           VARCHAR2(50) := 'INSERT INTO job VALUES ' ||
+                        '(:p_jobno, :p_jname)';
+    v_jobno         job.jobno%TYPE;
+    v_jname         job.jname%TYPE;
+BEGIN
+    v_jobno := 300;
+    v_jname := 'MANAGER';
+    EXECUTE IMMEDIATE v_sql USING v_jobno, v_jname;
+    v_jobno := 400;
+    v_jname := 'SALESMAN';
+    EXECUTE IMMEDIATE v_sql USING v_jobno, v_jname;
+    v_jobno := 500;
+    v_jname := 'PRESIDENT';
+    EXECUTE IMMEDIATE v_sql USING v_jobno, v_jname;
+END;
+```
+
+This example shows both the `INTO` and `USING` clauses. The last execution of the `SELECT` command returns the results into a record instead of individual variables.
+
+```sql
+DECLARE
+    v_sql           VARCHAR2(60);
+    v_jobno         job.jobno%TYPE;
+    v_jname         job.jname%TYPE;
+    r_job           job%ROWTYPE;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('JOBNO    JNAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    v_sql := 'SELECT jobno, jname FROM job WHERE jobno = :p_jobno';
+    EXECUTE IMMEDIATE v_sql INTO v_jobno, v_jname USING 100;
+    DBMS_OUTPUT.PUT_LINE(v_jobno || '      ' || v_jname);
+    EXECUTE IMMEDIATE v_sql INTO v_jobno, v_jname USING 200;
+    DBMS_OUTPUT.PUT_LINE(v_jobno || '      ' || v_jname);
+    EXECUTE IMMEDIATE v_sql INTO v_jobno, v_jname USING 300;
+    DBMS_OUTPUT.PUT_LINE(v_jobno || '      ' || v_jname);
+    EXECUTE IMMEDIATE v_sql INTO v_jobno, v_jname USING 400;
+    DBMS_OUTPUT.PUT_LINE(v_jobno || '      ' || v_jname);
+    EXECUTE IMMEDIATE v_sql INTO r_job USING 500;
+    DBMS_OUTPUT.PUT_LINE(r_job.jobno || '      ' || r_job.jname);
+END;
+```
+
+The following is the output from this anonymous block:
+
+```sql
+__OUTPUT__
+JOBNO    JNAME
+-----    -------
+100      ANALYST
+200      CLERK
+300      MANAGER
+400      SALESMAN
+500      PRESIDENT
+```
+
+You can use the `BULK COLLECT` clause to assemble the result set from an `EXECUTE IMMEDIATE` statement into a named collection. See [Using the BULK COLLECT clause](12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause), `EXECUTE IMMEDIATE BULK COLLECT` for more information.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/01_declaring_a_cursor.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/01_declaring_a_cursor.mdx
new file mode 100644
index 00000000000..53901cbeeea
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/01_declaring_a_cursor.mdx
@@ -0,0 +1,35 @@
+---
+title: "Declaring a cursor"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/01_declaring_a_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="declaring_a_cursor" class="registered_link"></div>
+
+Before you can use a cursor, you must first declare it in the declaration section of the SPL program. A cursor declaration appears as follows:
+
+```sql
+CURSOR <name> IS <query>;
+```
+
+Where:
+
+- `name` is an identifier used to reference the cursor and its result set later in the program. 
+- `query` is a SQL `SELECT` command that determines the result set retrievable by the cursor.
+
+!!! Note
+    An extension of this syntax allows the use of parameters. For details, see [Parameterized cursors](08_parameterized_cursors/#parameterized_cursors).
+
+This example shows some cursor declarations:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+    CURSOR emp_cur_2 IS SELECT empno, ename FROM emp;
+    CURSOR emp_cur_3 IS SELECT empno, ename FROM emp WHERE deptno = 10
+        ORDER BY empno;
+BEGIN
+    ...
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/02_opening_a_cursor.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/02_opening_a_cursor.mdx
new file mode 100644
index 00000000000..d32f5673458
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/02_opening_a_cursor.mdx
@@ -0,0 +1,28 @@
+---
+title: "Opening a cursor"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/02_opening_a_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="opening_a_cursor" class="registered_link"></div>
+
+Before you can use a cursor to retrieve rows, you must open it using the `OPEN` statement.
+
+```sql
+OPEN <name>;
+```
+
+`name` is the identifier of a cursor that was previously declared in the declaration section of the SPL program. Don't execute the `OPEN` statement on a cursor that is already open.
+
+This example shows an `OPEN` statement with its corresponding cursor declaration:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    CURSOR emp_cur_3 IS SELECT empno, ename FROM emp WHERE deptno = 10
+        ORDER BY empno;
+BEGIN
+    OPEN emp_cur_3;
+        ...
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/03_fetching_rows_from_a_cursor.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/03_fetching_rows_from_a_cursor.mdx
new file mode 100644
index 00000000000..8771c3886f0
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/03_fetching_rows_from_a_cursor.mdx
@@ -0,0 +1,75 @@
+---
+title: "Fetching rows from a cursor"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/03_fetching_rows_from_a_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="fetching_rows_from_a_cursor" class="registered_link"></div>
+
+Once a cursor is open, you can retrieve rows from the cursor’s result set by using the `FETCH` statement.
+
+## Syntax 
+
+```sql
+FETCH <name> INTO { <record> | <variable> [, <variable_2> ]... };
+```
+
+Where:
+
+- `name` is the identifier of a previously opened cursor. 
+- `record` is the identifier of a previously defined record (for example, using `table%ROWTYPE`). 
+
+`variable, variable_2...` are SPL variables that receive the field data from the fetched row. The fields in `record` or `variable, variable_2...` must match in number and order the fields returned in the `SELECT` list of the query given in the cursor declaration. The data types of the fields in the `SELECT` list must match or be implicitly convertible to the data types of the fields in `record` or the data types of `variable, variable_2...`
+
+!!! Note
+    A variation of `FETCH INTO` using the `BULK COLLECT` clause can return multiple rows at a time into a collection. See [Using the BULK COLLECT clause](../12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information on using the `BULK COLLECT` clause with the `FETCH INTO` statement.
+
+## Example 
+
+The following shows the `FETCH` statement:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    CURSOR emp_cur_3 IS SELECT empno, ename FROM emp WHERE deptno = 10
+        ORDER BY empno;
+BEGIN
+    OPEN emp_cur_3;
+    FETCH emp_cur_3 INTO v_empno, v_ename;
+        ...
+END;
+```
+
+Instead of explicitly declaring the data type of a target variable, you can use `%TYPE` instead. In this way, if the data type of the database column changes, the target variable declaration in the SPL program doesn't have to change. `%TYPE` picks up the new data type of the specified column.
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    CURSOR emp_cur_3 IS SELECT empno, ename FROM emp WHERE deptno = 10
+        ORDER BY empno;
+BEGIN
+    OPEN emp_cur_3;
+    FETCH emp_cur_3 INTO v_empno, v_ename;
+        ...
+END;
+```
+
+If all the columns in a table are retrieved in the order defined in the table, you can use `%ROWTYPE` to define a record into which the `FETCH` statement places the retrieved data. You can then access each field in the record using dot notation:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_emp_rec       emp%ROWTYPE;
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur_1;
+    FETCH emp_cur_1 INTO v_emp_rec;
+    DBMS_OUTPUT.PUT_LINE('Employee Number: ' || v_emp_rec.empno);
+    DBMS_OUTPUT.PUT_LINE('Employee Name  : ' || v_emp_rec.ename);
+        ...
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/04_closing_a_cursor.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/04_closing_a_cursor.mdx
new file mode 100644
index 00000000000..0be146a08ca
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/04_closing_a_cursor.mdx
@@ -0,0 +1,42 @@
+---
+title: "Closing a cursor"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/04_closing_a_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="closing_a_cursor" class="registered_link"></div>
+
+Once all the desired rows are retrieved from the cursor result set, close the cursor. After you close the cursor, you can no longer access the result set. 
+
+The `CLOSE` statement appears as follows:
+
+```sql
+CLOSE <name>;
+```
+
+`name` is the identifier of a cursor that's currently open. After you close a cursor, don't close it again. However, after you close the cursor, you can use the `OPEN` statement again on the closed cursor and rebuild the query result set. After that, the `FETCH` statement can then retrieve the rows of the new result set.
+
+This example uses the `CLOSE` statement:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_emp_rec       emp%ROWTYPE;
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur_1;
+    FETCH emp_cur_1 INTO v_emp_rec;
+    DBMS_OUTPUT.PUT_LINE('Employee Number: ' || v_emp_rec.empno);
+    DBMS_OUTPUT.PUT_LINE('Employee Name  : ' || v_emp_rec.ename);
+    CLOSE emp_cur_1;
+END;
+```
+
+This procedure produces the following output. Employee number `7369, SMITH` is the first row of the result set.
+
+```sql
+EXEC cursor_example;
+__OUTPUT__
+Employee Number: 7369
+Employee Name  : SMITH
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/05_using__rowtype_with_cursors.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/05_using__rowtype_with_cursors.mdx
new file mode 100644
index 00000000000..6022162be01
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/05_using__rowtype_with_cursors.mdx
@@ -0,0 +1,59 @@
+---
+title: "Using %ROWTYPE with cursors"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.075.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.169.html"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/05_using__rowtype_with_cursors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="[using]()%_rowtype_with_cursors" class="registered_link"></div>
+
+Using the `%ROWTYPE` attribute, you can define a record that contains fields corresponding to all columns fetched from a cursor or cursor variable. Each field takes on the data type of its corresponding column. The `%ROWTYPE` attribute is prefixed by a cursor name or cursor variable name.
+
+```text
+<record> <cursor>%ROWTYPE;
+```
+
+`record` is an identifier assigned to the record. `cursor` is an explicitly declared cursor in the current scope.
+
+This example shows how you can use a cursor with `%ROWTYPE` to get information about which employee works in which department:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_info
+IS
+    CURSOR empcur IS SELECT ename, deptno FROM emp;
+    myvar           empcur%ROWTYPE;
+BEGIN
+    OPEN empcur;
+    LOOP
+        FETCH empcur INTO myvar;
+        EXIT WHEN empcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE( myvar.ename || ' works in department '
+            || myvar.deptno );
+    END LOOP;
+    CLOSE empcur;
+END;
+```
+
+The following is the output from this procedure:
+
+```sql
+EXEC emp_info;
+__OUTPUT__
+SMITH works in department 20
+ALLEN works in department 30
+WARD works in department 30
+JONES works in department 20
+MARTIN works in department 30
+BLAKE works in department 30
+CLARK works in department 10
+SCOTT works in department 20
+KING works in department 10
+TURNER works in department 30
+ADAMS works in department 20
+JAMES works in department 30
+FORD works in department 20
+MILLER works in department 10
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/01_isopen.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/01_isopen.mdx
new file mode 100644
index 00000000000..bb53f7f94fd
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/01_isopen.mdx
@@ -0,0 +1,35 @@
+---
+title: "%ISOPEN"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/01_isopen/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="%isopen" class="registered_link"></div>
+
+Use the `%ISOPEN` attribute to test whether a cursor is open.
+
+```text
+<cursor_name>%ISOPEN
+```
+
+`cursor_name` is the name of the cursor for which a `BOOLEAN` data type of `TRUE` is returned if the cursor is open, `FALSE` otherwise.
+
+This example uses `%ISOPEN`:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+        ...
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+        ...
+BEGIN
+        ...
+    IF emp_cur_1%ISOPEN THEN
+        NULL;
+    ELSE
+        OPEN emp_cur_1;
+    END IF;
+    FETCH emp_cur_1 INTO ...
+        ...
+END;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/02_found.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/02_found.mdx
new file mode 100644
index 00000000000..87ede01dbe6
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/02_found.mdx
@@ -0,0 +1,64 @@
+---
+title: "%FOUND"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/02_found/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="%found" class="registered_link"></div>
+
+The `%FOUND` attribute tests whether a row is retrieved from the result set of the specified cursor after a `FETCH` on the cursor.
+
+```text
+<cursor_name>%FOUND
+```
+
+`cursor_name` is the name of the cursor for which a `BOOLEAN` data type of `TRUE` is returned if a row is retrieved from the result set of the cursor after a `FETCH`.
+
+After the last row of the result set is fetched, the next `FETCH` results in `%FOUND` returning `FALSE`. `FALSE` is also returned after the first `FETCH` if the result set has  no rows to begin with.
+
+Referencing `%FOUND` on a cursor before it's opened or after it's closed results in an `INVALID_CURSOR` exception.
+
+`%FOUND` returns `null` if it's referenced when the cursor is open but before the first `FETCH`.
+
+This example uses `%FOUND`:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_emp_rec       emp%ROWTYPE;
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur_1;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FETCH emp_cur_1 INTO v_emp_rec;
+    WHILE emp_cur_1%FOUND LOOP
+        DBMS_OUTPUT.PUT_LINE(v_emp_rec.empno || '     ' || v_emp_rec.ename);
+        FETCH emp_cur_1 INTO v_emp_rec;
+    END LOOP;
+    CLOSE emp_cur_1;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+EXEC cursor_example;
+__OUTPUT__
+EMPNO    ENAME
+-----    ------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/03_notfound.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/03_notfound.mdx
new file mode 100644
index 00000000000..315886b85dc
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/03_notfound.mdx
@@ -0,0 +1,64 @@
+---
+title: "%NOTFOUND"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/03_notfound/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="%notfound" class="registered_link"></div>
+
+The `%NOTFOUND` attribute is the logical opposite of `%FOUND`.
+
+```text
+<cursor_name>%NOTFOUND
+```
+
+`cursor_name` is the name of the cursor for which a `BOOLEAN` data type of `FALSE` is returned if a row is retrieved from the result set of the cursor after a `FETCH`.
+
+After the last row of the result set is fetched, the next `FETCH` results in `%NOTFOUND` returning `TRUE`. `TRUE` is also returned after the first `FETCH` if the result set has no rows to begin with.
+
+Referencing `%NOTFOUND` on a cursor before it's opened or after it's closed results in an `INVALID_CURSOR` exception.
+
+`%NOTFOUND` returns `null` if it's referenced when the cursor is open but before the first `FETCH`.
+
+This example uses `%NOTFOUND`:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_emp_rec       emp%ROWTYPE;
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur_1;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cur_1 INTO v_emp_rec;
+        EXIT WHEN emp_cur_1%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_emp_rec.empno || '     ' || v_emp_rec.ename);
+    END LOOP;
+    CLOSE emp_cur_1;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+EXEC cursor_example;
+__OUTPUT__
+EMPNO    ENAME
+-----    ------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/04_rowcount.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/04_rowcount.mdx
new file mode 100644
index 00000000000..f57ec0a22ee
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/04_rowcount.mdx
@@ -0,0 +1,66 @@
+---
+title: "%ROWCOUNT"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/04_rowcount/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="%rowcount" class="registered_link"></div>
+
+The `%ROWCOUNT` attribute returns an integer showing the number of rows fetched so far from the specified cursor.
+
+```text
+<cursor_name>%ROWCOUNT
+```
+
+`cursor_name` is the name of the cursor for which `%ROWCOUNT` returns the number of rows retrieved thus far. After the last row is retrieved, `%ROWCOUNT` remains set to the total number of rows returned until the cursor is closed. At that point, `%ROWCOUNT` throws an `INVALID_CURSOR` exception if referenced.
+
+Referencing `%ROWCOUNT` on a cursor before it's opened or after it's closed results in an `INVALID_CURSOR` exception.
+
+`%ROWCOUNT` returns `0` if it's referenced when the cursor is open but before the first `FETCH`. `%ROWCOUNT` also returns `0` after the first `FETCH` when the result set has no rows to begin with.
+
+This example uses `%ROWCOUNT`:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    v_emp_rec       emp%ROWTYPE;
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur_1;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cur_1 INTO v_emp_rec;
+        EXIT WHEN emp_cur_1%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_emp_rec.empno || '     ' || v_emp_rec.ename);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('**********************');
+    DBMS_OUTPUT.PUT_LINE(emp_cur_1%ROWCOUNT || ' rows were retrieved');
+    CLOSE emp_cur_1;
+END;
+```
+
+This procedure prints the total number of rows retrieved at the end of the employee list as follows:
+
+```sql
+EXEC cursor_example;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+**********************
+14 rows were retrieved
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/05_summary_of_cursor_states_and_attributes.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/05_summary_of_cursor_states_and_attributes.mdx
new file mode 100644
index 00000000000..1e823b16942
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/05_summary_of_cursor_states_and_attributes.mdx
@@ -0,0 +1,18 @@
+---
+title: "Summary of cursor states and attributes"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/05_summary_of_cursor_states_and_attributes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="summary_of_cursor_states_and_attributes" class="registered_link"></div>
+
+The table summarizes the possible cursor states and the values returned by the cursor attributes.
+
+| Cursor state                              | %ISOPEN | %FOUND                     | %NOTFOUND                  | %ROWCOUNT                  |
+| ----------------------------------------- | ------- | -------------------------- | -------------------------- | -------------------------- |
+| Before `OPEN`                             | False   | `INVALID_CURSOR` exception | `INVALID_CURSOR` exception | `INVALID_CURSOR` Exception |
+| After `OPEN` & before 1st `FETCH`         | True    | Null                       | Null                       | 0                          |
+| After 1st successful `FETCH`              | True    | True                       | False                      | 1                          |
+| After `nth` successful `FETCH` (last row) | True    | True                       | False                      | n                          |
+| After n+1st `FETCH` (after last row)      | True    | False                      | True                       | n                          |
+| After `CLOSE`                             | False   | `INVALID_CURSOR` exception | `INVALID_CURSOR` exception | `INVALID_CURSOR` Exception |
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/index.mdx
new file mode 100644
index 00000000000..599fe7da13c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/06_cursor_attributes/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Cursor attributes"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.076.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.170.html"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/06_cursor_attributes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="cursor_attributes" class="registered_link"></div>
+
+Each cursor has a set of attributes associated with it that allows the program to test its state. These attributes are `%ISOPEN`, `%FOUND`, `%NOTFOUND`, and `%ROWCOUNT`.
+
+<div class="toctree" maxdepth="3">
+
+%isopen %found %notfound %rowcount summary_of_cursor_states_and_attributes
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop.mdx
new file mode 100644
index 00000000000..c8ffd00aa7d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop.mdx
@@ -0,0 +1,66 @@
+---
+title: "Using a cursor FOR loop"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/07_cursor_for_loop/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="cursor_for_loop" class="registered_link"></div>
+
+The programming logic required to process the result set of a cursor usually includes a statement to open the cursor, a loop construct to retrieve each row of the result set, a test for the end of the result set, and a statement to close the cursor. The *cursor FOR loop* is a loop construct that eliminates the need to individually code these statements.
+
+The cursor `FOR` loop opens a previously declared cursor, fetches all rows in the cursor result set, and then closes the cursor.
+
+The syntax for creating a cursor `FOR` loop is as follows:
+
+```sql
+FOR <record> IN <cursor>
+LOOP
+   <statements>
+END LOOP;
+```
+
+Where:
+
+`record` is an identifier assigned to an implicitly declared record with definition `cursor%ROWTYPE`. 
+
+`cursor` is the name of a previously declared cursor. 
+
+`statements` are one or more SPL statements. There must be at least one statement.
+
+This example uses a cursor `FOR` loop:
+
+```sql
+CREATE OR REPLACE PROCEDURE cursor_example
+IS
+    CURSOR emp_cur_1 IS SELECT * FROM emp;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FOR v_emp_rec IN emp_cur_1 LOOP
+        DBMS_OUTPUT.PUT_LINE(v_emp_rec.empno || '     ' || v_emp_rec.ename);
+    END LOOP;
+END;
+```
+
+The following is the output from this procedure:
+
+```sql
+EXEC cursor_example;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/08_parameterized_cursors.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/08_parameterized_cursors.mdx
new file mode 100644
index 00000000000..0fe84a7fa1b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/08_parameterized_cursors.mdx
@@ -0,0 +1,39 @@
+---
+title: "Declaring parameterized cursors"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/08_parameterized_cursors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="parameterized_cursors" class="registered_link"></div>
+
+You can declare a static cursor that accepts parameters and can pass values for those parameters when opening that cursor. This example creates a parameterized cursor that displays the name and salary of all employees from the `emp` table that have a salary less than a specified value. This information is passed as a parameter.
+
+```sql
+DECLARE
+    my_record       emp%ROWTYPE;
+    CURSOR c1 (max_wage NUMBER) IS
+        SELECT * FROM emp WHERE sal < max_wage;
+BEGIN
+    OPEN c1(2000);
+    LOOP
+        FETCH c1 INTO my_record;
+        EXIT WHEN c1%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE('Name = ' || my_record.ename || ', salary = '
+            || my_record.sal);
+    END LOOP;
+    CLOSE c1;
+END;
+```
+
+For example, if you pass the value 2000 as `max_wage`, then you see only the name and salary of all employees that have a salary less than 2000. The following is the result of the above query:
+
+```sql
+Name = SMITH, salary = 800.00
+Name = ALLEN, salary = 1600.00
+Name = WARD, salary = 1250.00
+Name = MARTIN, salary = 1250.00
+Name = TURNER, salary = 1500.00
+Name = ADAMS, salary = 1100.00
+Name = JAMES, salary = 950.00
+Name = MILLER, salary = 1300.00
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/index.mdx
new file mode 100644
index 00000000000..d86d239aeaa
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/08_static_cursors/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "Working with static cursors"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.074.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.168.html"
+redirects:
+  - /epas/latest/epas_compat_spl/08_static_cursors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="static_cursors" class="registered_link"></div>
+
+Rather than executing a whole query at once, you can set up a *cursor* that encapsulates the query and then read the query result set one row at a time. This approach allows you to create SPL program logic that retrieves a row from the result set, does some processing on the data in that row, and then retrieves the next row and repeats the process.
+
+Cursors are most often used in the context of a `FOR` or `WHILE` loop. Include a conditional test in the SPL logic that detects when the end of the result set was reached so the program can exit the loop.
+
+<div class="toctree" maxdepth="3">
+
+declaring_a_cursor opening_a_cursor fetching_rows_from_a_cursor closing_a_cursor using\_%\_rowtype_with_cursors cursor_attributes cursor_for_loop parameterized_cursors
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/01_ref_cursor_overview.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/01_ref_cursor_overview.mdx
new file mode 100644
index 00000000000..eb4cd2e25bc
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/01_ref_cursor_overview.mdx
@@ -0,0 +1,13 @@
+---
+title: "REF CURSOR overview"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/01_ref_cursor_overview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ref_cursor_overview" class="registered_link"></div>
+
+A *cursor variable* is a cursor that contains a pointer to a query result set. The result set is determined by executing the `OPEN FOR` statement using the cursor variable.
+
+A cursor variable isn't tied to a single query like a static cursor is. You can open the same cursor variable a number of times with `OPEN FOR` statements containing different queries. Each time, a new result set is created from that query and made available by way of the cursor variable.
+
+You can pass `REF CURSOR` types as parameters to or from stored procedures and functions. The return type of a function can also be a `REF CURSOR` type. This ability lets you modularize the operations on a cursor into separate programs by passing a cursor variable between programs.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/01_declaring_a_sys_refcursor_cursor_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/01_declaring_a_sys_refcursor_cursor_variable.mdx
new file mode 100644
index 00000000000..59d1b2e4aa0
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/01_declaring_a_sys_refcursor_cursor_variable.mdx
@@ -0,0 +1,23 @@
+---
+title: "Declaring a SYS_REFCURSOR cursor variable"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/01_declaring_a_sys_refcursor_cursor_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="declaring_a_sys_refcursor_cursor_variable" class="registered_link"></div>
+
+The following is the syntax for declaring a `SYS_REFCURSOR` cursor variable:
+
+```sql
+<name> SYS_REFCURSOR;
+```
+
+Where `name` is an identifier assigned to the cursor variable.
+
+This example shows a `SYS_REFCURSOR` variable declaration:
+
+```sql
+DECLARE
+    emp_refcur      SYS_REFCURSOR;
+        ...
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/02_declaring_a_user_defined_ref_cursor_type_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/02_declaring_a_user_defined_ref_cursor_type_variable.mdx
new file mode 100644
index 00000000000..b50e7b1c140
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/02_declaring_a_user_defined_ref_cursor_type_variable.mdx
@@ -0,0 +1,27 @@
+---
+title: "Declaring a user-defined REF CURSOR type variable"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/02_declaring_a_user_defined_ref_cursor_type_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="declaring_a_user_defined_ref_cursor_type_variable" class="registered_link"></div>
+
+You must perform two distinct declaration steps to use a user-defined `REF CURSOR` variable:
+
+-   Create a referenced cursor `TYPE`.
+-   Declare the actual cursor variable based on that `TYPE`.
+
+The syntax for creating a user-defined `REF CURSOR` type:
+
+```sql
+TYPE <cursor_type_name> IS REF CURSOR [RETURN <return_type>];
+```
+
+This example shows a cursor variable declaration:
+
+```sql
+DECLARE
+    TYPE emp_cur_type IS REF CURSOR RETURN emp%ROWTYPE;
+    my_rec emp_cur_type;
+        ...
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/index.mdx
new file mode 100644
index 00000000000..1f1226f1810
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "Declaring a cursor variable"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/02_declaring_a_cursor_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="declaring_a_cursor_variable" class="registered_link"></div>
+
+SPL supports two ways of declaring a cursor variable:
+-  Using the `SYS_REFCURSOR` built-in data type. `SYS_REFCURSOR` is a `REF CURSOR` type that allows any result set to be associated with it. This is known as a *weakly-typed* `REF CURSOR`.
+-  Creating a type of `REF CURSOR` and then declaring a variable of that type. 
+
+Only the declaration of `SYS_REFCURSOR` and user-defined `REF CURSOR` variables differ. The remaining usage, such as opening the cursor, selecting into the cursor, and closing the cursor, is the same for both the cursor types. The examples primarily make use of the `SYS_REFCURSOR` cursors. To make the examples work for a user-defined `REF CURSOR`, change the declaration section.
+
+!!! Note
+    A *strongly-typed* `REF CURSOR` requires the result set to conform to a declared number and order of fields with compatible data types. It can also optionally return a result set.
+
+<div class="toctree" maxdepth="3">
+
+declaring_a_sys_refcursor_cursor_variable declaring_a_user_defined_ref_cursor_type_variable
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/03_opening_a_cursor_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/03_opening_a_cursor_variable.mdx
new file mode 100644
index 00000000000..0ebea20ae9d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/03_opening_a_cursor_variable.mdx
@@ -0,0 +1,34 @@
+---
+title: "Opening a cursor variable"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/03_opening_a_cursor_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="opening_a_cursor_variable" class="registered_link"></div>
+
+Once you declare a cursor variable, you must open it with an associated `SELECT` command. The `OPEN FOR` statement specifies the `SELECT` command to use to create the result set:
+
+```sql
+OPEN <name> FOR query;
+```
+
+Where:
+
+`name` is the identifier of a previously declared cursor variable. 
+
+`query` is a `SELECT` command that determines the result set when the statement is executed. 
+
+The value of the cursor variable after the `OPEN FOR` statement is executed identifies the result set.
+
+This example shows a result set that's a list of employee numbers and names from a selected department. You can use a variable or parameter in the `SELECT` command anywhere an expression can normally appear. In this case, a parameter is used in the equality test for department number.
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_by_dept (
+    p_deptno        emp.deptno%TYPE
+)
+IS
+    emp_refcur      SYS_REFCURSOR;
+BEGIN
+    OPEN emp_refcur FOR SELECT empno, ename FROM emp WHERE deptno = p_deptno;
+        ...
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/04_fetching_rows_from_a_cursor_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/04_fetching_rows_from_a_cursor_variable.mdx
new file mode 100644
index 00000000000..c5bb3ed5601
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/04_fetching_rows_from_a_cursor_variable.mdx
@@ -0,0 +1,31 @@
+---
+title: "Fetching rows From a cursor variable"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/04_fetching_rows_from_a_cursor_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="fetching_rows_from_a_cursor_variable" class="registered_link"></div>
+
+After you open a cursor variable, you can retrieve rows from the result set using the `FETCH` statement. For details, see [Fetching rows from a cursor](../08_static_cursors/03_fetching_rows_from_a_cursor/#fetching_rows_from_a_cursor).
+
+This example uses a `FETCH` statement to cause the result set to be returned into two variables and then displayed. You can also use the cursor attributes used to determine cursor state of static cursors with cursor variables. For details, see [Cursor attributes](../08_static_cursors/06_cursor_attributes/#cursor_attributes).
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_by_dept (
+    p_deptno        emp.deptno%TYPE
+)
+IS
+    emp_refcur      SYS_REFCURSOR;
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+BEGIN
+    OPEN emp_refcur FOR SELECT empno, ename FROM emp WHERE deptno = p_deptno;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+        ...
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/05_closing_a_cursor_variable.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/05_closing_a_cursor_variable.mdx
new file mode 100644
index 00000000000..8846b19ba76
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/05_closing_a_cursor_variable.mdx
@@ -0,0 +1,49 @@
+---
+title: "Closing a cursor variable"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/05_closing_a_cursor_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="closing_a_cursor_variable" class="registered_link"></div>
+
+Use the `CLOSE` statement described in [Closing a cursor](../08_static_cursors/04_closing_a_cursor/#closing_a_cursor) to release the result set.
+
+!!! Note
+    Unlike static cursors, you don't have to close a cursor variable before you can reopen it. When you reopen it, the result set from the previous open is lost.
+
+This example includes the `CLOSE` statement:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_by_dept (
+    p_deptno        emp.deptno%TYPE
+)
+IS
+    emp_refcur      SYS_REFCURSOR;
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+BEGIN
+    OPEN emp_refcur FOR SELECT empno, ename FROM emp WHERE deptno = p_deptno;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_refcur;
+END;
+```
+
+The following is the output from this procedure:
+
+```sql
+EXEC emp_by_dept(20)
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7566     JONES
+7788     SCOTT
+7876     ADAMS
+7902     FORD
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/06_usage_restrictions.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/06_usage_restrictions.mdx
new file mode 100644
index 00000000000..8aa7e5e5d83
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/06_usage_restrictions.mdx
@@ -0,0 +1,24 @@
+---
+title: "Usage restrictions"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/06_usage_restrictions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="usage_restrictions" class="registered_link"></div>
+
+The following are restrictions on cursor variable usage:
+
+-   You can't use comparison operators to test cursor variables for equality, inequality, null, or not null.
+-   You can't assign null to a cursor variable.
+-   You can't store the value of a cursor variable in a database column.
+-   Static cursors and cursor variables aren't interchangeable. For example, you can't use a static cursor in an `OPEN FOR` statement.
+
+The table shows the permitted parameter modes for a cursor variable used as a procedure or function parameter. This use depends on the operations on the cursor variable in the procedure or function.
+
+| Operation | IN    | IN OUT | OUT  |
+| --------- | ----- | ------ | ---- |
+| `OPEN`    | `No`  | `Yes`  | `No` |
+| `FETCH`   | `Yes` | `Yes`  | `No` |
+| `CLOSE`   | `Yes` | `Yes`  | `No` |
+
+For example, if a procedure performs all three operations&mdash;`OPEN FOR`, `FETCH`, and `CLOSE`&mdash;on a cursor variable declared as the procedure’s formal parameter, then that parameter must be declared with `IN OUT` mode.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/01_returning_a_ref_cursor_from_a_function.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/01_returning_a_ref_cursor_from_a_function.mdx
new file mode 100644
index 00000000000..132fbf7c221
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/01_returning_a_ref_cursor_from_a_function.mdx
@@ -0,0 +1,55 @@
+---
+title: "Returning a REF CURSOR from a function"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/01_returning_a_ref_cursor_from_a_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="returning_a_ref_cursor_from_a_function" class="registered_link"></div>
+
+This example opens the cursor variable with a query that selects employees with a given job. The cursor variable is specified in this function’s `RETURN` statement, which makes the result set available to the caller of the function.
+
+```sql
+CREATE OR REPLACE FUNCTION emp_by_job (p_job VARCHAR2)
+RETURN SYS_REFCURSOR
+IS
+    emp_refcur      SYS_REFCURSOR;
+BEGIN
+    OPEN emp_refcur FOR SELECT empno, ename FROM emp WHERE job = p_job;
+    RETURN emp_refcur;
+END;
+```
+
+This function is invoked in the following anonymous block by assigning the function’s return value to a cursor variable declared in the anonymous block’s declaration section. The result set is fetched using this cursor variable, and then it is closed.
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE := 'SALESMAN';
+    v_emp_refcur    SYS_REFCURSOR;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPLOYEES WITH JOB ' || v_job);
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    v_emp_refcur := emp_by_job(v_job);
+    LOOP
+        FETCH v_emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN v_emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE v_emp_refcur;
+END;
+```
+
+The following is the output when the anonymous block is executed:
+
+```sql
+__OUTPUT__
+EMPLOYEES WITH JOB SALESMAN
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7521     WARD
+7654     MARTIN
+7844     TURNER
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/02_modularizing_cursor_operations.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/02_modularizing_cursor_operations.mdx
new file mode 100644
index 00000000000..99a4c48d9d6
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/02_modularizing_cursor_operations.mdx
@@ -0,0 +1,165 @@
+---
+title: "Modularizing cursor operations"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/02_modularizing_cursor_operations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="modularizing_cursor_operations" class="registered_link"></div>
+
+This example shows how you can modularize the various operations on cursor variables into separate programs.
+
+The following procedure opens the given cursor variable with a `SELECT` command that retrieves all rows:
+
+```sql
+CREATE OR REPLACE PROCEDURE open_all_emp (
+    p_emp_refcur    IN OUT SYS_REFCURSOR
+)
+IS
+BEGIN
+    OPEN p_emp_refcur FOR SELECT empno, ename FROM emp;
+END;
+```
+
+This variation opens the given cursor variable with a `SELECT` command that retrieves all rows of a given department:
+
+```sql
+CREATE OR REPLACE PROCEDURE open_emp_by_dept (
+    p_emp_refcur    IN OUT SYS_REFCURSOR,
+    p_deptno        emp.deptno%TYPE
+)
+IS
+BEGIN
+    OPEN p_emp_refcur FOR SELECT empno, ename FROM emp
+        WHERE deptno = p_deptno;
+END;
+```
+
+This variation opens the given cursor variable with a `SELECT` command that retrieves all rows but from a different table. The function’s return value is the opened cursor variable.
+
+```sql
+CREATE OR REPLACE FUNCTION open_dept (
+    p_dept_refcur    IN OUT SYS_REFCURSOR
+) RETURN SYS_REFCURSOR
+IS
+    v_dept_refcur    SYS_REFCURSOR;
+BEGIN
+    v_dept_refcur := p_dept_refcur;
+    OPEN v_dept_refcur FOR SELECT deptno, dname FROM dept;
+    RETURN v_dept_refcur;
+END;
+```
+
+This procedure fetches and displays a cursor variable result set consisting of employee number and name:
+
+```sql
+CREATE OR REPLACE PROCEDURE fetch_emp (
+    p_emp_refcur    IN OUT SYS_REFCURSOR
+)
+IS
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH p_emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN p_emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+END;
+```
+
+This procedure fetches and displays a cursor variable result set consisting of department number and name:
+
+```sql
+CREATE OR REPLACE PROCEDURE fetch_dept (
+    p_dept_refcur   IN SYS_REFCURSOR
+)
+IS
+    v_deptno        dept.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('DEPT   DNAME');
+    DBMS_OUTPUT.PUT_LINE('----   ---------');
+    LOOP
+        FETCH p_dept_refcur INTO v_deptno, v_dname;
+        EXIT WHEN p_dept_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_deptno || '     ' || v_dname);
+    END LOOP;
+END;
+```
+
+This procedure closes the given cursor variable:
+
+```sql
+CREATE OR REPLACE PROCEDURE close_refcur (
+    p_refcur        IN OUT SYS_REFCURSOR
+)
+IS
+BEGIN
+    CLOSE p_refcur;
+END;
+```
+
+This anonymous block executes all the previous programs:
+
+```sql
+DECLARE
+    gen_refcur      SYS_REFCURSOR;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('ALL EMPLOYEES');
+    open_all_emp(gen_refcur);
+    fetch_emp(gen_refcur);
+    DBMS_OUTPUT.PUT_LINE('****************');
+
+    DBMS_OUTPUT.PUT_LINE('EMPLOYEES IN DEPT #10');
+    open_emp_by_dept(gen_refcur, 10);
+    fetch_emp(gen_refcur);
+    DBMS_OUTPUT.PUT_LINE('****************');
+
+    DBMS_OUTPUT.PUT_LINE('DEPARTMENTS');
+    fetch_dept(open_dept(gen_refcur));
+    DBMS_OUTPUT.PUT_LINE('*****************');
+
+    close_refcur(gen_refcur);
+END;
+```
+
+The following is the output from the anonymous block:
+
+```sql
+__OUTPUT__
+ALL EMPLOYEES
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+****************
+EMPLOYEES IN DEPT #10
+EMPNO    ENAME
+-----    -------
+7782     CLARK
+7839     KING
+7934     MILLER
+****************
+DEPARTMENTS
+DEPT   DNAME
+----   ---------
+10     ACCOUNTING
+20     RESEARCH
+30     SALES
+40     OPERATIONS
+*****************
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/index.mdx
new file mode 100644
index 00000000000..78ed4b8aea4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Cursor variable examples"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/07_examples/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="examples" class="registered_link"></div>
+
+The examples that follow show cursor variable usage.
+
+<div class="toctree" maxdepth="3">
+
+returning_a_ref_cursor_from_a_function modularizing_cursor_operations
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/08_dynamic_queries_with_ref_cursors.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/08_dynamic_queries_with_ref_cursors.mdx
new file mode 100644
index 00000000000..e92536afa04
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/08_dynamic_queries_with_ref_cursors.mdx
@@ -0,0 +1,127 @@
+---
+title: "Using dynamic queries with REF CURSOR"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/08_dynamic_queries_with_ref_cursors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dynamic_queries_with_ref_cursors" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports dynamic queries by way of the `OPEN FOR USING` statement. A string literal or string variable is supplied in the `OPEN FOR USING` statement to the `SELECT` command:
+
+```sql
+OPEN <name> FOR <dynamic_string>
+  [ USING <bind_arg> [, <bind_arg_2> ] ...];
+```
+
+Where: 
+
+`name` is the identifier of a previously declared cursor variable. 
+
+`dynamic_string` is a string literal or string variable containing a `SELECT` command without the terminating semi-colon. 
+
+`bind_arg, bind_arg_2...` are bind arguments that pass variables to corresponding placeholders in the `SELECT` command when the cursor variable is opened. The placeholders are identifiers prefixed by a colon character.
+
+This example shows a dynamic query using a string literal:
+
+```sql
+CREATE OR REPLACE PROCEDURE dept_query
+IS
+    emp_refcur      SYS_REFCURSOR;
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+BEGIN
+    OPEN emp_refcur FOR 'SELECT empno, ename FROM emp WHERE deptno = 30' ||
+        ' AND sal >= 1500';
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_refcur;
+END;
+```
+
+The following is the output from this procedure:
+
+```sql
+EXEC dept_query;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7698     BLAKE
+7844     TURNER
+```
+
+This example query uses bind arguments to pass the query parameters:
+
+```sql
+CREATE OR REPLACE PROCEDURE dept_query (
+    p_deptno        emp.deptno%TYPE,
+    p_sal           emp.sal%TYPE
+)
+IS
+    emp_refcur      SYS_REFCURSOR;
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+BEGIN
+    OPEN emp_refcur FOR 'SELECT empno, ename FROM emp WHERE deptno = :dept'
+        || ' AND sal >= :sal' USING p_deptno, p_sal;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_refcur;
+END;
+```
+
+The following is the resulting output:
+
+```sql
+EXEC dept_query(30, 1500);
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7499     ALLEN
+7698     BLAKE
+7844     TURNER
+```
+
+Finally, a string variable is used to pass the `SELECT`, providing the most flexibility:
+
+```sql
+CREATE OR REPLACE PROCEDURE dept_query (
+    p_deptno        emp.deptno%TYPE,
+    p_sal           emp.sal%TYPE
+)
+IS
+    emp_refcur      SYS_REFCURSOR;
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    p_query_string  VARCHAR2(100);
+BEGIN
+    p_query_string := 'SELECT empno, ename FROM emp WHERE ' ||
+        'deptno = :dept AND sal >= :sal';
+    OPEN emp_refcur FOR p_query_string USING p_deptno, p_sal;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_refcur INTO v_empno, v_ename;
+        EXIT WHEN emp_refcur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_refcur;
+END;
+EXEC dept_query(20, 1500);
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7566     JONES
+7788     SCOTT
+7902     FORD
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/index.mdx
new file mode 100644
index 00000000000..deb5797a616
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/09_ref_cursors_and_cursor_variables/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Working with REF CURSOR and cursor variables"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.077.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.171.html"
+redirects:
+  - /epas/latest/epas_compat_spl/09_ref_cursors_and_cursor_variables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ref_cursors_and_cursor_variables" class="registered_link"></div>
+
+The `REF CURSOR` provides greater flexibility than static cursors.
+
+<div class="toctree" maxdepth="3">
+
+ref_cursor_overview declaring_a_cursor_variable opening_a_cursor_variable fetching_rows_from_a_cursor_variable closing_a_cursor_variable usage_restrictions examples dynamic_queries_with_ref_cursors
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx
new file mode 100644
index 00000000000..1b7d75ab1ef
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/01_associative_arrays.mdx
@@ -0,0 +1,229 @@
+---
+title: "Using associative arrays"
+redirects:
+  - /epas/latest/epas_compat_spl/10_collections/01_associative_arrays/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="associative_arrays" class="registered_link"></div>
+
+An *associative array* is a type of collection that associates a unique key with a value. The key doesn't have to be numeric. It can be character data as well.
+
+## Associative array overview
+
+An associative array has the following characteristics:
+
+-   You must define an *associative array type* after which you can declare *array variables* of that array type. Data manipulation occurs using the array variable.
+-   When an array variable is declared, the associative array is created, but it is empty. Start assigning values to key values.
+-   The key can be any negative integer, positive integer, or zero if you specify `INDEX BY BINARY_INTEGER` or `PLS_INTEGER`.
+-   The key can be character data if you specify `INDEX BY VARCHAR2`.
+-   There's no predefined limit on the number of elements in the array. It grows dynamically as elements are added.
+-   The array can be sparse. There can be gaps in the assignment of values to keys.
+-   An attempt to reference an array element that hasn't been assigned a value results in an exception.
+
+## Defining an associative array
+
+The `TYPE IS TABLE OF ... INDEX BY` statement is used to define an associative array type:
+
+```sql
+TYPE <assoctype> IS TABLE OF { <datatype> | <rectype> | <objtype> }
+  INDEX BY { BINARY_INTEGER | PLS_INTEGER | VARCHAR2(<n>) };
+```
+
+Where: 
+
+`assoctype` is an identifier assigned to the array type. 
+
+`datatype` is a scalar data type such as `VARCHAR2` or `NUMBER`. 
+
+`rectype` is a previously defined record type. 
+
+`objtype` is a previously defined object type. 
+
+`n` is the maximum length of a character key.
+
+## Declaring a variable
+
+To make use of the array, you must declare a *variable* with that array type. The following is the syntax for declaring an array variable:
+
+```text
+<array> <assoctype>
+```
+
+Where:
+
+`array` is an identifier assigned to the associative array. 
+
+`assoctype` is the identifier of a previously defined array type.
+
+## Referencing an element of the array
+
+Reference an element of the array using the following syntax:
+
+```text
+<array>(<n>)[<.field> ]
+```
+
+`array` is the identifier of a previously declared array. 
+
+`n` is the key value, type-compatible with the data type given in the `INDEX BY` clause. 
+
+If the array type of `array` is defined from a record type or object type, then `[.field ]` must reference an individual field in the record type or attribute in the object type from which the array type is defined. Alternatively, you can reference the entire record by omitting `[.field ]`.
+
+## Examples
+
+This example reads the first 10 employee names from the `emp` table, stores them in an array, and then displays the results from the array:
+
+```sql
+DECLARE
+    TYPE emp_arr_typ IS TABLE OF VARCHAR2(10) INDEX BY BINARY_INTEGER;
+    emp_arr         emp_arr_typ;
+    CURSOR emp_cur IS SELECT ename FROM emp WHERE ROWNUM <= 10;
+    i               INTEGER := 0;
+BEGIN
+    FOR r_emp IN emp_cur LOOP
+        i := i + 1;
+        emp_arr(i) := r_emp.ename;
+    END LOOP;
+    FOR j IN 1..10 LOOP
+        DBMS_OUTPUT.PUT_LINE(emp_arr(j));
+    END LOOP;
+END;
+```
+
+This example produces the following output:
+
+```sql
+__OUTPUT__
+SMITH
+ALLEN
+WARD
+JONES
+MARTIN
+BLAKE
+CLARK
+SCOTT
+KING
+TURNER
+```
+
+This example uses a record type in the array definition:
+
+```sql
+DECLARE
+    TYPE emp_rec_typ IS RECORD (
+        empno       NUMBER(4),
+        ename       VARCHAR2(10)
+    );
+    TYPE emp_arr_typ IS TABLE OF emp_rec_typ INDEX BY BINARY_INTEGER;
+    emp_arr         emp_arr_typ;
+    CURSOR emp_cur IS SELECT empno, ename FROM emp WHERE ROWNUM <= 10;
+    i               INTEGER := 0;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FOR r_emp IN emp_cur LOOP
+        i := i + 1;
+        emp_arr(i).empno := r_emp.empno;
+        emp_arr(i).ename := r_emp.ename;
+    END LOOP;
+    FOR j IN 1..10 LOOP
+        DBMS_OUTPUT.PUT_LINE(emp_arr(j).empno || '     ' ||
+            emp_arr(j).ename);
+    END LOOP;
+END;
+```
+
+The following is the output from this anonymous block:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+```
+
+This example uses the `emp%ROWTYPE` attribute to define `emp_arr_typ` instead of using the `emp_rec_typ` record type:
+
+```sql
+DECLARE
+    TYPE emp_arr_typ IS TABLE OF emp%ROWTYPE INDEX BY BINARY_INTEGER;
+    emp_arr         emp_arr_typ;
+    CURSOR emp_cur IS SELECT empno, ename FROM emp WHERE ROWNUM <= 10;
+    i               INTEGER := 0;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FOR r_emp IN emp_cur LOOP
+        i := i + 1;
+        emp_arr(i).empno := r_emp.empno;
+        emp_arr(i).ename := r_emp.ename;
+    END LOOP;
+    FOR j IN 1..10 LOOP
+        DBMS_OUTPUT.PUT_LINE(emp_arr(j).empno || '     ' ||
+            emp_arr(j).ename);
+    END LOOP;
+END;
+```
+
+The results are the same as using a record type in the array definition.
+
+Instead of assigning each field of the record individually, you can make a record-level assignment from `r_emp` to `emp_arr`:
+
+```sql
+DECLARE
+    TYPE emp_rec_typ IS RECORD (
+        empno       NUMBER(4),
+        ename       VARCHAR2(10)
+    );
+    TYPE emp_arr_typ IS TABLE OF emp_rec_typ INDEX BY BINARY_INTEGER;
+    emp_arr         emp_arr_typ;
+    CURSOR emp_cur IS SELECT empno, ename FROM emp WHERE ROWNUM <= 10;
+    i               INTEGER := 0;
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FOR r_emp IN emp_cur LOOP
+        i := i + 1;
+        emp_arr(i) := r_emp;
+    END LOOP;
+    FOR j IN 1..10 LOOP
+        DBMS_OUTPUT.PUT_LINE(emp_arr(j).empno || '     ' ||
+            emp_arr(j).ename);
+    END LOOP;
+END;
+```
+
+This example uses the key of an associative array as character data:
+
+```sql
+DECLARE
+    TYPE job_arr_typ IS TABLE OF NUMBER INDEX BY VARCHAR2(9);
+    job_arr         job_arr_typ;
+BEGIN
+    job_arr('ANALYST')   := 100;
+    job_arr('CLERK')     := 200;
+    job_arr('MANAGER')   := 300;
+    job_arr('SALESMAN')  := 400;
+    job_arr('PRESIDENT') := 500;
+    DBMS_OUTPUT.PUT_LINE('ANALYST  : ' || job_arr('ANALYST'));
+    DBMS_OUTPUT.PUT_LINE('CLERK    : ' || job_arr('CLERK'));
+    DBMS_OUTPUT.PUT_LINE('MANAGER  : ' || job_arr('MANAGER'));
+    DBMS_OUTPUT.PUT_LINE('SALESMAN : ' || job_arr('SALESMAN'));
+    DBMS_OUTPUT.PUT_LINE('PRESIDENT: ' || job_arr('PRESIDENT'));
+END;
+
+ANALYST  : 100
+CLERK    : 200
+MANAGER  : 300
+SALESMAN : 400
+PRESIDENT: 500
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx
new file mode 100644
index 00000000000..1438206d820
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/02_nested_tables.mdx
@@ -0,0 +1,233 @@
+---
+title: "Working with nested tables"
+redirects:
+  - /epas/latest/epas_compat_spl/10_collections/02_nested_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="nested_tables" class="registered_link"></div>
+
+A *nested table* is a type of collection that associates a positive integer with a value. 
+
+## Nested tables overview
+
+A nested table has the following characteristics:
+
+-   You must define a *nested table type*. After that, you can declare *nested table variables* of that nested table type. Data manipulation occurs using the nested table variable, also known simply as a table.
+-   When you declare a nested table variable, the nested table doesn't yet exist. It is a null collection. You must initialize the null table with a *constructor*. You can also initialize the table by using an assignment statement where the right-hand side of the assignment is an initialized table of the same type. 
+!!! Note
+    Initialization of a nested table is mandatory in Oracle but optional in SPL.
+-   The key is a positive integer.
+-   The constructor establishes the number of elements in the table. The `EXTEND` method adds elements to the table. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods). 
+!!! Note
+    Using the constructor to establish the number of elements in the table and using the `EXTEND` method to add elements to the table are mandatory in Oracle but optional in SPL.
+-   The table can be sparse. There can be gaps in assigning values to keys.
+-   An attempt to reference a table element beyond its initialized or extended size results in a `SUBSCRIPT_BEYOND_COUNT` exception.
+
+## Defining a nested table
+
+Use the `TYPE IS TABLE` statement to define a nested table type in the declaration section of an SPL program:
+
+```sql
+TYPE <tbltype> IS TABLE OF { <datatype> | <rectype> | <objtype> };
+```
+
+Where: 
+
+`tbltype` is an identifier assigned to the nested table type. 
+
+`datatype` is a scalar data type such as `VARCHAR2` or `NUMBER`. 
+
+`rectype` is a previously defined record type. 
+
+`objtype` is a previously defined object type.
+
+!!! Note
+    You can use the `CREATE TYPE` command to define a nested table type that's available to all SPL programs in the database. See [SQL reference](../../../reference/oracle_compatibility_reference/epas_compat_sql/39_create_type/) for more information about the `CREATE TYPE` command.
+
+## Declaring a variable
+
+To use the table, you must declare a *variable* of that nested table type. The following is the syntax for declaring a table variable:
+
+```text
+<table> <tbltype>
+```
+
+Where: 
+
+`table` is an identifier assigned to the nested table. 
+
+`tbltype` is the identifier of a previously defined nested table type.
+
+## Initializing the nested table
+
+Initialize a nested table using the nested table type’s constructor:
+
+```sql
+<tbltype> ([ { <expr1> | NULL } [, { <expr2> | NULL } ] [, ...] ])
+```
+
+Where:
+
+`tbltype` is the identifier of the nested table type’s constructor, which has the same name as the nested table type. 
+
+`expr1, expr2, …` are expressions that are type-compatible with the element type of the table. If you specify `NULL`, the corresponding element is set to null. If the parameter list is empty, then an empty nested table is returned, which means the table has no elements. If the table is defined from an object type, then `exprn` must return an object of that object type. The object can be the return value of a function or the object type’s constructor. Or the object can be an element of another nested table of the same type.
+
+If you apply a collection method other than `EXISTS` to an uninitialized nested table, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods).
+
+This example shows a constructor for a nested table:
+
+```sql
+DECLARE
+    TYPE nested_typ IS TABLE OF CHAR(1);
+    v_nested        nested_typ := nested_typ('A','B');
+```
+
+## Referencing an element of the table
+
+Reference an element of the table using the following syntax:
+
+```text
+<table>(<n>)[<.element> ]
+```
+
+Where: 
+
+`table` is the identifier of a previously declared table. 
+
+`n` is a positive integer. 
+
+If the table type of `table` is defined from a record type or object type, then `[.element  ]` must reference an individual field in the record type or attribute in the object type from which the nested table type is defined. Alternatively, you can reference the entire record or object by omitting `[.element  ]`.
+
+## Examples
+
+This example shows a nested table where it's known that there are four elements:
+
+```sql
+DECLARE
+    TYPE dname_tbl_typ IS TABLE OF VARCHAR2(14);
+    dname_tbl       dname_tbl_typ;
+    CURSOR dept_cur IS SELECT dname FROM dept ORDER BY dname;
+    i               INTEGER := 0;
+BEGIN
+    dname_tbl := dname_tbl_typ(NULL, NULL, NULL, NULL);
+    FOR r_dept IN dept_cur LOOP
+        i := i + 1;
+        dname_tbl(i) := r_dept.dname;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('DNAME');
+    DBMS_OUTPUT.PUT_LINE('----------');
+    FOR j IN 1..i LOOP
+        DBMS_OUTPUT.PUT_LINE(dname_tbl(j));
+    END LOOP;
+END;
+```
+
+The following is the output from the example:
+
+```sql
+__OUTPUT__
+DNAME
+----------
+ACCOUNTING
+OPERATIONS
+RESEARCH
+SALES
+```
+
+This example reads the first 10 employee names from the `emp` table, stores them in a nested table, and then displays the results from the table. The SPL code is written to assume that the number of employees to return isn't known beforehand.
+
+```sql
+DECLARE
+    TYPE emp_rec_typ IS RECORD (
+        empno       NUMBER(4),
+        ename       VARCHAR2(10)
+    );
+    TYPE emp_tbl_typ IS TABLE OF emp_rec_typ;
+    emp_tbl         emp_tbl_typ;
+    CURSOR emp_cur IS SELECT empno, ename FROM emp WHERE ROWNUM <= 10;
+    i               INTEGER := 0;
+BEGIN
+    emp_tbl := emp_tbl_typ();
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    FOR r_emp IN emp_cur LOOP
+        i := i + 1;
+        emp_tbl.EXTEND;
+        emp_tbl(i) := r_emp;
+    END LOOP;
+    FOR j IN 1..10 LOOP
+        DBMS_OUTPUT.PUT_LINE(emp_tbl(j).empno || '     ' ||
+            emp_tbl(j).ename);
+    END LOOP;
+END;
+```
+
+An empty table with the constructor `emp_tbl_typ()` is created as the first statement in the executable section of the anonymous block. The `EXTEND` collection method is then used to add an element to the table for each employee returned from the result set. See [Extend](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend/#extend).
+
+The following is the output:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+```
+
+This example shows how you can use a nested table of an object type. First, create an object type with attributes for the department name and location:
+
+```sql
+CREATE TYPE dept_obj_typ AS OBJECT (
+    dname           VARCHAR2(14),
+    loc             VARCHAR2(13)
+);
+```
+
+This anonymous block defines a nested table type whose element consists of the `dept_obj_typ` object type. A nested table variable is declared, initialized, and then populated from the `dept` table. Finally, the elements from the nested table are displayed.
+
+```sql
+DECLARE
+    TYPE dept_tbl_typ IS TABLE OF dept_obj_typ;
+    dept_tbl        dept_tbl_typ;
+    CURSOR dept_cur IS SELECT dname, loc FROM dept ORDER BY dname;
+    i               INTEGER := 0;
+BEGIN
+    dept_tbl := dept_tbl_typ(
+        dept_obj_typ(NULL,NULL),
+        dept_obj_typ(NULL,NULL),
+        dept_obj_typ(NULL,NULL),
+        dept_obj_typ(NULL,NULL)
+    );
+    FOR r_dept IN dept_cur LOOP
+        i := i + 1;
+        dept_tbl(i).dname := r_dept.dname;
+        dept_tbl(i).loc   := r_dept.loc;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('DNAME          LOC');
+    DBMS_OUTPUT.PUT_LINE('----------     ----------');
+    FOR j IN 1..i LOOP
+        DBMS_OUTPUT.PUT_LINE(RPAD(dept_tbl(j).dname,14) || ' ' ||
+            dept_tbl(j).loc);
+    END LOOP;
+END;
+```
+
+The parameters that make up the nested table’s constructor, `dept_tbl_typ`, are calls to the object type’s constructor `dept_obj_typ.` The following is the output from the anonymous block:
+
+```sql
+__OUTPUT__
+DNAME          LOC
+----------     ----------
+ACCOUNTING     NEW YORK
+OPERATIONS     BOSTON
+RESEARCH       DALLAS
+SALES          CHICAGO
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/03_varrays.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/03_varrays.mdx
new file mode 100644
index 00000000000..f25b03d9e43
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/03_varrays.mdx
@@ -0,0 +1,127 @@
+---
+title: "Using varrays"
+redirects:
+  - /epas/latest/epas_compat_spl/10_collections/03_varrays/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="varrays" class="registered_link"></div>
+
+A *varray* or *variable-size array* is a type of collection that associates a positive integer with a value. In many respects, it's similar to a nested table.
+
+## Varray overview
+
+A varray has the following characteristics:
+
+-   You must define a *varray type* with a maximum size limit. After you define the varray type, you can declare *varray variables* of that varray type. Data manipulation occurs using the varray variable, also known simply as a varray. The number of elements in the varray can't exceed the maximum size limit set in the varray type definition.
+-   When you declare a varray variable, the varray at first is a null collection. You must initialize the null varray with a *constructor*. You can also initialize the varray by using an assignment statement where the right-hand side of the assignment is an initialized varray of the same type.
+-   The key is a positive integer.
+-   The constructor sets the number of elements in the varray, which must not exceed the maximum size limit. The `EXTEND` method can add elements to the varray up to the maximum size limit. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods).
+-   Unlike a nested table, a varray cannot be sparse. There are no gaps when assigning values to keys.
+-   An attempt to reference a varray element beyond its initialized or extended size but within the maximum size limit results in a `SUBSCRIPT_BEYOND_COUNT` exception.
+-   An attempt to reference a varray element beyond the maximum size limit or extend a varray beyond the maximum size limit results in a `SUBSCRIPT_OUTSIDE_LIMIT` exception.
+
+## Defining a varray type
+
+The `TYPE IS VARRAY` statement is used to define a varray type in the declaration section of an SPL program:
+
+```sql
+TYPE <varraytype> IS { VARRAY | VARYING ARRAY }(<maxsize>)
+  OF { <datatype> | <objtype> };
+```
+
+Where: 
+
+`varraytype` is an identifier assigned to the varray type. 
+
+`datatype` is a scalar data type such as `VARCHAR2` or `NUMBER`. 
+
+`maxsize` is the maximum number of elements permitted in varrays of that type. 
+
+`objtype` is a previously defined object type.
+
+You can use the `CREATE TYPE` command to define a varray type that's available to all SPL programs in the database. To make use of the varray, you must declare a *variable* of that varray type. The following is the syntax for declaring a varray variable:
+
+```text
+<varray> <varraytype>
+```
+
+Where: 
+
+`varray` is an identifier assigned to the varray. 
+
+`varraytype` is the identifier of a previously defined varray type.
+
+## Initializing a varray
+
+Initialize a varray using the varray type’s constructor:
+
+```text
+<varraytype> ([ { <expr1> | NULL } [, { <expr2> | NULL } ]
+  [, ...] ])
+```
+
+Where: 
+
+`varraytype` is the identifier of the varray type’s constructor, which has the same name as the varray type. 
+
+`expr1, expr2, …` are expressions that are type-compatible with the element type of the varray. If you specify `NULL`, the corresponding element is set to null. If the parameter list is empty, then an empty varray is returned, which means there are no elements in the varray. If the varray is defined from an object type, then `exprn` must return an object of that object type. The object can be the return value of a function or the return value of the object type’s constructor. The object can also be an element of another varray of the same varray type.
+
+If you apply a collection method other than `EXISTS` to an uninitialized varray, a `COLLECTION_IS_NULL` exception is thrown. For details, see [Collection methods](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/#collection_methods).
+
+The following is an example of a constructor for a varray:
+
+```sql
+DECLARE
+    TYPE varray_typ IS VARRAY(2) OF CHAR(1);
+    v_varray        varray_typ := varray_typ('A','B');
+```
+
+## Referencing an element of the varray
+
+Reference an element of the varray using this syntax:
+
+```text
+<varray>(<n>)[<.element> ]
+```
+
+Where:
+
+`varray` is the identifier of a previously declared varray. 
+
+`n` is a positive integer. 
+
+If the varray type of `varray` is defined from an object type, then `[.element ]` must reference an attribute in the object type from which the varray type is defined. Alternatively, you cam reference the entire object by omitting `[.element ].`
+
+This example shows a varray where it is known that there are four elements:
+
+```sql
+DECLARE
+    TYPE dname_varray_typ IS VARRAY(4) OF VARCHAR2(14);
+    dname_varray    dname_varray_typ;
+    CURSOR dept_cur IS SELECT dname FROM dept ORDER BY dname;
+    i               INTEGER := 0;
+BEGIN
+    dname_varray := dname_varray_typ(NULL, NULL, NULL, NULL);
+    FOR r_dept IN dept_cur LOOP
+        i := i + 1;
+        dname_varray(i) := r_dept.dname;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('DNAME');
+    DBMS_OUTPUT.PUT_LINE('----------');
+    FOR j IN 1..i LOOP
+        DBMS_OUTPUT.PUT_LINE(dname_varray(j));
+    END LOOP;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+__OUTPUT__
+DNAME
+----------
+ACCOUNTING
+OPERATIONS
+RESEARCH
+SALES
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/about_collections.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/about_collections.mdx
new file mode 100644
index 00000000000..1071875345f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/about_collections.mdx
@@ -0,0 +1,43 @@
+---
+title: "About collection types"
+---
+
+The most commonly known type of collection is an array. In EDB Postgres Advanced Server, the supported collection types are: 
+- [Associative arrays](01_associative_arrays) (formerly called *index-by-tables* in Oracle) 
+- [Nested tables](02_nested_tables)
+- [Varrays](03_varrays)
+
+## Defining the collection type
+
+To set up a collection:
+
+1. Define a collection of the desired type. You can do this in the declaration section of an SPL program, which results in a *local type* that you can access only in that program. For nested table and varray types, you can also do this using the `CREATE TYPE` command, which creates a persistent, *standalone type* that any SPL program in the database can reference.
+2. Declare variables of the collection type. The collection associated with the declared variable is uninitialized at this point if no value assignment is made as part of the variable declaration.
+
+## Initializing a null collection
+
+-   Uninitialized collections of nested tables and varrays are null. A *null collection* doesn't yet exist. Generally, a `COLLECTION_IS_NULL` exception is thrown if a collection method is invoked on a null collection.
+-   To initialize a null collection, you must either make it an empty collection or assign a non-null value to it. Generally, a null collection is initialized by using its *constructor*.
+
+## Adding elements to an associative array
+
+-   Uninitialized collections of associative arrays exist but have no elements. An existing collection with no elements is called an *empty collection*.
+-   To add elements to an empty associative array, you can assign values to its keys. For nested tables and varrays, generally its constructor is used to assign initial values to the nested table or varray. For nested tables and varrays, you then use the `EXTEND` method to grow the collection beyond its initial size set by the constructor.
+
+## Limitations
+
+- Multilevel collections (that is, where the data item of a collection is another collection) aren't supported.
+
+- Columns of collection types aren't supported.
+
+  For example, you can create an array `varchar2_t`, but you can't create a table using array `varchar2_t` as a column data type.
+
+  ```sql
+  --Create an array 
+  edb=# CREATE TYPE varchar2_t AS TABLE OF character varying;
+  CREATE TYPE
+  --Create a table using array as the column data type
+  edb=# CREATE TABLE t(a varchar2_t);
+  __OUTPUT__
+  ERROR:  column "a" has collection type varchar2_t, columns of collection types are not supported.
+  ```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/index.mdx
new file mode 100644
index 00000000000..380f4a99aeb
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/10_collections/index.mdx
@@ -0,0 +1,25 @@
+---
+title: "Working with collection types"
+indexCards: simple
+navigation:
+  - about_collections
+  - 01_associative_arrays
+  - 02_nested_tables
+  - 03_varrays
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.078.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.172.html"
+redirects:
+  - /epas/latest/epas_compat_spl/10_collections/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="collections" class="registered_link"></div>
+
+A *collection* is a set of ordered data items with the same data type. Generally, the data item is a scalar field. It can also be a user-defined type such as a record type or an object type. In this case, the structure and the data types that make up each field of the user-defined type must be the same for each element in the set. Reference each data item in the set by using subscript notation inside a pair of parentheses.
+
+<div class="toctree" maxdepth="3">
+
+associative_arrays nested_tables varrays
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/01_table.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/01_table.mdx
new file mode 100644
index 00000000000..82557b489cd
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/01_table.mdx
@@ -0,0 +1,32 @@
+---
+title: "Using the TABLE function"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/01_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="table" class="registered_link"></div>
+
+Use the `TABLE()` function to transform the members of an array into a set of rows. The signature is:
+
+```sql
+TABLE(<collection_value>)
+```
+
+Where `collection_value` is an expression that evaluates to a value of collection type.
+
+The `TABLE()` function expands the nested contents of a collection into a table format. You can use the `TABLE()` function anywhere you use a regular table expression.
+
+The `TABLE()` function returns a `SETOF ANYELEMENT`, which is a set of values of any type. For example, if the argument passed to this function is an array of `dates`, `TABLE()` returns a `SETOF dates`. If the argument passed to this function is an array of `paths`, `TABLE()` returns a `SETOF paths`.
+
+You can use the `TABLE()` function to expand the contents of a collection into table form:
+
+```sql
+postgres=# SELECT * FROM TABLE(monthly_balance(445.00, 980.20, 552.00));
+__OUTPUT__
+ monthly_balance
+----------------
+  445.00
+  980.20
+  552.00
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/02_using_the_multiset_union_operator.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/02_using_the_multiset_union_operator.mdx
new file mode 100644
index 00000000000..3b0c5b4aa7c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/02_using_the_multiset_union_operator.mdx
@@ -0,0 +1,264 @@
+---
+title: "Using the MULTISET operators"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/02_using_the_multiset_union_operator/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_the_multiset_union_operator" class="registered_link"></div>
+
+The `MULTISET` operators combine two collections to form a third collection.
+
+## Syntax
+
+```sql
+<coll_1> MULTISET [ UNION | INTERSECT | EXCEPT ] [ ALL | DISTINCT | UNIQUE ] <coll_2>
+```
+
+Where `coll_1` and `coll_2` specify the names of the collections to combine.
+
+Include the `ALL` keyword to specify to represent duplicate elements (elements that are present in both `coll_1` and `coll_2`) in the result, once for each time they're present in the original collections. This is the default behavior.
+
+Include the `DISTINCT` or `UNIQUE` keyword to include duplicate elements in the result only once. There is no difference between the `DISTINCT` and `UNIQUE` keywords.
+
+There are three forms of MULTISET operators:
+
+- MULTISET UNION
+- MULTISET INTERSECT
+- MULTISET EXCEPT
+
+## MULTISET UNION 
+
+`MULTISET UNION` takes as arguments two nested tables and returns a nested table whose values from both the input nested tables. The two input nested tables must be of the same type, and the returned nested table is of the same type as well.
+
+This example uses the `MULTISET UNION` operator to combine `collection_1` and `collection_2` into a third collection, `collection_3`:
+
+```sql
+DECLARE
+    TYPE int_arr_typ IS TABLE OF NUMBER(2);
+    collection_1    int_arr_typ;
+    collection_2    int_arr_typ;
+    collection_3    int_arr_typ;
+    v_results       VARCHAR2(50);
+BEGIN
+    collection_1 := int_arr_typ(10,20,30);
+    collection_2 := int_arr_typ(30,40);
+    collection_3 := collection_1 MULTISET UNION ALL collection_2;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || collection_3.COUNT);
+    FOR i IN collection_3.FIRST .. collection_3.LAST LOOP
+        IF collection_3(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || collection_3(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+Results: 10 20 30 30 40
+```
+
+The resulting collection includes one entry for each element in `collection_1` and `collection_2`. If you use the `DISTINCT` keyword, the results are as follows:
+
+```sql
+DECLARE
+    TYPE int_arr_typ IS TABLE OF NUMBER(2);
+    collection_1    int_arr_typ;
+    collection_2    int_arr_typ;
+    collection_3    int_arr_typ;
+    v_results       VARCHAR2(50);
+BEGIN
+    collection_1 := int_arr_typ(10,20,30);
+    collection_2 := int_arr_typ(30,40);
+    collection_3 := collection_1 MULTISET UNION DISTINCT collection_2;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || collection_3.COUNT);
+    FOR i IN collection_3.FIRST .. collection_3.LAST LOOP
+        IF collection_3(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || collection_3(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 4
+Results: 10 20 30 40
+```
+
+The resulting collection includes only those members with distinct values. 
+
+In this example, the `MULTISET UNION DISTINCT` operator removes duplicate entries that are stored in the same collection:
+
+```sql
+DECLARE
+    TYPE int_arr_typ IS TABLE OF NUMBER(2);
+    collection_1    int_arr_typ;
+    collection_2    int_arr_typ;
+    collection_3    int_arr_typ;
+    v_results       VARCHAR2(50);
+BEGIN
+    collection_1 := int_arr_typ(10,20,30,30);
+    collection_2 := int_arr_typ(40,50);
+    collection_3 := collection_1 MULTISET UNION DISTINCT collection_2;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || collection_3.COUNT);
+    FOR i IN collection_3.FIRST .. collection_3.LAST LOOP
+        IF collection_3(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || collection_3(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+Results: 10 20 30 40 50
+```
+
+### MULTISET INTERSECT
+
+`MULTISET INTERSECT` takes as arguments two nested tables and returns a nested table whose values are common in the two input nested tables. The two input nested tables must be of the same type, and the returned nested table is of the same type as well.
+
+This example uses the `MULTISET INTERSECT` operator to combine `color_name` and `fruit_name` into a third collection, `common_name`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Orange', 'Peach', 'Yellow', 'Peach');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach', 'Peach');
+  common_name := color_name MULTISET INTERSECT UNIQUE fruit_name;
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Orange
+Peach
+```
+
+This example shows the use of `MULTISET INTERSECT DISTINCT`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Orange', 'Peach', 'Yellow', 'Peach');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach', 'Peach');
+  common_name := color_name MULTISET INTERSECT DISTINCT fruit_name;
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Orange
+Peach
+```
+
+This example shows the use of `MULTISET INTERSECT ALL`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Orange', 'Peach', 'Yellow', 'Peach');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach', 'Peach');
+  common_name := color_name MULTISET INTERSECT ALL fruit_name;
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Orange
+Peach
+Peach
+```
+
+### MULTISET EXCEPT
+
+`MULTISET EXCEPT` takes two nested tables as arguments and returns a nested table whose elements are in the first nested table but not in the second nested table. The two input nested tables must be of the same type, and the returned nested table is of the same type as well.
+
+This example shows the use of `MULTISET EXCEPT UNIQUE`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Blue', 'Orange', 'Peach', 'Yellow');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach');
+  common_name := color_name MULTISET EXCEPT UNIQUE fruit_name;
+
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Blue
+Green
+Red
+Yellow
+```
+
+This example shows the use of `MULTISET EXCEPT DISTINCT`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Blue', 'Orange', 'Peach', 'Yellow');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach');
+  common_name := color_name MULTISET EXCEPT DISTINCT fruit_name;
+
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Blue
+Green
+Red
+Yellow
+```
+
+This example shows the use of `MULTISET EXCEPT ALL`:
+
+```sql
+DECLARE
+  TYPE name_typ IS TABLE OF VARCHAR(50);
+  color_name  name_typ;
+  fruit_name  name_typ;
+  common_name name_typ;
+BEGIN
+  color_name := name_typ('Red', 'Green', 'Blue', 'Blue', 'Orange', 'Peach', 'Yellow');
+  fruit_name := name_typ('Mango', 'Orange', 'Grapes', 'Banana', 'Peach');
+  common_name := color_name MULTISET EXCEPT ALL fruit_name;
+
+  FOR i IN common_name.FIRST .. common_name.LAST LOOP
+    DBMS_OUTPUT.PUT_LINE(common_name(i));
+  END LOOP;
+END;
+__OUTPUT__
+Red
+Green
+Blue
+Blue
+Yellow
+```
+
+
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx
new file mode 100644
index 00000000000..860cfa6e692
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement.mdx
@@ -0,0 +1,111 @@
+---
+title: "Using the FORALL statement"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_the_forall_statement" class="registered_link"></div>
+
+You can use collections to process DML commands more efficiently by passing all the values to be used for repetitive execution of a `DELETE`, `INSERT`, or `UPDATE` command in one pass to the database server. The alternative is to reiteratively invoke the DML command with new values. Specify the DML command to process this way with the `FORALL` statement. In addition, provide one or more collections in the DML command where you want to subsitute different values each time the command is executed.
+
+## Syntax 
+
+```sql
+FORALL <index> IN <lower_bound> .. <upper_bound>
+  { <insert_stmt> | <update_stmt> | <delete_stmt> };
+```
+
+`index` is the position in the collection given in the `insert_stmt`, `update_stmt`, or `delete_stmt` DML command that iterates from the integer value given as `lower_bound` up to and including `upper_bound.`
+
+## How it works
+
+If an exception occurs during any iteration of the `FORALL` statement, all updates that occurred since the start of the execution of the `FORALL` statement are rolled back. 
+
+!!! Note 
+    This behavior isn't compatible with Oracle databases. Oracle allows explicit use of the `COMMIT` or `ROLLBACK` commands to control whether to commit or roll back updates that occurred prior to the exception.
+
+The `FORALL` statement creates a loop. Each iteration of the loop increments the `index` variable. You typically use the `index` in the loop to select a member of a collection. Control the number of iterations with the `lower_bound .. upper_bound` clause. The loop executes once for each integer between the `lower_bound` and `upper_bound` (inclusive), and the index increments by one for each iteration. 
+
+For example:
+
+`FORALL i IN 2 .. 5`
+
+This expression creates a loop that executes four times. In the first iteration, `index (i)` is set to the value `2`. In the second iteration, the index is set to the value `3`, and so on. The loop executes for the value `5` and then terminates.
+
+## Using FORALL with CREATE
+
+This example creates a table `emp_copy` that's an empty copy of the `emp` table. The example declares a type `emp_tbl` that's an array. Each element in the array is of composite type, composed of the column definitions used to create the table `emp`. The example also creates an index on the `emp_tbl` type.
+
+`t_emp` is an associative array of type `emp_tbl`. The `SELECT` statement uses the `BULK COLLECT INTO` command to populate the `t_emp` array. After the `t_emp` array is populated, the `FORALL` statement iterates through the values `(i)` in the `t_emp` array index and inserts a row for each record into `emp_copy`.
+
+```sql
+CREATE TABLE emp_copy(LIKE emp);
+
+DECLARE
+
+    TYPE emp_tbl IS TABLE OF emp%ROWTYPE INDEX BY BINARY_INTEGER;
+
+    t_emp emp_tbl;
+
+BEGIN
+    SELECT * FROM emp BULK COLLECT INTO t_emp;
+
+    FORALL i IN t_emp.FIRST .. t_emp.LAST
+     INSERT INTO emp_copy VALUES t_emp(i);
+
+END;
+```
+
+## Using FORALL with UPDATE
+
+This example uses a `FORALL` statement to update the salary of three employees:
+
+```sql
+DECLARE
+    TYPE empno_tbl  IS TABLE OF emp.empno%TYPE INDEX BY BINARY_INTEGER;
+    TYPE sal_tbl    IS TABLE OF emp.ename%TYPE INDEX BY BINARY_INTEGER;
+    t_empno         EMPNO_TBL;
+    t_sal           SAL_TBL;
+BEGIN
+    t_empno(1)  := 9001;
+    t_sal(1)    := 3350.00;
+    t_empno(2)  := 9002;
+    t_sal(2)    := 2000.00;
+    t_empno(3)  := 9003;
+    t_sal(3)    := 4100.00;
+    FORALL i IN t_empno.FIRST..t_empno.LAST
+        UPDATE emp SET sal = t_sal(i) WHERE empno = t_empno(i);
+END;
+
+SELECT * FROM emp WHERE empno > 9000;
+__OUTPUT__
+ empno | ename  |   job   | mgr | hiredate |   sal   | comm | deptno
+-------+--------+---------+-----+----------+---------+------+--------
+  9001 | JONES  | ANALYST |     |          | 3350.00 |      |     40
+  9002 | LARSEN | CLERK   |     |          | 2000.00 |      |     40
+  9003 | WILSON | MANAGER |     |          | 4100.00 |      |     40
+(3 rows)
+```
+
+## Using FORALL with DELETE
+
+This example deletes three employees in a `FORALL` statement:
+
+```sql
+DECLARE
+    TYPE empno_tbl  IS TABLE OF emp.empno%TYPE INDEX BY BINARY_INTEGER;
+    t_empno         EMPNO_TBL;
+BEGIN
+    t_empno(1)  := 9001;
+    t_empno(2)  := 9002;
+    t_empno(3)  := 9003;
+    FORALL i IN t_empno.FIRST..t_empno.LAST
+        DELETE FROM emp WHERE empno = t_empno(i);
+END;
+
+SELECT * FROM emp WHERE empno > 9000;
+__OUTPUT__
+ empno | ename | job | mgr | hiredate | sal | comm | deptno
+-------+-------+-----+-----+----------+-----+------+--------
+(0 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx
new file mode 100644
index 00000000000..efabad8c21b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect.mdx
@@ -0,0 +1,112 @@
+---
+title: "SELECT BULK COLLECT"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="select_bulk_collect" class="registered_link"></div>
+
+The following shows the syntax for the `BULK COLLECT` clause with the `SELECT INTO` statement. For details on the `SELECT INTO` statement, see [SELECT INTO](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into/#select_into).
+
+```sql
+SELECT <select_expressions> BULK COLLECT INTO <collection>
+  [, ...] FROM ...;
+```
+
+If you specify a single collection, then `collection` can be a collection of a single field, or it can be a collection of a record type. If you specify more than one collection, then each `collection` must consist of a single field. `select_expressions` must match all fields in the target collections in number, order, and type-compatibility.
+
+This example uses the `BULK COLLECT` clause where the target collections are associative arrays consisting of a single field:
+
+```sql
+DECLARE
+    TYPE empno_tbl    IS TABLE OF emp.empno%TYPE    INDEX BY BINARY_INTEGER;
+    TYPE ename_tbl    IS TABLE OF emp.ename%TYPE    INDEX BY BINARY_INTEGER;
+    TYPE job_tbl      IS TABLE OF emp.job%TYPE      INDEX BY BINARY_INTEGER;
+    TYPE hiredate_tbl IS TABLE OF emp.hiredate%TYPE INDEX BY BINARY_INTEGER;
+    TYPE sal_tbl      IS TABLE OF emp.sal%TYPE      INDEX BY BINARY_INTEGER;
+    TYPE comm_tbl     IS TABLE OF emp.comm%TYPE     INDEX BY BINARY_INTEGER;
+    TYPE deptno_tbl   IS TABLE OF emp.deptno%TYPE   INDEX BY BINARY_INTEGER;
+    t_empno           EMPNO_TBL;
+    t_ename           ENAME_TBL;
+    t_job             JOB_TBL;
+    t_hiredate        HIREDATE_TBL;
+    t_sal             SAL_TBL;
+    t_comm            COMM_TBL;
+    t_deptno          DEPTNO_TBL;
+BEGIN
+    SELECT empno, ename, job, hiredate, sal, comm, deptno BULK COLLECT
+       INTO t_empno, t_ename, t_job, t_hiredate, t_sal, t_comm, t_deptno
+       FROM emp;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME    JOB        HIREDATE    ' ||
+        'SAL        ' || 'COMM      DEPTNO');
+    DBMS_OUTPUT.PUT_LINE('-----  -------  ---------  ---------   ' ||
+        '--------   ' || '--------  ------');
+    FOR i IN 1..t_empno.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(t_empno(i) || '   ' ||
+            RPAD(t_ename(i),8) || ' ' ||
+            RPAD(t_job(i),10) || ' ' ||
+            TO_CHAR(t_hiredate(i),'DD-MON-YY') || ' ' ||
+            TO_CHAR(t_sal(i),'99,999.99') || ' ' ||
+            TO_CHAR(NVL(t_comm(i),0),'99,999.99') || '  ' ||
+            t_deptno(i));
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME    JOB        HIREDATE    SAL        COMM      DEPTNO
+-----  -------  ---------  ---------   --------   --------  ------
+7369   SMITH    CLERK      17-DEC-80     800.00        .00  20
+7499   ALLEN    SALESMAN   20-FEB-81   1,600.00     300.00  30
+7521   WARD     SALESMAN   22-FEB-81   1,250.00     500.00  30
+7566   JONES    MANAGER    02-APR-81   2,975.00        .00  20
+7654   MARTIN   SALESMAN   28-SEP-81   1,250.00   1,400.00  30
+7698   BLAKE    MANAGER    01-MAY-81   2,850.00        .00  30
+7782   CLARK    MANAGER    09-JUN-81   2,450.00        .00  10
+7788   SCOTT    ANALYST    19-APR-87   3,000.00        .00  20
+7839   KING     PRESIDENT  17-NOV-81   5,000.00        .00  10
+7844   TURNER   SALESMAN   08-SEP-81   1,500.00        .00  30
+7876   ADAMS    CLERK      23-MAY-87   1,100.00        .00  20
+7900   JAMES    CLERK      03-DEC-81     950.00        .00  30
+7902   FORD     ANALYST    03-DEC-81   3,000.00        .00  20
+7934   MILLER   CLERK      23-JAN-82   1,300.00        .00  10
+```
+
+This example produces the same result but uses an associative array on a record type defined with the `%ROWTYPE` attribute:
+
+```sql
+DECLARE
+    TYPE emp_tbl IS TABLE OF emp%ROWTYPE INDEX BY BINARY_INTEGER;
+    t_emp           EMP_TBL;
+BEGIN
+    SELECT * BULK COLLECT INTO t_emp FROM emp;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME    JOB        HIREDATE    ' ||
+        'SAL        ' || 'COMM      DEPTNO');
+    DBMS_OUTPUT.PUT_LINE('-----  -------  ---------  ---------   ' ||
+        '--------   ' || '--------  ------');
+    FOR i IN 1..t_emp.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(t_emp(i).empno || '   ' ||
+            RPAD(t_emp(i).ename,8) || ' ' ||
+            RPAD(t_emp(i).job,10) || ' ' ||
+            TO_CHAR(t_emp(i).hiredate,'DD-MON-YY') || ' ' ||
+            TO_CHAR(t_emp(i).sal,'99,999.99') || ' ' ||
+            TO_CHAR(NVL(t_emp(i).comm,0),'99,999.99') || '  ' ||
+            t_emp(i).deptno);
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME    JOB        HIREDATE    SAL        COMM      DEPTNO
+-----  -------  ---------  ---------   --------   --------  ------
+7369   SMITH    CLERK      17-DEC-80     800.00        .00  20
+7499   ALLEN    SALESMAN   20-FEB-81   1,600.00     300.00  30
+7521   WARD     SALESMAN   22-FEB-81   1,250.00     500.00  30
+7566   JONES    MANAGER    02-APR-81   2,975.00        .00  20
+7654   MARTIN   SALESMAN   28-SEP-81   1,250.00   1,400.00  30
+7698   BLAKE    MANAGER    01-MAY-81   2,850.00        .00  30
+7782   CLARK    MANAGER    09-JUN-81   2,450.00        .00  10
+7788   SCOTT    ANALYST    19-APR-87   3,000.00        .00  20
+7839   KING     PRESIDENT  17-NOV-81   5,000.00        .00  10
+7844   TURNER   SALESMAN   08-SEP-81   1,500.00        .00  30
+7876   ADAMS    CLERK      23-MAY-87   1,100.00        .00  20
+7900   JAMES    CLERK      03-DEC-81     950.00        .00  30
+7902   FORD     ANALYST    03-DEC-81   3,000.00        .00  20
+7934   MILLER   CLERK      23-JAN-82   1,300.00        .00  10
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/02_fetch_bulk_collect.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/02_fetch_bulk_collect.mdx
new file mode 100644
index 00000000000..4580a46afad
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/02_fetch_bulk_collect.mdx
@@ -0,0 +1,110 @@
+---
+title: "FETCH BULK COLLECT"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/02_fetch_bulk_collect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="fetch_bulk_collect" class="registered_link"></div>
+
+You can use the `BULK COLLECT` clause with a `FETCH` statement. Instead of returning a single row at a time from the result set, the `FETCH BULK COLLECT` returns all rows at once from the result set into one or more specified collections (both scalar and composite types) unless restricted by the `LIMIT` clause:
+
+```sql
+FETCH <name> BULK COLLECT INTO <collection> [, ...] [ LIMIT <n> ];
+```
+
+For information on the `FETCH` statement, see [Fetching rows from a cursor](../../08_static_cursors/03_fetching_rows_from_a_cursor/#fetching_rows_from_a_cursor).
+
+If you specify a single collection, then `collection` can be a collection of a single field, or it can be a collection of a record type. If you specify more than one collection, then each `collection` must consist of a single field or a record type. The expressions in the `SELECT` list of the cursor identified by `name` must match all fields in the target collections in number, order, and type-compatibility. If you specify `LIMIT n`, the number of rows returned into the collection on each `FETCH` doesn't exceed `n`.
+
+This example uses the `FETCH BULK COLLECT` statement to retrieve rows into an associative array:
+
+```sql
+DECLARE
+    TYPE emp_tbl IS TABLE OF emp%ROWTYPE INDEX BY BINARY_INTEGER;
+    t_emp           EMP_TBL;
+    CURSOR emp_cur IS SELECT * FROM emp;
+BEGIN
+    OPEN emp_cur;
+    FETCH emp_cur BULK COLLECT INTO t_emp;
+    CLOSE emp_cur;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME    JOB        HIREDATE    ' ||
+        'SAL        ' || 'COMM      DEPTNO');
+    DBMS_OUTPUT.PUT_LINE('-----  -------  ---------  ---------   ' ||
+        '--------   ' || '--------  ------');
+    FOR i IN 1..t_emp.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(t_emp(i).empno || '   ' ||
+            RPAD(t_emp(i).ename,8) || ' ' ||
+            RPAD(t_emp(i).job,10) || ' ' ||
+            TO_CHAR(t_emp(i).hiredate,'DD-MON-YY') || ' ' ||
+            TO_CHAR(t_emp(i).sal,'99,999.99') || ' ' ||
+            TO_CHAR(NVL(t_emp(i).comm,0),'99,999.99') || '  ' ||
+            t_emp(i).deptno);
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME    JOB        HIREDATE    SAL        COMM      DEPTNO
+-----  -------  ---------  ---------   --------   --------  ------
+7369   SMITH    CLERK      17-DEC-80     800.00        .00  20
+7499   ALLEN    SALESMAN   20-FEB-81   1,600.00     300.00  30
+7521   WARD     SALESMAN   22-FEB-81   1,250.00     500.00  30
+7566   JONES    MANAGER    02-APR-81   2,975.00        .00  20
+7654   MARTIN   SALESMAN   28-SEP-81   1,250.00   1,400.00  30
+7698   BLAKE    MANAGER    01-MAY-81   2,850.00        .00  30
+7782   CLARK    MANAGER    09-JUN-81   2,450.00        .00  10
+7788   SCOTT    ANALYST    19-APR-87   3,000.00        .00  20
+7839   KING     PRESIDENT  17-NOV-81   5,000.00        .00  10
+7844   TURNER   SALESMAN   08-SEP-81   1,500.00        .00  30
+7876   ADAMS    CLERK      23-MAY-87   1,100.00        .00  20
+7900   JAMES    CLERK      03-DEC-81     950.00        .00  30
+7902   FORD     ANALYST    03-DEC-81   3,000.00        .00  20
+7934   MILLER   CLERK      23-JAN-82   1,300.00        .00  10
+```
+
+```sql
+-- Create two object types of composite data types
+CREATE TYPE db_type1 as OBJECT(a INT, b VARCHAR2(10));
+CREATE TYPE db_type2 as OBJECT(c VARCHAR2(10), d INT);
+
+-- Create a table using above object types
+CREATE TABLE db_tab(x DB_TYPE1, s1 NUMBER, y DB_TYPE2, s2 TIMESTAMP);
+
+-- Insert the rows into the table
+INSERT INTO db_tab values(DB_TYPE1(1, '10'), 1.1, DB_TYPE2('100',1000), '1-Jan-2021 12:30:11 PM');
+INSERT INTO db_tab values(DB_TYPE1(2, '20'), 2.2, DB_TYPE2('200',2000), '2-Feb-2022 08:40:52 AM');
+INSERT INTO db_tab values(DB_TYPE1(3, '30'), 3.3, DB_TYPE2('300',3000), '3-Jan-2023 04:20:33 PM');
+```
+
+```sql
+-- Use FETCH BULK COLLECT INTO clause for fetching both scalar and composite types
+DECLARE
+  TYPE type1_tbl IS TABLE OF db_type1 INDEX BY BINARY_INTEGER;
+  TYPE s1_tbl    IS TABLE OF number INDEX BY BINARY_INTEGER;
+  TYPE type2_tbl IS TABLE OF db_type2 INDEX BY BINARY_INTEGER;
+  TYPE s2_tbl    IS TABLE OF timestamp INDEX BY BINARY_INTEGER;
+  x type1_tbl;
+  s1 s1_tbl;
+  y type2_tbl;
+  s2 s2_tbl;
+  CURSOR c1 is SELECT * FROM db_tab ORDER BY s1;
+BEGIN
+  OPEN c1;
+  FETCH c1 BULK COLLECT INTO x, s1, y, s2;
+  FOR i IN 1..x.count LOOP
+    DBMS_OUTPUT.PUT_LINE(x(i)||' '||s1(i)||' '||y(i)||'"'||s2(i)||'"');
+  END LOOP;
+  CLOSE c1;
+
+  SELECT * BULK COLLECT INTO x, s1, y, s2 FROM db_tab ORDER BY s1;
+  FOR i IN 1..x.count LOOP
+    DBMS_OUTPUT.PUT_LINE(x(i)||' '||s1(i)||' '||y(i)||'"'||s2(i)||'"');
+  END LOOP;
+end;
+
+__OUTPUT__
+(1,10) 1.1 (100,1000) "Fri Jan 01 12:30:11 2021"
+(2,20) 2.2 (200,2000) "Wed Feb 02 08:40:52 2022"
+(3,30) 3.3 (300,3000) "Fri Mar 03 04:20:33 2023"
+(1,10) 1.1 (100,1000) "Fri Jan 01 12:30:11 2021"
+(2,20) 2.2 (200,2000) "Wed Feb 02 08:40:52 2022"
+(3,30) 3.3 (300,3000) "Fri Mar 03 04:20:33 2023"
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/03_execute_immediate_bulk_collect.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/03_execute_immediate_bulk_collect.mdx
new file mode 100644
index 00000000000..1c13762a6d4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/03_execute_immediate_bulk_collect.mdx
@@ -0,0 +1,32 @@
+---
+title: "EXECUTE IMMEDIATE BULK COLLECT"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/03_execute_immediate_bulk_collect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="execute_immediate_bulk_collect" class="registered_link"></div>
+
+You can use the `BULK COLLECT` clause with an `EXECUTE IMMEDIATE` statement to specify a collection to receive the returned rows:
+
+```sql
+EXECUTE IMMEDIATE '<sql_expression>;'
+   BULK COLLECT INTO <collection> [,...]
+   [USING {[<bind_type>] <bind_argument>} [, ...]}];
+```
+
+Where: 
+
+`collection` specifies the name of a collection.
+
+`bind_type` specifies the parameter mode of the `bind_argument`.
+
+-   A `bind_type` of `IN` specifies that the `bind_argument` contains a value that's passed to the `sql_expression`.
+-   A `bind_type` of `OUT` specifies that the `bind_argument` receives a value from the `sql_expression`.
+-   A `bind_type` of `IN OUT` specifies that the `bind_argument` is passed to `sql_expression` and then stores the value returned by `sql_expression`.
+
+`bind_argument` specifies a parameter that contains a value that either:
+-  Is passed to the `sql_expression` (specified with a `bind_type` of `IN`)
+-  Receives a value from the `sql_expression` (specified with a `bind_type` of `OUT`)
+-  Does both (specified with a `bind_type` of `IN OUT`). Currently `bind_type` is ignored and `bind_argument` is treated as `IN OUT`.
+
+If you specify a single collection, then `collection` can be a collection of a single field or a collection of a record type. If you specify more than one collection, each `collection` must consist of a single field.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx
new file mode 100644
index 00000000000..c46fe5daafa
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect.mdx
@@ -0,0 +1,144 @@
+---
+title: "RETURNING BULK COLLECT"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/04_returning_bulk_collect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="returning_bulk_collect" class="registered_link"></div>
+
+## Syntax 
+
+You can add `BULK COLLECT` to the `RETURNING INTO` clause of a `DELETE`, `INSERT`, or `UPDATE` command:
+
+```sql
+{ <insert> | <update> | <delete> }
+  RETURNING { * | <expr_1> [, <expr_2> ] ...}
+    BULK COLLECT INTO <collection> [, ...];
+```
+
+For information on the `RETURNING INTO` clause, see [Using the RETURNING INTO clause](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause/#using_the_returning_into_clause). `insert`, `update`, and `delete` are the same as the `INSERT`, `UPDATE`, and `DELETE` commands described in [INSERT](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert/#insert), [UPDATE](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/), and [DELETE](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/). 
+
+If you specify a single collection, then `collection` can be a collection of a single field, or it can be a collection of a record type. If you specify more than one collection, then each `collection` must consist of a single field. The expressions following the `RETURNING` keyword must match all fields in the target collections in number, order, and type-compatibility. Specifying `*` returns all columns in the affected table. 
+
+!!! Note 
+    The use of `*` is an EDB Postgres Advanced Server extension and isn't compatible with Oracle databases.
+
+The `clerkemp` table created by copying the `emp` table is used in the examples that follow.
+
+```sql
+CREATE TABLE clerkemp AS SELECT * FROM emp WHERE job = 'CLERK';
+
+SELECT * FROM clerkemp;
+__OUTPUT__
+ empno | ename  |  job  | mgr  |      hiredate      |   sal   | comm | deptno
+-------+--------+-------+------+--------------------+---------+------+-------
+-
+  7369 | SMITH  | CLERK | 7902 | 17-DEC-80 00:00:00 |  800.00 |      |    20
+  7876 | ADAMS  | CLERK | 7788 | 23-MAY-87 00:00:00 | 1100.00 |      |    20
+  7900 | JAMES  | CLERK | 7698 | 03-DEC-81 00:00:00 |  950.00 |      |    30
+  7934 | MILLER | CLERK | 7782 | 23-JAN-82 00:00:00 | 1300.00 |      |    10
+(4 rows)
+```
+
+## Examples 
+
+This example increases all employee salaries by 1.5, stores the employees’ numbers, names, and new salaries in three associative arrays, and displays the contents of these arrays:
+
+```sql
+DECLARE
+    TYPE empno_tbl IS TABLE OF emp.empno%TYPE INDEX BY BINARY_INTEGER;
+    TYPE ename_tbl IS TABLE OF emp.ename%TYPE INDEX BY BINARY_INTEGER;
+    TYPE sal_tbl   IS TABLE OF emp.sal%TYPE   INDEX BY BINARY_INTEGER;
+    t_empno         EMPNO_TBL;
+    t_ename         ENAME_TBL;
+    t_sal           SAL_TBL;
+BEGIN
+    UPDATE clerkemp SET sal = sal * 1.5 RETURNING empno, ename, sal
+        BULK COLLECT INTO t_empno, t_ename, t_sal;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME      SAL        ');
+    DBMS_OUTPUT.PUT_LINE('-----  -------    --------   ');
+    FOR i IN 1..t_empno.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(t_empno(i) || '   ' || RPAD(t_ename(i),8) ||
+            ' ' || TO_CHAR(t_sal(i),'99,999.99'));
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME      SAL
+-----  -------    --------
+7369   SMITH      1,200.00
+7876   ADAMS      1,650.00
+7900   JAMES      1,425.00
+7934   MILLER     1,950.00
+```
+
+This example uses a single collection defined with a record type to store the employees’ numbers, names, and new salaries:
+
+```sql
+DECLARE
+    TYPE emp_rec IS RECORD (
+        empno       emp.empno%TYPE,
+        ename       emp.ename%TYPE,
+        sal         emp.sal%TYPE
+    );
+    TYPE emp_tbl IS TABLE OF emp_rec INDEX BY BINARY_INTEGER;
+    t_emp           EMP_TBL;
+BEGIN
+    UPDATE clerkemp SET sal = sal * 1.5 RETURNING empno, ename, sal
+        BULK COLLECT INTO t_emp;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME      SAL        ');
+    DBMS_OUTPUT.PUT_LINE('-----  -------    --------   ');
+    FOR i IN 1..t_emp.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(t_emp(i).empno || '   ' ||
+            RPAD(t_emp(i).ename,8) || ' ' ||
+            TO_CHAR(t_emp(i).sal,'99,999.99'));
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME      SAL
+-----  -------    --------
+7369   SMITH      1,200.00
+7876   ADAMS      1,650.00
+7900   JAMES      1,425.00
+7934   MILLER     1,950.00
+```
+
+This example deletes all rows from the `clerkemp` table and returns information on the deleted rows into an associative array. It then displays the array.
+
+```sql
+DECLARE
+    TYPE emp_rec IS RECORD (
+        empno       emp.empno%TYPE,
+        ename       emp.ename%TYPE,
+        job         emp.job%TYPE,
+        hiredate    emp.hiredate%TYPE,
+        sal         emp.sal%TYPE,
+        comm        emp.comm%TYPE,
+        deptno      emp.deptno%TYPE
+    );
+    TYPE emp_tbl IS TABLE OF emp_rec INDEX BY BINARY_INTEGER;
+    r_emp           EMP_TBL;
+BEGIN
+    DELETE FROM clerkemp RETURNING empno, ename, job, hiredate, sal,
+        comm, deptno BULK COLLECT INTO r_emp;
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME    JOB        HIREDATE    ' ||
+        'SAL        ' || 'COMM      DEPTNO');
+    DBMS_OUTPUT.PUT_LINE('-----  -------  ---------  ---------   ' ||
+        '--------   ' || '--------  ------');
+    FOR i IN 1..r_emp.COUNT LOOP
+        DBMS_OUTPUT.PUT_LINE(r_emp(i).empno || '   ' ||
+            RPAD(r_emp(i).ename,8) || ' ' ||
+            RPAD(r_emp(i).job,10) || ' ' ||
+            TO_CHAR(r_emp(i).hiredate,'DD-MON-YY') || ' ' ||
+            TO_CHAR(r_emp(i).sal,'99,999.99') || ' ' ||
+            TO_CHAR(NVL(r_emp(i).comm,0),'99,999.99') || '  ' ||
+            r_emp(i).deptno);
+    END LOOP;
+END;
+__OUTPUT__
+EMPNO  ENAME    JOB        HIREDATE    SAL        COMM      DEPTNO
+-----  -------  ---------  ---------   --------   --------  ------
+7369   SMITH    CLERK      17-DEC-80   1,200.00        .00  20
+7876   ADAMS    CLERK      23-MAY-87   1,650.00        .00  20
+7900   JAMES    CLERK      03-DEC-81   1,425.00        .00  30
+7934   MILLER   CLERK      23-JAN-82   1,950.00        .00  10
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/index.mdx
new file mode 100644
index 00000000000..5b522e9e5ce
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Using the BULK COLLECT clause"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_the_bulk_collect_clause" class="registered_link"></div>
+
+SQL commands that return a result set consisting of a large number of rows might not operate efficiently. This is due to the constant context switching to transfer the entire result set that occurs between the database server and the client. 
+
+You can mitigate this inefficiency by using a collection to gather the entire result set in memory, which the client can then access. You use the `BULK COLLECT` clause to specify the aggregation of the result set into a collection.
+
+You can use the `BULK COLLECT` clause with the `SELECT INTO`, `FETCH INTO`, and `EXECUTE IMMEDIATE` commands. You can also use it with the `RETURNING INTO` clause of the `DELETE`, `INSERT`, and `UPDATE` commands. 
+
+<div class="toctree" maxdepth="3">
+
+select_bulk_collect fetch_bulk_collect execute_immediate_bulk_collect returning_bulk_collect
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages.mdx
new file mode 100644
index 00000000000..79753fba523
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages.mdx
@@ -0,0 +1,83 @@
+---
+title: "Errors and messages"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.081.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.175.html"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/05_errors_and_messages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="errors_and_messages" class="registered_link"></div>
+
+## Reporting messages
+
+Use the `DBMS_OUTPUT.PUT_LINE` statement to report messages:
+
+```sql
+DBMS_OUTPUT.PUT_LINE ( <message> );
+```
+
+Where `message` is any expression evaluating to a string.
+
+This example displays the message on the user’s output display:
+
+```sql
+DBMS_OUTPUT.PUT_LINE('My name is John');
+```
+
+The special variables `SQLCODE` and `SQLERRM` contain a numeric code and a text message, respectively, that describe the outcome of the last SQL command issued. If any other error occurs in the program such as division by zero, these variables contain information pertaining to the error.
+
+
+## SQLCODE and SQLERRM functions
+
+SQLCODE and SQLERRM functions are now available in EDB Postgres Advanced Server.
+
+In an exception handler, the `SQLCODE` function returns the numeric code of the exception being handled. Outside an exception handler, `SQLCODE` returns `0`.
+
+The `SQLERRM` function, returns the error messaage associated with an `SQLCODE` variable value. If the error code value is passed to the `SQLERRM` function, it returns an error message associated with the passed error code value, regardless of the current error raised.
+
+A SQL statement can't invoke `SQLCODE` and `SQLERRM` functions.
+
+Examples:
+
+```sql
+declare
+l_var number;
+begin
+l_var:=-1476;
+dbms_output.put_line(sqlerrm(l_var::int));
+l_var:=0;
+dbms_output.put_line(sqlerrm(l_var::int));
+l_var:=12;
+dbms_output.put_line(sqlerrm(l_var::int));
+l_var:=01403;
+dbms_output.put_line(sqlerrm(l_var::int));
+
+end;
+__OUTPUT__
+division_by_zero
+normal, successful completion
+message 12 not found
+message 1403 not found
+```
+
+
+```sql
+DECLARE
+Balance integer := 24;
+BEGIN
+IF (Balance <= 100) THEN
+Raise_Application_Error (-20343, 'The balance is too low.');
+END IF;
+exception
+    when others then
+        dbms_output.put_line('sqlcode ==>'|| sqlcode);
+        dbms_output.put_line('sqlerrm ==>'|| sqlerrm);
+        dbms_output.put_line('sqlerrm(sqlcode) ==>'|| sqlerrm(sqlcode));
+END;
+__OUTPUT__
+sqlcode ==>-20343
+sqlerrm ==>EDB-20343: The balance is too low.
+sqlerrm(sqlcode) ==>EDB-20343: The balance is too low.
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/index.mdx
new file mode 100644
index 00000000000..f51279460a1
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/12_working_with_collections/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Working with collections"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.080.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.174.html"
+redirects:
+  - /epas/latest/epas_compat_spl/12_working_with_collections/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="working_with_collections" class="registered_link"></div>
+
+Collection operators allow you to transform, query, and manipulate the contents of a collection. 
+
+<div class="toctree" maxdepth="3">
+
+table using_the_multiset_union_operator using_the_forall_statement using_the_bulk_collect_clause errors_and_messages
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/01_overview.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/01_overview.mdx
new file mode 100644
index 00000000000..8ae539a4132
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/01_overview.mdx
@@ -0,0 +1,17 @@
+---
+title: "Trigger overview"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.083.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.177.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/01_overview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="overview" class="registered_link"></div>
+
+A *trigger* is a named SPL code block that's associated with a table and stored in the database. When a specified event occurs on the associated table, the SPL code block executes. The trigger is said to be *fired* when the code block executes.
+
+The event that causes a trigger to fire can be any combination of an insert, update, or deletion carried out on the table, either directly or indirectly. If the table is the object of a SQL `INSERT`, `UPDATE`, `DELETE`, or `TRUNCATE` command, the trigger is directly fired when the corresponding insert, update, delete, or truncate event is defined as a *triggering event*. The events that fire the trigger are defined in the `CREATE TRIGGER` command.
+
+A trigger can fire indirectly if a triggering event occurs on the table as a result of an event initiated on another table. For example, suppose a trigger is defined on a table containing a foreign key defined with the `ON DELETE CASCADE` clause, and a row in the parent table is deleted. In this case, all children of the parent are deleted as well. If deletion is a triggering event on the child table, deleting the children causes the trigger to fire.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx
new file mode 100644
index 00000000000..347856c8faa
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/02_types_of_triggers.mdx
@@ -0,0 +1,25 @@
+---
+title: "Types of triggers"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.084.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.178.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/02_types_of_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="types_of_triggers" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports *row-level* and *statement-level* triggers. 
+
+- A row-level trigger fires once for each row that's affected by a triggering event. For example, suppose deletion is defined as a triggering event on a table, and a single `DELETE` command is issued that deletes five rows from the table. In this case, the trigger fires five times, once for each row.
+
+- A statement-level trigger fires once per triggering statement, regardless of the number of rows affected by the triggering event. In the previous example of a single `DELETE` command deleting five rows, a statement-level trigger fires only once.
+
+You can define the sequence of actions regarding whether the trigger code block executes before or after the triggering statement for statement-level triggers. For row-level triggers, you can define whether the trigger code block executes before or after each row is affected by the triggering statement.
+
+- In a *before* row-level trigger, the trigger code block executes before the triggering action is carried out on each affected row. In a *before* statement-level trigger, the trigger code block executes before the action of the triggering statement is carried out.
+
+- In an *after* row-level trigger, the trigger code block executes after the triggering action is carried out on each affected row. In an *after* statement-level trigger, the trigger code block executes after the action of the triggering statement is carried out.
+
+In a *compound trigger*, you can define a statement-level and a row-level trigger in a single trigger and fire it at more than one timing point. For details, see [Compound triggers](06_compound_triggers/#compound_triggers).
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/03_creating_triggers.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/03_creating_triggers.mdx
new file mode 100644
index 00000000000..5c072f9fe2e
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/03_creating_triggers.mdx
@@ -0,0 +1,209 @@
+---
+title: "Creating triggers"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.085.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.179.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/03_creating_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_triggers" class="registered_link"></div>
+
+The `CREATE TRIGGER` command defines and names a trigger that's stored in the database. You can create a simple trigger or a compound trigger.
+
+## Creating a simple trigger
+
+`CREATE TRIGGER` &mdash; Define a simple trigger.
+
+```sql
+CREATE [ OR REPLACE ] TRIGGER <name>
+  { BEFORE | AFTER | INSTEAD OF }
+  { INSERT | UPDATE | DELETE | TRUNCATE }
+      [ OR { INSERT | UPDATE | DELETE | TRUNCATE } ] [, ...]
+    ON <table>
+  [ REFERENCING { OLD AS <old> | NEW AS <new> } ...]
+  [ FOR EACH ROW ]
+  [ WHEN <condition> ]
+  [ DECLARE
+      [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+      <declaration>; [, ...] ]
+    BEGIN
+      <statement>; [, ...]
+  [ EXCEPTION
+    { WHEN <exception> [ OR <exception> ] [...] THEN
+        <statement>; [, ...] } [, ...]
+  ]
+    END
+```
+
+## Creating a compound trigger
+
+`CREATE TRIGGER` &mdash; Define a compound trigger.
+
+```sql
+CREATE [ OR REPLACE ] TRIGGER <name>
+  FOR { INSERT | UPDATE | DELETE | TRUNCATE }
+        [ OR { INSERT | UPDATE | DELETE | TRUNCATE } ] [, ...]
+           ON <table>
+       [ REFERENCING { OLD AS <old> | NEW AS <new>. } ...]
+       [ WHEN <condition> ]
+       COMPOUND TRIGGER
+       [ <private_declaration>; ] ...
+       [ <procedure_or_function_definition> ] ...
+       <compound_trigger_definition>
+         END
+```
+
+Where `private_declaration` is an identifier of a private variable that can be accessed by any procedure or function. There can be zero, one, or more private variables. `private_declaration` can be any of the following:
+
+-   Variable declaration
+-   Record declaration
+-   Collection declaration
+-   `REF CURSOR` and cursor variable declaration
+-   `TYPE` definitions for records, collections, and `REF CURSOR`
+-   Exception
+-   Object variable declaration
+
+Where `procedure_or_function_definition :=`
+
+`procedure_definition | function_definition`
+
+Where `procedure_definition :=`
+
+```sql
+PROCEDURE proc_name[ argument_list ]
+  [ options_list ]
+  { IS | AS }
+    procedure_body
+  END [ proc_name ] ;
+```
+
+Where `procedure_body :=`
+
+```sql
+[ <declaration>; ] [, ...]
+BEGIN
+  <statement>; [...]
+[ EXCEPTION
+   { WHEN <exception> [OR <exception>] [...]] THEN <statement>; }
+   [...]
+]
+```
+
+Where `function_definition :=`
+
+```sql
+FUNCTION func_name [ argument_list ]
+  RETURN rettype [ DETERMINISTIC ]
+  [ options_list ]
+  { IS | AS }
+    function_body
+  END [ func_name ] ;
+```
+
+Where `function_body :=`
+
+```sql
+[ <declaration>; ] [, ...]
+BEGIN
+  <statement>; [...]
+[ EXCEPTION
+  { WHEN <exception> [ OR <exception> ] [...] THEN <statement>; }
+  [...]
+]
+```
+
+Where `compound_trigger_definition` is:
+
+```sql
+{ compound_trigger_event } { IS | AS }
+  compound_trigger_body
+END [ compound_trigger_event ] [ ... ]
+```
+
+Where `compound_trigger_event:=`
+
+```sql
+[ BEFORE STATEMENT | BEFORE EACH ROW | AFTER EACH ROW | AFTER STATEMENT  | INSTEAD OF EACH ROW ]
+```
+
+Where `compound_trigger_body:=`
+
+```sql
+[ <declaration>; ] [, ...]
+BEGIN
+  <statement>; [...]
+[ EXCEPTION
+   { WHEN <exception> [OR <exception>] [...] THEN <statement>; }
+   [...]
+]
+```
+
+## Description
+
+`CREATE TRIGGER` defines a new trigger. `CREATE OR REPLACE TRIGGER` creates a new trigger or replaces an existing definition.
+
+If you're using the `CREATE TRIGGER` keywords to create a trigger, the name of the new trigger must not match any existing trigger defined on the same table. New triggers are created in the same schema as the table on which the triggering event is defined.
+
+If you're updating the definition of an existing trigger, use the `CREATE OR REPLACE TRIGGER` keywords.
+
+When you use syntax compatible with Oracle databases to create a trigger, the trigger runs as a `SECURITY DEFINER` function.
+
+## Parameters
+
+`name`
+
+ The name of the trigger to create.
+
+`BEFORE | AFTER`
+
+ Determines whether the trigger is fired before or after the triggering event.
+
+`INSTEAD OF`
+
+ Trigger that modifies an updatable view. The trigger executes to update the underlying tables appropriately. The `INSTEAD OF` trigger executes for each row of the view that's updated or modified.
+
+`INSERT | UPDATE | DELETE | TRUNCATE`
+
+ Defines the triggering event.
+
+`table`
+
+ The name of the table or view on which the triggering event occurs.
+
+`condition`
+
+ A Boolean expression that determines if the trigger actually executes. If `condition` evaluates to `TRUE`, the trigger fires.
+
+-   If the simple trigger definition includes the `FOR EACH ROW` keywords, the `WHEN` clause can refer to columns of the old or new row values by writing `OLD.column_name` or `NEW.column_name` respectively. `INSERT` triggers can't refer to `OLD`, and `DELETE` triggers can't refer to `NEW`.
+
+-   If the compound trigger definition includes a statement-level trigger having a `WHEN` clause, then the trigger executes without evaluating the expression in the `WHEN` clause. Similarly, if a compound trigger definition includes a row-level trigger having a `WHEN` clause, then the trigger executes if the expression evaluates to `TRUE`.
+
+-   If the trigger includes the `INSTEAD OF` keywords, it can't include a `WHEN` clause. A `WHEN` clause can't contain subqueries.
+
+`REFERENCING { OLD AS old | NEW AS new } ...`
+
+ `REFERENCING` clause to reference old rows and new rows but restricted in that `old` can be replaced only by an identifier named `old` or any equivalent that's saved in all lowercase. Examples include `REFERENCING OLD AS old`, `REFERENCING OLD AS OLD`, or `REFERENCING OLD AS "old"`. Also, `new` can be replaced only by an identifier named `new` or any equivalent that's saved in all lowercase. Examples include `REFERENCING NEW AS new`, `REFERENCING NEW AS NEW`, or `REFERENCING NEW AS "new"`.
+
+ You can specify one or both phrases `OLD AS old` and `NEW AS new` in the `REFERENCING` clause, such as `REFERENCING NEW AS New OLD AS Old`. This clause isn't compatible with Oracle databases in that you can't use identifiers other than `old` or `new`.
+
+`FOR EACH ROW`
+
+ Determines whether to fire the trigger once for every row affected by the triggering event or once per SQL statement. If specified, the trigger is fired once for every affected row (row-level trigger). Otherwise the trigger is a statement-level trigger.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the trigger as an autonomous transaction.
+
+`declaration`
+
+ A variable, type, `REF CURSOR`, or subprogram declaration. If subprogram declarations are included, you must declare them after all other variable, type, and `REF CURSOR` declarations.
+
+`statement`
+
+ An SPL program statement. A `DECLARE - BEGIN - END` block is considered an SPL statement. Thus, the trigger body can contain nested blocks.
+
+`exception`
+
+ An exception condition name such as `NO_DATA_FOUND`.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/04_trigger_variables.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/04_trigger_variables.mdx
new file mode 100644
index 00000000000..160b7221415
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/04_trigger_variables.mdx
@@ -0,0 +1,51 @@
+---
+title: "Trigger variables"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.086.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.180.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/04_trigger_variables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="trigger_variables" class="registered_link"></div>
+
+In the trigger code block, several special variables are available for use.
+
+## NEW
+
+ `NEW` is a pseudo-record name that refers to the new table row for insert and update operations in row-level triggers. This variable doesn't apply to statement-level triggers and delete operations of row-level triggers.
+
+ Its usage is: 
+ 
+ ```text
+ :NEW.column 
+ ```
+
+ Where `column` is the name of a column in the table where the trigger is defined.
+
+ The initial content of `:NEW.column` is the value in the named column of the new row to insert. Or, when used in a before row-level trigger, it's the value of the new row that replaces the old one. When used in an after row-level trigger, this value is already stored in the table since the action already occurred on the affected row.
+
+ In the trigger code block, you can use `:NEW.column` like any other variable. If a value is assigned to `:NEW.column` in the code block of a before row-level trigger, the assigned value is used in the new inserted or updated row.
+
+## OLD
+
+ `OLD` is a pseudo-record name that refers to the old table row for update and delete operations in row-level triggers. This variable doesn't apply in statement-level triggers and in insert operations of row-level triggers.
+
+ Its usage is: `:OLD.column`, where `column` is the name of a column in the table on which the trigger is defined.
+
+ The initial content of `:OLD.column` is the value in the named column of the row to delete or of the old row to replace with the new one when used in a before row-level trigger. When used in an after row-level trigger, this value is no longer stored in the table since the action already occurred on the affected row.
+
+ In the trigger code block, you can use `:OLD.column` like any other variable. Assigning a value to `:OLD.column` has no effect on the action of the trigger.
+
+## INSERTING
+
+ `INSERTING` is a conditional expression that returns `TRUE` if an insert operation fired the trigger. Otherwise it returns `FALSE`.
+
+## UPDATING
+
+ `UPDATING` is a conditional expression that returns `TRUE` if an update operation fired the trigger. Otherwise it returns `FALSE`.
+
+## DELETING
+
+ `DELETING` is a conditional expression that returns `TRUE` if a delete operation fired the trigger. Otherwise it returns `FALSE`.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/05_transactions_and_exceptions.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/05_transactions_and_exceptions.mdx
new file mode 100644
index 00000000000..6b128768968
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/05_transactions_and_exceptions.mdx
@@ -0,0 +1,17 @@
+---
+title: "Transactions and exceptions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.087.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.181.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/05_transactions_and_exceptions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="transactions_and_exceptions" class="registered_link"></div>
+
+A trigger is always executed as part of the same transaction in which the triggering statement is executing. When no exceptions occur in the trigger code block, the effects of any triggering commands in the trigger are committed only if the transaction containing the triggering statement is committed. Therefore, if the transaction is rolled back, the effects of any triggering commands in the trigger are also rolled back.
+
+If an exception does occur in the trigger code block, but it is caught and handled in an exception section, the effects of any triggering commands in the trigger are still rolled back. The triggering statement, however, is rolled back only if the application forces a rollback of the containing transaction.
+
+If an unhandled exception occurs in the trigger code block, the transaction that contains the trigger is aborted and rolled back. Therefore, the effects of any triggering commands in the trigger and the triggering statement are all rolled back.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/06_compound_triggers.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/06_compound_triggers.mdx
new file mode 100644
index 00000000000..e7cf9d6c4d2
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/06_compound_triggers.mdx
@@ -0,0 +1,74 @@
+---
+title: "Compound triggers"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/06_compound_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="compound_triggers" class="registered_link"></div>
+
+EDB Postgres Advanced Server has compatible syntax to support compound triggers. 
+
+## Compound trigger overview
+
+A compound trigger combines all the triggering timings under one trigger body that you can invoke at one or more *timing points*. A timing point is a point in time related to a triggering statement, which is an `INSERT`, `UPDATE`, `DELETE`, or `TRUNCATE` statement that modifies data. The supported timing points are:
+
+-   `BEFORE STATEMENT` &mdash; Before the triggering statement executes.
+-   `BEFORE EACH ROW` &mdash; Before each row that the triggering statement affects.
+-   `AFTER EACH ROW` &mdash; After each row that the triggering statement affects.
+-   `AFTER STATEMENT` &mdash; After the triggering statement executes.
+-   `INSTEAD OF EACH ROW` &mdash; Trigger fires once for every row affected by the triggering statement.
+
+A compound trigger can include any combination of timing points defined in a single trigger.
+
+The optional declaration section in a compound trigger allows you to declare trigger-level variables and subprograms. The content of the declaration is accessible to all timing points referenced by the trigger definition. The variables and subprograms created by the declaration persist only for the duration of the triggering statement.
+
+## Syntax 
+
+A compound trigger contains a declaration followed by a PL block for each timing point:
+
+```sql
+CREATE OR REPLACE TRIGGER compound_trigger_name
+FOR INSERT OR UPDATE OR DELETE ON table_name
+COMPOUND TRIGGER
+   -- Global Declaration Section (optional)
+   -- Variables declared here can be used inside any timing-point blocks.
+
+     BEFORE STATEMENT IS
+     BEGIN
+       NULL;
+     END BEFORE STATEMENT;
+
+     BEFORE EACH ROW IS
+     BEGIN
+       NULL;
+     END BEFORE EACH ROW;
+
+     AFTER EACH ROW IS
+     BEGIN
+       NULL;
+     END AFTER EACH ROW;
+
+
+     AFTER STATEMENT IS
+     BEGIN
+       NULL;
+     END AFTER STATEMENT;
+END compound_trigger_name;
+/
+Trigger created.
+```
+
+!!! Note
+    You don't have to have all the four timing blocks. You can create a compound trigger for any of the required timing points.
+
+## Restrictions
+
+A compound trigger has the following restrictions:
+
+-   A compound trigger body is made up of a compound trigger block.
+-   You can define a compound trigger on a table or a view.
+-   You can't transfer exceptions to another timing-point section. They must be handled separately in that section only by each compound trigger block.
+-   If a `GOTO` statement is specified in a timing-point section, then the target of the `GOTO` statement must also be specified in the same timing-point section.
+-   `:OLD` and `:NEW` variable identifiers can't exist in the declarative section, the `BEFORE STATEMENT` section, or the `AFTER STATEMENT` section.
+-   `:NEW` values are modified only by the `BEFORE EACH ROW` block.
+-   The sequence of compound trigger timing-point execution is specific. However, if a simple trigger is in the same timing point, then the simple trigger is fired first, followed by the compound triggers.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/01_before_statement_level_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/01_before_statement_level_trigger.mdx
new file mode 100644
index 00000000000..6ae46c32315
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/01_before_statement_level_trigger.mdx
@@ -0,0 +1,35 @@
+---
+title: "Before statement-level trigger"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/01_before_statement_level_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="before_statement_level_trigger" class="registered_link"></div>
+
+This example shows a simple before statement-level trigger that displays a message before an insert operation on the `emp` table:
+
+```sql
+CREATE OR REPLACE TRIGGER emp_alert_trig
+    BEFORE INSERT ON emp
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('New employees are about to be added');
+END;
+```
+
+The following `INSERT` is constructed so that several new rows are inserted upon a single execution of the command. For each row that has an employee id between 7900 and 7999, a new row is inserted with an employee id incremented by 1000. The following are the results of executing the command when three new rows are inserted:
+
+```sql
+INSERT INTO emp (empno, ename, deptno) SELECT empno + 1000, ename, 40
+    FROM emp WHERE empno BETWEEN 7900 AND 7999;
+New employees are about to be added
+
+SELECT empno, ename, deptno FROM emp WHERE empno BETWEEN 8900 AND 8999;
+__OUTPUT__
+     EMPNO ENAME          DEPTNO
+---------- ---------- ----------
+      8900 JAMES              40
+      8902 FORD               40
+      8934 MILLER             40
+```
+
+The message `New employees are about to be added` is displayed once by the firing of the trigger even though the result adds three rows.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/02_after_statement_level_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/02_after_statement_level_trigger.mdx
new file mode 100644
index 00000000000..57275266c9c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/02_after_statement_level_trigger.mdx
@@ -0,0 +1,60 @@
+---
+title: "After statement-level trigger"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/02_after_statement_level_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="after_statement_level_trigger" class="registered_link"></div>
+
+This example shows an after statement-level trigger. When an insert, update, or delete operation occurs on the `emp` table, a row is added to the `empauditlog` table recording the date, user, and action.
+
+```sql
+CREATE TABLE empauditlog (
+    audit_date      DATE,
+    audit_user      VARCHAR2(20),
+    audit_desc      VARCHAR2(20)
+);
+CREATE OR REPLACE TRIGGER emp_audit_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+DECLARE
+    v_action        VARCHAR2(20);
+BEGIN
+    IF INSERTING THEN
+        v_action := 'Added employee(s)';
+    ELSIF UPDATING THEN
+        v_action := 'Updated employee(s)';
+    ELSIF DELETING THEN
+        v_action := 'Deleted employee(s)';
+    END IF;
+    INSERT INTO empauditlog VALUES (SYSDATE, USER,
+        v_action);
+END;
+```
+
+In the following sequence of commands, two rows are inserted into the `emp` table using two `INSERT` commands. One `UPDATE` command updates the `sal` and `comm` columns of both rows. Then, one `DELETE` command deletes both rows.
+
+```sql
+INSERT INTO emp VALUES (9001,'SMITH','ANALYST',7782,SYSDATE,NULL,NULL,10);
+
+INSERT INTO emp VALUES (9002,'JONES','CLERK',7782,SYSDATE,NULL,NULL,10);
+
+UPDATE emp SET sal = 4000.00, comm = 1200.00 WHERE empno IN (9001, 9002);
+
+DELETE FROM emp WHERE empno IN (9001, 9002);
+
+SELECT TO_CHAR(AUDIT_DATE,'DD-MON-YY HH24:MI:SS') AS "AUDIT DATE",
+    audit_user, audit_desc FROM empauditlog ORDER BY 1 ASC;
+__OUTPUT__
+AUDIT DATE         AUDIT_USER           AUDIT_DESC
+------------------ -------------------- --------------------
+31-MAR-05 14:59:48 SYSTEM               Added employee(s)
+31-MAR-05 15:00:07 SYSTEM               Added employee(s)
+31-MAR-05 15:00:19 SYSTEM               Updated employee(s)
+31-MAR-05 15:00:34 SYSTEM               Deleted employee(s)
+```
+
+The contents of the `empauditlog` table show how many times the trigger was fired: 
+
+-  Once each for the two inserts
+-  Once for the update (even though two rows were changed)
+-  Once for the deletion (even though two rows were deleted)
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/03_before_row_level_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/03_before_row_level_trigger.mdx
new file mode 100644
index 00000000000..346e3634e0c
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/03_before_row_level_trigger.mdx
@@ -0,0 +1,35 @@
+---
+title: "Before row-level trigger"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/03_before_row_level_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="before_row_level_trigger" class="registered_link"></div>
+
+This example shows a before row-level trigger that calculates the commission of every new employee belonging to department 30 that's inserted into the `emp` table:
+
+```sql
+CREATE OR REPLACE TRIGGER emp_comm_trig
+    BEFORE INSERT ON emp
+    FOR EACH ROW
+BEGIN
+    IF :NEW.deptno = 30 THEN
+        :NEW.comm := :NEW.sal * .4;
+    END IF;
+END;
+```
+
+The listing following the addition of the two employees shows that the trigger computed their commissions and inserted it as part of the new employee rows:
+
+```sql
+INSERT INTO emp VALUES (9005,'ROBERS','SALESMAN',7782,SYSDATE,3000.00,NULL,30);
+
+INSERT INTO emp VALUES (9006,'ALLEN','SALESMAN',7782,SYSDATE,4500.00,NULL,30);
+
+SELECT * FROM emp WHERE empno IN (9005, 9006);
+__OUTPUT__
+ EMPNO ENAME  JOB       MGR    HIREDATE       SAL       COMM       DEPTNO
+------ ------ --------  ------ ---------- --------- ---------- -------------
+ 9005  ROBERS SALESMAN  7782   01-APR-05      3000       1200         30
+ 9006  ALLEN  SALESMAN  7782   01-APR-05      4500       1800         30
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/04_after_row_level_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/04_after_row_level_trigger.mdx
new file mode 100644
index 00000000000..43ac9b3eba4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/04_after_row_level_trigger.mdx
@@ -0,0 +1,114 @@
+---
+title: "After row-level trigger"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/04_after_row_level_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="after_row_level_trigger" class="registered_link"></div>
+
+This example shows an after row-level trigger. When a new employee row is inserted, the trigger adds a row to the `jobhist` table for that employee. When an existing employee is updated, the trigger sets the `enddate` column of the latest `jobhist` row (assumed to be the one with a null `enddate`) to the current date and inserts a new `jobhist` row with the employee’s new information.
+
+Then, the trigger adds a row to the `empchglog` table with a description of the action.
+
+```sql
+CREATE TABLE empchglog (
+    chg_date        DATE,
+    chg_desc        VARCHAR2(30)
+);
+CREATE OR REPLACE TRIGGER emp_chg_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+    FOR EACH ROW
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_action        VARCHAR2(7);
+    v_chgdesc       jobhist.chgdesc%TYPE;
+BEGIN
+    IF INSERTING THEN
+        v_action := 'Added';
+        v_empno := :NEW.empno;
+        v_deptno := :NEW.deptno;
+        INSERT INTO jobhist VALUES (:NEW.empno, SYSDATE, NULL,
+            :NEW.job, :NEW.sal, :NEW.comm, :NEW.deptno, 'New Hire');
+    ELSIF UPDATING THEN
+        v_action := 'Updated';
+        v_empno := :NEW.empno;
+        v_deptno := :NEW.deptno;
+        v_chgdesc := '';
+        IF NVL(:OLD.ename, '-null-') != NVL(:NEW.ename, '-null-') THEN
+            v_chgdesc := v_chgdesc || 'name, ';
+        END IF;
+        IF NVL(:OLD.job, '-null-') != NVL(:NEW.job, '-null-') THEN
+            v_chgdesc := v_chgdesc || 'job, ';
+        END IF;
+        IF NVL(:OLD.sal, -1) != NVL(:NEW.sal, -1) THEN
+            v_chgdesc := v_chgdesc || 'salary, ';
+        END IF;
+        IF NVL(:OLD.comm, -1) != NVL(:NEW.comm, -1) THEN
+            v_chgdesc := v_chgdesc || 'commission, ';
+        END IF;
+        IF NVL(:OLD.deptno, -1) != NVL(:NEW.deptno, -1) THEN
+            v_chgdesc := v_chgdesc || 'department, ';
+        END IF;
+        v_chgdesc := 'Changed ' || RTRIM(v_chgdesc, ', ');
+        UPDATE jobhist SET enddate = SYSDATE WHERE empno = :OLD.empno
+            AND enddate IS NULL;
+        INSERT INTO jobhist VALUES (:NEW.empno, SYSDATE, NULL,
+            :NEW.job, :NEW.sal, :NEW.comm, :NEW.deptno, v_chgdesc);
+    ELSIF DELETING THEN
+        v_action := 'Deleted';
+        v_empno := :OLD.empno;
+        v_deptno := :OLD.deptno;
+    END IF;
+
+    INSERT INTO empchglog VALUES (SYSDATE,
+        v_action || ' employee # ' || v_empno);
+END;
+```
+
+In the first sequence of the following commands, two employees are added using two separate `INSERT` commands. Then both are updated using a single `UPDATE` command. The contents of the `jobhist` table show the action of the trigger for each affected row: two new-hire entries for the two new employees and two changed commission records for the updated commissions on the two employees. The `empchglog` table also shows the trigger was fired a total of four times, once for each action on the two rows.
+
+```sql
+INSERT INTO emp VALUES (9003,'PETERS','ANALYST',7782,SYSDATE,5000.00,NULL,40);
+
+INSERT INTO emp VALUES (9004,'AIKENS','ANALYST',7782,SYSDATE,4500.00,NULL,40);
+
+UPDATE emp SET comm = sal * 1.1 WHERE empno IN (9003, 9004);
+
+SELECT * FROM jobhist WHERE empno IN (9003, 9004);
+__OUTPUT__
+   EMPNO STARTDATE ENDDATE   JOB              SAL       COMM     DEPTNO   CHGDESC
+---------- --------- --------- --------- ---------- ---------- ---------- -------------
+    9003 31-MAR-05 31-MAR-05 ANALYST         5000                    40   New Hire
+    9004 31-MAR-05 31-MAR-05 ANALYST         4500                    40   New Hire
+    9003 31-MAR-05           ANALYST         5000       5500         40   Changed commission
+    9004 31-MAR-05           ANALYST         4500       4950         40   Changed commission
+```
+```sql
+SELECT * FROM empchglog;
+__OUTPUT__
+CHG_DATE  CHG_DESC
+--------- ------------------------------
+31-MAR-05 Added employee # 9003
+31-MAR-05 Added employee # 9004
+31-MAR-05 Updated employee # 9003
+31-MAR-05 Updated employee # 9004
+```
+
+Then, a single `DELETE` command deletes both employees. The `empchglog` table shows the trigger was fired twice, once for each deleted employee.
+
+```sql
+DELETE FROM emp WHERE empno IN (9003, 9004);
+
+SELECT * FROM empchglog;
+__OUTPUT__
+CHG_DATE  CHG_DESC
+--------- ------------------------------
+31-MAR-05 Added employee # 9003
+31-MAR-05 Added employee # 9004
+31-MAR-05 Updated employee # 9003
+31-MAR-05 Updated employee # 9004
+31-MAR-05 Deleted employee # 9003
+31-MAR-05 Deleted employee # 9004
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/05_instead_of_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/05_instead_of_trigger.mdx
new file mode 100644
index 00000000000..1df7dac19a3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/05_instead_of_trigger.mdx
@@ -0,0 +1,63 @@
+---
+title: "INSTEAD OF trigger"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/05_instead_of_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="instead_of_trigger" class="registered_link"></div>
+
+This example shows an `INSTEAD OF` trigger for inserting a new employee row into the `emp_vw` view. The `CREATE VIEW` statement creates the `emp_vw` view by joining the two tables. The trigger adds the corresponding new rows into the `emp` and `dept` tables, respectively, for a specific employee.
+
+```sql
+CREATE VIEW emp_vw AS SELECT * FROM emp e JOIN dept d USING(deptno);
+CREATE VIEW
+
+CREATE OR REPLACE TRIGGER empvw_instead_of_trig
+    INSTEAD OF INSERT ON emp_vw
+    FOR EACH ROW
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_loc           dept.loc%TYPE;
+    v_action        VARCHAR2(7);
+BEGIN
+    v_empno     := :NEW.empno;
+    v_ename     := :New.ename;
+    v_deptno    := :NEW.deptno;
+    v_dname     := :NEW.dname;
+    v_loc       := :NEW.loc;
+     INSERT INTO emp(empno, ename, deptno) VALUES(v_empno, v_ename, v_deptno);
+     INSERT INTO dept(deptno, dname, loc) VALUES(v_deptno, v_dname, v_loc);
+END;
+CREATE TRIGGER
+```
+
+Next, insert the values into the `emp_vw` view. The insert action inserts a new row and produces the following output:
+
+```sql
+INSERT INTO emp_vw (empno, ename, deptno, dname, loc ) VALUES(1234, 'ASHTON', 50, 'IT', 'NEW JERSEY');
+__OUTPUT__
+INSERT 0 1
+```
+
+```sql
+SELECT empno, ename, deptno FROM emp  WHERE deptno = 50;
+__OUTPUT__
+ empno | ename  | deptno
+-------+--------+--------
+  1234 | ASHTON |     50
+(1 row)
+```
+
+```sql
+SELECT * FROM dept  WHERE deptno = 50;
+__OUTPUT__
+ deptno | dname |    loc
+--------+-------+------------
+     50 | IT    | NEW JERSEY
+(1 row)
+```
+
+Similarly, if you specify an `UPDATE` or `DELETE` statement, the trigger performs the appropriate actions for `UPDATE` or `DELETE` events.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx
new file mode 100644
index 00000000000..9f267d486f1
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger.mdx
@@ -0,0 +1,260 @@
+---
+title: "Compound triggers"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/06_compound_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="compound_trigger" class="registered_link"></div>
+
+## Defining a compound trigger on a table
+
+This example shows a compound trigger that records a change to the employee salary by defining a compound trigger named `hr_trigger` on the `emp` table.
+
+1. Create a table named `emp`:
+
+   ```sql
+   CREATE TABLE emp(EMPNO INT, ENAME TEXT, SAL INT, DEPTNO INT);
+   CREATE TABLE
+   ```
+
+2. Create a compound trigger named `hr_trigger`. The trigger uses each of the four timing points to modify the salary with an `INSERT`, `UPDATE`, or `DELETE` statement. In the global declaration section, the initial salary is declared as `10,000`.
+
+   ```sql
+   CREATE OR REPLACE TRIGGER hr_trigger
+     FOR INSERT OR UPDATE OR DELETE ON emp
+       COMPOUND TRIGGER
+     -- Global declaration.
+     var_sal NUMBER := 10000;
+
+     BEFORE STATEMENT IS
+     BEGIN
+       var_sal := var_sal + 1000;
+       DBMS_OUTPUT.PUT_LINE('Before Statement: ' || var_sal);
+     END BEFORE STATEMENT;
+
+     BEFORE EACH ROW IS
+     BEGIN
+       var_sal := var_sal + 1000;
+       DBMS_OUTPUT.PUT_LINE('Before Each Row: ' || var_sal);
+     END BEFORE EACH ROW;
+
+     AFTER EACH ROW IS
+     BEGIN
+       var_sal := var_sal + 1000;
+       DBMS_OUTPUT.PUT_LINE('After Each Row: ' || var_sal);
+     END AFTER EACH ROW;
+
+     AFTER STATEMENT IS
+     BEGIN
+       var_sal := var_sal + 1000;
+       DBMS_OUTPUT.PUT_LINE('After Statement: ' || var_sal);
+     END AFTER STATEMENT;
+
+   END hr_trigger;
+
+   Output: Trigger created.
+   ```
+
+3. Insert the record into table `emp`:
+
+   ```sql
+   INSERT INTO emp (EMPNO, ENAME, SAL, DEPTNO) VALUES(1111,'SMITH', 10000, 20);
+   ```
+
+   The `INSERT` statement produces the following output:
+
+   ```sql
+   __OUTPUT__
+   Before Statement: 11000
+   Before each row: 12000
+   After each row: 13000
+   After statement: 14000
+   INSERT 0 1
+   ```
+
+4. The `UPDATE` statement updates the employee salary record, setting the salary to `15000` for a specific employee number:
+
+   ```sql
+   UPDATE emp SET SAL = 15000 where EMPNO = 1111;
+   ```
+
+   The `UPDATE` statement produces the following output:
+
+   ```sql
+   Before Statement: 11000
+   Before each row: 12000
+   After each row: 13000
+   After statement: 14000
+   UPDATE 1
+
+   SELECT * FROM emp;
+   __OUTPUT__
+    EMPNO | ENAME |  SAL  | DEPTNO
+   -------+-------+-------+--------
+     1111 | SMITH | 15000 |     20
+   (1 row)
+   ```
+
+### DELETE
+
+The `DELETE` statement deletes the employee salary record:
+
+```sql
+DELETE from emp where EMPNO = 1111;
+```
+
+The `DELETE` statement produces the following output:
+
+```sql
+Before Statement: 11000
+Before each row: 12000
+After each row: 13000
+After statement: 14000
+DELETE 1
+
+SELECT * FROM emp;
+__OUTPUT__
+ EMPNO | ENAME | SAL | DEPTNO
+-------+-------+-----+--------
+(0 rows)
+```
+### TRUNCATE
+
+The `TRUNCATE` statement removes all the records from the `emp` table:
+
+```sql
+CREATE OR REPLACE TRIGGER hr_trigger
+  FOR TRUNCATE ON emp
+    COMPOUND TRIGGER
+  -- Global declaration.
+  var_sal NUMBER := 10000;
+  BEFORE STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('Before Statement: ' || var_sal);
+  END BEFORE STATEMENT;
+
+  AFTER STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('After Statement: ' || var_sal);
+  END AFTER STATEMENT;
+
+END hr_trigger;
+
+Output: Trigger created.
+```
+
+The `TRUNCATE` statement produces the following output:
+
+```sql
+TRUNCATE emp;
+__OUTPUT__
+Before Statement: 11000
+After statement: 12000
+TRUNCATE TABLE
+```
+
+!!! Note
+    You can use the `TRUNCATE` statement only at a `BEFORE STATEMENT` or `AFTER STATEMENT` timing point.
+
+## Creating a compound trigger on a table with a WHEN condition
+
+This example creates a compound trigger named `hr_trigger` on the `emp` table with a `WHEN` condition. The `WHEN` condition checks and prints the employee salary when an `INSERT`, `UPDATE`, or `DELETE` statement affects the `emp` table. The database evaluates the `WHEN` condition for a row-level trigger, and the trigger executes once per row if the `WHEN` condition evaluates to `TRUE`. The statement-level trigger executes regardless of the `WHEN` condition.
+
+```sql
+CREATE OR REPLACE TRIGGER hr_trigger
+  FOR INSERT OR UPDATE OR DELETE ON emp
+  REFERENCING NEW AS new OLD AS old
+  WHEN (old.sal > 5000 OR new.sal < 8000)
+    COMPOUND TRIGGER
+
+  BEFORE STATEMENT IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('Before Statement');
+  END BEFORE STATEMENT;
+
+  BEFORE EACH ROW IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('Before Each Row: ' || :OLD.sal ||' ' || :NEW.sal);
+  END BEFORE EACH ROW;
+
+  AFTER EACH ROW IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('After Each Row: ' || :OLD.sal ||' ' || :NEW.sal);
+  END AFTER EACH ROW;
+
+  AFTER STATEMENT IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('After Statement');
+  END AFTER STATEMENT;
+
+END hr_trigger;
+```
+### INSERT
+
+Insert the record into table `emp`:
+
+```sql
+INSERT INTO emp(EMPNO, ENAME, SAL, DEPTNO) VALUES(1111, 'SMITH', 1600, 20);
+```
+
+The `INSERT` statement produces the following output:
+
+```sql
+__OUTPUT__
+Before Statement
+Before Each Row: 1600
+After Each Row: 1600
+After Statement
+INSERT 0 1
+```
+
+### UPDATE
+
+The `UPDATE` statement updates the employee salary record, setting the salary to `7500`:
+
+```sql
+UPDATE emp SET SAL = 7500 where EMPNO = 1111;
+```
+
+The `UPDATE` statement produces the following output:
+
+```sql
+Before Statement
+Before Each Row: 1600 7500
+After Each Row: 1600 7500
+After Statement
+UPDATE 1
+
+SELECT * from emp;
+__OUTPUT__
+ empno | ename | sal  | deptno
+-------+-------+------+--------
+  1111 | SMITH | 7500 |     20
+(1 row)
+```
+
+### DELETE
+
+The `DELETE` statement deletes the employee salary record:
+
+```sql
+DELETE from emp where EMPNO = 1111;
+```
+
+The `DELETE` statement produces the following output:
+
+```sql
+Before Statement
+Before Each Row: 7500
+After Each Row: 7500
+After Statement
+DELETE 1
+
+SELECT * from emp;
+__OUTPUT__
+ empno | ename | sal | deptno
+-------+-------+-----+--------
+(0 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/index.mdx
new file mode 100644
index 00000000000..6b6a1eed179
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/07_trigger_examples/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Trigger examples"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.088.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.182.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/07_trigger_examples/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="trigger_examples" class="registered_link"></div>
+
+The examples that follow show each type of trigger.
+
+<div class="toctree" maxdepth="3">
+
+before_statement_level_trigger after_statement_level_trigger before_row_level_trigger after_row_level_trigger instead_of_trigger compound_trigger
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/index.mdx
new file mode 100644
index 00000000000..e54cec7267b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/13_triggers/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Working with triggers"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.082.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.176.html"
+redirects:
+  - /epas/latest/epas_compat_spl/13_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="triggers" class="registered_link"></div>
+
+As with procedures and functions, you write triggers in the SPL language. 
+
+<div class="toctree" maxdepth="3">
+
+overview types_of_triggers creating_triggers trigger_variables transactions_and_exceptions compound_triggers trigger_examples
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/14_packages.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/14_packages.mdx
new file mode 100644
index 00000000000..96a2be851a3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/14_packages.mdx
@@ -0,0 +1,22 @@
+---
+title: "Working with packages"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.089.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.183.html"
+redirects:
+  - /epas/latest/epas_compat_spl/14_packages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="packages" class="registered_link"></div>
+
+EDB Postgres Advanced Server provides a collection of packages that provide compatibility with Oracle packages.
+
+A *package* is a named collection of functions, procedures, variables, cursors, user-defined record types, and records that are referenced using a common qualifier, known as the package identifier. Packages have the following characteristics:
+
+-   Packages provide a convenient means of organizing the functions and procedures that perform a related purpose. Permission to use the package functions and procedures depends on one privilege granted to the entire package. All of the package programs must be referenced with a common name.
+-   Certain functions, procedures, variables, types, and so on in the package can be declared as *public*. Public entities are visible and can be referenced by other programs that are given `EXECUTE` privilege on the package. For public functions and procedures, only their signatures are visible, that is, the program names, parameters, if any, and return types of functions. The SPL code of these functions and procedures isn't accessible to others, therefore applications that use a package depend only on the information available in the signature and not in the procedural logic itself.
+-   You can declare Other functions, procedures, variables, types, and so on in the package as *private*. Private entities can be referenced and used by function and procedures in the package but not by other external applications. Private entities are for use only by programs in the package.
+-   You can overload function and procedure names in a package. One or more functions or procedures can be defined with the same name but with different signatures. This ability lets you create identically named programs that perform the same job but on different types of input.
+
+For more information about the package support provided by EDB Postgres Advanced Server, see [Built-in packages](../../reference/oracle_compatibility_reference/epas_compat_bip_guide/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/01_attributes.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/01_attributes.mdx
new file mode 100644
index 00000000000..92cdc00cb46
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/01_attributes.mdx
@@ -0,0 +1,15 @@
+---
+title: "Attributes"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/01_attributes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="attributes" class="registered_link"></div>
+
+Every object type must contain at least one attribute. The data type of an attribute can be any of the following:
+
+-   A base data type such as `NUMBER` or `VARCHAR2`
+-   Another object type
+-   A globally defined collection type (created by the `CREATE TYPE` command) such as a nested table or varray
+
+An attribute gets its initial value, which can be null, when an object instance is first created. Each object instance has its own set of attribute values.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx
new file mode 100644
index 00000000000..4e7ba1654be
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods.mdx
@@ -0,0 +1,13 @@
+---
+title: "Methods"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/02_methods/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="methods" class="registered_link"></div>
+
+Methods are SPL procedures or functions defined in an object type. Methods are categorized into three general types:
+
+-   **Member methods** &mdash; Procedures or functions that operate in the context of an object instance. Member methods have access to and can change the attributes of the object instance on which they're operating.
+-   **Static methods** &mdash; Procedures or functions that operate independently of any particular object instance. Static methods don't have access to and can't change the attributes of an object instance.
+-   **Constructor methods** &mdash; Functions used to create an instance of an object type. A default constructor method is always provided when an object type is defined.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/03_overloading_methods.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/03_overloading_methods.mdx
new file mode 100644
index 00000000000..24e3dadc253
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/03_overloading_methods.mdx
@@ -0,0 +1,11 @@
+---
+title: "Overloading methods"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/03_overloading_methods/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="overloading_methods" class="registered_link"></div>
+
+In an object type you can define two or more identically named methods (that is, a procedure or function) of the same type but with different signatures. Such methods are referred to as *overloaded* methods.
+
+A method’s signature consists of the number of formal parameters, the data types of its formal parameters, and their order.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx
new file mode 100644
index 00000000000..89c4ee511b3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "Basic object concepts"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.091.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.213.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/01_basic_object_concepts/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="basic_object_concepts" class="registered_link"></div>
+
+An object type is a description or definition of some entity. This definition of an object type is characterized by two components:
+
+-   Attributes &mdash; Fields that describe particular characteristics of an object instance. For a person object, examples are name, address, gender, date of birth, height, weight, eye color, and occupation.
+-   Methods &mdash; Programs that perform some type of function or operation on or are related to an object. For a person object, examples are calculating the person’s age, displaying the person’s attributes, and changing the values assigned to the person’s attributes.
+
+<div class="toctree" maxdepth="3">
+
+attributes methods overloading_methods
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx
new file mode 100644
index 00000000000..180f9fbf8a0
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax.mdx
@@ -0,0 +1,127 @@
+---
+title: "Object type specification syntax"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/02_object_type_components/01_object_type_specification_syntax/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="object_type_specification_syntax" class="registered_link"></div>
+
+The following is the syntax of the object type specification:
+
+```sql
+CREATE [ OR REPLACE ] TYPE <name>
+  [ AUTHID { DEFINER | CURRENT_USER } ]
+  { IS | AS } OBJECT
+( { <attribute> { <datatype> | <objtype> | <collecttype> } }
+    [, ...]
+  [ <method_spec> ] [, ...]
+  [ <constructor> ] [, ...]
+) [ [ NOT ] { FINAL | INSTANTIABLE } ] ...;
+```
+
+Where `method_spec` is the following:
+
+```sql
+[ [ NOT ] { FINAL | INSTANTIABLE } ] ...
+[ OVERRIDING ]
+  <subprogram_spec>
+```
+
+Where `subprogram_spec` is the following:
+
+```sql
+{ MEMBER | STATIC }
+{ PROCEDURE <proc_name>
+    [ ( [  SELF [ IN | IN OUT ] <name> ]
+        [, <parm1> [ IN | IN OUT | OUT ] <datatype1>
+                   [ DEFAULT <value1> ] ]
+        [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+                   [ DEFAULT <value2> ]
+        ] ...)
+    ]
+|
+  FUNCTION <func_name>
+    [ ( [  SELF [ IN | IN OUT ] <name> ]
+        [, <parm1> [ IN | IN OUT | OUT ] <datatype1>
+                   [ DEFAULT <value1> ] ]
+        [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+                   [ DEFAULT <value2> ]
+        ] ...)
+    ]
+  RETURN <return_type>
+}
+```
+
+Where `constructor` is the following:
+
+```sql
+CONSTRUCTOR FUNCTION <func_name>
+  [ ( [ <parm1> [ IN | IN OUT | OUT ] <datatype1>
+                 [ DEFAULT <value1> ] ]
+      [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+                 [ DEFAULT <value2> ]
+      ] ...)
+  ]
+RETURN <return_type>;
+```
+
+!!! Note
+    -   You can't use the `OR REPLACE` option to add, delete, or modify the attributes of an existing object type. Use the `DROP TYPE` command to first delete the existing object type. You can use the `OR REPLACE` option to add, delete, or modify the methods in an existing object type.
+
+    -   You can use the PostgreSQL form of the `ALTER TYPE ALTER ATTRIBUTE` command to change the data type of an attribute in an existing object type. However, the `ALTER TYPE` command can't add or delete attributes in the object type.
+
+`name` is an identifier (optionally schema-qualified) assigned to the object type.
+
+If you omit the `AUTHID` clause or specify `DEFINER`, the rights of the object type owner are used to determine access privileges to database objects. If you specify `CURRENT_USER`, the rights of the current user executing a method in the object determine access privileges.
+
+## Syntax 
+
+`attribute` is an identifier assigned to an attribute of the object type.
+
+`datatype` is a base data type.
+
+`objtype` is a previously defined object type.
+
+`collecttype` is a previously defined collection type.
+
+Following the closing parenthesis of the `CREATE TYPE` definition, `[ NOT ] FINAL` specifies whether a subtype can be derived from this object type. `FINAL`, which is the default, means that no subtypes can be derived from this object type. Specify `NOT FINAL` if you want to allow subtypes to be defined under this object type.
+
+!!! Note
+    Even though the specification of `NOT FINAL` is accepted in the `CREATE TYPE` command, SPL doesn't currently support creating subtypes.
+
+Following the closing parenthesis of the `CREATE TYPE` definition, `[ NOT ] INSTANTIABLE` specifies whether an object instance of this object type can be created. `INSTANTIABLE`, which is the default, means that an instance of this object type can be created. Specify `NOT INSTANTIABLE` if this object type is to be used only as a parent “template” from which other specialized subtypes are defined. If `NOT INSTANTIABLE` is specified, then you must specify `NOT FINAL` as well. If any method in the object type contains the `NOT INSTANTIABLE` qualifier, then the object type must be defined with `NOT INSTANTIABLE` and `NOT FINAL`.
+
+!!! Note
+    Even though specifying `NOT INSTANTIABLE` is accepted in the `CREATE TYPE` command, SPL doesn't currently support creating subtypes.
+
+## method_spec
+
+`method_spec` denotes the specification of a member method or static method.
+
+Before defining a method, use `[ NOT ] FINAL` to specify whether the method can be overridden in a subtype. `NOT FINAL` is the default, meaning the method can be overridden in a subtype.
+
+Before defining a method, specify `OVERRIDING` if the method overrides an identically named method in a supertype. The overriding method must have the same number of identically named method parameters with the same data types and parameter modes, in the same order, and with the same return type (if the method is a function) as defined in the supertype.
+
+Before defining a method, use `[ NOT ] INSTANTIABLE` to specify whether the object type definition provides an implementation for the method. If you specify `INSTANTIABLE`, then the `CREATE TYPE BODY` command for the object type must specify the implementation of the method. If you specify `NOT INSTANTIABLE`, then the `CREATE TYPE BODY` command for the object type must not contain the implementation of the method. In this latter case, it is assumed a subtype contains the implementation of the method, overriding the method in this object type. If there are any `NOT INSTANTIABLE` methods in the object type, then the object type definition must specify `NOT INSTANTIABLE` and `NOT FINAL` following the closing parenthesis of the object type specification. The default is `INSTANTIABLE`.
+
+## subprogram_spec 
+
+`subprogram_spec` denotes the specification of a procedure or function and begins with the specification of either `MEMBER` or `STATIC`. A member subprogram must be invoked with respect to a particular object instance while a static subprogram isn't invoked with respect to any object instance.
+
+`proc_name` is an identifier of a procedure. If you specify the `SELF` parameter, `name` is the object type name given in the `CREATE TYPE` command. If specified, `parm1, parm2, …` are the formal parameters of the procedure. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN`, `IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. The default is `IN`. `value1, value2, …` are default values that you can specify for `IN` parameters.
+
+## CONSTRUCTOR 
+
+Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function.
+
+`func_name` is an identifier of a function. If specified, `parm1, parm2, …` are the formal parameters of the function. `datatype1, datatype2, …` are the data types of `parm1, parm2, …` respectively. `IN`, `IN OUT`, and `OUT` are the possible parameter modes for each formal parameter. The default is `IN`. `value1, value2, …` are default values that you can specify for `IN` parameters. `return_type` is the data type of the value the function returns.
+
+Note the following about an object type specification:
+
+-   There must be at least one attribute defined in the object type.
+
+-   There can be zero, one, or more methods defined in the object type.
+
+-   A static method can't be overridden. You can't specify `OVERRIDING` and `STATIC` together in `method_spec`.
+
+-   A static method must be instantiable. You can't specify `NOT INSTANTIABLE` and `STATIC` together in `method_spec`.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx
new file mode 100644
index 00000000000..af5c54d3085
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax.mdx
@@ -0,0 +1,104 @@
+---
+title: "Object type body syntax"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/02_object_type_components/02_object_type_body_syntax/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="object_type_body_syntax" class="registered_link"></div>
+
+The following is the syntax of the object type body:
+
+```sql
+CREATE [ OR REPLACE ] TYPE BODY <name>
+  { IS | AS }
+  <method_spec> [...]
+  [<constructor>] [...]
+END;
+```
+
+Where `method_spec` is `subprogram_spec`, and `subprogram_spec` is the following:
+
+```sql
+{ MEMBER | STATIC }
+{ PROCEDURE <proc_name>
+    [ ( [  SELF [ IN | IN OUT ] <name> ]
+        [, <parm1> [ IN | IN OUT | OUT ] <datatype1>
+                 [ DEFAULT <value1> ] ]
+        [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+                 [ DEFAULT <value2> ]
+        ] ...)
+    ]
+{ IS | AS }
+  [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+  [ <declarations> ]
+  BEGIN
+    <statement>; ...
+[ EXCEPTION
+    WHEN ... THEN
+      <statement>; ...]
+  END;
+|
+  FUNCTION <func_name>
+    [ ( [  SELF [ IN | IN OUT ] <name> ]
+        [, <parm1> [ IN | IN OUT | OUT ] <datatype1>
+                 [ DEFAULT <value1> ] ]
+        [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+                 [ DEFAULT <value2> ]
+        ] ...)
+    ]
+  RETURN <return_type>
+{ IS | AS }
+  [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+  [ <declarations> ]
+  BEGIN
+    <statement>; ...
+[ EXCEPTION
+    WHEN ... THEN
+      <statement>; ...]
+  END;
+```
+
+Where `constructor` is:
+
+```sql
+CONSTRUCTOR FUNCTION <func_name>
+  [ ( [ <parm1> [ IN | IN OUT | OUT ] <datatype1>
+               [ DEFAULT <value1> ] ]
+      [, <parm2> [ IN | IN OUT | OUT ] <datatype2>
+               [ DEFAULT <value2> ]
+      ] ...)
+  ]
+RETURN <return_type>;
+{ IS | AS }
+[ <declarations> ]
+BEGIN
+  <statement>; ...
+[ EXCEPTION
+  WHEN ... THEN
+    <statement>; ...]
+END;
+```
+
+Where:
+
+`name` is an identifier (optionally schema-qualified) assigned to the object type.
+
+`method_spec` denotes the implementation of an instantiable method that was specified in the `CREATE TYPE` command.
+
+If `INSTANTIABLE` was specified or omitted in `method_spec` of the `CREATE TYPE` command, then there must be a `method_spec` for this method in the `CREATE TYPE BODY` command.
+
+If `NOT INSTANTIABLE` was specified in `method_spec` of the `CREATE TYPE` command, then there must be no `method_spec` for this method in the `CREATE TYPE BODY` command.
+
+`subprogram_spec` denotes the specification of a procedure or function and begins with the specification of either `MEMBER` or `STATIC`. The same qualifier must be used as specified in `subprogram_spec` of the `CREATE TYPE` command.
+
+`proc_name` is an identifier of a procedure specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command. They must be specified in the `CREATE TYPE BODY` command in the same manner as in the `CREATE TYPE` command.
+
+Include the `CONSTRUCTOR FUNCTION` keyword and function definition to define a constructor function.
+
+`func_name` is an identifier of a function specified in the `CREATE TYPE` command. The parameter declarations have the same meaning as described for the `CREATE TYPE` command and must be specified in the `CREATE TYPE BODY` command in the same manner as in the `CREATE TYPE` command. `return_type` is the data type of the value the function returns and must match the `return_type` given in the `CREATE TYPE` command.
+
+`PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the procedure or function as an autonomous transaction.
+
+`declarations` are variable, cursor, type, or subprogram declarations. If subprogram declarations are included, they must be declared after all other variable, cursor, and type declarations.
+
+`statement` is an SPL program statement.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/index.mdx
new file mode 100644
index 00000000000..cb64ccbfbe0
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/02_object_type_components/index.mdx
@@ -0,0 +1,24 @@
+---
+title: "Object type components"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.092.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.214.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/02_object_type_components/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="object_type_components" class="registered_link"></div>
+
+Object types are created and stored in the database by using the following two constructs of the SPL language:
+
+-   The *object type specification*. This construct is the public interface specifying the attributes and method signatures of the object type.
+-   The *object type body*. This construct contains the implementation of the methods specified in the object type specification.
+
+
+<div class="toctree" maxdepth="3">
+
+object_type_specification_syntax object_type_body_syntax
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/01_member_methods.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/01_member_methods.mdx
new file mode 100644
index 00000000000..4b8d99c2520
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/01_member_methods.mdx
@@ -0,0 +1,59 @@
+---
+title: "Member methods"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/01_member_methods/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="member_methods" class="registered_link"></div>
+
+A *member method* is a function or procedure that's defined in an object type and can be invoked only through an instance of that type. Member methods have access to, and can change the attributes of, the object instance on which they're operating.
+
+This object type specification creates the `emp_obj_typ` object type:
+
+```sql
+CREATE OR REPLACE TYPE emp_obj_typ AS OBJECT
+(
+    empno           NUMBER(4),
+    ename           VARCHAR2(20),
+    addr            ADDR_OBJ_TYP,
+    MEMBER PROCEDURE display_emp(SELF IN OUT emp_obj_typ)
+);
+```
+
+Object type `emp_obj_typ` contains a member method named `display_emp`. `display_emp` uses a `SELF` parameter, which passes the object instance on which the method is invoked.
+
+A `SELF` parameter is a parameter whose data type is that of the object type being defined. `SELF` always refers to the instance that's invoking the method. A `SELF` parameter is the first parameter in a member procedure or function regardless of whether it's explicitly declared in the parameter list.
+
+The following code defines an object type body for `emp_obj_typ`:
+
+```sql
+CREATE OR REPLACE TYPE BODY emp_obj_typ AS
+    MEMBER PROCEDURE display_emp (SELF IN OUT emp_obj_typ)
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Employee No   : ' || empno);
+        DBMS_OUTPUT.PUT_LINE('Name          : ' || ename);
+        DBMS_OUTPUT.PUT_LINE('Street        : ' || addr.street);
+        DBMS_OUTPUT.PUT_LINE('City/State/Zip: ' || addr.city || ', ' ||
+            addr.state || ' ' || LPAD(addr.zip,5,'0'));
+    END;
+END;
+```
+
+You can also use the `SELF` parameter in an object type body. Using the `SELF` parameter in the `CREATE TYPE BODY` command, you can write the same object type body as follows:
+
+```sql
+CREATE OR REPLACE TYPE BODY emp_obj_typ AS
+    MEMBER PROCEDURE display_emp (SELF IN OUT emp_obj_typ)
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Employee No   : ' || SELF.empno);
+        DBMS_OUTPUT.PUT_LINE('Name          : ' || SELF.ename);
+        DBMS_OUTPUT.PUT_LINE('Street        : ' || SELF.addr.street);
+        DBMS_OUTPUT.PUT_LINE('City/State/Zip: ' || SELF.addr.city || ', ' ||
+            SELF.addr.state || ' ' || LPAD(SELF.addr.zip,5,'0'));
+    END;
+END;
+```
+
+Both versions of the `emp_obj_typ` body are equivalent.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/02_static_methods.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/02_static_methods.mdx
new file mode 100644
index 00000000000..da256e13d03
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/02_static_methods.mdx
@@ -0,0 +1,59 @@
+---
+title: "Static methods"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/02_static_methods/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="static_methods" class="registered_link"></div>
+
+Like a member method, a static method belongs to a type. A static method, however, is invoked not by an instance of the type, but by using the name of the type. For example, to invoke a static function named `get_count`, defined in the `emp_obj_type type`, you can write:
+
+```sql
+emp_obj_type.get_count();
+```
+
+A static method doesn't have access to and can't change the attributes of an object instance. It doesn't typically work with an instance of the type.
+
+The following object type specification includes a static function `get_dname` and a member procedure `display_dept`:
+
+```sql
+CREATE OR REPLACE TYPE dept_obj_typ AS OBJECT (
+    deptno          NUMBER(2),
+    STATIC FUNCTION get_dname(p_deptno IN NUMBER) RETURN VARCHAR2,
+    MEMBER PROCEDURE display_dept
+);
+```
+
+The object type body for `dept_obj_typ` defines a static function named `get_dname` and a member procedure named `display_dept`:
+
+```sql
+CREATE OR REPLACE TYPE BODY dept_obj_typ AS
+    STATIC FUNCTION get_dname(p_deptno IN NUMBER) RETURN VARCHAR2
+    IS
+        v_dname     VARCHAR2(14);
+    BEGIN
+        CASE p_deptno
+            WHEN 10 THEN v_dname := 'ACCOUNTING';
+            WHEN 20 THEN v_dname := 'RESEARCH';
+            WHEN 30 THEN v_dname := 'SALES';
+            WHEN 40 THEN v_dname := 'OPERATIONS';
+            ELSE v_dname := 'UNKNOWN';
+        END CASE;
+        RETURN v_dname;
+    END;
+
+    MEMBER PROCEDURE display_dept
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Dept No    : ' || SELF.deptno);
+        DBMS_OUTPUT.PUT_LINE('Dept Name  : ' ||
+            dept_obj_typ.get_dname(SELF.deptno));
+    END;
+END;
+```
+
+The static function `get_dname` can't reference `SELF`. Since a static function is invoked independently of any object instance, it has no implicit access to any object attribute.
+
+Member procedure `display_dept` can access the `deptno` attribute of the object instance passed in the `SELF` parameter. It isn't necessary to explicitly declare the `SELF` parameter in the `display_dept` parameter list.
+
+The last `DBMS_OUTPUT.PUT_LINE` statement in the `display_dept` procedure includes a call to the static function `get_dname`, qualified by its object type name `dept_obj_typ`.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx
new file mode 100644
index 00000000000..3ce3180cc15
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods.mdx
@@ -0,0 +1,87 @@
+---
+title: "Constructor methods"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/03_constructor_methods/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="constructor_methods" class="registered_link"></div>
+
+A constructor method is a function that creates an instance of an object type, typically by assigning values to the members of the object. An object type can define several constructors to accomplish different tasks. A constructor method is a member function invoked with a `SELF` parameter whose name matches the name of the type.
+
+For example, if you define a type named `address`, each constructor is named `address`. You can overload a constructor by creating one or more different constructor functions with the same name but with different argument types.
+
+The SPL compiler provides a default constructor for each object type. The default constructor is a member function whose name matches the name of the type and whose argument list matches the type members in order. For example, given an object type such as:
+
+```sql
+CREATE TYPE address AS OBJECT
+(
+  street_address VARCHAR2(40),
+  postal_code    VARCHAR2(10),
+  city           VARCHAR2(40),
+  state          VARCHAR2(2)
+)
+```
+
+The SPL compiler provides a default constructor with the following signature:
+
+```sql
+CONSTRUCTOR FUNCTION address
+(
+  street_address VARCHAR2(40),
+  postal_code    VARCHAR2(10),
+  city           VARCHAR2(40),
+  state          VARCHAR2(2)
+)
+```
+
+The body of the default constructor sets each member to `NULL`.
+
+To create a custom constructor, using the keyword constructor, declare the constructor function in the `CREATE TYPE` command, and define the construction function in the `CREATE TYPE BODY` command. For example, you might want to create a custom constructor for the `address` type that computes the city and state given a `street_address` and `postal_code`:
+
+```sql
+CREATE TYPE address AS OBJECT
+(
+  street_address VARCHAR2(40),
+  postal_code    VARCHAR2(10),
+  city           VARCHAR2(40),
+  state          VARCHAR2(2),
+
+  CONSTRUCTOR FUNCTION address
+   (
+     street_address VARCHAR2,
+     postal_code VARCHAR2
+    ) RETURN self AS RESULT
+)
+CREATE TYPE BODY address AS
+ CONSTRUCTOR FUNCTION address
+  (
+    street_address VARCHAR2,
+    postal_code VARCHAR2
+   ) RETURN self AS RESULT
+ IS
+   BEGIN
+     self.street_address := street_address;
+     self.postal_code := postal_code;
+     self.city := postal_code_to_city(postal_code);
+     self.state := postal_code_to_state(postal_code);
+     RETURN;
+   END;
+END;
+```
+
+To create an instance of an object type, you invoke one of the constructor methods for that type. For example:
+
+```sql
+DECLARE
+  cust_addr address := address('100 Main Street', 02203');
+BEGIN
+  DBMS_OUTPUT.PUT_LINE(cust_addr.city);  -- displays Boston
+  DBMS_OUTPUT.PUT_LINE(cust_addr.state); -- displays MA
+END;
+```
+
+Custom constructor functions are:
+
+- Typically used to compute member values when given incomplete information. The example computes the values for `city` and `state` when given a postal code.
+
+- Also used to enforce business rules that restrict the state of an object. For example, if you define an object type to represent a `payment`, you can use a custom constructor to ensure that no object of type `payment` can be created with an `amount` that is `NULL`, negative, or zero. The default constructor sets `payment.amount` to `NULL`, so you must create a custom constructor whose signature matches the default constructor to prohibit `NULL` amounts.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/index.mdx
new file mode 100644
index 00000000000..4ffd504f1b8
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/index.mdx
@@ -0,0 +1,34 @@
+---
+title: "Creating object types"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.093.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.215.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/03_creating_object_types/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_object_types" class="registered_link"></div>
+
+You can use the `CREATE TYPE` command to create an object type specification and the `CREATE TYPE BODY` command to create an object type body. The examples that follow use the `CREATE TYPE` and `CREATE TYPE BODY` commands.
+
+The first example creates the `addr_object_type` object type that contains only attributes and no methods:
+
+```sql
+CREATE OR REPLACE TYPE addr_object_type AS OBJECT
+(
+    street          VARCHAR2(30),
+    city            VARCHAR2(20),
+    state           CHAR(2),
+    zip             NUMBER(5)
+);
+```
+
+Since there are no methods in this object type, an object type body isn't required. This example creates a composite type, which allows you to treat related objects as a single attribute.
+
+<div class="toctree" maxdepth="3">
+
+member_methods static_methods constructor_methods
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/04_creating_object_instances.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/04_creating_object_instances.mdx
new file mode 100644
index 00000000000..048058fcc80
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/04_creating_object_instances.mdx
@@ -0,0 +1,76 @@
+---
+title: "Creating object instances"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.094.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.216.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/04_creating_object_instances/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_object_instances" class="registered_link"></div>
+
+## Creating an instance 
+
+To create an instance of an object type, you must first declare a variable of the object type and then initialize the declared object variable. The syntax for declaring an object variable is:
+
+```text
+<object> <obj_type>
+```
+
+Where:
+
+`object` is an identifier assigned to the object variable.
+
+`obj_type` is the identifier of a previously defined object type.
+
+## Invoking a constructor method
+
+After declaring the object variable, you must invoke a *constructor method* to initialize the object with values. Use the following syntax to invoke the constructor method:
+
+```sql
+[NEW] <obj_type> ({<expr1> | NULL} [, {<expr2> | NULL} ] [, ...])
+```
+
+Where: 
+
+`obj_type` is the identifier of the object type’s constructor method. The constructor method has the same name as the previously declared object type.
+
+`expr1, expr2, …` are expressions that are type-compatible with the first attribute of the object type, the second attribute of the object type, and so on. If an attribute is of an object type, then the corresponding expression can be `NULL`, an object initialization expression, or any expression that returns that object type.
+
+This anonymous block declares and initializes a variable:
+
+```sql
+DECLARE
+    v_emp           EMP_OBJ_TYP;
+BEGIN
+    v_emp := emp_obj_typ (9001,'JONES',
+        addr_obj_typ('123 MAIN STREET','EDISON','NJ',08817));
+END;
+```
+
+The variable `v_emp` is declared with a previously defined object type named `EMP_OBJ_TYPE`. The body of the block initializes the variable using the `emp_obj_typ` and `addr_obj_type` constructors.
+
+You can include the `NEW` keyword when creating a new instance of an object in the body of a block. The `NEW` keyword invokes the object constructor whose signature matches the arguments provided.
+
+## Example 
+
+This example declares two variables named `mgr` and `emp`. The variables are both of `EMP_OBJ_TYPE`. The `mgr` object is initialized in the declaration, while the `emp` object is initialized to `NULL` in the declaration and assigned a value in the body.
+
+```sql
+DECLARE
+    mgr  EMP_OBJ_TYPE := (9002,'SMITH');
+    emp  EMP_OBJ_TYPE;
+BEGIN
+    emp := NEW EMP_OBJ_TYPE (9003,'RAY');
+END;
+```
+
+!!! Note
+    In EDB Postgres Advanced Server, you can use the following alternate syntax in place of the constructor method.
+
+```sql
+[ ROW ] ({ <expr1> | NULL } [, { <expr2> | NULL } ] [, ...])
+```
+
+`ROW` is an optional keyword if two or more terms are specified in the parenthesis-enclosed, comma-delimited list. If you specify only one term, then you must specify the `ROW` keyword.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/05_referencing_an_object.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/05_referencing_an_object.mdx
new file mode 100644
index 00000000000..964c3d945f7
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/05_referencing_an_object.mdx
@@ -0,0 +1,137 @@
+---
+title: "Referencing an object"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.095.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.217.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/05_referencing_an_object/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="referencing_an_object" class="registered_link"></div>
+
+## Syntax
+
+After you create and initialize an object variable, you can reference individual attributes using dot notation of the form:
+
+```text
+<object>.<attribute>
+```
+
+Where: 
+
+`object` is the identifier assigned to the object variable. 
+
+`attribute` is the identifier of an object type attribute.
+
+If `attribute` is of an object type, then the reference must take the form:
+
+```text
+<object>.<attribute>.<attribute_inner>
+```
+
+Where `attribute_inner` is an identifier belonging to the object type to which `attribute` references in its definition of `object`.
+
+## Examples
+
+This example displays the values assigned to the `emp_obj_typ` object:
+
+```sql
+DECLARE
+    v_emp          EMP_OBJ_TYP;
+BEGIN
+    v_emp := emp_obj_typ(9001,'JONES',
+        addr_obj_typ('123 MAIN STREET','EDISON','NJ',08817));
+    DBMS_OUTPUT.PUT_LINE('Employee No   : ' || v_emp.empno);
+    DBMS_OUTPUT.PUT_LINE('Name          : ' || v_emp.ename);
+    DBMS_OUTPUT.PUT_LINE('Street        : ' || v_emp.addr.street);
+    DBMS_OUTPUT.PUT_LINE('City/State/Zip: ' || v_emp.addr.city || ', ' ||
+        v_emp.addr.state || ' ' || LPAD(v_emp.addr.zip,5,'0'));
+END;
+```
+
+The following is the output from this anonymous block:
+
+```sql
+__OUTPUT__
+Employee No   : 9001
+Name          : JONES
+Street        : 123 MAIN STREET
+City/State/Zip: EDISON, NJ 08817
+```
+
+Methods are called in a similar manner as attributes.
+
+Once an object variable is created and initialized, member procedures or functions are called using dot notation of the form:
+
+```text
+<object>.<prog_name>
+```
+
+Where:
+
+`object` is the identifier assigned to the object variable. 
+
+`prog_name` is the identifier of the procedure or function.
+
+Static procedures or functions aren't called using an object variable. Instead call the procedure or function using the object type name:
+
+```text
+<object_type>.<prog_name>
+```
+
+Where:
+
+`object_type` is the identifier assigned to the object type. 
+
+`prog_name` is the identifier of the procedure or function.
+
+You can duplicate the results of the previous anonymous block by calling the member procedure `display_emp`:
+
+```sql
+DECLARE
+    v_emp          EMP_OBJ_TYP;
+BEGIN
+    v_emp := emp_obj_typ(9001,'JONES',
+        addr_obj_typ('123 MAIN STREET','EDISON','NJ',08817));
+    v_emp.display_emp;
+END;
+```
+
+The following is the output from this anonymous block:
+
+```sql
+__OUTPUT__
+Employee No   : 9001
+Name          : JONES
+Street        : 123 MAIN STREET
+City/State/Zip: EDISON, NJ 08817
+```
+
+This anonymous block creates an instance of `dept_obj_typ` and calls the member procedure `display_dept`:
+
+```sql
+DECLARE
+    v_dept          DEPT_OBJ_TYP := dept_obj_typ (20);
+BEGIN
+    v_dept.display_dept;
+END;
+```
+
+The following is the output from this anonymous block:
+
+```sql
+__OUTPUT__
+Dept No    : 20
+Dept Name  : RESEARCH
+```
+
+You can call the static function defined in `dept_obj_typ` directly by qualifying it by the object type name as follows:
+
+```sql
+BEGIN
+    DBMS_OUTPUT.PUT_LINE(dept_obj_typ.get_dname(20));
+END;
+
+RESEARCH
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/06_dropping_an_object_type.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/06_dropping_an_object_type.mdx
new file mode 100644
index 00000000000..53c58d7bd9e
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/06_dropping_an_object_type.mdx
@@ -0,0 +1,47 @@
+---
+title: "Dropping an object type"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.096.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.218.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/06_dropping_an_object_type/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dropping_an_object_type" class="registered_link"></div>
+
+
+## Deleting an object type
+
+The syntax for deleting an object type is as follows:
+
+```sql
+DROP TYPE <objtype>;
+```
+
+Where `objtype` is the identifier of the object type to drop. If the definition of `objtype` contains attributes that are themselves object types or collection types, you must drop these nested object types or collection types last.
+
+If an object type body is defined for the object type, the `DROP TYPE` command deletes the object-type body as well as the object-type specification. To re-create the complete object type, you must reissue both the `CREATE TYPE` and `CREATE TYPE BODY` commands.
+
+This example drops the `emp_obj_typ` and the `addr_obj_typ` object types. You must drop `emp_obj_typ` first since it contains `addr_obj_typ` in its definition as an attribute.
+
+```sql
+DROP TYPE emp_obj_typ;
+DROP TYPE addr_obj_typ;
+```
+
+## Dropping only the object type body
+
+The syntax for deleting an object type body but not the object type specification is:
+
+```sql
+DROP TYPE BODY <objtype>;
+```
+
+You can re-create the object type body by issuing the `CREATE TYPE BODY` command.
+
+This example drops only the object type body of the `dept_obj_typ`:
+
+```sql
+DROP TYPE BODY dept_obj_typ;
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/index.mdx
new file mode 100644
index 00000000000..ba89c2a52cb
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/15_object_types_and_objects/index.mdx
@@ -0,0 +1,29 @@
+---
+title: "Using object types and objects"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.090.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.212.html"
+redirects:
+  - /epas/latest/epas_compat_spl/15_object_types_and_objects/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="object_types_and_objects" class="registered_link"></div>
+
+You can use object-oriented programming techniques in SPL. Object-oriented programming as seen in programming languages such as Java and C++ centers on the concept of *objects*. An object represents a real-world entity such as a person, place, or thing. The generic description or definition of a particular object such as a person, for example, is called an *object type*. Specific people, such as “Joe” or “Sally”, are said to be *objects of object type* person. They're also known as *instances* of the object type person or, simply, person objects.
+
+You can create objects and object types in SPL.
+
+!!! Note
+    -   The terms “database objects” and “objects” are different from the terms "object type" and "object" used in object-oriented programming. Database objects are the entities that can be created in a database, such as tables, views, indexes, and users. In the context of object-oriented program, object type and object refer to specific data structures supported by the SPL programming language to implement object-oriented concepts.
+
+    -   In Oracle, the term *abstract data type* (ADT) describes object types in PL/SQL. The SPL implementation of object types is intended to be compatible with Oracle abstract data types.
+
+    -   EDB Postgres Advanced Server hasn't yet implemented support for some features of object-oriented programming languages.
+
+<div class="toctree" maxdepth="3">
+
+basic_object_concepts object_type_components creating_object_types creating_object_instances referencing_an_object dropping_an_object_type
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definer's_rights_package.png b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definer's_rights_package.png
new file mode 100755
index 00000000000..eff47bf9058
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definer's_rights_package.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89d79f4e078a0a507127191caae821b82c85590b59f8de7dac54afc184ca0099
+size 19423
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definers_rights_package.png b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definers_rights_package.png
new file mode 100755
index 00000000000..049b2568c14
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/definers_rights_package.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:93558bcf05875dcb2ed2e49dcb1e732ade405f27e808260369e8e17dba632bf9
+size 21636
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/invokers_rights_programs.png b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/invokers_rights_programs.png
new file mode 100755
index 00000000000..0447f5d9f7e
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/images/invokers_rights_programs.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd88c09a0907e24e609303655d3364f4f218982a14dccf3d419a6c9cf74611fc
+size 22493
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_spl/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_spl/index.mdx
new file mode 100644
index 00000000000..6702df8b4d6
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_spl/index.mdx
@@ -0,0 +1,21 @@
+---
+navTitle: Stored procedural language
+title: "Using the stored procedural language"
+indexCards: simple
+description: "How to use SPL to create stored procedures, functions, triggers, and packages for the EDB Postgres Advanced Server database"
+redirects:
+  - /epas/latest/epas_compat_spl/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server's stored procedural language (SPL) is a highly productive, procedural programming language for writing custom procedures, functions, triggers, and packages for EDB Postgres Advanced Server. It provides:
+
+-   Full procedural programming functionality to complement the SQL language
+-   A single, common language to create stored procedures, functions, triggers, and packages for the EDB Postgres Advanced Server database
+-   A seamless development and testing environment
+-   The use of reusable code
+-   Ease of use
+
+For reference information about the SPL program types, programming statements, control structures, collection types, and collection methods, see [Stored procedural language (SPL) reference](/epas/latest/reference/application_programmer_reference/stored_procedural_language_reference/).
+
+
+
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/01_oracle_compat_summary.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/01_oracle_compat_summary.mdx
new file mode 100644
index 00000000000..9d857ff7329
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/01_oracle_compat_summary.mdx
@@ -0,0 +1,14 @@
+---
+title: "Oracle table partitioning compatibility summary"
+---
+
+EDB Postgres Advanced Server supports aspects of table partitioning that are compatible with Oracle databases.
+
+!!! Note
+    The *declarative partitioning* feature, introduced with PostgreSQL version 10, is not covered here. However, PostgreSQL declarative partitioning is supported in EDB Postgres Advanced Server 10 in addition to the table partitioning compatible with Oracle databases described here. For information about declarative partitioning, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/ddl-partitioning.html).
+
+The PostgreSQL `INSERT... ON CONFLICT DO NOTHING/UPDATE` clause, commonly known as `UPSERT`, isn't supported on Oracle-styled partitioned tables. If you include the `ON CONFLICT DO NOTHING/UPDATE` clause when invoking the INSERT command to add data to a partitioned table, an error occurs.
+
+!!! Note
+    EDB Postgres Advanced Server doesn't support global indexes, so the index isn't inherited when you define a primary key on the partitioned table that doesn't include partition key columns. However, all partitions defined in `CREATE TABLE` have an independent primary index on the column. You can re-create the primary key on all newly added partitions by using `ALTER TABLE ... ADD CONSTRAINT`. This primary index enforces uniqueness in each partition but not across the entire partition hierarchy. In other words, you can have the same value repeated for the primary index column in two or more partitions.
+
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx
new file mode 100644
index 00000000000..b95324f0067
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning.mdx
@@ -0,0 +1,31 @@
+---
+title: "Interval range partitioning"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="interval_range_partitioning" class="registered_link"></div>
+
+Interval range partitioning is an extension to range partitioning that allows a database to create a partition when the inserted data exceeds the range of an existing partition. To implement interval range partitioning, include the `INTERVAL` clause, and specify the range size for a new partition.
+
+The high value of a range partition, also known as the transition point, is determined by the range partitioning key value. The database creates partitions for inserted data with values that are beyond that high value.
+
+## Interval range partitioning example
+
+Suppose an interval is set to one month. If data is inserted for two months after the current transition point, only the partition for the second month is created and not the intervening partition. For example, you can create an interval-range-partitioned table with a monthly interval and a current transition point of February 15, 2023. If you try to insert data for May 10, 2023, then the required partition for April 15 to May 15, 2023 is created and data is inserted into that partition. The partition for February 15, 2023 to March 15, 2023 and March 15, 2023 to April 15, 2023 is skipped.
+
+For information about interval range partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/).
+
+## Restrictions on interval range partitioning
+
+The following restrictions apply to the `INTERVAL` clause:
+
+-   Interval range partitioning is restricted to a single partition key. That key must be a numerical or date range.
+-   You must define at least one range partition.
+-   The `INTERVAL` clause isn't supported for index-organized tables.
+-   You can't create a domain index on an interval-range-partitioned table.
+-   In composite partitioning, the interval range partitioning can be useful as a primary partitioning mechanism but isn't supported at the subpartition level.
+-   You can't define `DEFAULT` and `MAXVALUE` for an interval-range-partitioned table.
+-   You can't specify `NULL`, `Not-a-Number`, and `Infinity` values in the partitioning key column.
+-   Interval range partitioning expression must yield constant value and can't be a negative value.
+-   You must create the partitions for an interval-range-partitioned table in increasing order.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx
new file mode 100644
index 00000000000..e44e9e933ad
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning.mdx
@@ -0,0 +1,21 @@
+---
+title: "Automatic list partitioning"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="automatic_list_partitioning" class="registered_link"></div>
+
+Automatic list partitioning is an extension to `LIST` partitioning that allows a database to create a partition for any new distinct value of the list partitioning key. A new partition is created when data is inserted into the `LIST` partitioned table and the inserted value doesn't match any of the existing table partition. Use the `AUTOMATIC` clause to implement automatic list partitioning.
+
+For example, consider a table named `sales` with a `sales_state` column that contains the existing partition values `CALIFORNIA` and `FLORIDA`. Each of the `sales_state` values increases with a rise in the statewise sales. A sale in a new state, for example, `INDIANA` and `OHIO`, requires creating new partitions. If you implement automatic list partitioning, the new partitions `INDIANA` and `OHIO` are automatically created, and data is entered into the `sales` table.
+
+For information about automatic list partitioning syntax, see [CREATE TABLE...PARTITION BY](../../../reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/).
+
+## Restrictions for automatic list partitioning
+
+The following restrictions apply to the `AUTOMATIC` clause:
+
+-   A table that enables automatic list partitioning can't have a `DEFAULT` partition.
+-   Automatic list partitioning doesn't support multi-column list partitioning.
+-   In composite partitioning, the automatic list partitioning can be useful as a primary partitioning mechanism but isn't supported at the subpartition level.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/index.mdx
new file mode 100644
index 00000000000..5585239fda5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/index.mdx
@@ -0,0 +1,50 @@
+---
+title: "Selecting a partition type"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.101.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.326.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.051.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/02_selecting_a_partition_type/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="selecting_a_partition_type" class="registered_link"></div>
+
+When you create a partitioned table, you specify `LIST`, `RANGE`, or `HASH` partitioning rules. The partitioning rules provide a set of constraints that define the data that's stored in each partition. As you add rows to the partitioned table, the server uses the partitioning rules to decide which partition contains each row.
+
+EDB Postgres Advanced Server can also use the partitioning rules to enforce partition pruning, which improves performance when responding to user queries. When selecting a partitioning type and partitioning keys for a table, consider how the data that's stored in a table is queried, and include often-queried columns in the partitioning rules.
+
+## List partitioning
+
+When you create a list-partitioned table, you specify a single partitioning key column. When adding a row to the table, the server compares the key values specified in the partitioning rule to the corresponding column in the row. If the column value matches a value in the partitioning rule, the row is stored in the partition named in the rule.
+
+!!! Note
+    List partitioning doesn't support multi-column list partitioning.
+
+See [Automatic list partitioning](02_automatic_list_partitioning.mdx) for information about an extension to `LIST` partitioning that enables a database to automatically create a partition for any new distinct value of the list partitioning key.
+
+## Range partitioning
+
+When you create a range-partitioned table, you specify one or more partitioning key columns. When you add a row to the table, the server compares the value of the partitioning keys to the corresponding columns in a table entry. If the column values satisfy the conditions specified in the partitioning rule, the row is stored in the partition named in the rule.
+
+See [Interval range partitioning](01_interval_range_partitioning.mdx) for information about an extension to range partitioning that enables a database to create a partition when the inserted data exceeds the range of an existing partition.
+
+## Hash partitioning
+
+When you create a hash-partitioned table, you specify one or more partitioning key columns. Data is divided into approximately equal-sized partitions among the specified partitions. When you add a row to a hash-partitioned table, the server computes a hash value for the data in the specified columns and stores the row in a partition according to the hash value.
+
+!!! Note
+    When upgrading EDB Postgres Advanced Server, you must rebuild each hash-partitioned table on the upgraded version server.
+
+## Subpartitioning
+
+Subpartitioning breaks a partitioned table into smaller subsets. You must store all subsets in the same database server cluster. A table is typically subpartitioned by a different set of columns. It can have a different subpartitioning type from the parent partition. If you subpartition one partition, then each partition has at least one subpartition.
+
+If you subpartition a table, no data is stored in any of the partition tables. Instead, the data is stored in the corresponding subpartitions.
+
+<div class="toctree" maxdepth="3">
+
+interval_range_partitioning automatic_list_partitioning
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/01_example_partition_pruning.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/01_example_partition_pruning.mdx
new file mode 100644
index 00000000000..ff4ccd00c29
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/01_example_partition_pruning.mdx
@@ -0,0 +1,123 @@
+---
+title: "Example: Partition pruning"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.103.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.328.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/03_using_partition_pruning/01_example_partition_pruning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_pruning" class="registered_link"></div>
+
+The `EXPLAIN` statement displays the execution plan of a statement. You can use the `EXPLAIN` statement to confirm that EDB Postgres Advanced Server is pruning partitions from the execution plan of a query.
+
+This example shows the efficiency of partition pruning. Create a simple table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Perform a constrained query that includes the `EXPLAIN` statement:
+
+```sql
+EXPLAIN (COSTS OFF) SELECT * FROM sales WHERE country = 'INDIA';
+```
+
+The resulting query plan shows that the server scans only the `sales_asia` table. That's the table in which a row with a `country` value of `INDIA` is stored.
+
+```sql
+edb=# EXPLAIN (COSTS OFF) SELECT * FROM sales WHERE country = 'INDIA';
+__OUTPUT__
+                    QUERY PLAN
+---------------------------------------------------
+ Append
+   ->  Seq Scan on sales_asia
+         Filter: ((country)::text = 'INDIA'::text)
+(3 rows)
+```
+
+Suppose you perform a query that searches for a row that matches a value not included in the partitioning key:
+
+```sql
+EXPLAIN (COSTS OFF) SELECT * FROM sales WHERE dept_no = '30';
+```
+
+The resulting query plan shows that the server must look in all of the partitions to locate the rows that satisfy the query:
+
+```sql
+edb=# EXPLAIN (COSTS OFF) SELECT * FROM sales WHERE dept_no = '30';
+__OUTPUT__
+                QUERY PLAN
+-------------------------------------------
+ Append
+   ->  Seq Scan on sales_americas
+         Filter: (dept_no = '30'::numeric)
+   ->  Seq Scan on sales_europe
+         Filter: (dept_no = '30'::numeric)
+   ->  Seq Scan on sales_asia
+         Filter: (dept_no = '30'::numeric)
+(7 rows)
+```
+
+Constraint exclusion also applies when querying subpartitioned tables:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date) SUBPARTITION BY LIST (country)
+(
+  PARTITION "2011" VALUES LESS THAN('01-JAN-2012')
+  (
+    SUBPARTITION europe_2011 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2011 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2011 VALUES ('US', 'CANADA')
+  ),
+  PARTITION "2012" VALUES LESS THAN('01-JAN-2013')
+  (
+    SUBPARTITION europe_2012 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2012 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2012 VALUES ('US', 'CANADA')
+  ),
+  PARTITION "2013" VALUES LESS THAN('01-JAN-2015')
+  (
+    SUBPARTITION europe_2013 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2013 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2013 VALUES ('US', 'CANADA')
+  )
+);
+```
+
+When you query the table, the query planner prunes any partitions or subpartitions from the search path that can't contain the desired result set:
+
+```sql
+edb=# EXPLAIN (COSTS OFF) SELECT * FROM sales WHERE country = 'US' AND date = 'Dec 12, 2012';
+__OUTPUT__
+                                                   QUERY PLAN
+-----------------------------------------------------------------------------
+------------------------------------
+ Append
+   ->  Seq Scan on sales_americas_2012
+         Filter: (((country)::text = 'US'::text) AND (date = '12-DEC-12
+         00:00:00'::timestamp without time zone))
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/index.mdx
new file mode 100644
index 00000000000..9457070c77b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/03_using_partition_pruning/index.mdx
@@ -0,0 +1,145 @@
+---
+title: "Using partition pruning"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.102.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.327.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.052.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/03_using_partition_pruning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_partition_pruning" class="registered_link"></div>
+
+EDB Postgres Advanced Server's query planner uses *partition pruning* to compute an efficient plan to locate any rows that match the conditions specified in the `WHERE` clause of a `SELECT` statement. To successfully prune partitions from an execution plan, the `WHERE` clause must constrain the information that's compared to the partitioning key column specified when creating the partitioned table. 
+
+| When querying a...         | Partition pruning is effective when... |
+|----------------------------|----------------------------------------|
+| List-partitioned table     | The `WHERE` clause compares a literal value to the partitioning key using operators like equal (=) or `AND`. |
+| Range-partitioned table    | The `WHERE` clause compares a literal value to a partitioning key using operators such as equal (=), less than (&lt;), or greater than (>).
+| Hash-partitioned table     | The `WHERE` clause compares a literal value to the partitioning key using an operator such as equal (=). |
+
+## Partition pruning techniques
+
+The partition pruning mechanism uses two optimization techniques:
+
+-   Constraint exclusion
+-   Fast pruning
+
+Partition pruning techniques limit the search for data only to those partitions where the values you're searching for might reside. Both pruning techniques remove partitions from a query's execution plan, improving performance.
+
+The difference between the fast pruning and constraint exclusion is that fast pruning understands the relationship between the partitions in an Oracle-partitioned table. Constraint exclusion doesn't. For example, when a query searches for a specific value in a list-partitioned table, fast pruning can reason that only a specific partition can hold that value. Constraint exclusion must examine the constraints defined for each partition. Fast pruning occurs early in the planning process to reduce the number of partitions that the planner must consider. Constraint exclusion occurs late in the planning process.
+
+[This example](01_example_partition_pruning.mdx) shows the efficiency of partition pruning, using the `EXPLAIN` statement to confirm that EDB Postgres Advanced Server is pruning partitions from the execution plan of a query.
+
+## Using constraint exclusion
+
+The `constraint_exclusion` parameter controls constraint exclusion. The `constraint_exclusion` parameter can have a value of `on`, `off`, or `partition`. To enable constraint exclusion, you must set the parameter to either `partition` or `on`. By default, the parameter is set to `partition`.
+
+For more information about constraint exclusion, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/static/ddl-partitioning.html).
+
+When constraint exclusion is enabled, the server examines the constraints defined for each partition to determine if that partition can satisfy a query.
+
+When you execute a `SELECT` statement that doesn't contain a `WHERE` clause, the query planner must recommend an execution plan that searches the entire table. When you execute a `SELECT` statement that contains a `WHERE` clause, the query planner:
+
+-  Determines the partition to store the row
+-  Sends query fragments to that partition
+-  Prunes the partitions that can't contain that row from the execution plan
+
+If you aren't using partitioned tables, disabling constraint exclusion might improve performance.
+
+## Using fast pruning
+
+Like constraint exclusion, fast pruning can optimize only queries that include a `WHERE` or join clause. However, the qualifiers in the `WHERE` clause must match a certain form. In both cases, the query planner avoids searching for data in partitions that can't hold the data required by the query.
+
+Fast pruning is controlled by a Boolean configuration parameter named `edb_enable_pruning`. Set `edb_enable_pruning` to `ON` to enable fast pruning of certain queries. Set `edb_enable_pruning` to `OFF` to disable fast pruning.
+
+!!! Note
+    Fast pruning can optimize queries against subpartitioned tables or optimize queries against range-partitioned tables only for tables that are partitioned on one column.
+
+For LIST-partitioned tables, EDB Postgres Advanced Server can fast prune queries that contain a `WHERE` clause that constrains a partitioning column to a literal value. For example, given a LIST-partitioned table such as:
+
+```sql
+CREATE TABLE sales_hist(..., country text, ...)
+PARTITION BY LIST(country)
+(
+    PARTITION americas VALUES('US', 'CA', 'MX'),
+    PARTITION europe VALUES('BE', 'NL', 'FR'),
+    PARTITION asia VALUES('JP', 'PK', 'CN'),
+    PARTITION others VALUES(DEFAULT)
+)
+```
+
+Fast pruning can reason about `WHERE` clauses such as:
+
+ `WHERE country = 'US'`
+
+ `WHERE country IS NULL;`
+
+With the first `WHERE` clause, fast pruning eliminates partitions `europe`, `asia`, and `others` because those partitions can't hold rows that satisfy the qualifier `WHERE country = 'US'`.
+
+With the second `WHERE` clause, fast pruning eliminates partitions `americas`, `europe`, and `asia` because those partitions can't hold rows where `country IS NULL`.
+
+The operator specified in the `WHERE` clause must be an equals sign (=) or the equality operator appropriate for the data type of the partitioning column.
+
+For range-partitioned tables, EDB Postgres Advanced Server can fast prune queries that contain a `WHERE` clause that constrains a partitioning column to a literal value. However, the operator can be any of the following:
+
+ `>`
+
+ `>=`
+
+ `=`
+
+ `<=`
+
+ `<`
+
+Fast pruning also reasons about more complex expressions involving `AND` and `BETWEEN` operators, such as:
+
+```sql
+WHERE size > 100 AND size <= 200
+WHERE size BETWEEN 100 AND 200
+```
+
+Fast pruning can't prune based on expressions involving `OR` or `IN`. For example, when querying a RANGE-partitioned table, such as:
+
+```sql
+CREATE TABLE boxes(id int, size int, color text)
+  PARTITION BY RANGE(size)
+(
+    PARTITION small VALUES LESS THAN(100),
+    PARTITION medium VALUES LESS THAN(200),
+    PARTITION large VALUES LESS THAN(300)
+)
+```
+
+Fast pruning can reason about `WHERE` clauses such as:
+
+ `WHERE size > 100     -- scan partitions 'medium' and 'large'`
+
+ `WHERE size >= 100    -- scan partitions 'medium' and 'large'`
+
+ `WHERE size = 100     -- scan partition 'medium'`
+
+ `WHERE size <= 100    -- scan partitions 'small' and 'medium'`
+
+ `WHERE size < 100     -- scan partition 'small'`
+
+ `WHERE size > 100 AND size < 199     -- scan partition 'medium'`
+
+ `WHERE size BETWEEN 100 AND 199      -- scan partition 'medium'`
+
+ `WHERE color = 'red' AND size = 100  -- scan 'medium'`
+
+ `WHERE color = 'red' AND (size > 100 AND size < 199) -- scan 'medium'`
+
+In each case, fast pruning requires that the qualifier refer to a partitioning column and literal value (or `IS NULL/IS NOT NULL`).
+
+!!! Note
+    Fast pruning can also optimize `DELETE` and `UPDATE` statements containing these `WHERE` clauses.
+  
+<div class="toctree" maxdepth="3">
+
+example_partition_pruning
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_default_partition.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_default_partition.mdx
new file mode 100644
index 00000000000..17201a836a4
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_default_partition.mdx
@@ -0,0 +1,206 @@
+---
+title: "Defining a DEFAULT partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+A `DEFAULT` partition captures any rows that don't fit into any other partition in a `LIST` partitioned or subpartitioned table. If you don't include a `DEFAULT` rule, any row that doesn't match one of the values in the partitioning constraints causes an error. Each `LIST` partition or subpartition can have its own `DEFAULT` rule.
+
+The syntax of a `DEFAULT` rule is:
+
+```sql
+PARTITION [<partition_name>] VALUES (DEFAULT)
+```
+
+Where `partition_name` specifies the name of the partition or subpartition that stores any rows that don't match the rules specified for other partitions.
+
+## Adding a DEFAULT partition
+
+You can create a list-partitioned table in which the server decides the partition for storing the data based on the value of the `country` column. In that case, if you attempt to add a row in which the value of the `country` column contains a value not listed in the rules, an error is reported:
+
+```sql
+edb=# INSERT INTO sales VALUES
+edb-#  (40, '3000x', 'IRELAND', '01-Mar-2012', '45000');
+ERROR:  no partition of relation "sales_2012" found for row
+DETAIL:  Partition key of the failing row contains (country) = (IRELAND).
+```
+
+This example creates such a table but adds a `DEFAULT` partition. The server stores any rows that don't match a value specified in the partitioning rules for `europe`, `asia`, or `americas` partitions in the `others` partition.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA'),
+  PARTITION others VALUES (DEFAULT)
+);
+```
+## Testing the DEFAULT partition
+
+To test the `DEFAULT` partition, add a row with a value in the `country` column that doesn't match one of the countries specified in the partitioning constraints:
+
+```text
+INSERT INTO sales VALUES
+  (40, '3000x', 'IRELAND', '01-Mar-2012', '45000');
+```
+
+Query the contents of the `sales` table to confirm that the previously rejected row is now stored in the `sales_others` partition:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_americas |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_americas |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_americas |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_americas |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_americas |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_americas |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_americas |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+ sales_others   |      40 | 3000x   | IRELAND  | 01-MAR-12 00:00:00 |  45000
+(18 rows)
+```
+
+EDB Postgres Advanced Server provides the following methods to reassign the contents of a `DEFAULT` partition or subpartition:
+
+-   You can use the `ALTER TABLE… ADD PARTITION` command to add a partition to a table with a `DEFAULT` rule. There can't be conflicting values between existing rows in the table and the values of the partition you're adding. You can alternatively use the `ALTER TABLE… SPLIT PARTITION` command to split an existing partition. 
+-   You can use the `ALTER TABLE… ADD SUBPARTITION` command to add a subpartition to a table with a `DEFAULT` rule. There can't be conflicting values between existing rows in the table and the values of the subpartition you're adding. You can alternatively use the `ALTER TABLE… SPLIT SUBPARTITION` command to split an existing subpartition.
+
+## Example: Adding a partition to a table with a DEFAULT partition
+
+This example uses the `ALTER TABLE... ADD PARTITION` command. It assumes there's no conflicting values between the existing rows in the table and the values of the partition to add.
+
+```sql
+edb=# ALTER TABLE sales ADD PARTITION africa values ('SOUTH AFRICA', 'KENYA');
+ALTER TABLE
+```
+
+When the following rows are inserted into the table, an error occurs, indicating that there are conflicting values:
+
+```sql
+edb=# INSERT INTO sales (dept_no, country) VALUES
+(1,'FRANCE'),(2,'INDIA'),(3,'US'),(4,'SOUTH AFRICA'),(5,'NEPAL');
+INSERT 0 5
+```
+
+Row `(4,'SOUTH AFRICA')` conflicts with the `VALUES` list in the `ALTER TABLE... ADD PARTITION` statement, thus resulting in an error:
+
+```sql
+edb=# ALTER TABLE sales ADD PARTITION africa values ('SOUTH AFRICA', 'KENYA');
+ERROR:  updated partition constraint for default partition "sales_others"
+would be violated by some row
+```
+
+## Example: Splitting a DEFAULT partition
+
+This example splits a `DEFAULT` partition, redistributing the partition's content between two new partitions in the table `sales`. 
+
+This command inserts rows into the table, including rows into the `DEFAULT` partition:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (30, '9519b', 'US', '12-Apr-2012', '145000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (40, '4519b', 'SOUTH AFRICA', '08-Apr-2012', '120000'),
+  (40, '4519b', 'KENYA', '08-Apr-2012', '120000'),
+  (50, '3788a', 'CHINA', '12-May-2012', '4950');
+```
+
+The partitions include the `DEFAULT others` partition:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+ OTHERS         | DEFAULT
+(4 rows)
+```
+
+This command shows the rows distributed among the partitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid     | dept_no| part_no |   country    |        date        | amount
+--------------+--------+---------+--------------+--------------------+-------
+sales_americas|     30 | 9519b   | US           | 12-APR-12 00:00:00 |145000
+sales_americas|     30 | 7588b   | CANADA       | 14-DEC-12 00:00:00 | 50000
+sales_europe  |     10 | 4519b   | FRANCE       | 17-JAN-12 00:00:00 | 45000
+sales_europe  |     10 | 9519b   | ITALY        | 07-JUL-12 00:00:00 | 15000
+sales_asia    |     20 | 3788a   | INDIA        | 01-MAR-12 00:00:00 | 75000
+sales_asia    |     20 | 3788a   | PAKISTAN     | 04-JUN-12 00:00:00 | 37500
+sales_others  |     40 | 4519b   | SOUTH AFRICA | 08-APR-12 00:00:00 |120000
+sales_others  |     40 | 4519b   | KENYA        | 08-APR-12 00:00:00 |120000
+sales_others  |     50 | 3788a   | CHINA        | 12-MAY-12 00:00:00 |  4950
+(9 rows)
+```
+
+This command splits the `DEFAULT others` partition into partitions named `africa` and `others`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION others VALUES
+  ('SOUTH AFRICA', 'KENYA')
+  INTO (PARTITION africa, PARTITION others);
+```
+
+The partitions now include the `africa` partition along with the `DEFAULT others` partition:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |       high_value
+----------------+-------------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+ AFRICA         | 'SOUTH AFRICA', 'KENYA'
+ OTHERS         | DEFAULT
+(5 rows)
+```
+
+This command shows that the rows were redistributed across the new partitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid      |dept_no | part_no |   country   |        date        | amount
+---------------+--------+---------+-------------+--------------------+-------
+sales_americas |     30 | 9519b   | US          | 12-APR-12 00:00:00 |145000
+sales_americas |     30 | 7588b   | CANADA      | 14-DEC-12 00:00:00 | 50000
+sales_europe   |     10 | 4519b   | FRANCE      | 17-JAN-12 00:00:00 | 45000
+sales_europe   |     10 | 9519b   | ITALY       | 07-JUL-12 00:00:00 | 15000
+sales_asia     |     20 | 3788a   | INDIA       | 01-MAR-12 00:00:00 | 75000
+sales_asia     |     20 | 3788a   | PAKISTAN    | 04-JUN-12 00:00:00 | 37500
+sales_africa   |     40 | 4519b   | SOUTH AFRICA| 08-APR-12 00:00:00 |120000
+sales_africa   |     40 | 4519b   | KENYA       | 08-APR-12 00:00:00 |120000
+sales_others_1 |     50 | 3788a   | CHINA       | 12-MAY-12 00:00:00 | 4950
+(9 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_maxvalue_partition.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_maxvalue_partition.mdx
new file mode 100644
index 00000000000..09100aadf71
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/defining_a_maxvalue_partition.mdx
@@ -0,0 +1,83 @@
+---
+title: "Defining a MAXVALUE partition"
+---
+
+A `MAXVALUE` partition or subpartition captures any rows that don't fit into any other partition in a range-partitioned or subpartitioned table. If you don't include a `MAXVALUE` rule, any row that exceeds the maximum limit specified by the partitioning rules causes in an error. Each partition or subpartition can have its own `MAXVALUE` partition.
+
+The syntax of a `MAXVALUE` rule is:
+
+```sql
+PARTITION [<partition_name>] VALUES LESS THAN (MAXVALUE)
+```
+
+Where `partition_name` specifies the name of the partition that stores any rows that don't match the rules specified for other partitions.
+
+[This example](../06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table/) created a range-partitioned table in which the data was partitioned based on the value of the `date` column. If you attempt to add a row with a `date` value that exceeds a date listed in the partitioning constraints, EDB Postgres Advanced Server reports an error.
+
+```sql
+edb=# INSERT INTO sales VALUES
+edb-#   (40, '3000x', 'IRELAND', '01-Mar-2013', '45000');
+ERROR:  no partition of relation "sales" found for row
+DETAIL:  Partition key of the failing row contains (date) = (01-MAR-13 00:00:00).
+```
+
+This `CREATE TABLE` command creates the same table but with a `MAXVALUE` partition. Instead of throwing an error, the server stores any rows that don't match the previous partitioning constraints in the `others` partition.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+(
+  PARTITION q1_2012 VALUES LESS THAN('2012-Apr-01'),
+  PARTITION q2_2012 VALUES LESS THAN('2012-Jul-01'),
+  PARTITION q3_2012 VALUES LESS THAN('2012-Oct-01'),
+  PARTITION q4_2012 VALUES LESS THAN('2013-Jan-01'),
+  PARTITION others VALUES LESS THAN (MAXVALUE)
+);
+```
+
+To test the `MAXVALUE` partition, add a row with a value in the `date` column that exceeds the last date value listed in a partitioning rule. The server stores the row in the `others` partition.
+
+```sql
+INSERT INTO sales VALUES
+  (40, '3000x', 'IRELAND', '01-Mar-2013', '45000');
+```
+
+Query the contents of the `sales` table to confirm that the previously rejected row is now stored in the `sales_others` partition:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid    | dept_no | part_no | country  |        date        | amount
+---------------+---------+---------+----------+--------------------+--------
+ sales_q1_2012 |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_q1_2012 |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_q1_2012 |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_q2_2012 |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_q2_2012 |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_q2_2012 |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_q2_2012 |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_q3_2012 |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_q3_2012 |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_q3_2012 |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_q3_2012 |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_q3_2012 |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_q4_2012 |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_q4_2012 |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_q4_2012 |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_q4_2012 |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_q4_2012 |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+ sales_others  |      40 | 3000x   | IRELAND  | 01-MAR-13 00:00:00 |  45000
+(18 rows)
+```
+
+EDB Postgres Advanced Server doesn't have a way to reassign the contents of a `MAXVALUE` partition or subpartition.
+
+-   You can't use the `ALTER TABLE… ADD PARTITION` statement to add a partition to a table with a `MAXVALUE` rule. However, you can use the `ALTER TABLE… SPLIT PARTITION` statement to split an existing partition.
+-   You can't use the `ALTER TABLE… ADD SUBPARTITION` statement to add a subpartition to a table with a `MAXVALUE` rule. However, you can split an existing subpartition with the `ALTER TABLE… SPLIT SUBPARTITION` statement.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/index.mdx
new file mode 100644
index 00000000000..22224ea2759
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/index.mdx
@@ -0,0 +1,17 @@
+---
+title: "Handling stray values in a LIST or RANGE partitioned table"
+indexCards: simple
+navigation:
+  - defining_a_default_partition
+  - defining_a_maxvalue_partition
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.118.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.343.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.067.html"
+---
+
+<div id="handling_stray_values_in_a_list_or_range_partitioned_table" class="registered_link"></div>
+
+A `DEFAULT` or `MAXVALUE` partition or subpartition captures any rows that don't meet the other partitioning rules defined for a table.
+
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table.mdx
new file mode 100644
index 00000000000..5c80faa758b
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table.mdx
@@ -0,0 +1,55 @@
+---
+title: "Specifying multiple partitioning keys in a RANGE partitioned table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.119.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.344.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.068.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/06_specifying_multiple_partitioning_keys_in_a_range_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="specifying_multiple_partitioning_keys_in_a_range_partitioned_table" class="registered_link"></div>
+
+You can often improve performance by specifying multiple key columns for a `RANGE` partitioned table. If you often select rows using comparison operators on a small set of columns based on a greater-than or less-than value, consider using those columns in `RANGE` partitioning rules.
+
+Range-partitioned table definitions can include multiple columns in the partitioning key. To specify multiple partitioning keys for a range-partitioned table, include the column names in a comma-separated list after the `PARTITION BY RANGE` clause:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no      number,
+  part_no      varchar2,
+  country      varchar2(20),
+  sale_year    number,
+  sale_month   number,
+  sale_day     number,
+  amount       number
+)
+PARTITION BY RANGE(sale_year, sale_month)
+(
+  PARTITION q1_2012
+    VALUES LESS THAN(2012, 4),
+  PARTITION q2_2012
+    VALUES LESS THAN(2012, 7),
+  PARTITION q3_2012
+    VALUES LESS THAN(2012, 10),
+  PARTITION q4_2012
+    VALUES LESS THAN(2013, 1)
+);
+```
+
+If a table is created with multiple partitioning keys, you must specify multiple key values when querying the table to take full advantage of partition pruning:
+
+```sql
+edb=# EXPLAIN SELECT * FROM sales WHERE sale_year = 2012 AND sale_month = 8;
+__OUTPUT__
+                                QUERY PLAN
+----------------------------------------------------------------------------
+ Append  (cost=0.00..14.35 rows=1 width=250)
+   ->  Seq Scan on sales_q3_2012  (cost=0.00..14.35 rows=1 width=250)
+         Filter: ((sale_year = '2012'::numeric) AND (sale_month = '8'::numeric))
+(3 rows)
+```
+
+Since all rows with a value of `8` in the `sale_month` column and a value of `2012` in the `sale_year` column are stored in the `q3_2012` partition, EDB Postgres Advanced Server searches only that partition.
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/index.mdx
new file mode 100644
index 00000000000..7df3532b769
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/index.mdx
@@ -0,0 +1,52 @@
+---
+title: "Retrieving information about a partitioned table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.120.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.345.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.069.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="retrieving_information_about_a_partitioned_table" class="registered_link"></div>
+
+EDB Postgres Advanced Server provides five system catalog views that you can use to view information about the structure of partitioned tables.
+
+## Querying the partitioning views
+
+You can query the following views to retrieve information about partitioned and subpartitioned tables:
+
+-   `ALL_PART_TABLES`
+-   `ALL_TAB_PARTITIONS`
+-   `ALL_TAB_SUBPARTITIONS`
+-   `ALL_PART_KEY_COLUMNS`
+-   `ALL_SUBPART_KEY_COLUMNS`
+
+The structure of each view is explained in [Table partitioning views reference](../../../reference/application_programmer_reference/01_table_partitioning_views_reference/#table_partitioning_views_reference). If you're using the EDB-PSQL client, you can also learn about the structure of a view by entering:
+
+ `\d <view_name>`
+
+Where `view_name` specifies the name of the table partitioning view.
+
+Querying a view can provide information about the structure of a partitioned or subpartitioned table. For example, this code displays the names of a subpartitioned table:
+
+```sql
+edb=# SELECT subpartition_name, partition_name FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name | partition_name
+-------------------+----------------
+ EUROPE_2011       | EUROPE
+ EUROPE_2012       | EUROPE
+ ASIA_2011         | ASIA
+ ASIA_2012         | ASIA
+ AMERICAS_2011     | AMERICAS
+ AMERICAS_2012     | AMERICAS
+(6 rows)
+```
+
+<div class="toctree" maxdepth="3">
+
+table_partitioning_views_reference
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/index.mdx b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/index.mdx
new file mode 100644
index 00000000000..7f26f50e8a3
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/epas_compat_table_partitioning/index.mdx
@@ -0,0 +1,17 @@
+---
+navTitle: Table partitioning
+title: "Using table partitioning"
+indexCards: simple
+description: "How to take advantage of the table partitioning support in EDB Postgres Advanced Server"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+In a partitioned table, one logically large table is broken into smaller physical pieces. Partitioning can provide several benefits:
+
+-   Query performance can improve dramatically, particularly when most of the heavily accessed rows of the table are in a single partition or a small number of partitions. Partitioning allows you to omit the partition column from the front of an index. This approach reduces index size and makes it more likely that the heavily used parts of the index fit in memory.
+-   When a query or update accesses a large percentage of a single partition, performance might improve. This improvement happens because the server performs a sequential scan of the partition instead of using an index and random-access reads scattered across the whole table.
+-   If you plan the requirement into the partitioning design, you can implement a bulk load or unload by adding or removing partitions. `ALTER TABLE` is far faster than a bulk operation. It also avoids the `VACUUM` overhead caused by a bulk `DELETE`.
+-   You can migrate seldom-used data to less-expensive or slower storage media.
+
+Table partitioning is worthwhile when a table is becoming very large. The exact point at which a table benefits from partitioning depends on the application. A good guideline is for the size of the table not to exceed the physical memory of the database server.
diff --git a/product_docs/docs/epas/16/application_programming/index.mdx b/product_docs/docs/epas/16/application_programming/index.mdx
new file mode 100644
index 00000000000..e4987f9a7cc
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/index.mdx
@@ -0,0 +1,6 @@
+---
+title: "Application programming"
+indexCards: simple
+---
+
+EDB Postgres Advanced Server includes features designed to increase application programmer productivity, such as user-defined objects, autonomous transactions, synonyms, and 200+ prepackaged utility functions. 
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/01_default_optimization_modes.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/01_default_optimization_modes.mdx
new file mode 100644
index 00000000000..27d545f2d7d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/01_default_optimization_modes.mdx
@@ -0,0 +1,86 @@
+---
+title: "Default optimization modes"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.038.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.121.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.130.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/01_default_optimization_modes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="default_optimization_modes" class="registered_link"></div>
+
+You can choose an optimization mode as the default setting for an EDB Postgres Advanced Server database cluster. You can also change this setting on a per-session basis by using the `ALTER SESSION` command as well as in individual `DELETE`, `SELECT`, and `UPDATE` commands in an optimizer hint. The configuration parameter that controls these default modes is `OPTIMIZER_MODE`.
+
+The table shows the possible values.
+
+| Hint              | Description                                                                                                                                                                                                             |
+| ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `ALL_ROWS`        | Optimizes for retrieving all rows of the result set.                                                                                                                                                                  |
+| `CHOOSE`          | Does no default optimization based on assumed number of rows to retrieve from the result set. This is the default.                                                                                                  |
+| `FIRST_ROWS`      | Optimizes for retrieving only the first row of the result set.                                                                                                                                                        |
+| `FIRST_ROWS_10`   | Optimizes for retrieving the first 10 rows of the results set.                                                                                                                                                        |
+| `FIRST_ROWS_100`  | Optimizes for retrieving the first 100 rows of the result set.                                                                                                                                                        |
+| `FIRST_ROWS_1000` | Optimizes for retrieving the first 1000 rows of the result set.                                                                                                                                                       |
+| `FIRST_ROWS(n)`   | Optimizes for retrieving the first *n* rows of the result set. You can't use this form as the object of the `ALTER SESSION SET OPTIMIZER_MODE` command. You can use it only in the form of a hint in a SQL command. |
+
+These optimization modes are based on the assumption that the client submitting the SQL command is interested in viewing only the first *n* rows of the result set and not the remainder of the result set. Resources allocated to the query are adjusted as such.
+
+## Example: Specifying the number of rows to retrieve in the result set
+
+Alter the current session to optimize for retrieval of the first 10 rows of the result set:
+
+```sql
+ALTER SESSION SET OPTIMIZER_MODE = FIRST_ROWS_10;
+```
+
+## Example: Showing the current value of the OPTIMIZER_MODE parameter
+
+You can show the current value of the `OPTIMIZER_MODE` parameter by using the `SHOW` command. This command depends on the utility. In PSQL, use the `SHOW` command as follows:
+
+```sql
+SHOW OPTIMIZER_MODE;
+__OUTPUT__
+optimizer_mode
+-----------------
+ first_rows_10
+(1 row)
+```
+
+The `SHOW` command compatible with Oracle databases has the following syntax:
+
+```sql
+SHOW PARAMETER OPTIMIZER_MODE;
+
+NAME
+--------------------------------------------------
+VALUE
+--------------------------------------------------
+optimizer_mode
+first_rows_10
+```
+
+This example shows an optimization mode used in a `SELECT` command as a hint:
+
+```sql
+SELECT /*+ FIRST_ROWS(7) */ * FROM emp;
+__OUTPUT__
+empno| ename |  job     | mgr  |      hiredate      | sal     | comm  | deptno
+-----+-------+----------+------+--------------------+---------+-------+-------
+7369 | SMITH | CLERK    | 7902 | 17-DEC-80 00:00:00 | 800.00  |       | 20
+7499 | ALLEN | SALESMAN | 7698 | 20-FEB-81 00:00:00 | 1600.00 | 300.00| 30
+7521 | WARD  | SALESMAN | 7698 | 22-FEB-81 00:00:00 | 1250.00 | 500.00| 30
+7566 | JONES | MANAGER  | 7839 | 02-APR-81 00:00:00 | 2975.00 |       | 20
+7654 | MARTIN| SALESMAN | 7698 | 28-SEP-81 00:00:00 | 1250.00 |1400.00| 30
+7698 | BLAKE | MANAGER  | 7839 | 01-MAY-81 00:00:00 | 2850.00 |       | 30
+7782 | CLARK | MANAGER  | 7839 | 09-JUN-81 00:00:00 | 2450.00 |       | 10
+7788 | SCOTT | ANALYST  | 7566 | 19-APR-87 00:00:00 | 3000.00 |       | 20
+7839 | KING  | PRESIDENT|      | 17-NOV-81 00:00:00 | 5000.00 |       | 10
+7844 | TURNER| SALESMAN | 7698 | 08-SEP-81 00:00:00 | 1500.00 | 0.00  | 30
+7876 | ADAMS | CLERK    | 7788 | 23-MAY-87 00:00:00 | 1100.00 |       | 20
+7900 | JAMES | CLERK    | 7698 | 03-DEC-81 00:00:00 |  950.00 |       | 30
+7902 | FORD  | ANALYST  | 7566 | 03-DEC-81 00:00:00 | 3000.00 |       | 20
+7934 | MILLER| CLERK    | 7782 | 23-JAN-82 00:00:00 | 1300.00 |       | 10
+(14 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/02_access_method_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/02_access_method_hints.mdx
new file mode 100644
index 00000000000..73931a3ad2d
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/02_access_method_hints.mdx
@@ -0,0 +1,278 @@
+---
+title: "Access method hints"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.039.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.122.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.131.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/02_access_method_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="access_method_hints" class="registered_link"></div>
+
+The following hints influence how the optimizer accesses relations to create the result set.
+
+| Hint                              | Description                                           |
+| --------------------------------- | ----------------------------------------------------- |
+| `FULL(table)`                     | Perform a full sequential scan on `table`.            |
+| `INDEX(table [ index ] [...])`    | Use `index` on `table` to access the relation.        |
+| `NO_INDEX(table [ index ] [...])` | Don't use `index` on `table` to access the relation. |
+
+In addition, you can use the `ALL_ROWS`, `FIRST_ROWS`, and `FIRST_ROWS(n)` hints.
+
+`INDEX` and `NO_INDEX` hints for the partitioned table internally  expand to include the corresponding inherited child indexes and apply in later processing.
+
+## About the examples
+
+The sample application doesn't have enough data to show the effects of optimizer hints. Thus the remainder of these examples use a banking database created by the `pgbench` application located in the EDB Postgres Advanced Server `bin` subdirectory.
+
+## Example: Create a sample database and tables
+
+The following steps create a database named, `bank` populated by the tables `pgbench_accounts, pgbench_branches, pgbench_tellers`, and `pgbench_history`. The `–s 20` option specifies a scaling factor of 20, which results in the creation of 20 branches. Each branch has 100,000 accounts. The result is a total of 2,000,000 rows in the `pgbench_accounts` table and 20 rows in the `pgbench_branches` table. Ten tellers are assigned to each branch resulting, in a total of 200 rows in the `pgbench_tellers` table.
+
+The following initializes the `pgbench` application in the `bank` database.
+
+```sql
+createdb -U enterprisedb bank
+CREATE DATABASE
+
+pgbench -i -s 20 -U enterprisedb bank
+
+NOTICE:  table "pgbench_history" does not exist, skipping
+NOTICE:  table "pgbench_tellers" does not exist, skipping
+NOTICE:  table "pgbench_accounts" does not exist, skipping
+NOTICE:  table "pgbench_branches" does not exist, skipping
+creating tables...
+100000 of 2000000 tuples (5%) done (elapsed 0.11 s, remaining 2.10 s)
+200000 of 2000000 tuples (10%) done (elapsed 0.22 s, remaining 1.98 s)
+300000 of 2000000 tuples (15%) done (elapsed 0.33 s, remaining 1.84 s)
+400000 of 2000000 tuples (20%) done (elapsed 0.42 s, remaining 1.67 s)
+500000 of 2000000 tuples (25%) done (elapsed 0.52 s, remaining 1.57 s)
+600000 of 2000000 tuples (30%) done (elapsed 0.62 s, remaining 1.45 s)
+700000 of 2000000 tuples (35%) done (elapsed 0.73 s, remaining 1.35 s)
+800000 of 2000000 tuples (40%) done (elapsed 0.87 s, remaining 1.31 s)
+900000 of 2000000 tuples (45%) done (elapsed 0.98 s, remaining 1.19 s)
+1000000 of 2000000 tuples (50%) done (elapsed 1.09 s, remaining 1.09 s)
+1100000 of 2000000 tuples (55%) done (elapsed 1.22 s, remaining 1.00 s)
+1200000 of 2000000 tuples (60%) done (elapsed 1.36 s, remaining 0.91 s)
+1300000 of 2000000 tuples (65%) done (elapsed 1.51 s, remaining 0.82 s)
+1400000 of 2000000 tuples (70%) done (elapsed 1.65 s, remaining 0.71 s)
+1500000 of 2000000 tuples (75%) done (elapsed 1.78 s, remaining 0.59 s)
+1600000 of 2000000 tuples (80%) done (elapsed 1.93 s, remaining 0.48 s)
+1700000 of 2000000 tuples (85%) done (elapsed 2.10 s, remaining 0.37 s)
+1800000 of 2000000 tuples (90%) done (elapsed 2.23 s, remaining 0.25 s)
+1900000 of 2000000 tuples (95%) done (elapsed 2.37 s, remaining 0.12 s)
+2000000 of 2000000 tuples (100%) done (elapsed 2.48 s, remaining 0.00 s)
+vacuum...
+set primary keys...
+done.
+```
+
+A total of 500,00 transactions are then processed. These transactions populate the `pgbench_history` table with 500,000 rows.
+
+```sql
+pgbench -U enterprisedb -t 500000 bank
+
+starting vacuum...end.
+transaction type: <builtin: TPC-B (sort of)>
+scaling factor: 20
+query mode: simple
+number of clients: 1
+number of threads: 1
+number of transactions per client: 500000
+number of transactions actually processed: 500000/500000
+latency average: 0.000 ms
+tps = 1464.338375 (including connections establishing)
+tps = 1464.350357 (excluding connections establishing)
+```
+
+The following are the table definitions:
+
+```sql
+\d pgbench_accounts
+
+   Table "public.pgbench_accounts"
+  Column  |     Type      | Modifiers
+----------+---------------+-----------
+ aid      | integer       | not null
+ bid      | integer       |
+ abalance | integer       |
+ filler   | character(84) |
+Indexes:
+    "pgbench_accounts_pkey" PRIMARY KEY, btree (aid)
+
+\d pgbench_branches
+
+   Table "public.pgbench_branches"
+  Column  |     Type      | Modifiers
+----------+---------------+-----------
+ bid      | integer       | not null
+ bbalance | integer       |
+ filler   | character(88) |
+Indexes:
+    "pgbench_branches_pkey" PRIMARY KEY, btree (bid)
+
+\d pgbench_tellers
+
+   Table "public.pgbench_tellers"
+  Column  |     Type      | Modifiers
+----------+---------------+-----------
+ tid      | integer       | not null
+ bid      | integer       |
+ tbalance | integer       |
+ filler   | character(84) |
+Indexes:
+    "pgbench_tellers_pkey" PRIMARY KEY, btree (tid)
+
+\d pgbench_history
+
+          Table "public.pgbench_history"
+ Column |            Type             | Modifiers
+--------+-----------------------------+-----------
+ tid    | integer                     |
+ bid    | integer                     |
+ aid    | integer                     |
+ delta  | integer                     |
+ mtime  | timestamp without time zone |
+ filler | character(22)               |
+```
+
+The `EXPLAIN` command shows the plan selected by the query planner. In this example, `aid` is the primary key column, so an indexed search is used on index `pgbench_accounts_pkey`:
+
+```sql
+EXPLAIN SELECT * FROM pgbench_accounts WHERE aid = 100;
+
+                                       QUERY PLAN
+-----------------------------------------------------------------------------
+------------------
+Index Scan using pgbench_accounts_pkey on pgbench_accounts  (cost=0.43..8.45
+rows=1 width=97)
+   Index Cond: (aid = 100)
+(2 rows)
+```
+
+## Example: FULL hint 
+
+The `FULL` hint forces a full sequential scan instead of using the index:
+
+```sql
+EXPLAIN SELECT /*+ FULL(pgbench_accounts) */ * FROM pgbench_accounts WHERE
+aid = 100;
+
+                          QUERY PLAN
+---------------------------------------------------------------------
+Seq Scan on pgbench_accounts  (cost=0.00..58781.69 rows=1 width=97)
+  Filter: (aid = 100)
+(2 rows)
+```
+
+## Example: NO_INDEX hint
+
+The `NO_INDEX` hint forces a parallel sequential scan instead of using the index:
+
+```sql
+EXPLAIN SELECT /*+ NO_INDEX(pgbench_accounts pgbench_accounts_pkey) */ *
+FROM pgbench_accounts WHERE aid = 100;
+
+                                  QUERY PLAN
+-----------------------------------------------------------------------------
+-------
+ Gather  (cost=1000.00..45094.80 rows=1 width=97)
+   Workers Planned: 2
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..44094.70 rows=1
+   width=97)
+           Filter: (aid = 100)
+(4 rows)
+```
+
+## Example: Tracing optimizer hints
+
+You can obtain more detailed information than the `EXPLAIN` command provides about whether the planner used a hint. To do so, set the `trace_hints` configuration parameter as follows:
+
+```sql
+SET trace_hints TO on;
+```
+
+The `SELECT` command with the `NO_INDEX` hint shows the additional information produced when you set the `trace_hints` configuration parameters:
+
+```sql
+EXPLAIN SELECT /*+ NO_INDEX(pgbench_accounts pgbench_accounts_pkey) */ *
+FROM pgbench_accounts WHERE aid = 100;
+
+INFO:  [HINTS] Index Scan of [pgbench_accounts].[pgbench_accounts_pkey]
+rejected due to NO_INDEX hint.
+                                  QUERY PLAN
+-----------------------------------------------------------------------------
+-------
+ Gather  (cost=1000.00..45094.80 rows=1 width=97)
+   Workers Planned: 2
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..44094.70 rows=1
+width=97)
+         Filter: (aid = 100)
+(4 rows)
+```
+
+## Example: Hint ignored
+
+If a hint is ignored, the `INFO: [HINTS]` line doesn't appear. This might indicate a syntax error or some other misspelling in the hint. In this example, the index name is misspelled.
+
+```sql
+EXPLAIN SELECT /*+ NO_INDEX(pgbench_accounts pgbench_accounts_xxx) */ * FROM
+pgbench_accounts WHERE aid = 100;
+
+                                       QUERY PLAN
+-----------------------------------------------------------------------------
+------------------
+Index Scan using pgbench_accounts_pkey on pgbench_accounts  (cost=0.43..8.45
+rows=1 width=97)
+   Index Cond: (aid = 100)
+(2 rows)
+```
+
+## Example: INDEX hint for the partitioned table
+
+
+```sql 
+CREATE TABLE t_1384(col1 int, col2 int, col3 int) 
+PARTITION BY RANGE(col1)
+(PARTITION p1 VALUES LESS THAN(500),
+PARTITION p2 VALUES LESS THAN(1000));
+    
+ALTER TABLE t_1384 ADD PRIMARY KEY(col1);
+    
+CREATE INDEX idx1 ON t_1384(col2);
+ 
+CREATE INDEX idx2 ON t_1384(col1, col2);
+ 
+SET enable_hints = true;
+    
+SET trace_hints TO on;
+ 
+-- Use primary index
+EXPLAIN (COSTS OFF) SELECT /*+ INDEX(s t_1384_pkey) */ * FROM t_1384 s
+WHERE col2 = 10;
+
+INFO:  [HINTS] SeqScan of [s] rejected due to INDEX hint.
+INFO:  [HINTS] Parallel SeqScan of [s] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p1_col1_col2_idx] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p1_col2_idx] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p1_pkey] accepted.
+INFO:  [HINTS] SeqScan of [s] rejected due to INDEX hint.
+INFO:  [HINTS] Parallel SeqScan of [s] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p2_col1_col2_idx] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p2_col2_idx] rejected due to INDEX hint.
+INFO:  [HINTS] Index Scan of [s].[t_1384_p2_pkey] accepted.
+                 QUERY PLAN                      
+-----------------------------------------------------
+Append
+  ->  Bitmap Heap Scan on t_1384_p1 s_1
+        Recheck Cond: (col2 = 10)
+        ->  Bitmap Index Scan on t_1384_p1_col2_idx
+            Index Cond: (col2 = 10)
+  ->  Bitmap Heap Scan on t_1384_p2 s_2
+        Recheck Cond: (col2 = 10)
+        ->  Bitmap Index Scan on t_1384_p2_col2_idx
+            Index Cond: (col2 = 10)
+(9 rows)
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/03_specifying_a_join_order.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/03_specifying_a_join_order.mdx
new file mode 100644
index 00000000000..450983aa89a
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/03_specifying_a_join_order.mdx
@@ -0,0 +1,37 @@
+---
+title: "Specifying a join order"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.040.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.123.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.132.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/03_specifying_a_join_order/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="specifying_a_join_order" class="registered_link"></div>
+
+Include the `ORDERED` directive to instruct the query optimizer to join tables in the order in which they're listed in the `FROM` clause. If you don't include the `ORDERED` keyword, the query optimizer chooses the order in which to join the tables.
+
+For example, the following command allows the optimizer to choose the order in which to join the tables listed in the `FROM` clause:
+
+```sql
+SELECT e.ename, d.dname, h.startdate
+  FROM emp e, dept d, jobhist h
+  WHERE d.deptno = e.deptno
+  AND h.empno = e.empno;
+```
+
+The following command instructs the optimizer to join the tables in the order specified:
+
+```sql
+SELECT /*+ ORDERED */ e.ename, d.dname, h.startdate
+  FROM emp e, dept d, jobhist h
+  WHERE d.deptno = e.deptno
+  AND h.empno = e.empno;
+```
+
+In the `ORDERED` version of the command, EDB Postgres Advanced Server first joins `emp e` with `dept d` before joining the results with `jobhist h`. Without the `ORDERED` directive, the query optimizer selects the join order.
+
+!!! Note
+    The `ORDERED` directive doesn't work for Oracle-style outer joins (joins that contain a + sign).
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/04_joining_relations_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/04_joining_relations_hints.mdx
new file mode 100644
index 00000000000..b58494af652
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/04_joining_relations_hints.mdx
@@ -0,0 +1,140 @@
+---
+title: "Joining relations hints"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.041.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.124.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.133.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/04_joining_relations_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="joining_relations_hints" class="registered_link"></div>
+
+When you join two tables, you can use any of three plans to perform the join.
+
+-   **Nested loop join** &mdash; A table is scanned once for every row in the other joined table.
+-   **Merge sort join** &mdash; Each table is sorted on the join attributes before the join starts. The two tables are then scanned in parallel, and the matching rows are combined to form the join rows.
+-   **Hash join** &mdash; A table is scanned and its join attributes are loaded into a hash table using its join attributes as hash keys. The other joined table is then scanned and its join attributes are used as hash keys to locate the matching rows from the first table.
+
+## List of optimizer hints for join plans
+
+The following table lists the optimizer hints that you can use to influence the planner to use one type of join plan over another.
+
+| Hint                        | Description                                |
+| --------------------------- | ------------------------------------------ |
+| `USE_HASH(table [...])`     | Use a hash join for `table`.               |
+| `NO_USE_HASH(table [...])`  | Don't use a hash join for `table`.        |
+| `USE_MERGE(table [...])`    | Use a merge sort join for `table`.         |
+| `NO_USE_MERGE(table [...])` | Don't use a merge sort join for `table`.  |
+| `USE_NL(table [...])`       | Use a nested loop join for `table`.        |
+| `NO_USE_NL(table [...])`    | Don't use a nested loop join for `table`. |
+
+## Example: Hash join
+
+In this example, the `USE_HASH` hint is used for a join on the `pgbench_branches` and `pgbench_accounts` tables. The query plan shows that a hash join is used by creating a hash table from the join attribute of the `pgbench_branches` table:
+
+```sql
+EXPLAIN SELECT /*+ USE_HASH(b) */ b.bid, a.aid, abalance FROM
+pgbench_branches b, pgbench_accounts a WHERE b.bid = a.bid;
+__OUTPUT__
+                                 QUERY PLAN
+-----------------------------------------------------------------------------
+------
+  Hash Join  (cost=21.45..81463.06 rows=2014215 width=12)
+    Hash Cond: (a.bid = b.bid)
+    ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=12)
+    ->  Hash  (cost=21.20..21.20 rows=20 width=4)
+         ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+(5 rows)
+```
+
+Next, the `NO_USE_HASH(a b)` hint forces the planner to use an approach other than hash tables. The result is a merge join.
+
+```sql
+EXPLAIN SELECT /*+ NO_USE_HASH(a b) */ b.bid, a.aid, abalance FROM
+pgbench_branches b, pgbench_accounts a WHERE b.bid = a.bid;
+__OUTPUT__
+                                       QUERY PLAN
+-----------------------------------------------------------------------------
+------------------
+  Merge Join  (cost=333526.08..368774.94 rows=2014215 width=12)
+    Merge Cond: (b.bid = a.bid)
+    ->  Sort  (cost=21.63..21.68 rows=20 width=4)
+          Sort Key: b.bid
+          ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+    ->  Materialize  (cost=333504.45..343575.53 rows=2014215 width=12)
+          ->  Sort  (cost=333504.45..338539.99 rows=2014215 width=12)
+                Sort Key: a.bid
+                ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=12)
+(9 rows)
+```
+
+Finally, the `USE_MERGE` hint forces the planner to use a merge join:
+
+```sql
+EXPLAIN SELECT /*+ USE_MERGE(a) */ b.bid, a.aid, abalance FROM
+pgbench_branches b, pgbench_accounts a WHERE b.bid = a.bid;
+__OUTPUT__
+                                       QUERY PLAN
+-----------------------------------------------------------------------------
+------------------
+  Merge Join  (cost=333526.08..368774.94 rows=2014215 width=12)
+    Merge Cond: (b.bid = a.bid)
+    ->  Sort  (cost=21.63..21.68 rows=20 width=4)
+          Sort Key: b.bid
+          ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+    ->  Materialize  (cost=333504.45..343575.53 rows=2014215 width=12)
+          ->  Sort  (cost=333504.45..338539.99 rows=2014215 width=12)
+                Sort Key: a.bid
+                ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=12)
+(9 rows)
+```
+
+## Example: Three-table join
+
+In this three-table join example, the planner first performs a hash join on the `pgbench_branches` and `pgbench_history` tables. Then it performs a hash join of the result with the `pgbench_accounts` table.
+
+```sql
+EXPLAIN SELECT h.mtime, h.delta, b.bid, a.aid FROM pgbench_history h, pgbench_branches b, 
+pgbench_accounts a WHERE h.bid = b.bid AND h.aid = a.aid;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+-----------
+ Hash Join  (cost=86814.29..123103.29 rows=500000 width=20)
+  Hash Cond: (h.aid = a.aid)
+  ->  Hash Join  (cost=21.45..15081.45 rows=500000 width=20)
+        Hash Cond: (h.bid = b.bid)
+        ->  Seq Scan on pgbench_history h  (cost=0.00..8185.00 rows=500000 width=20)
+        ->  Hash  (cost=21.20..21.20 rows=20 width=4)
+             ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+  ->  Hash  (cost=53746.15..53746.15 rows=2014215 width=4)
+        ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=4)
+(9 rows)
+```
+
+This plan is altered by using hints to force a combination of a merge sort join and a hash join:
+
+```sql
+EXPLAIN SELECT /*+ USE_MERGE(h b) USE_HASH(a) */ h.mtime, h.delta, b.bid, a.aid FROM 
+pgbench_history h, pgbench_branches b, pgbench_accounts a WHERE h.bid = b.bid AND h.aid = a.aid;
+__OUTPUT__
+                                         QUERY PLAN
+-----------------------------------------------------------------------------
+---------------------
+ Hash Join  (cost=152583.39..182562.49 rows=500000 width=20)
+   Hash Cond: (h.aid = a.aid)
+   ->  Merge Join  (cost=65790.55..74540.65 rows=500000 width=20)
+         Merge Cond: (b.bid = h.bid)
+         ->  Sort  (cost=21.63..21.68 rows=20 width=4)
+               Sort Key: b.bid
+               ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+         ->  Materialize  (cost=65768.92..68268.92 rows=500000 width=20)
+               ->  Sort  (cost=65768.92..67018.92 rows=500000 width=20)
+                     Sort Key: h.bid
+                     ->  Seq Scan on pgbench_history h  (cost=0.00..8185.00 rows=500000 width=20)
+   ->  Hash  (cost=53746.15..53746.15 rows=2014215 width=4)
+         ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=4)
+(13 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/05_global_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/05_global_hints.mdx
new file mode 100644
index 00000000000..8ccd89c0269
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/05_global_hints.mdx
@@ -0,0 +1,150 @@
+---
+title: "Global hints"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.042.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.125.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.134.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/05_global_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="global_hints" class="registered_link"></div>
+
+In addition to applying hints directly to tables that are referenced in the SQL command, you can apply hints to tables that appear in a view when the view is referenced in the SQL command. The hint doesn't appear in the view but in the SQL command that references the view.
+
+When specifying a hint that applies to a table in a view, give the view and table names in dot notation in the hint argument list.
+
+## Synopsis
+
+```sql
+<hint>(<view>.<table>)
+```
+
+## Parameters
+
+`hint`
+
+  Any of the hints in the table [Access method hints](02_access_method_hints/#access_method_hints), [Joining relations hints](04_joining_relations_hints/#joining_relations_hints).
+
+`view`
+
+  The name of the view containing `table`.
+
+`table`
+
+  The table on which to apply the hint.
+
+## Example: Applying hints to a stored view
+
+A view named `tx` is created from the three-table join of `pgbench_history`, `pgbench_branches`, and `pgbench_accounts`, shown in the last example of [Joining relations hints](04_joining_relations_hints/#joining_relations_hints).
+
+```sql
+CREATE VIEW tx AS SELECT h.mtime, h.delta, b.bid, a.aid FROM pgbench_history
+h, pgbench_branches b, pgbench_accounts a WHERE h.bid = b.bid AND h.aid =
+a.aid;
+```
+
+The query plan produced by selecting from this view is:
+
+```sql
+EXPLAIN SELECT * FROM tx;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+-----------
+ Hash Join  (cost=86814.29..123103.29 rows=500000 width=20)
+   Hash Cond: (h.aid = a.aid)
+   ->  Hash Join  (cost=21.45..15081.45 rows=500000 width=20)
+         Hash Cond: (h.bid = b.bid)
+         ->  Seq Scan on pgbench_history h  (cost=0.00..8185.00 rows=500000 width=20)
+         ->  Hash  (cost=21.20..21.20 rows=20 width=4)
+               ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+   ->  Hash  (cost=53746.15..53746.15 rows=2014215 width=4)
+         ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=4)
+(9 rows)
+```
+
+The same hints that were applied to this join at the end of [Joining relations hints](04_joining_relations_hints/#joining_relations_hints) can be applied to the view:
+
+```sql
+EXPLAIN SELECT /*+ USE_MERGE(tx.h tx.b) USE_HASH(tx.a) */ * FROM tx;
+__OUTPUT__
+                                         QUERY PLAN
+-----------------------------------------------------------------------------
+---------------------
+ Hash Join  (cost=152583.39..182562.49 rows=500000 width=20)
+   Hash Cond: (h.aid = a.aid)
+   ->  Merge Join  (cost=65790.55..74540.65 rows=500000 width=20)
+         Merge Cond: (b.bid = h.bid)
+         ->  Sort  (cost=21.63..21.68 rows=20 width=4)
+               Sort Key: b.bid
+               ->  Seq Scan on pgbench_branches b  (cost=0.00..21.20 rows=20 width=4)
+         ->  Materialize  (cost=65768.92..68268.92 rows=500000 width=20)
+               ->  Sort  (cost=65768.92..67018.92 rows=500000 width=20)
+                     Sort Key: h.bid
+                     ->  Seq Scan on pgbench_history h  (cost=0.00..8185.00 rows=500000 width=20)
+   ->  Hash  (cost=53746.15..53746.15 rows=2014215 width=4)
+         ->  Seq Scan on pgbench_accounts a  (cost=0.00..53746.15 rows=2014215 width=4)
+(13 rows)
+```
+
+## Applying hints to tables in subqueries
+
+In addition to applying hints to tables in stored views, you can apply hints to tables in subqueries. In this query on the sample application `emp` table, employees and their managers are listed by joining the `emp` table with a subquery of the `emp` table identified by the alias `b`:
+
+```sql
+SELECT a.empno, a.ename, b.empno "mgr empno", b.ename "mgr ename" FROM emp a, 
+(SELECT * FROM emp) b WHERE a.mgr = b.empno;
+__OUTPUT__
+ empno | ename  | mgr empno | mgr ename
+-------+--------+-----------+-----------
+  7369 | SMITH  |      7902 | FORD
+  7499 | ALLEN  |      7698 | BLAKE
+  7521 | WARD   |      7698 | BLAKE
+  7566 | JONES  |      7839 | KING
+  7654 | MARTIN |      7698 | BLAKE
+  7698 | BLAKE  |      7839 | KING
+  7782 | CLARK  |      7839 | KING
+  7788 | SCOTT  |      7566 | JONES
+  7844 | TURNER |      7698 | BLAKE
+  7876 | ADAMS  |      7788 | SCOTT
+  7900 | JAMES  |      7698 | BLAKE
+  7902 | FORD   |      7566 | JONES
+  7934 | MILLER |      7782 | CLARK
+(13 rows)
+```
+
+This code shows the plan chosen by the query planner:
+
+```sql
+EXPLAIN SELECT a.empno, a.ename, b.empno "mgr empno", b.ename "mgr ename"
+FROM emp a, (SELECT * FROM emp) b WHERE a.mgr = b.empno;
+__OUTPUT__
+                        QUERY PLAN
+-----------------------------------------------------------------
+ Hash Join  (cost=1.32..2.64 rows=13 width=22)
+   Hash Cond: (a.mgr = emp.empno)
+   ->  Seq Scan on emp a  (cost=0.00..1.14 rows=14 width=16)
+   ->  Hash  (cost=1.14..1.14 rows=14 width=11)
+         ->  Seq Scan on emp  (cost=0.00..1.14 rows=14 width=11)
+(5 rows)
+```
+
+You can apply a hint to the `emp` table in the subquery to perform an index scan on index `emp_pk` instead of a table scan. Note the difference in the query plans.
+
+```sql
+EXPLAIN SELECT /*+ INDEX(b.emp emp_pk) */ a.empno, a.ename, b.empno "mgr
+empno", b.ename "mgr ename" FROM emp a, (SELECT * FROM emp) b WHERE a.mgr =
+b.empno;
+__OUTPUT__
+                             QUERY PLAN
+---------------------------------------------------------------------------
+  Merge Join  (cost=4.17..13.11 rows=13 width=22)
+    Merge Cond: (a.mgr = emp.empno)
+    ->  Sort  (cost=1.41..1.44 rows=14 width=16)
+          Sort Key: a.mgr
+          ->  Seq Scan on emp a  (cost=0.00..1.14 rows=14 width=16)
+    ->  Index Scan using emp_pk on emp  (cost=0.14..12.35 rows=14 width=11)
+(6 rows)
+```
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/06_using_the_append_optimizer_hint.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/06_using_the_append_optimizer_hint.mdx
new file mode 100644
index 00000000000..c7da61ab619
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/06_using_the_append_optimizer_hint.mdx
@@ -0,0 +1,42 @@
+---
+title: "APPEND optimizer hint"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.043.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.126.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.135.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/06_using_the_append_optimizer_hint/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_the_append_optimizer_hint" class="registered_link"></div>
+
+By default, EDB Postgres Advanced Server adds new data into the first available free space in a table vacated by vacuumed records. Include the `APPEND` directive after an `INSERT` or `SELECT` command to bypass midtable free space and affix new rows to the end of the table. This optimizer hint can be particularly useful when bulk loading data.
+
+The syntax is:
+
+```sql
+/*+APPEND*/
+```
+
+For example, the following command, compatible with Oracle databases, instructs the server to append the data in the `INSERT` statement to the end of the `sales` table:
+
+```sql
+INSERT /*+APPEND*/ INTO sales VALUES
+(10, 10, '01-Mar-2011', 10, 'OR');
+```
+
+EDB Postgres Advanced Server supports the `APPEND` hint when adding multiple rows in a single `INSERT` statement:
+
+```sql
+INSERT /*+APPEND*/ INTO sales VALUES
+(20, 20, '01-Aug-2011', 20, 'NY'),
+(30, 30, '01-Feb-2011', 30, 'FL'),
+(40, 40, '01-Nov-2011', 40, 'TX');
+```
+
+You can also include the `APPEND` hint in the `SELECT` clause of an `INSERT INTO` statement:
+
+```sql
+INSERT INTO sales_history SELECT /*+APPEND*/ FROM sales;
+```
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/07_parallelism_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/07_parallelism_hints.mdx
new file mode 100644
index 00000000000..81c081016b5
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/07_parallelism_hints.mdx
@@ -0,0 +1,210 @@
+---
+title: "Parallelism hints"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.044.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/07_parallelism_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="parallelism_hints" class="registered_link"></div>
+
+*Parallel scanning* is the use of multiple background workers to simultaneously perform a scan of a table, that is, in parallel, for a given query. This process provides performance improvement over other methods such as the sequential scan.
+
+- The `PARALLEL` optimizer hint forces parallel scanning.
+- The `NO_PARALLEL` optimizer hint prevents use of a parallel scan.
+
+## Synopsis
+
+```sql
+PARALLEL (<table> [ <parallel_degree> | DEFAULT ])
+
+NO_PARALLEL (<table>)
+```
+
+## Parameters
+
+`table`
+
+  The table to which to apply the parallel hint.
+
+`parallel_degree | DEFAULT`
+
+  `parallel_degree` is a positive integer that specifies the desired number of workers to use for a parallel scan. If specified, the lesser of `parallel_degree` and configuration parameter `max_parallel_workers_per_gather` is used as the planned number of workers. For information on the `max_parallel_workers_per_gather` parameter, see *Asynchronous Behavior* under *Resource Consumption* in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/runtime-config-resource.html).
+
+  - If you specify `DEFAULT`, then the maximum possible parallel degree is used.
+  - If you omit both `parallel_degree` and `DEFAULT`, then the query optimizer determines the parallel degree. In this case, if `table` was set with the `parallel_workers` storage parameter, then this value is used as the parallel degree. Otherwise, the optimizer uses the maximum possible parallel degree as if `DEFAULT` were specified. For information on the `parallel_workers` storage parameter, see `Storage Parameters` under `CREATE TABLE` in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createtable.html).
+
+  Regardless of the circumstance, the parallel degree never exceeds the setting of configuration parameter `max_parallel_workers_per_gather`.
+
+## About the examples
+
+For these exammples, the following configuration parameter settings are in effect:
+
+```sql
+SHOW max_worker_processes;
+__OUTPUT__
+ max_worker_processes
+----------------------
+ 8
+(1 row)
+```
+```sql
+SHOW max_parallel_workers_per_gather;
+__OUTPUT__
+ max_parallel_workers_per_gather
+---------------------------------
+ 2
+(1 row)
+```
+
+## Example: Default scan
+
+This example shows the default scan on table `pgbench_accounts`. A sequential scan is shown in the query plan.
+
+```sql
+SET trace_hints TO on;
+
+EXPLAIN SELECT * FROM pgbench_accounts;
+__OUTPUT__
+                             QUERY PLAN
+---------------------------------------------------------------------------
+ Seq Scan on pgbench_accounts  (cost=0.00..53746.15 rows=2014215 width=97)
+(1 row)
+```
+
+## Example: PARALLEL hint
+
+This example uses the `PARALLEL` hint. In the query plan, the Gather node, which launches the background workers, indicates the plan to use two workers:
+
+!!! Note
+    If `trace_hints` is set to `on`, the `INFO: [HINTS]` lines appear stating that `PARALLEL` was accepted for `pgbench_accounts` and other hint information. For the remaining examples, these lines aren't displayed as they generally show the same output, that is, `trace_hints` was reset to `off`.
+
+```sql
+EXPLAIN SELECT /*+ PARALLEL(pgbench_accounts) */ * FROM pgbench_accounts;
+__OUTPUT__
+INFO:  [HINTS] SeqScan of [pgbench_accounts] rejected due to PARALLEL hint.
+INFO:  [HINTS] PARALLEL on [pgbench_accounts] accepted.
+INFO:  [HINTS] Index Scan of [pgbench_accounts].[pgbench_accounts_pkey]
+rejected due to PARALLEL hint.
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+------------
+ Gather  (cost=1000.00..244418.06 rows=2014215 width=97)
+   Workers Planned: 2
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..41996.56 rows=839256 width=97)
+(3 rows)
+```
+
+Now, the `max_parallel_workers_per_gather` setting is increased:
+
+```sql
+SET max_parallel_workers_per_gather TO 6;
+
+SHOW max_parallel_workers_per_gather;
+__OUTPUT__
+ max_parallel_workers_per_gather
+---------------------------------
+ 6
+(1 row)
+```
+
+The same query on `pgbench_accounts` is issued again with no parallel degree specification in the `PARALLEL` hint. The number of planned workers has increased to 4, as determined by the optimizer.
+
+```sql
+EXPLAIN SELECT /*+ PARALLEL(pgbench_accounts) */ * FROM pgbench_accounts;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+------------
+ Gather  (cost=1000.00..241061.04 rows=2014215 width=97)
+   Workers Planned: 4
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..38639.54 rows=503554 width=97)
+(3 rows)
+```
+
+Now, a value of `6` is specified for the parallel degree parameter of the `PARALLEL` hint. The planned number of workers is returned as this specified value:
+
+```sql
+EXPLAIN SELECT /*+ PARALLEL(pgbench_accounts 6) */ * FROM pgbench_accounts;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+------------
+ Gather  (cost=1000.00..239382.52 rows=2014215 width=97)
+   Workers Planned: 6
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..36961.03 rows=335702 width=97)
+(3 rows)
+```
+
+The same query is now issued with the `DEFAULT` setting for the parallel degree. The results indicate that the maximum allowable number of workers is planned.
+
+```sql
+EXPLAIN SELECT /*+ PARALLEL(pgbench_accounts DEFAULT) */ * FROM
+pgbench_accounts;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+------------
+ Gather  (cost=1000.00..239382.52 rows=2014215 width=97)
+   Workers Planned: 6
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..36961.03 rows=335702 width=97)
+(3 rows)
+```
+
+Table `pgbench_accounts` is now altered so that the `parallel_workers` storage parameter is set to `3`.
+
+!!! Note
+    This format of the `ALTER TABLE` command to set the `parallel_workers` parameter isn't compatible with Oracle databases.
+
+The `parallel_workers` setting is shown by the PSQL `\d+` command.
+
+```sql
+ALTER TABLE pgbench_accounts SET (parallel_workers=3);
+__OUTPUT__
+\d+ pgbench_accounts
+                    Table "public.pgbench_accounts"
+ Column  |     Type      | Modifiers | Storage  | Stats target | Description
+---------+---------------+-----------+----------+--------------+------------
+-
+ aid     | integer       | not null  | plain    |              |
+ bid     | integer       |           | plain    |              |
+ abalance| integer       |           | plain    |              |
+ filler  | character(84) |           | extended |              |
+Indexes:
+    "pgbench_accounts_pkey" PRIMARY KEY, btree (aid)
+Options: fillfactor=100, parallel_workers=3
+```
+
+## Example: PARALLEL hint is given with no parallel degree
+
+When the `PARALLEL` hint is given with no parallel degree, the resulting number of planned workers is the value from the `parallel_workers` parameter:
+
+```sql
+EXPLAIN SELECT /*+ PARALLEL(pgbench_accounts) */ * FROM pgbench_accounts;
+__OUTPUT__
+                                    QUERY PLAN
+-----------------------------------------------------------------------------
+------------
+ Gather  (cost=1000.00..242522.97 rows=2014215 width=97)
+   Workers Planned: 3
+   ->  Parallel Seq Scan on pgbench_accounts  (cost=0.00..40101.47 rows=649747 width=97)
+(3 rows)
+```
+
+Specifying a parallel degree value or `DEFAULT` in the `PARALLEL` hint overrides the `parallel_workers` setting.
+
+## Example: NO_PARALLEL hint
+
+This example shows the `NO_PARALLEL` hint. With `trace_hints` set to `on`, the `INFO: [HINTS]` message states that the parallel scan was rejected due to the `NO_PARALLEL` hint.
+
+```sql
+EXPLAIN SELECT /*+ NO_PARALLEL(pgbench_accounts) */ * FROM pgbench_accounts;
+__OUTPUT__
+INFO:  [HINTS] Parallel SeqScan of [pgbench_accounts] rejected due to
+NO_PARALLEL hint.
+                             QUERY PLAN
+---------------------------------------------------------------------------
+ Seq Scan on pgbench_accounts  (cost=0.00..53746.15 rows=2014215 width=97)
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/08_conflicting_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/08_conflicting_hints.mdx
new file mode 100644
index 00000000000..4db494f2725
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/08_conflicting_hints.mdx
@@ -0,0 +1,25 @@
+---
+title: "Conflicting hints"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.045.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.127.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.136.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/08_conflicting_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="conflicting_hints" class="registered_link"></div>
+
+If a command includes two or more conflicting hints, the server ignores the contradicting hints. The following table lists hints that contradict each other.
+
+| Hint                         | Conflicting hint                                                                         |
+| ---------------------------- | ---------------------------------------------------------------------------------------- |
+| `ALL_ROWS`                   | `FIRST_ROWS` - all formats                                                               |
+| `FULL(table)`                | `INDEX(table [ index ])`<br /><br />`PARALLEL(table [ degree ])`                         |
+| `INDEX(table)`               | `FULL(table)`<br /><br />`NO_INDEX(table)`<br /><br />`PARALLEL(table [ degree ])`       |
+| `INDEX(table index)`         | `FULL(table)`<br /><br />`NO_INDEX(table index)`<br /><br />`PARALLEL(table [ degree ])` |
+| `PARALLEL(table [ degree ])` | `FULL(table)`<br /><br />`INDEX(table)`<br /><br />`NO_PARALLEL(table)`                  |
+| `USE_HASH(table)`            | `NO_USE_HASH(table)`                                                                     |
+| `USE_MERGE(table)`           | `NO_USE_MERGE(table)`                                                                    |
+| `USE_NL(table)`              | `NO_USE_NL(table)`                                                                       |
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx
new file mode 100644
index 00000000000..0fd018abed8
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/about_optimizer_hints.mdx
@@ -0,0 +1,52 @@
+---
+title: "About optimizer hints"
+---
+
+An *optimizer hint* is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set.
+
+## Synopsis
+
+```sql
+{ DELETE | INSERT | SELECT | UPDATE } /*+ { <hint> [ <comment> ] } [...] */
+  <statement_body>
+
+{ DELETE | INSERT | SELECT | UPDATE } --+ { <hint> [ <comment> ] } [...]
+  <statement_body>
+```
+
+ In both forms, a plus sign (+) must immediately follow the `/*` or `--` opening comment symbols, with no intervening space. Otherwise the server doesn't interpret the tokens that follow as hints.
+
+If you're using the first form, the hint and optional comment might span multiple lines. In the second form, all hints and comments must occupy a single line. The rest of the statement must start on a new line.
+
+## Description
+
+Note:
+
+-   The database server always tries to use the specified hints if at all possible.
+-   If a planner method parameter is set so as to disable a certain plan type, then this plan isn't used even if it's specified in a hint, unless there are no other possible options for the planner. Examples of planner method parameters are `enable_indexscan`, `enable_seqscan`, `enable_hashjoin`, `enable_mergejoin`, and `enable_nestloop`. These are all Boolean parameters.
+-   The hint is embedded in a comment. As a consequence, if the hint is misspelled or if any parameter to a hint, such as view, table, or column name, is misspelled or nonexistent in the SQL command, there's no indication that an error occurred. No syntax error is given. The entire hint is silently ignored.
+-   If an alias is used for a table name in the SQL command, then you must use the alias name in the hint, not the original table name. For example, in the command `SELECT /*+ FULL(acct) */ * FROM accounts acct ..., acct`, you must specify the alias for `accounts` in the `FULL` hint, not in the table name `accounts`.
+
+Use the `EXPLAIN` command to ensure that the hint is correctly formed and the planner is using the hint. 
+
+In general, don't use optimizer hints in a production application, where table data changes throughout the life of the application. By ensuring that dynamic columns are analyzed frequently via the `ANALYZE` command, the column statistics are updated to reflect value changes. The planner uses such information to produce the lowest-cost plan for any given command execution. Use of optimizer hints defeats the purpose of this process and results in the same plan regardless of how the table data changes.
+
+## Parameters
+
+`hint`
+
+  An optimizer hint directive.
+
+`comment`
+
+  A string with additional information. Comments have restrictions as to what characters you can include. Generally, `comment` can consist only of alphabetic, numeric, the underscore, dollar sign, number sign, and space characters. These must also conform to the syntax of an identifier. Any subsequent hint is ignored if the comment isn't in this form.
+
+`statement_body`
+
+  The remainder of the `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command.
+
+<div class="toctree" maxdepth="3">
+
+default_optimization_modes access_method_hints specifying_a_join_order joining_relations_hints global_hints using_the_append_optimizer_hint parallelism_hints conflicting_hints
+
+</div>
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/index.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/index.mdx
new file mode 100644
index 00000000000..a16f5829369
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/05_optimizer_hints/index.mdx
@@ -0,0 +1,32 @@
+---
+title: "Using optimizer hints"
+description: "Describes how to generate and use optimizer hints"
+indexCards: simple
+navigation:
+- about_optimizer_hints
+- 01_default_optimization_modes
+- 02_access_method_hints
+- 03_specifying_a_join_order
+- 04_joining_relations_hints
+- 05_global_hints
+- 06_using_the_append_optimizer_hint
+- 07_parallelism_hints
+- 08_conflicting_hints
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.037.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.120.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/05_optimizer_hints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="optimizer_hints" class="registered_link"></div>
+
+When you invoke a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command, the server generates a set of execution plans. After analyzing those execution plans, the server selects a plan that generally returns the result set in the least amount of time. The server's choice of plan depends on several factors:
+
+-   The estimated execution cost of data handling operations
+-   Parameter values assigned to parameters in the `Query Tuning` section of the `postgresql.conf` file
+-   Column statistics that were gathered by the ANALYZE command
+
+As a rule, the query planner selects the least expensive plan. You can use an *optimizer hint* to influence the server as it selects a query plan. 
+
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/index.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/index.mdx
new file mode 100644
index 00000000000..6226b7fe76f
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Optimizing code"
+description: "Describes using EDB Postgres Advanced Server features to optimize database performance"
+indexCards: simple
+redirects:
+  - /epas/latest/application_programming/optimizing_code/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server includes features designed to help application programmers address database performance problems. SQL Profiler helps you locate and optimize poorly running SQL code. You can use optimizer hints to influence the server as it selects a query plan when you invoke a DELETE, INSERT, SELECT, or UPDATE command. 
diff --git a/product_docs/docs/epas/16/application_programming/optimizing_code/optimizing_code.mdx b/product_docs/docs/epas/16/application_programming/optimizing_code/optimizing_code.mdx
new file mode 100644
index 00000000000..de6fcf6d57a
--- /dev/null
+++ b/product_docs/docs/epas/16/application_programming/optimizing_code/optimizing_code.mdx
@@ -0,0 +1,8 @@
+---
+title: "Optimizing inefficient SQL code"
+description: "Describes the benefits of using the SQL Profiler utility to optimize code"
+---
+
+Inefficient SQL code is a leading cause of database performance problems. The challenge for database administrators and developers is locating and then optimizing this code in large, complex systems.
+
+See [SQL Profiler](../../managing_performance/03_sql_profiler/) to see how the utility can help you locate and optimize poorly running SQL code.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx
new file mode 100644
index 00000000000..58c24e2d638
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/01_setting_new_parameters.mdx
@@ -0,0 +1,174 @@
+---
+title: "Setting configuration parameters"
+navTitle: "Setting configuration parameters"
+description: "Describes how to set the configuration parameters for EDB Postgres Advanced Server"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.09.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.009.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/01_setting_new_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="setting_new_parameters" class="registered_link"></div>
+
+<div id="setting_configuration_parameters" class="registered_link"></div>
+
+Set each configuration parameter using a name/value pair. Parameter names aren't case sensitive. The parameter name is typically separated from its value by an optional equals sign (`=`).
+
+This example shows some configuration parameter settings in the `postgresql.conf` file:
+
+```ini
+# This is a comment
+log_connections = yes
+log_destination = 'syslog'
+search_path = '"$user", public'
+shared_buffers = 128MB
+```
+
+## Types of parameter values
+
+Parameter values are specified as one of five types:
+
+-   **Boolean** &mdash; Acceptable values are `on`, `off`, `true`, `false`, `yes`, `no`, `1`, `0`, or any unambiguous prefix of these.
+-   **Integer** &mdash; Number without a fractional part.
+-   **Floating point** &mdash; Number with an optional fractional part separated by a decimal point.
+-   **String** &mdash; Text value enclosed in single quotes if the value isn't a simple identifier or number, that is, the value contains special characters such as spaces or other punctuation marks.
+-   **Enum** &mdash; Specific set of string values. The allowed values can be found in the system view `pg_settings.enumvals`. Enum values are not case sensitive.
+
+Some settings specify a memory or time value. Each of these has an implicit unit, which is kilobytes, blocks (typically 8 kilobytes), milliseconds, seconds, or minutes. You can find default units by referencing the system view `pg_settings.unit`. You can specify a different unit explicitly.
+
+Valid memory units are:
+- `kB` (kilobytes)
+- `MB` (megabytes)
+- `GB` (gigabytes). 
+
+Valid time units are:
+- `ms` (milliseconds) 
+- `s` (seconds)
+- `min` (minutes)
+- `h` (hours)
+- `d` (days). 
+
+The multiplier for memory units is 1024.
+
+## Specifying configuration parameter settings
+
+A number of parameter settings are set when the EDB Postgres Advanced Server database product is built. These are read-only parameters, and you can't change their values. A couple of parameters are also permanently set for each database when the database is created. These parameters are read-only and you can't later change them for the database. However, there are a number of ways to specify the configuration parameter settings:
+
+-   The initial settings for almost all configurable parameters across the entire database cluster are listed in the `postgresql.conf` configuration file. These settings are put into effect upon database server start or restart. You can override some of these initial parameter settings. All configuration parameters have built-in default settings that are in effect unless you explicitly override them.
+
+-   Configuration parameters in the `postgresql.conf` file are overridden when the same parameters are included in the `postgresql.auto.conf` file. Use the `ALTER SYSTEM` command to manage the configuration parameters in the `postgresql.auto.conf` file.
+
+-   You can modify parameter settings in the configuration file while the database server is running. If the configuration file is then reloaded (meaning a SIGHUP signal is issued), for certain parameter types, the changed parameters settings immediately take effect. For some of these parameter types, the new settings are available in a currently running session immediately after the reload. For others, you must start a new session to use the new settings. And for some others, modified settings don't take effect until the database server is stopped and restarted. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/config-setting.html) for information on how to reload the configuration file.
+
+-   You can use the SQL commands `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` to modify certain parameter settings. The modified parameter settings take effect for new sessions after you execute the command. `ALTER DATABASE` affects new sessions connecting to the specified database. `ALTER ROLE` affects new sessions started by the specified role. `ALTER ROLE IN DATABASE` affects new sessions started by the specified role connecting to the specified database. Parameter settings established by these SQL commands remain in effect indefinitely, across database server restarts, overriding settings established by the other methods. You can change parameter settings established using the `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands by either: 
+
+    -  Reissuing these commands with a different parameter value.
+
+    -  Issuing these commands using the `SET parameter TO DEFAULT` clause or the `RESET parameter` clause. These clauses change the parameter back to using the setting set by the other methods. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-commands.html) for the syntax of these SQL commands.
+
+-   You can make changes for certain parameter settings for the duration of individual sessions using the `PGOPTIONS` environment variable or by using the `SET` command in the EDB-PSQL or PSQL command-line programs. Parameter settings made this way override settings established using any of the methods discussed earlier, but only during that session.
+
+## Modifying the postgresql.conf file
+
+The configuration parameters in the `postgresql.conf` file specify server behavior with regard to auditing, authentication, encryption, and other behaviors. On Linux and Windows hosts, the `postgresql.conf` file resides in the `data` directory under your EDB Postgres Advanced Server installation.
+
+Parameters that are preceded by a pound sign (#) are set to their default value. To change a parameter value, remove the pound sign and enter a new value. After setting or changing a parameter, you must either `reload` or `restart` the server for the new parameter value to take effect.
+
+In the `postgresql.conf` file, some parameters contain comments that indicate `change requires restart`. To view a list of the parameters that require a server restart, use the following query at the psql command line:
+
+```sql
+SELECT name FROM pg_settings WHERE context = 'postmaster';
+```
+
+<div id="modifying_the_pg_hba_conf_file" class="registered_link"></div>
+
+## Modifying the pg_hba.conf file
+
+Appropriate authentication methods provide protection and security. Entries in the `pg_hba.conf` file specify the authentication methods that the server uses with connecting clients. Before connecting to the server, you might need to modify the authentication properties specified in the `pg_hba.conf` file.
+
+When you invoke the initdb utility to create a cluster, the utility creates a `pg_hba.conf` file for that cluster that specifies the type of authentication required from connecting clients. You can modify this file. After modifying the authentication settings in the `pg_hba.conf` file, restart the server and apply the changes. For more information about authentication and modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/auth-pg-hba-conf.html).
+
+When the server receives a connection request, it verifies the credentials provided against the authentication settings in the `pg_hba.conf` file before allowing a connection to a database. To log the `pg_hba.conf` file entry to authenticate a connection to the server, set the `log_connections` parameter to `ON` in the `postgresql.conf` file.
+
+A record specifies a connection type, database name, user name, client IP address, and the authentication method to authorize a connection upon matching these parameters in the `pg_hba.conf` file. Once the connection to a server is authorized, you can see the matched line number and the authentication record from the `pg_hba.conf` file.
+
+This example shows a log detail for a valid `pg_hba.conf` entry after successful authentication:
+
+```shell
+2020-05-08 10:42:17 IST LOG:  connection received: host=[local]
+2020-05-08 10:42:17 IST LOG:  connection authorized: user=u1 database=edb
+application_name=psql
+2020-05-08 10:42:17 IST DETAIL:  Connection matched pg_hba.conf line 84:
+"local   all             all               md5"
+```
+
+## Obfuscating the LDAP password
+
+When using [LDAP](https://www.postgresql.org/docs/15/auth-ldap.html) for authentication, the LDAP password used to connect to the LDAP server (the ldapbindpasswd password) is stored in the `pg_hba.conf` file. You can store the password there in an obfuscated form, which can then be de-obfuscated by a loadable module that you supply. The loadable module supplies a hook function that performs the de-obfuscation.
+
+For example, this C-loadable module uses `rot13_passphrase` as the hook function to de-obfuscate the password from the `pg_hba.conf` file:
+
+   ```c
+   #include "postgres.h"
+
+   #include <float.h>
+   #include <stdio.h>
+
+   #include "libpq/libpq.h"
+   #include "libpq/libpq-be.h"
+   #include "libpq/auth.h"
+   #include "utils/guc.h"
+
+   PG_MODULE_MAGIC;
+
+   void		_PG_init(void);
+   void		_PG_fini(void);
+
+   /* hook function */
+   static char*	rot13_passphrase(char *password);
+
+   /*
+   * Module load callback
+   */
+   void
+   _PG_init(void)
+   {
+	   ldap_password_hook = rot13_passphrase;
+   }
+
+   void
+   _PG_fini(void)
+   {
+	  /* do  nothing yet */
+   }
+
+   static char*
+   rot13_passphrase(char *pw)
+   {
+	  size_t size = strlen(pw) + 1;
+
+	  char* new_pw = (char*) palloc(size);
+	  strlcpy(new_pw, pw, size);
+	  for (char *p = new_pw; *p; p++)
+	  {
+		 char		c = *p;
+
+		 if ((c >= 'a' && c <= 'm') || (c >= 'A' && c <= 'M'))
+			 *p = c + 13;
+		 else if ((c >= 'n' && c <= 'z') || (c >= 'N' && c <= 'Z'))
+			 *p = c - 13;
+	  }
+
+	 return new_pw;
+   }
+   ```
+
+Add your module to the `shared_preload_libraries` parameter in the `postgresql.conf` file. For example:
+
+   ```ini
+   shared_preload_libraries = '$libdir/ldap_password_func'
+   ```
+
+Restart your server to load the changes in this parameter.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/01_shared_buffers.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/01_shared_buffers.mdx
new file mode 100644
index 00000000000..6733196bc28
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/01_shared_buffers.mdx
@@ -0,0 +1,27 @@
+---
+title: "shared_buffers"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/01_shared_buffers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="shared_buffers" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 32MB
+
+**Range:** 128kB to system dependent
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the amount of memory the database server uses for shared memory buffers. The default is typically 32MB but might be less if your kernel settings don't support it, as determined during `initdb`. This setting must be at least 128kB. (Nondefault values of `BLCKSZ` change the minimum.) However, you usually need settings significantly higher than the minimum for good performance.
+
+If you have a dedicated database server with 1GB or more of RAM, a reasonable starting value for `shared_buffers` is 25% of the memory in your system. For some workloads, even large settings for `shared_buffers` are effective. However, because EDB Postgres Advanced Server also relies on the operating system cache, allocating more than 40% of RAM to `shared_buffers` isn't likely to work better than a smaller amount.
+
+On systems with less than 1GB of RAM, a smaller percentage of RAM is appropriate to leave space for the operating system. Fifteen percent of memory is more typical in these situations. Also, on Windows, large values for `shared_buffers` aren't as effective. You might have better results keeping the setting relatively low and using the operating system cache more instead. The useful range for `shared_buffers` on Windows systems is generally from 64MB to 512MB.
+
+Increasing this parameter might cause EDB Postgres Advanced Server to request more System V shared memory than your operating system's default configuration allows. See [Shared Memory and Semaphores](https://www.postgresql.org/docs/15/kernel-resources.html#SYSVIPC) in the PostgreSQL core documentation for information on how to adjust those parameters.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/02_work_mem.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/02_work_mem.mdx
new file mode 100644
index 00000000000..2a70aead93e
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/02_work_mem.mdx
@@ -0,0 +1,27 @@
+---
+title: "work_mem"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/02_work_mem/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="work_mem" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 1MB
+
+**Range:** 64kB to 2097151kB
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Specifies the amount of memory for internal sort operations and hash tables to use before writing to temporary disk files. 
+
+For a complex query, several sort or hash operations might run in parallel. Each operation is allowed to use as much memory as this value specifies before it starts to write data into temporary files. Also, several running sessions might perform such operations concurrently. Therefore, the total memory used might be many times the value of `work_mem`. Keep this information in mind when choosing the value. 
+
+Sort operations are used for `ORDER BY`, `DISTINCT`, and merge joins. Hash tables are used in hash joins, hash-based aggregation, and hash-based processing of `IN` subqueries.
+
+Reasonable values are typically between 4MB and 64MB, depending on the size of your machine, how many concurrent connections you expect (determined by `max_connections`), and the complexity of your queries.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/03_maintenance_work_mem.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/03_maintenance_work_mem.mdx
new file mode 100644
index 00000000000..27c4f4c2001
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/03_maintenance_work_mem.mdx
@@ -0,0 +1,25 @@
+---
+title: "maintenance_work_mem"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/03_maintenance_work_mem/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="maintenance_work_mem" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 16MB
+
+**Range:** 1024kB to 2097151kB
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Specifies the maximum amount of memory used by maintenance operations such as `VACUUM`, `CREATE INDEX`, and `ALTER TABLE ADD FOREIGN KEY`. It defaults to 16MB. Since a database session can execute only one of these operations at a time, and an installation normally doesn't have many of them running concurrently, it's safe to set this value significantly larger than `work_mem`. Larger settings might improve performance for vacuuming and for restoring database dumps.
+
+When autovacuum runs, you can allocate up to `autovacuum_max_workers` times, so be careful not to set the default value too high.
+
+A good rule of thumb is to set this to about 5% of system memory but not more than about 512MB. Larger values don't necessarily improve performance.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/04_wal_buffers.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/04_wal_buffers.mdx
new file mode 100644
index 00000000000..2a8693952de
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/04_wal_buffers.mdx
@@ -0,0 +1,25 @@
+---
+title: "wal_buffers"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/04_wal_buffers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="wal_buffers" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 64kB
+
+**Range:** 32kB to system dependent
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+The amount of memory used in shared memory for WAL data. Because the data is written out to disk at every transaction commit, the setting must be large enough only to hold the amount of WAL data generated by one typical transaction.
+
+Increasing this parameter might cause EDB Postgres Advanced Server to request more System V shared memory than your operating system's default configuration allows. See [Shared Memory and Semaphores](https://www.postgresql.org/docs/15/kernel-resources.html#SYSVIPC) in the PostgreSQL core documentation for information on how to adjust those parameters.
+
+Although even this very small setting doesn't always cause a problem, in some situations it can result in extra `fsync` calls and degrade overall system throughput. Increasing this value to about 1MB can address this problem. On very busy systems, you might need an even higher value, up to a maximum of about 16MB. Like `shared_buffers`, this parameter increases EDB Postgres Advanced Server’s initial shared memory allocation. If increasing it causes an EDB Postgres Advanced Server start failure, increase the operating system limit.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/05_checkpoint_segments.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/05_checkpoint_segments.mdx
new file mode 100644
index 00000000000..30e200d712d
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/05_checkpoint_segments.mdx
@@ -0,0 +1,9 @@
+---
+title: "checkpoint_segments"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/05_checkpoint_segments/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="checkpoint_segments" class="registered_link"></div>
+
+Deprecated. This parameter isn't supported by EDB Postgres Advanced Server. 
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/06_checkpoint_completion_target.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/06_checkpoint_completion_target.mdx
new file mode 100644
index 00000000000..68776eb7f8e
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/06_checkpoint_completion_target.mdx
@@ -0,0 +1,23 @@
+---
+title: "checkpoint_completion_target"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/06_checkpoint_completion_target/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="checkpoint_completion_target" class="registered_link"></div>
+
+**Parameter type:** Floating point
+
+**Default value:** 0.5
+
+**Range:** 0 to 1
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the target of checkpoint completion as a fraction of total time between checkpoints. This parameter spreads out the checkpoint writes while the system starts working toward the next checkpoint.
+
+The default of 0.5 aims to finish the checkpoint writes when 50% of the next checkpoint is ready. A value of 0.9 aims to finish the checkpoint writes when 90% of the next checkpoint is done. This value throttles the checkpoint writes over a larger amount of time and avoids spikes of performance bottlenecking.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/07_checkpoint_timeout.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/07_checkpoint_timeout.mdx
new file mode 100644
index 00000000000..e89eacbb8cd
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/07_checkpoint_timeout.mdx
@@ -0,0 +1,25 @@
+---
+title: "checkpoint_timeout"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/07_checkpoint_timeout/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="checkpoint_timeout" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 5min
+
+**Range:** 30s to 3600s
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Maximum time between automatic WAL checkpoints, in seconds. Increasing this parameter can increase the amount of time needed for crash recovery.
+
+Increasing `checkpoint_timeout` to a larger value, such as 15 minutes, can reduce the I/O load on your system, especially when using large values for `shared_buffers`.
+
+The downside of making these adjustments to the checkpoint parameters is that your system uses a modest amount of additional disk space and takes longer to recover in the event of a crash. However, for most users, this is worth it for a significant performance improvement.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size.mdx
new file mode 100644
index 00000000000..5f658625064
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size.mdx
@@ -0,0 +1,23 @@
+---
+title: "max_wal_size"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/08_max_wal_size/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="max_wal_size" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 1 GB
+
+**Range:** 2 to 2147483647
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+`max_wal_size` specifies the maximum size for the WAL to reach between automatic WAL checkpoints. This is a soft limit. WAL size can exceed `max_wal_size` under special circumstances, such as when under a heavy load, with a failing archive_command, or with a high `wal_keep_segments` setting.
+
+Increasing this parameter can increase the amount of time needed for crash recovery. You can set this parameter in the `postgresql.conf` file or on the server command line.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/09_min_wal_size.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/09_min_wal_size.mdx
new file mode 100644
index 00000000000..74bd9913365
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/09_min_wal_size.mdx
@@ -0,0 +1,21 @@
+---
+title: "min_wal_size"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/09_min_wal_size/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="min_wal_size" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 80 MB
+
+**Range:** 2 to 2147483647
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+If WAL disk usage stays below the value specified by `min_wal_size`, old WAL files are recycled for future use at a checkpoint rather than removed. This feature ensures that enough WAL space is reserved to handle spikes in WAL usage, like when running large batch jobs. You can set this parameter in the `postgresql.conf` file or on the server command line.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/10_bgwriter_delay.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/10_bgwriter_delay.mdx
new file mode 100644
index 00000000000..498f32a09f5
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/10_bgwriter_delay.mdx
@@ -0,0 +1,25 @@
+---
+title: "bgwriter_delay"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/10_bgwriter_delay/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="bgwriter_delay" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 200ms
+
+**Range:** 10ms to 10000ms
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the delay between activity rounds for the background writer. In each round, the writer issues writes for some number of dirty buffers. (You can control the number of dirty buffers using the `bgwriter_lru_maxpages` and `bgwriter_lru_multiplier` parameters.) It then sleeps for `bgwriter_delay` milliseconds, and repeats.
+
+On many systems, the effective resolution of sleep delays is 10ms. Setting `bgwriter_delay` to a value that isn't a multiple of 10 might have the same results as setting it to the next higher multiple of 10.
+
+Typically, when tuning `bgwriter_delay`, you reduce it from its default value. This parameter is rarely increased. Saving on power consumption on a system with very low use is one case when you might increase the value.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/11_seq_page_cost.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/11_seq_page_cost.mdx
new file mode 100644
index 00000000000..c51fc30eee4
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/11_seq_page_cost.mdx
@@ -0,0 +1,23 @@
+---
+title: "seq_page_cost"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/11_seq_page_cost/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="seq_page_cost" class="registered_link"></div>
+
+**Parameter type:** Floating point
+
+**Default value:** 1
+
+**Range:** 0 to 1.79769e+308
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Sets the planner's estimate of the cost of a disk page fetch that's part of a series of sequential fetches. You can override this value for a particular tablespace by setting the tablespace parameter of the same name. See [`ALTER TABLESPACE`](https://www.postgresql.org/docs/current/sql-altertablespace.html) in the PostgreSQL core documentation.
+
+The default value assumes very little caching, so it's often a good idea to reduce it. Even if your database is significantly larger than physical memory, you might want to try setting this parameter to something lower than the default value of 1 to see if you get better query plans that way. If your database fits entirely in memory, you can lower this value much more, for example, to 0.1.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/12_random_page_cost.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/12_random_page_cost.mdx
new file mode 100644
index 00000000000..446f5cfd14f
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/12_random_page_cost.mdx
@@ -0,0 +1,27 @@
+---
+title: "random_page_cost"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/12_random_page_cost/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="random_page_cost" class="registered_link"></div>
+
+**Parameter type:** Floating point
+
+**Default value:** 4
+
+**Range:** 0 to 1.79769e+308
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Sets the planner's estimate of the cost of a nonsequentially fetched disk page. You can override the default for a particular tablespace by setting the tablespace parameter of the same name. See [`ALTER TABLESPACE`](https://www.postgresql.org/docs/current/sql-altertablespace.html) in the PostgreSQL core documentation.
+
+Reducing this value relative to `seq_page_cost` causes the system to prefer index scans. Raising it makes index scans look relatively more expensive. You can raise or lower both values together to change the importance of disk I/O costs relative to CPU costs, which are described by the `cpu_tuple_cost` and `cpu_index_tuple_cost` parameters.
+
+The default value assumes very little caching, so it's often a good idea to reduce it. Even if your database is significantly larger than physical memory, you might want to try setting this parameter to 2 (that is, lower than the default) to see whether you get better query plans that way. If your database fits entirely in memory, you can lower this value much more, for example, to 0.1.
+
+Although the system allows it, never set `random_page_cost` less than `seq_page_cost`. However, setting them equal or very close to equal makes sense if the database fits mostly or entirely in memory, since in that case there's no penalty for touching pages out of sequence. Also, in a heavily cached database, lower both values relative to the CPU parameters, since the cost of fetching a page already in RAM is much smaller than it normally is.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/13_effective_cache_size.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/13_effective_cache_size.mdx
new file mode 100644
index 00000000000..a0ce1ece3ae
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/13_effective_cache_size.mdx
@@ -0,0 +1,27 @@
+---
+title: "effective_cache_size"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/13_effective_cache_size/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="effective_cache_size" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 128MB
+
+**Range:** 8kB to 17179869176kB
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Sets the planner's assumption about the effective size of the disk cache that's available to a single query. This assumption is factored into estimates of the cost of using an index. A higher value makes it more likely index scans are used. A lower value makes it more likely sequential scans are used. 
+
+When setting this parameter, consider both EDB Postgres Advanced Server’s shared buffers and the portion of the kernel's disk cache that are used for EDB Postgres Advanced Server data files. Also, consider the expected number of concurrent queries on different tables, since they have to share the available space. 
+
+This parameter doesn't affect the size of shared memory allocated by EDB Postgres Advanced Server, and it doesn't reserve kernel disk cache. Use it only for estimating. 
+
+If this parameter is set too low, the planner might decide not to use an index even when it's helpful to do so. Setting `effective_cache_size` to 50% of physical memory is a normal, conservative setting. A more aggressive setting is approximately 75% of physical memory.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/14_synchronous_commit.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/14_synchronous_commit.mdx
new file mode 100644
index 00000000000..52ff714212c
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/14_synchronous_commit.mdx
@@ -0,0 +1,27 @@
+---
+title: "synchronous_commit"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/14_synchronous_commit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="synchronous_commit" class="registered_link"></div>
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Specifies whether a transaction commit waits for WAL records to be written to disk before the command returns a `success` indication to the client. The safe setting is on, which is the default. When off, there can be a delay between when success is reported to the client and when the transaction is really guaranteed to be safe against a server crash. (The maximum delay is three times `wal_writer_delay`.)
+
+Unlike `fsync`, setting this parameter to off does not create any risk of database inconsistency. An operating system or database crash might result in some recent "allegedly committed" transactions being lost. However, the database state is the same as if those transactions aborted cleanly.
+
+So, turning `synchronous_commit` off can be a useful alternative when performance is more important than exact certainty about the durability of a transaction. See [`Asynchronous Commit`](https://www.postgresql.org/docs/current/wal-async-commit.html) in the PostgreSQL core documentation for information.
+
+You can change this parameter at any time. The behavior for any one transaction is determined by the setting in effect when it commits. It's therefore possible and useful to have some transactions commit synchronously and others asynchronously. For example, to make a single multistatement transaction commit asynchronously when the default is the opposite, issue `SET LOCAL synchronous_commit TO OFF` in the transaction.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/15_edb_max_spins_per_delay.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/15_edb_max_spins_per_delay.mdx
new file mode 100644
index 00000000000..c8c9087e5ef
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/15_edb_max_spins_per_delay.mdx
@@ -0,0 +1,23 @@
+---
+title: "edb_max_spins_per_delay"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/15_edb_max_spins_per_delay/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_max_spins_per_delay" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 1000
+
+**Range:** 10 to 1000
+
+**Minimum scope of effect:** Per cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the maximum number of times that a session spins while waiting for a spin lock. If a lock isn't acquired, the session sleeps.
+
+This parameter can be useful for systems that use non-uniform memory access (NUMA) architecture.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/16_pg_prewarm.autoprewarm.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/16_pg_prewarm.autoprewarm.mdx
new file mode 100644
index 00000000000..e247ff7d8ba
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/16_pg_prewarm.autoprewarm.mdx
@@ -0,0 +1,39 @@
+---
+title: "pg_prewarm.autoprewarm"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/16_pg_prewarm.autoprewarm/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="pg_prewarm_autoprewarm" class="registered_link"></div>
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Controls whether the database server runs `autoprewarm`, a background worker process that dumps shared buffers to disk before a shutdown. It then *prewarms* the shared buffers the next time the server is started, meaning it loads blocks from the disk back into the buffer pool.
+
+The advantage to this parameter is that it shortens the warmup times after the server restarts by loading the data that was dumped to disk before shutdown.
+
+Set `pg_prewarm.autoprewarm` to on to enable the `autoprewarm` worker. Set it to off to disable `autoprewarm`. 
+
+Before you can use `autoprewarm`, you must add `$libdir/pg_prewarm` to the libraries listed in the `shared_preload_libraries` configuration parameter of the `postgresql.conf` file, as this example shows:
+
+```ini
+shared_preload_libraries = '$libdir/dbms_pipe,$libdir/edb_gen,$libdir/dbms_aq,$libdir/pg_prewarm'
+```
+
+After modifying the `shared_preload_libraries` parameter, restart the database server. After the restart, the `autoprewarm` background worker launches immediately after the server reaches a consistent state.
+
+The `autoprewarm` process starts loading blocks that were previously recorded in `$PGDATA/autoprewarm.blocks` until no free buffer space is left in the buffer pool. In this manner, any new blocks that were loaded either by the recovery process or by the querying clients aren't replaced.
+
+Once the `autoprewarm` process finishes loading buffers from disk, it periodically dumps shared buffers to disk at the interval specified by the `pg_prewarm.autoprewarm_interval` parameter. At the next server restart, the `autoprewarm` process prewarms shared buffers with the blocks that were last dumped to disk.
+
+See [pg_prewarm.autoprewarm_interval](17_pg_prewarm.autoprewarm_interval/#pg_prewarm_autoprewarm_interval) for information on the `autoprewarm` background worker. 
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/17_pg_prewarm.autoprewarm_interval.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/17_pg_prewarm.autoprewarm_interval.mdx
new file mode 100644
index 00000000000..9245ed2aba2
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/17_pg_prewarm.autoprewarm_interval.mdx
@@ -0,0 +1,23 @@
+---
+title: "pg_prewarm.autoprewarm_interval"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/17_pg_prewarm.autoprewarm_interval/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="pg_prewarm_autoprewarm_interval" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 300s
+
+**Range:** 0s to 2147483s
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+The minimum number of seconds after which the `autoprewarm` background worker dumps shared buffers to disk. If set to 0, shared buffers aren't dumped at regular intervals. They're dumped only when you shut down the server.
+
+See the [pg_prewarm.autoprewarm](16_pg_prewarm.autoprewarm/#pg_prewarm_autoprewarm) for information on the `autoprewarm` background worker.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/index.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/index.mdx
new file mode 100644
index 00000000000..311fcc1738d
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/index.mdx
@@ -0,0 +1,20 @@
+---
+title: "Top performance-related parameters"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.12.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.012.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/01_top_performance_related_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="top_performance_related_parameters" class="registered_link"></div>
+
+These configuration parameters have the most immediate impact on performance.
+
+<div class="toctree" maxdepth="3">
+
+shared_buffers work_mem maintenance_work_mem wal_buffers checkpoint_segments checkpoint_completion_target checkpoint_timeout max_wal_size min_wal_size bgwriter_delay seq_page_cost random_page_cost effective_cache_size synchronous_commit edb_max_spins_per_delay pg_prewarm.autoprewarm pg_prewarm.autoprewarm_interval
+
+</div>
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/02_resource_usage_memory.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/02_resource_usage_memory.mdx
new file mode 100644
index 00000000000..a9ae8c4e873
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/02_resource_usage_memory.mdx
@@ -0,0 +1,63 @@
+---
+title: "Resource usage/memory"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.13.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.013.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/02_resource_usage_memory/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="resource_usage_memory" class="registered_link"></div>
+
+These configuration parameters control resource use pertaining to memory.
+
+## edb_dynatune
+
+**Parameter type:** Integer
+
+**Default value:** 0
+
+**Range:** 0 to 100
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Determines how much of the host system’s resources for the database server to use based on the host machine’s total available resources and the intended use of the host machine.
+
+When you first install EDB Postgres Advanced Server, you set `edb_dynatune` according to the use of the host machine on which it was installed, that is, development machine, mixed-use machine, or dedicated server. For most purposes, the database administrator doesn't need to adjust the various configuration parameters in the `postgresql.conf` file to improve performance.
+
+You can set the `edb_dynatune` parameter to any integer value from 0 to 100. A value of 0 turns off the dynamic tuning feature, which leaves the database server resource use under the control of the other configuration parameters in the `postgresql.conf` file.
+
+A low, non-zero value, for example, 1 to 33, dedicates the least amount of the host machine’s resources to the database server. These values are suitable for a development machine where many other applications are being used.
+
+A value in the range of 34 to 66 dedicates a moderate amount of resources to the database server. This setting might be used for a dedicated application server that has a fixed number of other applications running on the same machine as EDB Postgres Advanced Server.
+
+The highest values of 67 to 100 dedicate most of the server’s resources to the database server. Use settings in this range for a host machine that's dedicated to running EDB Postgres Advanced Server.
+
+After you select a value for `edb_dynatune`, you can further fine-tune database server performance by adjusting the other configuration parameters in the `postgresql.conf` file. Any adjusted setting overrides the corresponding value chosen by `edb_dynatune`. To change the value of a parameter, uncomment the configuration parameter, specify the desired value, and restart the database server.
+
+## edb_dynatune_profile
+
+**Parameter type:** Enum
+
+**Default value:** `oltp`
+
+**Range:** `{oltp | reporting | mixed}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Controls tuning aspects based on the expected workload profile on the database server.
+
+The following are the possible values:
+
+-   `oltp`. Recommended when the database server is processing heavy online transaction processing workloads.
+-   `reporting`. Recommended for database servers used for heavy data reporting.
+-   `mixed`. Recommended for servers that provide a mix of transaction processing and data reporting.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/03_resource_usage_edb_resource_manager.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/03_resource_usage_edb_resource_manager.mdx
new file mode 100644
index 00000000000..d1e94d96eca
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/03_resource_usage_edb_resource_manager.mdx
@@ -0,0 +1,45 @@
+---
+title: "Resource usage/EDB Resource Manager"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/03_resource_usage_edb_resource_manager/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="resource_usage_edb_resource_manager" class="registered_link"></div>
+
+These configuration parameters control resource use through [EDB Resource Manager](../../10_edb_resource_manager/).
+
+## edb_max_resource_groups
+
+**Parameter type:** Integer
+
+**Default value:** 16
+
+**Range:** 0 to 65536
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Controls the maximum number of resource groups that EDB Resource Manager can use simultaneously. You can create more resource groups than the value specified by `edb_max_resource_groups`. However, the number of resource groups in active use by processes in these groups can't exceed this value.
+
+Set this parameter large enough to handle the number of groups you expect to maintain.
+
+## edb_resource_group
+
+**Parameter type:** String
+
+**Default value:** none
+
+**Range:** n/a
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+The name of the resource group for EDB Resource Manager to control in the current session according to the group’s resource type settings.
+
+If you don't set this parameter, then the current session doesn't use EDB Resource Manager.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/04_query_tuning.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/04_query_tuning.mdx
new file mode 100644
index 00000000000..01fbb30ae05
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/04_query_tuning.mdx
@@ -0,0 +1,29 @@
+---
+title: "Query tuning"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.14.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.014.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/04_query_tuning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="query_tuning" class="registered_link"></div>
+
+These configuration parameters are used for [optimizer hints](../../../application_programming/optimizing_code/05_optimizer_hints/).
+
+## enable_hints
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Enables optimizer hints embedded in SQL commands. Optimizer hints are ignored when this parameter is off.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/05_query_tuning_planner_method_configuration.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/05_query_tuning_planner_method_configuration.mdx
new file mode 100644
index 00000000000..7a3025e2fb1
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/05_query_tuning_planner_method_configuration.mdx
@@ -0,0 +1,33 @@
+---
+title: "Query tuning/planner method configuration"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/05_query_tuning_planner_method_configuration/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="query_tuning_planner_method_configuration" class="registered_link"></div>
+
+These configuration parameters are used for planner method configuration.
+
+## edb_enable_pruning
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Allows the query planner to *early prune* partitioned tables. Early pruning means that the query planner can "prune" (that is, ignore) partitions that aren't searched in a query before generating query plans. This setting helps improve performance because it prevents generating query plans of partitions that aren't searched.
+
+Conversely, *late pruning* means that the query planner prunes partitions after generating query plans for each partition. The `constraint_exclusion` configuration parameter controls late pruning.
+
+The ability to early prune depends on the nature of the query in the `WHERE` clause. You can use early pruning in only simple queries with constraints like `WHERE column = literal`, for example, `WHERE deptno = 10`.
+
+Don't use early pruning for more complex queries such as `WHERE column = expression`, for example, `WHERE deptno = 10 + 5`.
+
+This parameter is deprecated from version 15 and later. Use `enable_partition_pruning` instead.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log.mdx
new file mode 100644
index 00000000000..1923e86e2a1
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log.mdx
@@ -0,0 +1,75 @@
+---
+title: "Reporting and logging/what to log"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.15.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.015.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/06_reporting_and_logging_what_to_log/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="reporting_and_logging_what_to_log" class="registered_link"></div>
+
+These configuration parameters control reporting and logging.
+
+## trace_hints
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required Aauthorization to activate:** Session user
+
+Use with the optimizer hints feature to provide more detailed information about whether the planner used a hint. Set the `client_min_messages` and `trace_hints` configuration parameters as follows:
+
+```sql
+SET client_min_messages TO info;
+SET trace_hints TO true;
+```
+
+This example shows how the `SELECT` command with the `NO_INDEX` hint displays the added information produced when you set those configuration parameters:
+
+```sql
+EXPLAIN SELECT /*+ NO_INDEX(accounts accounts_pkey) */ * FROM accounts
+WHERE aid = 100;
+
+INFO: [HINTS] Index Scan of [accounts].[accounts_pkey] rejected because
+of NO_INDEX hint.
+
+INFO: [HINTS] Bitmap Heap Scan of [accounts].[accounts_pkey] rejected
+because of NO_INDEX hint.
+__OUTPUT__
+                          QUERY PLAN
+
+-------------------------------------------------------------
+
+Seq Scan on accounts (cost=0.00..14461.10 rows=1 width=97)
+  Filter: (aid = 100)
+(2 rows)
+```
+
+## edb_log_every_bulk_value
+
+<div id="edb_log_every_bulk_value_1" class="registered_link"></div>
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Superuser
+
+Bulk processing logs the resulting statements into both the EDB Postgres Advanced Server log file and the EDB Audit log file. However, logging every statement in bulk processing is costly. You can control the bulk processing statements that are logged with the `edb_log_every_bulk_value` configuration parameter. 
+
+When this parameter is set to `true`, every statement in bulk processing is logged. During bulk execution, when `edb_log_every_bulk_value` is set to `false`, a log message is recorded once per bulk processing along with the number of rows processed. The duration is emitted once per bulk processing. 
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/01_edb_audit.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/01_edb_audit.mdx
new file mode 100644
index 00000000000..b0ddee5a52f
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/01_edb_audit.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/01_edb_audit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit" class="registered_link"></div>
+
+**Parameter type:** Enum
+
+**Default value:** `none`
+
+**Range:** `{none | csv | xml}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Enables or disables database auditing. The values `xml` or `csv` enable database auditing. These values determine the file format in which to capture auditing information. `none` disables database auditing.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/02_edb_audit_directory.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/02_edb_audit_directory.mdx
new file mode 100644
index 00000000000..5b31cb78ab7
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/02_edb_audit_directory.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_directory"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/02_edb_audit_directory/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_directory" class="registered_link"></div>
+
+**Parameter type:** String
+
+**Default value:** `edb_audit`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the directory where the audit log files are created. Specify either an absolute path or a path relative to the EDB Postgres Advanced Server `data` directory.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/03_edb_audit_filename.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/03_edb_audit_filename.mdx
new file mode 100644
index 00000000000..9cf103d1a14
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/03_edb_audit_filename.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_filename"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/03_edb_audit_filename/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_filename" class="registered_link"></div>
+
+**Parameter type:** String
+
+**Default value:** `audit-%Y%m%d_%H%M%S`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the file name of the audit file where the auditing information is stored. The default file name is `audit-%Y%m%d_%H%M%S`. The escape sequences, such as `%Y` and `%m`, are replaced by the appropriate current values of the system date and time.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/04_edb_audit_rotation_day.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/04_edb_audit_rotation_day.mdx
new file mode 100644
index 00000000000..aacc42c780c
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/04_edb_audit_rotation_day.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_rotation_day"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/04_edb_audit_rotation_day/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_rotation_day" class="registered_link"></div>
+
+**Parameter type:** String
+
+**Default value:** `every`
+
+**Range:** `{none | every | sun | mon | tue | wed | thu | fri | sat} ...`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the day of the week on which to rotate the audit files. Valid values are `sun`, `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `every`, and `none`. To disable rotation, set the value to `none`. To rotate the file every day, set the `edb_audit_rotation_day` value to `every`. To rotate the file on a specific day of the week, set the value to the desired day of the week.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/05_edb_audit_rotation_size.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/05_edb_audit_rotation_size.mdx
new file mode 100644
index 00000000000..3a8804ade0b
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/05_edb_audit_rotation_size.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_rotation_size"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/05_edb_audit_rotation_size/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_rotation_size" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 0MB
+
+**Range:** 0MB to 5000MB
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies a file size threshold in megabytes when file rotation occurs. If the parameter is commented out or set to 0, rotating the file based on size doesn't occur.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/06_edb_audit_rotation_seconds.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/06_edb_audit_rotation_seconds.mdx
new file mode 100644
index 00000000000..72941062da8
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/06_edb_audit_rotation_seconds.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_rotation_seconds"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/06_edb_audit_rotation_seconds/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_rotation_seconds" class="registered_link"></div>
+
+**Parameter type:** Integer
+
+**Default value:** 0s
+
+**Range:** 0s to 2147483647s
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the rotation time in seconds when a new log file is created. To disable this feature, leave this parameter set to 0.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/07_edb_audit_connect.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/07_edb_audit_connect.mdx
new file mode 100644
index 00000000000..cf795e65eb4
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/07_edb_audit_connect.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_connect"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/07_edb_audit_connect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_connect" class="registered_link"></div>
+
+**Parameter type:** Enum
+
+**Default value:** `failed`
+
+**Range:** `{none | failed | all}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Enables auditing of database connection attempts by users. To disable auditing of all connection attempts, set `edb_audit_connect` to `none`. To audit all failed connection attempts, set the value to `failed`. To audit all connection attempts, set the value to `all`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/08_edb_audit_disconnect.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/08_edb_audit_disconnect.mdx
new file mode 100644
index 00000000000..a3df7658b45
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/08_edb_audit_disconnect.mdx
@@ -0,0 +1,21 @@
+---
+title: "edb_audit_disconnect"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/08_edb_audit_disconnect/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_disconnect" class="registered_link"></div>
+
+**Parameter type:** Enum
+
+**Default value:** `none`
+
+**Range:** `{none | all}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Enables auditing of database disconnections by connected users. To enable auditing of disconnections, set the value to `all`. To disable, set the value to `none`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/09_edb_audit_statement.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/09_edb_audit_statement.mdx
new file mode 100644
index 00000000000..b225660b6fe
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/09_edb_audit_statement.mdx
@@ -0,0 +1,32 @@
+---
+title: "edb_audit_statement"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/09_edb_audit_statement/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_statement" class="registered_link"></div>
+
+**Parameter type:** String
+
+**Default value:** `ddl, error`
+
+**Range:** `{none | ddl | dml | insert | update | delete | truncate | select | error | create | drop | alter | grant | revoke | rollback | set | all | { select | update | delete | insert }@groupname} ...`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies auditing of different categories of SQL statements as well as statements related to specific SQL commands. 
+
+-  To log errors, set the parameter value to `error`. 
+-  To audit all DDL statements, such as `CREATE TABLE` and `ALTER TABLE`, set the parameter value to `ddl`. 
+-  To audit specific types of DDL statements, the parameter values can include those specific SQL commands (`create`, `drop`, or `alter`). In addition, you can specify the object type following the command, such as `create table`, `create view`, and `drop role`. 
+-  To audit all modification statements, such as `INSERT`, `UPDATE`, `DELETE`, or `TRUNCATE`, set `edb_audit_statement` to `dml`. 
+-  To audit specific types of DML statements, the parameter values can include the specific SQL commands `insert`, `update`, `delete`, or `truncate`. Include parameter values `select`, `grant`, `revoke`, or `rollback` to audit statements regarding those SQL commands. 
+-  To audit `SET` statements, include the parameter value `SET`.
+-  To audit every statement, set the value to `all`. 
+-  To disable this feature, set the value to `none`.
+
+The per-object level auditing audits the operations permitted by object privileges, such as `SELECT`, `UPDATE`, `DELETE`, and `INSERT` statements, including `(@)` and excluding `(-)` groups on a given table. To audit a specific type of object, specify the name of the object group to audit. The `edb_audit_statement` parameter can include the specific SQL commands (`select`, `update`, `delete`, or `insert`) associated with a group name with `(@)` include and `(-)` exclude symbol.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/10_edb_audit_tag.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/10_edb_audit_tag.mdx
new file mode 100644
index 00000000000..c00a6a2a6fd
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/10_edb_audit_tag.mdx
@@ -0,0 +1,19 @@
+---
+title: "edb_audit_tag"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/10_edb_audit_tag/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_tag" class="registered_link"></div>
+
+**Parameter type:** String
+
+**Default value:** none
+
+**Minimum scope of effect:** Session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** User
+
+Specifies a string value to include in the audit log when the `edb_audit` parameter is set to `csv` or `xml`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/11_edb_audit_destination.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/11_edb_audit_destination.mdx
new file mode 100644
index 00000000000..40788146cb1
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/11_edb_audit_destination.mdx
@@ -0,0 +1,26 @@
+---
+title: "edb_audit_destination"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/11_edb_audit_destination/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_destination" class="registered_link"></div>
+
+**Parameter type:** Enum
+
+**Default value:** `file`
+
+**Range:** `{file | syslog}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies whether to record the audit log information in the directory as given by the `edb_audit_directory` parameter or to the directory and file managed by the `syslog` process. Set to `file` to use the directory specified by `edb_audit_directory`.
+
+Set to `syslog` to use the syslog process and its location as configured in the `/etc/syslog.conf` file. The `syslog` setting is valid only for EDB Postgres Advanced Server running on a Linux host. It isn't supported on Windows systems.
+
+!!! Note
+    In recent Linux versions, `syslog` was replaced with `rsyslog`, and the configuration file is in `/etc/rsyslog.conf`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/12_edb_log_every_bulk_value.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/12_edb_log_every_bulk_value.mdx
new file mode 100644
index 00000000000..7ed0815e20e
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/12_edb_log_every_bulk_value.mdx
@@ -0,0 +1,9 @@
+---
+title: "edb_log_every_bulk_value"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/12_edb_log_every_bulk_value/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_log_every_bulk_value" class="registered_link"></div>
+
+For information on `edb_log_every_bulk_value`, see [edb_log_every_bulk_value](../06_reporting_and_logging_what_to_log/#edb_log_every_bulk_value_1).
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx
new file mode 100644
index 00000000000..54678857595
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "Auditing settings"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/07_auditing_settings/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="auditing_settings" class="registered_link"></div>
+
+These configuration parameters are for use with the EDB Postgres Advanced Server database [auditing feature](../../../../epas_security_guide/05_edb_audit_logging/).
+
+<div class="toctree" maxdepth="3">
+
+edb_audit edb_audit_directory edb_audit_filename edb_audit_rotation_day edb_audit_rotation_size edb_audit_rotation_seconds edb_audit_connect edb_audit_disconnect edb_audit_statement edb_audit_tag edb_audit_destination edb_log_every_bulk_value
+
+</div>
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/08_ccd_locale_and_formatting.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/08_ccd_locale_and_formatting.mdx
new file mode 100644
index 00000000000..bcc1793a5f1
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/08_ccd_locale_and_formatting.mdx
@@ -0,0 +1,36 @@
+---
+title: "Client connection defaults/locale and formatting"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.16.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.016.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/08_ccd_locale_and_formatting/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ccd_locale_and_formatting" class="registered_link"></div>
+
+These configuration parameters affect locale and formatting.
+
+## icu_short_form
+
+**Parameter type:** String
+
+**Default value:** none
+
+**Range:** n/a
+
+**Minimum scope of effect:** Database
+
+**When value changes take effect:** n/a
+
+**Required authorization to activate:** n/a
+
+Contains the default ICU short-form name assigned to a database or to the EDB Postgres Advanced Server instance. See [Unicode collation algorithm](../../../tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm) for general information about the ICU short form and the Unicode collation algorithm.
+
+Set this configuration parameter either when:
+
+-  Using the `CREATE DATABASE` command with the `ICU_SHORT_FORM` parameter. In this case, set the specified short-form name. It appears in the `icu_short_form` configuration parameter when connected to this database. 
+-  Creating an EDB Postgres Advanced Server instance with the `initdb` command used with the `--icu_short_form` option. In this case, set the specified short-form name. It appears in the `icu_short_form` configuration parameter when connected to a database in that EDB Postgres Advanced Server instance. The database doesn't override it with its own `ICU_SHORT_FORM` parameter and a different short form.
+
+Once you set this parameter, you can't change it.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/09_ccd_statement_behaviour.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/09_ccd_statement_behaviour.mdx
new file mode 100644
index 00000000000..767ae126d61
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/09_ccd_statement_behaviour.mdx
@@ -0,0 +1,57 @@
+---
+title: "Client connection defaults/statement behavior"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/09_ccd_statement_behaviour/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ccd_statement_behaviour" class="registered_link"></div>
+
+These configuration parameters affect statement behavior.
+
+## default_heap_fillfactor
+
+**Parameter type:** Integer
+
+**Default value:** 100
+
+**Range:** 10 to 100
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Sets the fill factor for a table when the `FILLFACTOR` storage parameter is omitted from a `CREATE TABLE` command.
+
+The fill factor for a table is a percentage from 10 to 100, where 100 is complete packing. When you specify a smaller fill factor, `INSERT` operations pack table pages only to the indicated percentage. The remaining space on each page is reserved for updating rows on that page. This approach gives `UPDATE` a chance to place the updated copy of a row on the same page as the original, which is more efficient than placing it on a different page. 
+
+For a table whose entries are never updated, complete packing is the best choice. In heavily updated tables, use smaller fill factors.
+
+## edb_data_redaction
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Data redaction is the support of policies to limit the exposure of certain sensitive data to certain users by altering the displayed information.
+
+When set to `TRUE`, the data redaction is applied to all users except for superusers and the table owner:
+
+-   Superusers and table owner bypass data redaction.
+-   All other users get the redaction policy applied and see the reformatted data.
+
+When set to `FALSE`, the following occurs:
+
+-   Superusers and table owner still bypass data redaction.
+-   All other users get an error.
+
+For information on data redaction, see [EDB Postgres Advanced Server Security Features](../../../epas_security_guide/).
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/10_ccd_other_defaults.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/10_ccd_other_defaults.mdx
new file mode 100644
index 00000000000..09265aad0ab
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/10_ccd_other_defaults.mdx
@@ -0,0 +1,65 @@
+---
+title: "Client connection defaults/other defaults"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/10_ccd_other_defaults/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ccd_other_defaults" class="registered_link"></div>
+
+These parameters set miscellaneous client connection defaults.
+
+## oracle_home
+
+**Parameter type:** String
+
+**Default value:** none
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Before creating a link to an Oracle server, you must direct EDB Postgres Advanced Server to the correct Oracle home directory. Set the `LD_LIBRARY_PATH` environment variable on Linux or `PATH` on Windows to the `lib` directory of the Oracle client installation directory.
+
+Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The value specified in the `oracle_home` configuration parameter overrides the `LD_LIBRARY_PATH` environment variable in Linux and `PATH` environment variable in Windows.
+
+!!! Note
+    The `oracle_home` configuration parameter must provide the correct path to the Oracle client, that is,`OCI` library.
+
+To set the `oracle_home` configuration parameter in the `postgresql.conf` file, add the following line:
+
+```text
+oracle_home = '<lib_directory>'
+```
+
+&lt;lib_directory> is the name of the `oracle_home` path to the Oracle client installation directory that contains `libclntsh.so` in Linux and `oci.dll` in Windows.
+
+After setting the `oracle_home` configuration parameter, you must restart the server for the changes to take effect. Restart the server:
+
+-   On Linux, using the `systemctl` command or `pg_ctl` services
+
+-   On Windows, from the Windows Services console
+
+
+## odbc_lib_path
+
+**Parameter type:** String
+
+**Default value:** none
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+If you're using an ODBC driver manager and if it's installed in a nonstandard location, specify the location by setting the `odbc_lib_path` configuration parameter in the `postgresql.conf` file:
+
+`odbc_lib_path = 'complete_path_to_libodbc.so'`
+
+The configuration file must include the complete pathname to the driver manager shared library, which is typically `libodbc.so`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options.mdx
new file mode 100644
index 00000000000..4f0c69f1bdc
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options.mdx
@@ -0,0 +1,375 @@
+---
+title: "Compatibility options"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.17.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.017.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/11_compatibility_options/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="compatibility_options" class="registered_link"></div>
+
+These configuration parameters control various database compatibility features.
+
+## edb_redwood_date
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Translates `DATE` to `TIMESTAMP` when `DATE` appears as the data type of a column in the commands and the table definition is stored in the database. A time component is stored in the column along with the date.
+
+If `edb_redwood_date` is set to `FALSE`, the column’s data type in a `CREATE TABLE` or `ALTER TABLE` command remains as a native PostgreSQL `DATE` data type and is stored as such in the database. The PostgreSQL `DATE` data type stores only the date without a time component in the column.
+
+Regardless of the setting of `edb_redwood_date`, when `DATE` appears as a data type in any other context, it's always internally translated to a `TIMESTAMP`. It can thus handle a time component if present. Examples of these contexts include:
+
+-  The data type of a variable in an SPL declaration section 
+-  The data type of a formal parameter in an SPL procedure or SPL function
+-  The return type of an SPL function
+
+## edb_redwood_greatest_least
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+The `GREATEST` function returns the parameter with the greatest value from its list of parameters. The `LEAST` function returns the parameter with the least value from its list of parameters.
+
+When `edb_redwood_greatest_least` is set to `TRUE`, the `GREATEST` and `LEAST` functions return null when at least one of the parameters is null.
+
+```sql
+SET edb_redwood_greatest_least TO on;
+
+SELECT GREATEST(1, 2, NULL, 3);
+__OUTPUT__
+greatest
+----------
+
+(1 row)
+```
+
+When `edb_redwood_greatest_least` is set to `FALSE`, null parameters are ignored except when all parameters are null. In that case, the functions return null.
+
+```sql
+SET edb_redwood_greatest_least TO off;
+
+SELECT GREATEST(1, 2, NULL, 3);
+__OUTPUT__
+greatest
+----------
+
+        3
+(1 row)
+```
+```sql
+SELECT GREATEST(NULL, NULL, NULL);
+__OUTPUT__
+greatest
+----------
+
+(1 row)
+```
+
+## edb_redwood_raw_names
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+When `edb_redwood_raw_names` is set to `FALSE`, database object names such as table names, column names, trigger names, program names, and user names appear in uppercase letters when viewed from Redwood catalogs (that is, system catalogs prefixed by `ALL_`, `DBA_`, or `USER_`). In addition, quotation marks enclose names that were created with enclosing quotation marks.
+
+When `edb_redwood_raw_names` is set to `TRUE`, the database object names are displayed as they're stored in the PostgreSQL system catalogs when viewed from the Redwood catalogs. Names created without quotation marks around them appear in lower case as expected in PostgreSQL. Names created enclosed by quotation marks appear as they were created but without the quotation marks.
+
+For example, the following user name is created, and then a session is started with that user:
+
+```sql
+CREATE USER reduser IDENTIFIED BY password;
+edb=# \c - reduser
+Password for user reduser:
+You are now connected to database "edb" as user "reduser".
+```
+
+When connected to the database as `reduser`, the following tables are created:
+
+```sql
+CREATE TABLE all_lower (col INTEGER);
+CREATE TABLE ALL_UPPER (COL INTEGER);
+CREATE TABLE "Mixed_Case" ("Col" INTEGER);
+```
+
+When viewed from the Redwood catalog `USER_TABLES`, with `edb_redwood_raw_names` set to the default value `FALSE`, the names appear in upper case. The exception is the `Mixed_Case` name, which appears as created and also enclosed by quotation marks.
+
+```sql
+edb=> SELECT * FROM USER_TABLES;
+__OUTPUT__
+ schema_name  | table_name   | tablespace_name  | status  | temporary
+--------------+--------------+------------------+---------+-----------
+ REDUSER      | ALL_LOWER    |                  | VALID   | N
+ REDUSER      | ALL_UPPER    |                  | VALID   | N
+ REDUSER      | "Mixed_Case" |                  | VALID   | N
+(3 rows)
+```
+
+When viewed with `edb_redwood_raw_names` set to `TRUE`, the names appear in lower case except for the `Mixed_Case` name, which appears as created but without quotation marks.
+
+```sql
+edb=> SET edb_redwood_raw_names TO true;
+SET
+edb=> SELECT  * FROM USER_TABLES;
+__OUTPUT__
+ schema_name | table_name | tablespace_name  | status | temporary
+-------------+------------+------------------+--------+-----------
+reduser      | all_lower  |                  | VALID  | N
+reduser      | all_upper  |                  | VALID  | N
+reduser      | Mixed_Case |                  | VALID  | N
+(3 rows)
+```
+
+These names now match the case when viewed from the PostgreSQL `pg_tables` catalog:
+
+```sql
+edb=> SELECT schemaname, tablename, tableowner FROM pg_tables WHERE
+tableowner = 'reduser';
+__OUTPUT__
+ schemaname | tablename  | tableowner
+------------+------------+------------
+reduser     | all_lower  | reduser
+reduser     | all_upper  | reduser
+reduser     | Mixed_Case | reduser
+(3 rows)
+```
+
+## edb_redwood_strings
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+If the `edb_redwood_strings` parameter is set to `TRUE`, when a string is concatenated with a null variable or null column, the result is the original string. If `edb_redwood_strings` is set to `FALSE`, the native PostgreSQL behavior is maintained, which is the concatenation of a string with a null variable or null column that gives a null result.
+
+This example shows the difference. The sample application contains a table of employees. This table has a column named `comm` that's null for most employees. The following query is run with `edb_redwood_string` set to `FALSE`. Concatenating a null column with non-empty strings produces a final result of null, so only employees that have a commission appear in the query result. The output line for all other employees is null.
+
+```sql
+SET edb_redwood_strings TO off;
+
+SELECT RPAD(ename,10) || ' ' || TO_CHAR(sal,'99,999.99') || ' ' ||
+TO_CHAR(comm,'99,999.99') "EMPLOYEE COMPENSATION" FROM emp;
+__OUTPUT__
+   EMPLOYEE COMPENSATION
+----------------------------------
+
+ ALLEN        1,600.00     300.00
+ WARD         1,250.00     500.00
+
+ MARTIN       1,250.00   1,400.00
+
+
+
+
+ TURNER       1,500.00        .00
+
+
+(14 rows)
+```
+
+The following is the same query executed when `edb_redwood_strings` is set to `TRUE`. Here, the value of a null column is treated as an empty string. Concatenating an empty string with a non-empty string produces the non-empty string.
+
+```sql
+SET edb_redwood_strings TO on;
+
+SELECT RPAD(ename,10) || ' ' || TO_CHAR(sal,'99,999.99') || ' ' ||
+TO_CHAR(comm,'99,999.99') "EMPLOYEE COMPENSATION" FROM emp;
+__OUTPUT__
+      EMPLOYEE COMPENSATION
+
+----------------------------------
+
+ SMITH 800.00
+ ALLEN 1,600.00 300.00
+ WARD 1,250.00 500.00
+ JONES 2,975.00
+ MARTIN 1,250.00 1,400.00
+ BLAKE 2,850.00
+ CLARK 2,450.00
+ SCOTT 3,000.00
+ KING 5,000.00
+ TURNER 1,500.00 .00
+ ADAMS 1,100.00
+ JAMES 950.00
+ FORD 3,000.00
+ MILLER 1,300.00
+(14 rows)
+```
+
+## edb_stmt_level_tx
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+The term *statement-level transaction isolation* describes the behavior in which a runtime error occurs in a SQL command, and all the updates on the database caused by that single command are rolled back. For example, if a single `UPDATE` command successfully updates five rows, but an attempt to update a sixth row results in an exception, the updates to all six rows made by this `UPDATE` command are rolled back. The effects of prior SQL commands that haven't yet been committed or rolled back are pending until a `COMMIT` or `ROLLBACK` command is executed.
+
+In EDB Postgres Advanced Server, if an exception occurs while executing a SQL command, all the updates on the database since the start of the transaction are rolled back. In addition, the transaction is left in an aborted state, and either a `COMMIT` or `ROLLBACK` command must be issued before another transaction can start.
+
+If `edb_stmt_level_tx` is set to `TRUE`, then an exception doesn't roll back prior uncommitted database updates. If `edb_stmt_level_tx` is set to `FALSE`, then an exception rolls back uncommitted database updates.
+
+!!! Note
+    Use `edb_stmt_level_tx` set to `TRUE` only when necessary, as it can have have a negative performance impact.
+
+This example, run in PSQL, shows that when `edb_stmt_level_tx` is `FALSE`, the abort of the second `INSERT` command also rolls back the first `INSERT` command. In PSQL, you must issue the command `\set AUTOCOMMIT off`. Otherwise every statement commits automatically, which doesn't show the effect of `edb_stmt_level_tx`.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO off;
+
+INSERT INTO emp (empno,ename,deptno) VALUES (9001, 'JONES', 40);
+INSERT INTO emp (empno,ename,deptno) VALUES (9002, 'JONES', 00);
+ERROR:  insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+DETAIL:  Key (deptno)=(0) is not present in table "dept".
+
+COMMIT;
+SELECT empno, ename, deptno FROM emp WHERE empno > 9000;
+__OUTPUT__
+empno  | ename | deptno
+-------+-------+--------
+(0 rows)
+```
+
+In this example, with `edb_stmt_level_tx` set to `TRUE`, the first `INSERT` command wasn't rolled back after the error on the second `INSERT` command. At this point, the first INSERT command can either be committed or rolled back.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO on;
+
+INSERT INTO emp (empno,ename,deptno) VALUES (9001, 'JONES', 40);
+INSERT INTO emp (empno,ename,deptno) VALUES (9002, 'JONES', 00);
+ERROR:  insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+DETAIL:  Key (deptno)=(0) is not present in table "dept"
+
+SELECT empno, ename, deptno FROM emp WHERE empno > 9000;
+__OUTPUT__
+empno  | ename | deptno
+-------+-------+--------
+  9001 | JONES |     40
+(1 row)
+
+COMMIT;
+```
+
+If a `ROLLBACK` command is issued instead of the `COMMIT` command, the insert of employee number `9001` is rolled back as well.
+
+## db_dialect
+
+**Parameter type:** Enum
+
+**Default value:** `postgres`
+
+**Range:** `{postgres | redwood}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+In addition to the native PostgreSQL system catalog `pg_catalog`, EDB Postgres Advanced Server contains an extended catalog view. This is the `sys` catalog for the expanded catalog view. The `db_dialect` parameter controls the order in which these catalogs are searched for name resolution.
+
+When set to `postgres`, the namespace precedence is `pg_catalog` and then `sys`, giving the PostgreSQL catalog the highest precedence. When set to `redwood`, the namespace precedence is `sys` and then `pg_catalog`, giving the expanded catalog views the highest precedence.
+
+## default_with_rowids
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+When set to `on`, `CREATE TABLE` includes a `ROWID` column in newly created tables, which you can then reference in SQL commands. In earlier versions of EDB Postgres Advanced Server, `ROWIDs` were mapped to `OIDs`. With EDB Postgres Advanced Server version 12 and later, the `ROWID` is an autoincrementing value based on a sequence that starts with 1. It's assigned to each row of a table created with the `ROWIDs` option. By default, a unique index is created on a `ROWID` column.
+
+The `ALTER` and `DROP` operations are restricted on a `ROWID` column.
+
+To restore a database with `ROWIDs` with EDB Postgres Advanced Server 11 or an earlier version, you must perform the following:
+
+-   `pg_dump`: If a table includes `OIDs` then specify `--convert-oids-to-rowids` to dump a database. Otherwise, ignore the `OIDs` to continue table creation on EDB Postgres Advanced Server version 12 and later.
+-   `pg_upgrade`: Errors out. But if a table includes `OIDs` or `ROWIDs`, then you must perform the following:
+    1.  Take a dump of the tables by specifying the `--convert-oids-to-rowids` option.
+    2.  Drop the tables, and then perform the upgrade.
+    3.  After the upgrade is successful, restore the dump into a new cluster that contains the dumped tables into a target database.
+
+## optimizer_mode
+
+**Parameter type:** Enum
+
+**Default value:** `choose`
+
+**Range:** `{choose | ALL_ROWS | FIRST_ROWS | FIRST_ROWS_10 | FIRST_ROWS_100 | FIRST_ROWS_1000}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Sets the default optimization mode for analyzing optimizer hints.
+
+The following table shows the possible values.
+
+| Hint              | Description                                                                                                            |
+| ----------------- | ---------------------------------------------------------------------------------------------------------------------- |
+| `ALL_ROWS`        | Optimizes for retrieval of all rows of the result set.                                                                 |
+| `CHOOSE`          | Does no default optimization based on assumed number of rows to retrieve from the result set. This is the default. |
+| `FIRST_ROWS`      | Optimizes for retrieval of only the first row of the result set.                                                       |
+| `FIRST_ROWS_10`   | Optimizes for retrieval of the first 10 rows of the results set.                                                       |
+| `FIRST_ROWS_100`  | Optimizes for retrieval of the first 100 rows of the result set.                                                       |
+| `FIRST_ROWS_1000` | Optimizes for retrieval of the first 1000 rows of the result set.                                                      |
+
+These optimization modes are based on the assumption that the client submitting the SQL command is interested in viewing only the first `n` rows of the result set and then abandons the rest of the result set. Resources allocated to the query are adjusted as such.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx
new file mode 100644
index 00000000000..41d34a503da
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options.mdx
@@ -0,0 +1,392 @@
+---
+title: "Customized options"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.18.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.018.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/12_customized_options/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="customized_options" class="registered_link"></div>
+
+## custom_variable_classes
+
+The `custom_variable_classes` parameter was deprecated in EDB Postgres Advanced Server 9.2. Parameters that previously depended on this parameter no longer require its support. In previous releases of EDB Postgres Advanced Server, `custom_variable_classes` was required by parameters not normally known to be added by add-on modules, such as procedural languages.
+
+## dbms_alert.max_alerts
+
+**Parameter type:** Integer
+
+**Default value:** 100
+
+**Range:** 0 to 500
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the maximum number of concurrent alerts allowed on a system using the `DBMS_ALERTS` package.
+
+## dbms_pipe.total_message_buffer
+
+**Parameter type:** Integer
+
+**Default value:** 30 Kb
+
+**Range:** 30 Kb to 256 Kb
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the total size of the buffer used for the `DBMS_PIPE` package.
+
+## index_advisor.enabled
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Temporarily suspends Index Advisor in an EDB-PSQL or PSQL session. To use this configuration parameter, the Index Advisor plugin `index_advisor` must be loaded in the EDB-PSQL or PSQL session.
+
+You can load the Index Advisor plugin as follows:
+
+```sql
+$ psql -d edb -U enterprisedb
+Password for user enterprisedb:
+psql (14.0.0)
+Type "help" for help.
+
+edb=# LOAD 'index_advisor';
+LOAD
+```
+
+Use the `SET` command to change the parameter setting to control whether Index Advisor generates an alternative query plan:
+
+```text
+edb=# SET index_advisor.enabled TO off;
+SET
+edb=# EXPLAIN SELECT * FROM t WHERE a < 10000;
+__OUTPUT__
+                     QUERY PLAN
+
+-------------------------------------------------------
+ Seq Scan on t (cost=0.00..1693.00 rows=9864 width=8)
+   Filter: (a < 10000)
+(2 rows)
+```
+```sql
+edb=# SET index_advisor.enabled TO on;
+SET
+edb=# EXPLAIN SELECT * FROM t WHERE a < 10000;
+__OUTPUT__
+                      QUERY PLAN
+-----------------------------------------------------------------------------
+ Seq Scan on t (cost=0.00..1693.00 rows=9864 width=8)
+   Filter: (a < 10000)
+ Result (cost=0.00..327.88 rows=9864 width=8)
+   One-Time Filter: '===[ HYPOTHETICAL PLAN ]==='::text
+   -> Index Scan using "<hypothetical-index>:1" on t (cost=0.00..327.88
+ rows=9864 width=8)
+          Index Cond: (a < 10000)
+(6 rows)
+```
+
+## edb_sql_protect.enabled
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Controls whether SQL/Protect is actively monitoring protected roles by analyzing SQL statements issued by those roles and reacting according to the setting of `edb_sql_protect.level`. When you're ready to begin monitoring with SQL/Protect, set this parameter to `on`.
+
+## edb_sql_protect.level
+
+**Parameter type:** Enum
+
+**Default value:** `passive`
+
+**Range:** `{learn | passive | active}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the action taken by SQL/Protect when a SQL statement is issued by a protected role.
+
+You can set this parameter to one of the following values to use learn mode, passive mode, or active mode:
+
+-   `learn`. Tracks the activities of protected roles and records the relations used by the roles. Use this value when initially configuring SQL/Protect so the expected behaviors of the protected applications are learned.
+-   `passive`. Issues warnings if protected roles are breaking the defined rules but doesn't stop any SQL statements from executing. This is the next step after SQL/Protect learns the expected behavior of the protected roles. This essentially behaves in intrusion detection mode. You can run it in production if you monitor it.
+-   `active`. Stops all invalid statements for a protected role. This behavior acts as a SQL firewall that prevents dangerous queries from running. This is particularly effective against early penetration testing when the attacker is trying to determine the vulnerability point and the type of database behind the application. Not only does SQL/Protect close those vulnerability points, it tracks the blocked queries. This behavior can alert administrators before the attacker finds an alternative method of penetrating the system.
+
+If you're using SQL/Protect for the first time, set `edb_sql_protect.level` to `learn`.
+
+## edb_sql_protect.max_protected_relations
+
+**Parameter type:** Integer
+
+**Default value:** 1024
+
+**Range:** 1 to 2147483647
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the maximum number of relations that can be protected per role. The total number of protected relations for the server is the number of protected relations times the number of protected roles. Every protected relation consumes space in shared memory. The space for the maximum possible protected relations is reserved during database server startup.
+
+If the server is started when `edb_sql_protect.max_protected_relations` is set to a value outside of the valid range (for example, a value of 2,147,483,648), then a warning message is logged in the database server log file:
+
+```sql
+2014-07-18 16:04:12 EDT WARNING: invalid value for parameter
+"edb_sql_protect.max_protected_relations": "2147483648"
+2014-07-18 16:04:12 EDT HINT: Value exceeds integer range.
+```
+
+The database server starts successfully but with `edb_sql_protect.max_protected_relations` set to the default value of 1024.
+
+Although the upper range for the parameter is listed as the maximum value for an integer data type, the practical setting depends on how much shared memory is available and the parameter value used during database server startup.
+
+As long as the space required can be reserved in shared memory, the value is acceptable. If the value is such that the space in shared memory can't be reserved, the database server startup fails with an error message like the following:
+
+```sql
+2014-07-18 15:22:17 EDT FATAL: could not map anonymous shared memory:
+Cannot allocate memory
+2014-07-18 15:22:17 EDT HINT: This error usually means that PostgreSQL's
+request for a shared memory segment exceeded available memory, swap
+space or huge pages. To reduce the request size (currently 2070118400
+bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing
+shared_buffers or max_connections.
+```
+
+In this case, reduce the parameter value until you can start the database server successfully.
+
+## edb_sql_protect.max_protected_roles
+
+**Parameter type:** Integer
+
+**Default value:** 64
+
+**Range:** 1 to 2147483647
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the maximum number of roles that can be protected.
+
+Every protected role consumes space in shared memory. The server reserves space for the number of protected roles times the number of protected relations (`edb_sql_protect.max_protected_relations`). The space for the maximum possible protected roles is reserved during database server startup.
+
+If the database server is started when `edb_sql_protect.max_protected_roles` is set to a value outside of the valid range (for example, a value of 2,147,483,648), then a warning message is logged in the database server log file:
+
+```sql
+2014-07-18 16:04:12 EDT WARNING: invalid value for parameter
+"edb_sql_protect.max_protected_roles": "2147483648"
+2014-07-18 16:04:12 EDT HINT: Value exceeds integer range.
+```
+
+The database server starts successfully but with `edb_sql_protect.max_protected_roles` set to the default value of 64.
+
+Although the upper range for the parameter is listed as the maximum value for an integer data type, the practical setting depends on how much shared memory is available and the parameter value used during database server startup.
+
+As long as the space required can be reserved in shared memory, the value is acceptable. If the value is such that the space in shared memory can't be reserved, the database server startup fails with an error message such as the following:
+
+```sql
+2014-07-18 15:22:17 EDT FATAL: could not map anonymous shared memory:
+Cannot allocate memory
+2014-07-18 15:22:17 EDT HINT: This error usually means that PostgreSQL's
+request for a shared memory segment exceeded available memory, swap
+space or huge pages. To reduce the request size (currently 2070118400
+bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing
+shared_buffers or max_connections.
+```
+
+In this cases, reduce the parameter value until you can start the database server successfully.
+
+## edb_sql_protect.max_queries_to_save
+
+**Parameter type:** Integer
+
+**Default value:** 5000
+
+**Range:** 100 to 2147483647
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the maximum number of offending queries to save in the view `edb_sql_protect_queries`.
+
+Every saved query consumes space in shared memory. The space for the maximum possible queries that can be saved is reserved during database server startup.
+
+If the database server is started when `edb_sql_protect.max_queries_to_save` is set to a value outside of the valid range (for example, a value of 10), then a warning message is logged in the database server log file:
+
+```sql
+2014-07-18 13:05:31 EDT WARNING:  10 is outside the valid range for
+parameter "edb_sql_protect.max_queries_to_save" (100 .. 2147483647)
+```
+
+The database server starts successfully but with `edb_sql_protect.max_queries_to_save` set to the default value of 5000.
+
+Although the upper range for the parameter is listed as the maximum value for an integer data type, the practical setting depends on how much shared memory is available and the parameter value used during database server startup.
+
+As long as the space required can be reserved in shared memory, the value is acceptable. If the value is such that the space in shared memory can't be reserved, the database server startup fails with an error message like the following:
+
+```sql
+2014-07-18 15:22:17 EDT FATAL: could not map anonymous shared memory:
+Cannot allocate memory
+2014-07-18 15:22:17 EDT HINT: This error usually means that PostgreSQL's
+request for a shared memory segment exceeded available memory, swap
+space or huge pages. To reduce the request size (currently 2070118400
+bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing
+shared_buffers or max_connections.
+```
+
+In this case, reduce the parameter value until you can start the database server successfully.
+
+## edb_wait_states.directory
+
+**Parameter type:** String
+
+**Default value:** `edb_wait_states`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the directory path where the EDB wait states log files are stored. Use a full, absolute path, not a relative path. However, the default setting is `edb_wait_states`, which makes `$PGDATA/edb_wait_states` the default directory location.  See [EDB Wait States](/pg_extensions/wait_states/) for more information.
+
+## edb_wait_states.retention_period
+
+**Parameter type:** Integer
+
+**Default value:** 604800s
+
+**Range:** 86400s to 2147483647s
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the time to wait before deleting the log files for EDB wait states. The default is 604,800 seconds, which is 7 days. See [EDB Wait States](/pg_extensions/wait_states/) for more information.
+
+## edb_wait_states.sampling_interval
+
+**Parameter type:** Integer
+
+**Default value:** 1s
+
+**Range:** 1s to 2147483647s
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Sets the timing interval between two sampling cycles for EDB wait states. The default setting is 1 second. See [EDB Wait States](/pg_extensions/wait_states/) for more information.
+
+## edbldr.empty_csv_field
+
+**Parameter type:** Enum
+
+**Default value:** `NULL`
+
+**Range:** `{NULL | empty_string | pgsql}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Use the `edbldr.empty_csv_field` parameter to specify how EDB\*Loader treats an empty string. The table shows the valid values for the `edbldr.empty_csv_field` parameter.
+
+| Parameter setting   | EDB\*Loader behavior                                                                                              |
+| ------------------- | ----------------------------------------------------------------------------------------------------------------- |
+| `NULL`              | An empty field is treated as `NULL`.                                                                              |
+| `empty_string`      | An empty field is treated as a string of length zero.                                                             |
+| `pgsql`             | An empty field is treated as a `NULL` if it doesn't contain quotes and as an empty string if it contains quotes. |
+
+For more information about the `edbldr.empty_csv_field` parameter in EDB\*Loader, see [Tools, utilities, and components](../../02_edb_loader).
+
+## utl_encode.uudecode_redwood
+
+**Parameter type:** Boolean
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+When set to `TRUE`, EDB Postgres Advanced Server’s `UTL_ENCODE.UUDECODE` function can decode uuencoded data that was created by the Oracle implementation of the `UTL_ENCODE.UUENCODE` function.
+
+When set to `FALSE`, EDB Postgres Advanced Server’s `UTL_ENCODE.UUDECODE` function can decode uuencoded data created by EDB Postgres Advanced Server’s `UTL_ENCODE.UUENCODE` function.
+
+## utl_file.umask
+
+**Parameter type:** String
+
+**Default value:** 0077
+
+**Range:** Octal digits for umask settings
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+The `utl_file.umask` parameter sets the *file mode creation mask* in a manner similar to the Linux `umask` command. This is for use only within the EDB Postgres Advanced Server `UTL_FILE` package.
+
+!!! Note
+    The `utl_file.umask` parameter isn't supported on Windows systems.
+
+The value specified for `utl_file.umask` is a three- or four-character octal string that's valid for the Linux `umask` command. The setting determines the permissions on files created by the `UTL_FILE` functions and procedures.
+
+The following shows the results of the default `utl_file.umask` setting of 0077. All permissions are denied on users belonging to the `enterprisedb` group as well as all other users. Only the user `enterprisedb` has read and write permissions on the file.
+
+```text
+-rw------- 1 enterprisedb enterprisedb 21 Jul 24 16:08 utlfile
+```
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/13_ungrouped.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/13_ungrouped.mdx
new file mode 100644
index 00000000000..07771383ae8
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/13_ungrouped.mdx
@@ -0,0 +1,101 @@
+---
+title: "Ungrouped configuration parameters"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.19.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.019.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/13_ungrouped/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ungrouped" class="registered_link"></div>
+
+These configuration parameters apply only to EDB Postgres Advanced Server and are for a specific, limited purpose.
+
+## nls_length_semantics
+
+**Parameter type:** Enum
+
+**Default value:** `byte`
+
+**Range:** `{byte | char}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Superuser
+
+This parameter has no effect in EDB Postgres Advanced Server. For example, this form of the `ALTER SESSION` command is accepted in EDB Postgres Advanced Server without throwing a syntax error. However, it doesn't alter the session environment.
+
+```sql
+ALTER SESSION SET nls_length_semantics = char;
+```
+
+!!! Note
+    Since setting this parameter has no effect on the server environment, it doesn't appear in the system view `pg_settings`.
+
+## query_rewrite_enabled
+
+**Parameter type:** Enum
+
+**Default value:** `false`
+
+**Range:** `{true | false | force}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+This parameter has no effect in EDB Postgres Advanced Server. For example, this form of the `ALTER SESSION` command is accepted in EDB Postgres Advanced Server without throwing a syntax error. However, it doesn't alter the session environment.
+
+```sql
+ALTER SESSION SET query_rewrite_enabled = force;
+```
+
+!!! Note
+    Since setting this parameter has no effect on the server environment, it doesn't appear in the system view `pg_settings`.
+
+## query_rewrite_integrity
+
+**Parameter type:** Enum
+
+**Default value:** `enforced`
+
+**Range:** `{enforced | trusted | stale_tolerated}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Superuser
+
+This parameter has no effect in EDB Postgres Advanced Server. For example, this form of the `ALTER SESSION` command is accepted in EDB Postgres Advanced Server without throwing a syntax error. However, it doesn't alter the session environment.
+
+```sql
+ALTER SESSION SET query_rewrite_integrity = stale_tolerated;
+```
+
+!!! Note
+    Since setting this parameter has no effect on the server environment, it doesn't appear in the system view `pg_settings`.
+
+## timed_statistics
+
+**Parameter type:** Boolean
+
+**Default value:** `true`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Per session
+
+**When value changes take effect:** Immediate
+
+**Required authorization to activate:** Session user
+
+Controls collecting timing data for the Dynamic Runtime Instrumentation Tools Architecture (DRITA) feature. When set to `on`, timing data is collected.
+
+!!! Note
+    When EDB Postgres Advanced Server is installed, the `postgresql.conf` file contains an explicit entry that setts `timed_statistics` to `off`. If this entry is commented out and the configuration file is reloaded, timed statistics collection uses the default value, which is `on`.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx
new file mode 100644
index 00000000000..bc83700ebe8
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver.mdx
@@ -0,0 +1,194 @@
+---
+title: "Audit archiving parameters"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/14_audit_archiver/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="audit_archiver" class="registered_link"></div>
+
+These configuration parameters are used by the EDB Postgres Advanced Server database [audit archiving feature](../../../epas_security_guide/05_edb_audit_logging/08_audit_log_archiving/).
+
+## edb_audit_archiver
+
+**Parameter type:** Enum
+
+**Default value:** `false`
+
+**Range:** `{true | false}`
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Restart
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Enables or disables database audit archiving. 
+
+## edb_audit_archiver_timeout
+
+**Parameter type:** Integer
+
+**Default value:** 300s
+
+**Range:** 30s to 1d
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Enforces a timeout in seconds when a database attempts to archive a log file. 
+
+## edb_audit_archiver_filename_prefix
+
+**Parameter type:** String
+
+**Default value:** `audit-`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the file name of an audit log file that needs to be archived. The file name must align with the `edb_audit_filename` parameter. The audit files with `edb_audit_archiver_filename_prefix` in the `edb_audit_directory` are eligible for compression or expiration.
+
+## edb_audit_archiver_compress_time_limit
+
+**Parameter type:** Integer
+
+**Default value:** -1
+
+**Allowed value:** 0, -1, or any positive number value in seconds
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the time in seconds after which audit logs are eligible for compression. The possible values to set this parameter are: 
+
+-  `0`. Compression starts as soon as the log file isn't a current file. 
+-  `-1`. Compression of the log file on a timely basis doesn't occur.
+
+## edb_audit_archiver_compress_size_limit
+
+**Parameter type:** Integer
+
+**Default value:** -1
+
+**Allowed value:** 0, -1, or any positive number value in megabytes
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies a file size threshold in megabytes, after which audit logs are eligible for compression. If the parameter is set to -1, no compression of the log file occurs based on size.
+
+## edb_audit_archiver_compress_command
+
+**Parameter type:** String
+
+**Default value:** `gzip %p`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the command to execute compressing of the audit log files. The default value for `edb_audit_archiver_compress_command` is `gzip %p`. The `gzip` provides a standard method of compressing files. The `%p` in the string is replaced by the path name of the file to archive.
+
+## edb_audit_archiver_compress_suffix
+
+**Parameter type:** String
+
+**Default value:** `.gz`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the file name of an already compressed log file. The file name must align with `edb_audit_archiver_compress_command`. The default file name is `.gz`. 
+
+## edb_audit_archiver_expire_time_limit
+
+**Parameter type:** Integer
+
+**Default value:** -1
+
+**Allowed value:** 0, -1, or any positive number value in seconds
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the time in seconds after which audit logs are eligible to expire. The possible values to set this parameter are: 
+
+-  `0`. Expiration starts as soon as the log file isn't a current file. 
+-  `-1`. Expiration of the log file on a timely basis doesn't occur.
+
+## edb_audit_archiver_expire_size_limit 
+
+**Parameter type:** Integer
+
+**Default value:** -1
+
+**Allowed value:** 0, -1, or any positive number value in megabytes
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies a file size threshold in megabytes, after which audit logs are eligible to expire. If the parameter is set to -1, no expiration of a log file based on size occurs.
+
+## edb_audit_archiver_expire_command 
+
+**Parameter type:** String
+
+**Default value:** ''
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Specifies the command to execute on an expired audit log file before removal.
+
+## edb_audit_archiver_sort_file 
+
+**Parameter type:** String
+
+**Default value:** `mtime`
+
+**Range:** n/a
+
+**Minimum scope of effect:** Cluster
+
+**When value changes take effect:** Reload
+
+**Required authorization to activate:** EDB Postgres Advanced Server service account
+
+Identifies the oldest log file to sort alphabetically or based on `mtime`. 
+
+-  `mtime` sorts files based on file modification time. 
+-  `alphabetic` sorts files alphabetically based on the file name.
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx
new file mode 100644
index 00000000000..65b3f98a07a
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/attribute_descriptions.mdx
@@ -0,0 +1,15 @@
+---
+title: "Description of parameter attributes"
+---
+
+The description of each group of parameters includes this list of attributes:
+
+-   **Parameter type.** Type of values the parameter can accept. See [Setting configuration parameters](../01_setting_new_parameters/#setting_configuration_parameters) for a discussion of parameter type values.
+-   **Default value.** Default setting if a value isn't explicitly set in the configuration file.
+-   **Range.** Allowed range of values.
+-   **Minimum scope of effect.** Smallest scope for which a distinct setting can be made. Generally, the minimal scope of a distinct setting is either:
+    -  The entire cluster, meaning the setting is the same for all databases in the cluster and its sessions 
+    -  `per session`, which means the setting might vary by role, database, or individual session. 
+    This attribute has the same meaning as the `Scope of effect` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/).
+-   **When value changes take effect.** Least invasive action required to activate a change to a parameter’s value. All parameter setting changes made in the configuration file can be put into effect by restarting the database server. However, certain parameters require a database server `restart`. Some parameter setting changes can be put into effect with a `reload` of the configuration file without stopping the database server. Finally, other parameter setting changes can be put into effect with some client-side action whose result is `immediate`. This attribute has the same meaning as the `When takes effect` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/).
+-   **Required authorization to activate.** The type of user authorization to activate a change to a parameter’s setting. If a database server restart or a configuration file reload is required, then the user must be an EDB Postgres Advanced Server service account (`enterprisedb` or `postgres`, depending on the EDB Postgres Advanced Server compatibility installation mode). This attribute has the same meaning as the `Authorized user` column in the table of [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/).
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/index.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/index.mdx
new file mode 100644
index 00000000000..7a299650e61
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Configuration parameters by functionality"
+indexCards: simple
+description: "Provides a detailed description of the configuration parameters, grouped by function"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.11.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.011.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/03_configuration_parameters_by_functionality/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="configuration_parameters_by_functionality" class="registered_link"></div>
+
+Configuration parameters can be grouped by function. See [Description of parameter attributes](attribute_descriptions) for the list of attributes included in each configuration parameter description. 
+
+<div class="toctree" maxdepth="3">
+
+top_performance_related_parameters resource_usage_memory resource_usage_edb_resource_manager query_tuning query_tuning_planner_method_configuration reporting_and_logging_what_to_log auditing_settings ccd_locale_and_formatting ccd_statement_behaviour ccd_other_defaults compatibility_options customized_options ungrouped audit_archiver
+
+</div>
diff --git a/product_docs/docs/epas/16/database_administration/01_configuration_parameters/index.mdx b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/index.mdx
new file mode 100644
index 00000000000..0dd62389ff1
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/01_configuration_parameters/index.mdx
@@ -0,0 +1,25 @@
+---
+title: "Setting configuration parameters"
+indexCards: simple
+description: "How to set configuration parameters that control the database server’s behavior and environment"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.08.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.008.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="configuration_parameters" class="registered_link"></div>
+
+The EDB Postgres Advanced Server configuration parameters control various aspects of the database server’s behavior and environment such as data file and log file locations, connection, authentication and security settings, resource allocation and consumption, archiving and replication settings, error logging and statistics gathering, optimization and performance tuning, and locale and formatting settings
+
+Configuration parameters that apply only to EDB Postgres Advanced Server are noted in [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/), which lists all EDB Postgres Advanced Server configuration parameters along with a number of key attributes of the parameters.
+
+You can find more information about configuration parameters in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/runtime-config.html).
+
+<div class="toctree" maxdepth="3">
+
+setting_new_parameters summary_of_configuration_parameters configuration_parameters_by_functionality
+
+</div>
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/control_file_examples.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/control_file_examples.mdx
new file mode 100644
index 00000000000..1fc84dd2d81
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/control_file_examples.mdx
@@ -0,0 +1,486 @@
+---
+title: "EDB*Loader control file examples"
+navTitle: "Control file examples"
+description: "Provides examples of control files and their corresponding data files"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/control_file_examples/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The following are some examples of control files and their corresponding data files.
+
+## Delimiter-separated field data file
+
+This control file uses a delimiter-separated data file that appends rows to the `emp` table. The `APPEND` clause is used to allow inserting additional rows into the `emp` table.
+
+
+```sql
+LOAD DATA
+  INFILE 'emp.dat'
+    BADFILE 'emp.bad'
+  APPEND
+  INTO TABLE emp
+    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
+    TRAILING NULLCOLS
+  (
+    empno,
+    ename,
+    job,
+    mgr,
+    hiredate,
+    sal,
+    deptno,
+    comm
+  )
+```
+
+The following is the corresponding delimiter-separated data file:
+
+```sql
+9101,ROGERS,CLERK,7902,17-DEC-10,1980.00,20
+9102,PETERSON,SALESMAN,7698,20-DEC-10,2600.00,30,2300.00
+9103,WARREN,SALESMAN,7698,22-DEC-10,5250.00,30,2500.00
+9104,"JONES, JR.",MANAGER,7839,02-APR-09,7975.00,20
+```
+
+The use of the `TRAILING NULLCOLS` clause allows you to omit the last field supplying the `comm` column from the first and last records. The `comm` column is set to null for the rows inserted from these records.
+
+Double quotation marks surround the value `JONES, JR.` in the last record since the comma delimiter character is part of the field value.
+
+This query displays the rows added to the table after the EDB\*Loader session:
+
+```sql
+SELECT * FROM emp WHERE empno > 9100;
+__OUTPUT__
+ empno| ename     | job     | mgr|   hiredate        | sal   | comm   |deptno
+------+-----------+---------+----+-------------------+-------+--------+------
+  9101| ROGERS    | CLERK   |7902| 17-DEC-10 00:00:00|1980.00|        |  20
+  9102| PETERSON  | SALESMAN|7698| 20-DEC-10 00:00:00|2600.00| 2300.00|  30
+  9103| WARREN    | SALESMAN|7698| 22-DEC-10 00:00:00|5250.00| 2500.00|  30
+  9104| JONES, JR.| MANAGER |7839| 02-APR-09 00:00:00|7975.00|        |  20
+(4 rows)
+```
+
+## Fixed-width field data file
+
+This control file loads the same rows into the `emp` table. It uses a data file containing fixed-width fields. The `FIELDS TERMINATED BY` and `OPTIONALLY ENCLOSED BY` clauses are absent. Instead, each field includes the `POSITION` clause.
+
+```sql
+LOAD DATA
+  INFILE 'emp_fixed.dat'
+    BADFILE 'emp_fixed.bad'
+  APPEND
+  INTO TABLE emp
+    TRAILING NULLCOLS
+  (
+    empno POSITION (1:4),
+    ename POSITION (5:14),
+    job POSITION (15:23),
+    mgr POSITION (24:27),
+    hiredate POSITION (28:38),
+    sal POSITION (39:46),
+    deptno POSITION (47:48),
+    comm POSITION (49:56)
+  )
+```
+
+The following is the corresponding data file containing fixed-width fields:
+
+```sql
+9101ROGERS    CLERK    790217-DEC-10    1980.0020
+9102PETERSON  SALESMAN 769820-DEC-10    2600.0030 2300.00
+9103WARREN    SALESMAN 769822-DEC-10    5250.0030 2500.00
+9104JONES, JR.MANAGER  783902-APR-09    7975.0020
+```
+
+## Single physical record data file – RECORDS DELIMITED BY clause
+
+This control file loads the same rows into the `emp` table but uses a data file with one physical record. Terminate each record loaded as a row in the table using a semicolon (`;`). The `RECORDS DELIMITED BY` clause specifies this value.
+
+```sql
+LOAD DATA
+  INFILE 'emp_recdelim.dat'
+    BADFILE 'emp_recdelim.bad'
+  APPEND
+  INTO TABLE emp
+    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
+    RECORDS DELIMITED BY ';'
+    TRAILING NULLCOLS
+  (
+    empno,
+    ename,
+    job,
+    mgr,
+    hiredate,
+    sal,
+    deptno,
+    comm
+  )
+```
+
+The following is the corresponding data file. The content is a single physical record in the data file. The record delimiter character is included following the last record, that is, at the end of the file.
+
+```sql
+9101,ROGERS,CLERK,7902,17-DEC-10,1980.00,20,;9102,PETERSON,SALESMAN,7698,20-DEC-10,
+2600.00,30,2300.00;9103,WARREN,SALESMAN,7698,22-DEC-10,5250.00,30,2500.00;9104,"JONES, 
+JR.",MANAGER,7839,02-APR-09,7975.00,20,;
+```
+
+## FILLER clause
+
+This control file uses the `FILLER` clause in the data fields for the `sal` and `comm` columns. EDB\*Loader ignores the values in these fields and sets the corresponding columns to null.
+
+```sql
+LOAD DATA
+  INFILE       'emp_fixed.dat'
+    BADFILE    'emp_fixed.bad'
+  APPEND
+  INTO TABLE emp
+    TRAILING NULLCOLS
+  (
+    empno       POSITION (1:4),
+    ename       POSITION (5:14),
+    job         POSITION (15:23),
+    mgr         POSITION (24:27),
+    hiredate    POSITION (28:38),
+    sal         FILLER POSITION (39:46),
+    deptno      POSITION (47:48),
+    comm        FILLER POSITION (49:56)
+  )
+```
+
+Using the same fixed-width data file as in the prior fixed-width field example, the resulting rows in the table appear as follows:
+
+```sql
+SELECT * FROM emp WHERE empno > 9100;
+__OUTPUT__
+ empno| ename     | job     | mgr|   hiredate        | sal   | comm   |deptno
+------+-----------+---------+----+-------------------+-------+--------+------
+  9101| ROGERS    | CLERK   |7902| 17-DEC-10 00:00:00|       |        |  20
+  9102| PETERSON  | SALESMAN|7698| 20-DEC-10 00:00:00|       |        |  30
+  9103| WARREN    | SALESMAN|7698| 22-DEC-10 00:00:00|       |        |  30
+  9104| JONES, JR.| MANAGER |7839| 02-APR-09 00:00:00|       |        |  20
+(4 rows)
+```
+
+## BOUNDFILLER clause
+
+This control file uses the `BOUNDFILLER` clause in the data fields for the `job` and `mgr` columns. EDB\*Loader ignores the values in these fields and sets the corresponding columns to null in the same manner as the `FILLER` clause. However, unlike columns with the `FILLER` clause, you can use columns with the `BOUNDFILLER` clause in an expression, as shown for column `jobdesc`.
+
+```sql
+LOAD DATA
+  INFILE    'emp.dat'
+    BADFILE 'emp.bad'
+  APPEND
+  INTO TABLE empjob
+    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
+    TRAILING NULLCOLS
+  (
+    empno,
+    ename,
+    job          BOUNDFILLER,
+    mgr          BOUNDFILLER,
+    hiredate     FILLER,
+    sal          FILLER,
+    deptno       FILLER,
+    comm         FILLER,
+    jobdesc      ":job || ' for manager ' || :mgr"
+  )
+```
+
+The following is the delimiter-separated data file used in this example:
+
+```sql
+9101,ROGERS,CLERK,7902,17-DEC-10,1980.00,20
+9102,PETERSON,SALESMAN,7698,20-DEC-10,2600.00,30,2300.00
+9103,WARREN,SALESMAN,7698,22-DEC-10,5250.00,30,2500.00
+9104,"JONES, JR.",MANAGER,7839,02-APR-09,7975.00,20
+```
+
+The following table is loaded using the preceding control file and data file:
+
+```sql
+CREATE TABLE empjob (
+    empno               NUMBER(4) NOT NULL CONSTRAINT empjob_pk PRIMARY KEY,
+    ename               VARCHAR2(10),
+    job                 VARCHAR2(9),
+    mgr                 NUMBER(4),
+    jobdesc             VARCHAR2(25)
+);
+```
+
+The resulting rows in the table appear as follows:
+
+```sql
+SELECT * FROM empjob;
+__OUTPUT__
+ empno |    ename   | job | mgr |         jobdesc
+-------+------------+-----+-----+---------------------------
+ 9101  | ROGERS     |     |     | CLERK for manager 7902
+ 9102  | PETERSON   |     |     | SALESMAN for manager 7698
+ 9103  | WARREN     |     |     | SALESMAN for manager 7698
+ 9104  | JONES, JR. |     |     | MANAGER for manager 7839
+(4 rows)
+```
+
+## Field types with length specification
+
+This control file contains the field-type clauses with the length specification:
+
+```sql
+LOAD DATA
+  INFILE 'emp_fixed.dat'
+    BADFILE 'emp_fixed.bad'
+  APPEND
+  INTO TABLE emp
+    TRAILING NULLCOLS
+  (
+    empno       CHAR(4),
+    ename       CHAR(10),
+    job         POSITION (15:23) CHAR(9),
+    mgr         INTEGER EXTERNAL(4),
+    hiredate    DATE(11) "DD-MON-YY",
+    sal         DECIMAL EXTERNAL(8),
+    deptno      POSITION (47:48),
+    comm        POSITION (49:56) DECIMAL EXTERNAL(8)
+  )
+```
+
+!!! Note
+    You can use the `POSITION` clause and the `fieldtype(length)` clause individually or in combination as long as each field definition contains at least one of the two clauses.
+
+The following is the corresponding data file containing fixed-width fields:
+
+```sql
+9101ROGERS     CLERK      790217-DEC-10  1980.0020
+9102PETERSON   SALESMAN   769820-DEC-10  2600.0030  2300.00
+9103WARREN     SALESMAN   769822-DEC-10  5250.0030  2500.00
+9104JONES, JR. MANAGER    783902-APR-09  7975.0020
+```
+
+The resulting rows in the table appear as follows:
+
+```sql
+SELECT * FROM emp WHERE empno > 9100;
+__OUTPUT__
+ empno| ename     | job     | mgr|   hiredate        | sal   | comm   |deptno
+------+-----------+---------+----+-------------------+-------+--------+------
+  9101| ROGERS    | CLERK   |7902| 17-DEC-10 00:00:00|1980.00|        |  20
+  9102| PETERSON  | SALESMAN|7698| 20-DEC-10 00:00:00|2600.00| 2300.00|  30
+  9103| WARREN    | SALESMAN|7698| 22-DEC-10 00:00:00|5250.00| 2500.00|  30
+  9104| JONES, JR.| MANAGER |7839| 02-APR-09 00:00:00|7975.00|        |  20
+(4 rows)
+```
+
+## NULLIF clause
+
+This example uses the `NULLIF` clause on the `sal` column to set it to null for employees of job `MANAGER`. It also uses the clause on the `comm` column to set it to null if the employee isn't a `SALESMAN` and isn't in department `30`. In other words, a `comm` value is accepted if the employee is a `SALESMAN` or is a member of department `30`.
+
+The following is the control file:
+
+```sql
+LOAD DATA
+  INFILE    'emp_fixed_2.dat'
+    BADFILE 'emp_fixed_2.bad'
+  APPEND
+  INTO TABLE emp
+    TRAILING NULLCOLS
+  (
+    empno       POSITION (1:4),
+    ename       POSITION (5:14),
+    job         POSITION (15:23),
+    mgr         POSITION (24:27),
+    hiredate    POSITION (28:38),
+    sal         POSITION (39:46) NULLIF job = 'MANAGER',
+    deptno      POSITION (47:48),
+    comm        POSITION (49:56) NULLIF job <> 'SALESMAN' AND deptno <> '30'
+  )
+```
+
+The following is the corresponding data file:
+
+```sql
+9101ROGERS       CLERK        790217-DEC-10     1980.0020
+9102PETERSON     SALESMAN     769820-DEC-10     2600.0030     2300.00
+9103WARREN       SALESMAN     769822-DEC-10     5250.0030     2500.00
+9104JONES, JR.   MANAGER      783902-APR-09     7975.0020
+9105ARNOLDS      CLERK        778213-SEP-10     3750.0030     800.00
+9106JACKSON      ANALYST      756603-JAN-11     4500.0040     2000.00
+9107MAXWELL      SALESMAN     769820-DEC-10     2600.0010     1600.00
+```
+
+The resulting rows in the table appear as follows:
+
+```sql
+SELECT empno, ename, job, NVL(TO_CHAR(sal),'--null--') "sal",
+  NVL(TO_CHAR(comm),'--null--') "comm", deptno FROM emp WHERE empno > 9100;
+__OUTPUT__
+ empno |   ename    |    job   |   sal    |   comm   | deptno
+-------+------------+----------+----------+----------+-------
+  9101 | ROGERS     | CLERK    | 1980.00  | --null-- |   20
+  9102 | PETERSON   | SALESMAN | 2600.00  | 2300.00  |   30
+  9103 | WARREN     | SALESMAN | 5250.00  | 2500.00  |   30
+  9104 | JONES, JR. | MANAGER  | --null-- | --null-- |   20
+  9105 | ARNOLDS    | CLERK    | 3750.00  |  800.00  |   30
+  9106 | JACKSON    | ANALYST  | 4500.00  | --null-- |   40
+  9107 | MAXWELL    | SALESMAN | 2600.00  | 1600.00  |   10
+(7 rows)
+```
+
+!!! Note
+    The `sal` column for employee `JONES, JR.` is null since the job is `MANAGER`.
+
+The `comm` values from the data file for employees `PETERSON`, `WARREN`, `ARNOLDS`, and `MAXWELL` are all loaded into the `comm` column of the `emp` table since these employees are either `SALESMAN` or members of department `30`.
+
+The `comm` value of `2000.00` in the data file for employee `JACKSON` is ignored, and the `comm` column of the `emp` table is set to null. This employee isn't a `SALESMAN` or a member of department `30`.
+
+## SELECT statement in a field expression
+
+This example uses a `SELECT` statement in the expression of the field definition to return the value to load into the column:
+
+```sql
+LOAD DATA
+  INFILE    'emp_fixed.dat'
+    BADFILE 'emp_fixed.bad'
+  APPEND
+  INTO TABLE emp
+    TRAILING NULLCOLS
+  (
+    empno       POSITION (1:4),
+    ename       POSITION (5:14),
+    job         POSITION (15:23) "(SELECT dname FROM dept WHERE deptno = :deptno)",
+    mgr         POSITION (24:27),
+    hiredate    POSITION (28:38),
+    sal         POSITION (39:46),
+    deptno      POSITION (47:48),
+    comm        POSITION (49:56)
+  )
+```
+
+The following is the content of the `dept` table used in the `SELECT` statement:
+
+```sql
+SELECT * FROM dept;
+__OUTPUT__
+ deptno |    dname   |   loc
+---------+------------+---------
+   10   | ACCOUNTING | NEW YORK
+   20   | RESEARCH   | DALLAS
+   30   | SALES      | CHICAGO
+   40   | OPERATIONS | BOSTON
+(4 rows)
+```
+
+The following is the corresponding data file:
+
+```sql
+9101ROGERS     CLERK     790217-DEC-10    1980.0020
+9102PETERSON   SALESMAN  769820-DEC-10    2600.0030   2300.00
+9103WARREN     SALESMAN  769822-DEC-10    5250.0030   2500.00
+9104JONES, JR. MANAGER   783902-APR-09    7975.0020
+```
+
+The resulting rows in the table appear as follows:
+
+```sql
+SELECT * FROM emp WHERE empno > 9100;
+__OUTPUT__
+ empno| ename     | job     | mgr|   hiredate        | sal   | comm   |deptno
+------+-----------+---------+----+-------------------+-------+--------+------
+  9101| ROGERS    | RESEARCH|7902| 17-DEC-10 00:00:00|1980.00|        |  20
+  9102| PETERSON  | SALES   |7698| 20-DEC-10 00:00:00|2600.00| 2300.00|  30
+  9103| WARREN    | SALES   |7698| 22-DEC-10 00:00:00|5250.00| 2500.00|  30
+  9104| JONES, JR.| RESEARCH|7839| 02-APR-09 00:00:00|7975.00|        |  20
+(4 rows)
+```
+
+!!! Note
+    The `job` column contains the value from the `dname` column of the `dept` table returned by the `SELECT` statement instead of the job name from the data file.
+
+## Multiple INTO TABLE clauses
+
+This example uses multiple `INTO TABLE` clauses. For this example, two empty tables are created with the same data definition as the `emp` table. The following `CREATE TABLE` commands create these two empty tables without inserting rows from the original `emp` table:
+
+```sql
+CREATE TABLE emp_research AS SELECT * FROM emp WHERE deptno = 99;
+CREATE TABLE emp_sales AS SELECT * FROM emp WHERE deptno = 99;
+```
+
+This control file contains two `INTO TABLE` clauses. Without an `APPEND` clause, it uses the default operation of `INSERT`. For this operation, the tables `emp_research` and `emp_sales` must be empty.
+
+```sql
+LOAD DATA
+  INFILE        'emp_multitbl.dat'
+    BADFILE     'emp_multitbl.bad'
+    DISCARDFILE 'emp_multitbl.dsc'
+  INTO TABLE emp_research
+    WHEN (47:48) = '20'
+    TRAILING NULLCOLS
+  (
+    empno      POSITION (1:4),
+    ename      POSITION (5:14),
+    job        POSITION (15:23),
+    mgr        POSITION (24:27),
+    hiredate   POSITION (28:38),
+    sal        POSITION (39:46),
+    deptno     CONSTANT '20',
+    comm       POSITION (49:56)
+  )
+  INTO TABLE emp_sales
+    WHEN (47:48) = '30'
+    TRAILING NULLCOLS
+  (
+    empno     POSITION (1:4),
+    ename     POSITION (5:14),
+    job       POSITION (15:23),
+    mgr       POSITION (24:27),
+    hiredate  POSITION (28:38),
+    sal       POSITION (39:46),
+    deptno    CONSTANT '30',
+    comm      POSITION (49:56) "ROUND(:comm + (:sal * .25), 0)"
+  )
+```
+
+The `WHEN` clauses specify that when the field designated by columns 47 through 48 contains `20`, the record is inserted into the `emp_research` table. When that same field contains `30`, the record is inserted into the `emp_sales` table. If neither condition is true, the record is written to the discard file `emp_multitbl.dsc`.
+
+The `CONSTANT` clause is given for column `deptno`, so the specified constant value is inserted into `deptno` for each record. When the `CONSTANT` clause is used, it must be the only clause in the field definition other than the column name to which the constant value is assigned.
+
+Column `comm` of the `emp_sales` table is assigned a SQL expression. Expressions can reference column names by prefixing the column name with a colon character (`:`).
+
+The following is the corresponding data file:
+
+```sql
+9101ROGERS     CLERK     790217-DEC-10   1980.0020
+9102PETERSON   SALESMAN  769820-DEC-10   2600.0030  2300.00
+9103WARREN     SALESMAN  769822-DEC-10   5250.0030  2500.00
+9104JONES, JR. MANAGER   783902-APR-09   7975.0020
+9105ARNOLDS    CLERK     778213-SEP-10   3750.0010
+9106JACKSON    ANALYST   756603-JAN-11   4500.0040
+```
+
+The records for employees `ARNOLDS` and `JACKSON` contain `10` and `40` in columns 47 through 48, which don't satisfy any of the `WHEN` clauses. EDB\*Loader writes these two records to the discard file, `emp_multitbl.dsc`, with the following content:
+
+```sql
+9105ARNOLDS   CLERK     778213-SEP-10   3750.0010
+9106JACKSON   ANALYST   756603-JAN-11   4500.0040
+```
+
+The following are the rows loaded into the `emp_research` and `emp_sales` tables:
+
+```sql
+SELECT * FROM emp_research;
+__OUTPUT__
+empno  |   ename    |   job   |  mgr |      hiredate      |   sal   | comm | deptno
+-------+------------+---------+------+--------------------+---------+------+-------
+ 9101  | ROGERS     | CLERK   | 7902 | 17-DEC-10 00:00:00 | 1980.00 |      | 20.00
+ 9104  | JONES, JR. | MANAGER | 7839 | 02-APR-09 00:00:00 | 7975.00 |      | 20.00
+(2 rows)
+```
+```sql
+SELECT * FROM emp_sales;
+__OUTPUT__
+empno  |   ename  |    job   |  mgr |       hiredate     |    sal  |   comm  | deptno
+-------+----------+----------+------+--------------------+---------+---------+--------
+ 9102  | PETERSON | SALESMAN | 7698 | 20-DEC-10 00:00:00 | 2600.00 | 2950.00 | 30.00
+ 9103  | WARREN   | SALESMAN | 7698 | 22-DEC-10 00:00:00 | 5250.00 | 3813.00 | 30.00
+(2 rows)
+```
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/index.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/index.mdx
new file mode 100644
index 00000000000..e9859ab365d
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/building_the_control_file/index.mdx
@@ -0,0 +1,114 @@
+---
+title: "Building the EDB*Loader control file"
+navTitle: "Building the control file"
+description: "Provides information necessary to build a control file"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/building_the_control_file/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="building_the_edb_loader_control_file" class="registered_link"></div>
+
+When you invoke EDB\*Loader, the list of arguments provided must include the name of a control file. The control file includes the instructions that EDB\*Loader uses to load the tables from the input data file. 
+
+## Contents of the control file
+
+The control file includes information such as:
+
+-   The name of the input data file containing the data to load
+-   The name of the tables to load from the data file
+-   Names of the columns in the tables and their corresponding field placement in the data file
+-   Specification of whether the data file uses a delimiter string to separate the fields or if the fields occupy fixed column positions
+-   Optional selection criteria to choose the records from the data file to load into a given table
+-   The name of the file that collects illegally formatted records
+-   The name of the discard file that collects records that don't meet the selection criteria of any table
+
+## Control file syntax
+
+The syntax for the EDB\*Loader control file is:
+
+```sql
+[ OPTIONS (<param=value> [, <param=value> ] ...) ]
+LOAD DATA
+  [ CHARACTERSET <charset> ]
+  [ INFILE '{ <data_file> | <stdin> }' ]
+  [ BADFILE '<bad_file>' ]
+  [ DISCARDFILE '<discard_file>' ]
+  [ { DISCARDMAX | DISCARDS } <max_discard_recs> ]
+[ INSERT | APPEND | REPLACE | TRUNCATE ]
+[ PRESERVE BLANKS ]
+{ INTO TABLE <target_table>
+  [ WHEN <field_condition> [ AND <field_condition> ] ...]
+  [ FIELDS TERMINATED BY '<termstring>'
+    [ OPTIONALLY ENCLOSED BY '<enclstring>' ] ]
+  [ RECORDS DELIMITED BY '<delimstring>' ]
+  [ TRAILING NULLCOLS ]
+   (<field_def> [, <field_def> ] ...)
+} ...
+```
+
+Where `field_def` defines a field in the specified `data_file`. The field describes the location, data format, or value of the data to insert into `column_name` of `target_table`. The syntax of `field_def` is:
+
+```sql
+<column_name> {
+  CONSTANT <val> |
+  FILLER [ POSITION (<start:end>) ] [ <fieldtype> ] |
+  BOUNDFILLER [ POSITION (<start:end>) ] [ <fieldtype> ] |
+  [ POSITION (<start:end>) ] [ <fieldtype> ]
+  [ NULLIF <field_condition> [ AND <field_condition> ] ...]
+  [ PRESERVE BLANKS ] [ "<expr>" ]
+}
+```
+
+Where `fieldtype` is one of:
+
+```sql
+CHAR [(<length>)] | DATE [(<length>)] | TIMESTAMP [(<length>)] [ "<datemask>" ] | 
+INTEGER EXTERNAL [(<length>)] |
+FLOAT EXTERNAL [(<length>)] | DECIMAL EXTERNAL [(<length>)] |
+ZONED EXTERNAL [(<length>)] | ZONED [(<precision> [,<scale>])]
+```
+
+## Setting the variables
+
+The specification of `data_file`, `bad_file`, and `discard_file` can include the full directory path or a relative directory path to the filename. If the filename is specified alone or with a relative directory path, the file is then assumed to exist, in the case of `data_file`, relative to the current working directory from which you invoke `edbldr`. In the case of `bad_file` or `discard_file`, it's created.
+
+You can include references to environment variables in the EDB\*Loader control file when referring to a directory path or filename. Environment variable references are formatted differently on Windows systems than on Linux systems:
+
+-   On Linux, the format is `$ENV_VARIABLE` or `${ENV_VARIABLE}`.
+-   On Windows, the format is `%ENV_VARIABLE%`.
+
+Where `ENV_VARIABLE` is the environment variable that's set to the directory path or filename.
+
+Set the `EDBLDR_ENV_STYLE` environment variable to interpret environment variable references as Windows-styled references or Linux-styled references regardless of the operating system on which EDB\*Loader resides. You can use this environment variable to create portable control files for EDB\*Loader.
+
+-   On a Windows system, set `EDBLDR_ENV_STYLE` to `linux` or `unix` to recognize Linux-style references in the control file.
+-   On a Linux system, set `EDBLDR_ENV_STYLE` to `windows` to recognize Windows-style references in the control file.
+
+The operating system account enterprisedb must have read permission on the directory and file specified by `data_file`. It must have write permission to the directories where `bad_file` and `discard_file` are written.
+
+!!! Note
+    The filenames for `data_file`, `bad_file`, and `discard_file` must have extensions `.dat`, `.bad`, and `.dsc`, respectively. If the provided filename doesn't have an extension, EDB\*Loader assumes the actual filename includes the appropriate extension.
+
+## Example scenarios
+
+Suppose an EDB\*Loader session results in data format errors, the `BADFILE` clause isn't specified, and the `BAD` parameter isn't given on the command line when `edbldr` is invoked. In this case, a bad file is created with the name `control_file_base.bad` in the directory from which `edbldr` is invoked. `control_file_base` is the base name of the control file used in the `edbldr` session.
+
+If all of the following conditions are true, the discard file isn't created even if the EDB\*Loader session results in discarded records:
+
+-   The `DISCARDFILE` clause for specifying the discard file isn't included in the control file.
+-   The `DISCARD` parameter for specifying the discard file isn't included on the command line.
+-   The `DISCARDMAX` clause for specifying the maximum number of discarded records isn't included in the control file.
+-   The `DISCARDS` clause for specifying the maximum number of discarded records isn't included in the control file.
+-   The `DISCARDMAX` parameter for specifying the maximum number of discarded records isn't included on the command line.
+
+Suppose you don't specify the `DISCARDFILE` clause and the `DISCARD` parameter for explicitly specifying the discard filename, but you do specify `DISCARDMAX` or `DISCARDS`. In this case, the EDB\*Loader session creates a discard file using the data filename with an extension of `.dsc`.
+
+!!! Note
+    The keywords `DISCARD` and `DISCARDS` differ. `DISCARD` is an EDB\*Loader command line parameter used to specify the discard filename. `DISCARDS` is a clause of the `LOAD DATA` directive that can appear only in the control file. Keywords `DISCARDS` and `DISCARDMAX` provide the same functionality of specifying the maximum number of discarded records allowed before terminating the EDB\*Loader session. Records loaded into the database before terminating the EDB\*Loader session due to exceeding the `DISCARDS` or `DISCARDMAX` settings are kept in the database. They aren't rolled back.
+
+Specifying one of `INSERT`, `APPEND`, `REPLACE`, or `TRUNCATE` establishes the default action for adding rows to target tables. The default action is `INSERT`.
+
+If you specify the `FIELDS TERMINATED BY` clause, then you can't specify the `POSITION (start:end)` clause for any `field_def`. Alternatively, if you don't specify the `FIELDS TERMINATED BY` clause, then every `field_def` must contain the `POSITION (start:end)` clause, the `fieldtype(length)` clause, or the `CONSTANT` clause.
+
+For complete descriptions of the parameters available for each clause, see [EDB\*Loader control file parameters](../../../reference/database_administrator_reference/edb_loader_control_file_parameters/).
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/data_loading_methods.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/data_loading_methods.mdx
new file mode 100644
index 00000000000..5bde3714902
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/data_loading_methods.mdx
@@ -0,0 +1,17 @@
+---
+title: "Overview of data loading methods"
+navTitle: "Data loading methods"
+description: "Description of the data loading methods supported by EDB*Loader"
+---
+
+As with Oracle SQL\*Loader, EDB\*Loader supports three data loading methods:
+
+- **Conventional path load** &mdash; Conventional path load is the default method used by EDB\*Loader. Use basic insert processing to add rows to the table. The advantage of a conventional path load is that table constraints and database objects defined on the table are enforced during a conventional path load. Table constraints and database objects include primary keys, not null constraints, check constraints, unique indexes, foreign key constraints, triggers, and so on. One exception is that the EDB Postgres Advanced Server rules defined on the table aren't enforced. EDB\*Loader can load tables on which rules are defined. However, the rules aren't executed. As a consequence, you can't load partitioned tables implemented using rules with EDB\*Loader. See [Conventional path load](invoking_edb_loader/conventional_path_load.mdx).
+
+- **Direct path load** &mdash; A direct path load is faster than a conventional path load but requires removing most types of constraints and triggers from the table. See [Direct path load](invoking_edb_loader/direct_path_load.mdx).
+
+- **Parallel direct path load** &mdash; A parallel direct path load provides even greater performance improvement by permitting multiple EDB\*Loader sessions to run simultaneously to load a single table. See [Parallel direct path load](invoking_edb_loader/parallel_direct_path_load.mdx).
+
+!!! Note
+    Create EDB Postgres Advanced Server rules using the `CREATE RULE` command. EDB Postgres Advanced Server rules aren't the same database objects as rules and rule sets used in Oracle.
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx
new file mode 100644
index 00000000000..8b0ed6c0e48
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/edb_loader_overview_and_restrictions.mdx
@@ -0,0 +1,32 @@
+---
+title: "EDB*Loader key concepts and compatability"
+navTitle: "Key concepts and compatability"
+description: "Provides an overview of the key features of EDB*Loader as well as important compatability information"
+---
+
+## Key features 
+
+EDB\*Loader features include:
+
+-   Support for the Oracle SQL\*Loader data loading methods (conventional path load, direct path load, and parallel direct path load)
+-   Syntax for control file directives compatible with Oracle SQL\*Loader
+-   Input data with delimiter-separated or fixed-width fields
+-   Bad file for collecting rejected records
+-   Loading of multiple target tables
+-   Discard file for collecting records that don't meet the selection criteria of any target table
+-   Log file for recording the EDB\*Loader session and any error messages
+-   Data loading from standard input and remote loading, particularly useful for large data sources on remote hosts
+
+## Version compatibility restrictions
+
+The important version compatibility restrictions between the EDB\*Loader client and the database server are:
+
+-   When you invoke the EDB\*Loader program (called `edbldr`), you pass in parameters and directive information to the database server. We strongly recommend that you use the version of the EDB\*Loader client, the `edbldr` program supplied with the version of EDB Postgres Advanced Server you are using, to load data only into the database server. In general, use the same version for the EDB\*Loader client and database server.
+
+-   Using EDB\*Loader with connection poolers such as PgPool-II and PgBouncer isn't supported. EDB\*Loader must connect directly to EDB Postgres Advanced Server version 16. Alternatively, you can use these commands for loading data through connection poolers:
+
+```shell
+psql \copy
+jdbc copyIn
+psycopg2 copy_from
+```
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx
new file mode 100644
index 00000000000..8e9503d26d5
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/index.mdx
@@ -0,0 +1,53 @@
+---
+title: "Loading bulk data"
+navTitle: "EDB*Loader"
+indexCards: simple
+description: "How to use EDB*Loader, the high-performance bulk data loader"
+navigation:
+  - edb_loader_overview_and_restrictions
+  - data_loading_methods
+  - using_edb_loader
+  - building_the_control_file
+  - invoking_edb_loader
+redirects:
+  - /epas/latest/epas_compat_tools_guide/02_edb_loader
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.16.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.15.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.11.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.12.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.08.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.14.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.13.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.10.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.09.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.314.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.315.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.311.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.312.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.313.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.309.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.310.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.308.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.307.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.092.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.093.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.091.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.089.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.087.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.090.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.088.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.086.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.085.html"
+---
+
+EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader.
+
+
+
+
+
+
+
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/conventional_path_load.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/conventional_path_load.mdx
new file mode 100644
index 00000000000..8e36c81fbd6
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/conventional_path_load.mdx
@@ -0,0 +1,108 @@
+---
+title: "Updating a table with a conventional path load"
+navTitle: "Conventional path load"
+description: "Describes how to use EDB*Loader with a conventional path load to update the rows in a table"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/conventional_path_load/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="updating_a_table_with_a_conventional_path_load" class="registered_link"></div>
+
+You can use EDB\*Loader with a conventional path load to update the rows in a table, merging new data with the existing data. When you invoke EDB\*Loader to perform an update, the server searches the table for an existing row with a matching primary key:
+
+-   If the server locates a row with a matching key, it replaces the existing row with the new row.
+-   If the server doesn't locate a row with a matching key, it adds the new row to the table.
+
+To use EDB\*Loader to update a table, the table must have a primary key. You can't use EDB\*Loader to update a partitioned table.
+
+## Performing the update
+
+To perform `UPDATE`, use the same steps as when performing a conventional path load:
+
+1.  Create a data file that contains the rows you want to update or insert.
+2.  Define a control file that uses the `INFILE` keyword to specify the name of the data file. For information about building the EDB\*Loader control file, see [Building the EDB\*Loader control file](../building_the_control_file/).
+3.  Invoke EDB\*Loader, specifying the database name, connection information, and the name of the control file. For information about invoking EDB\*Loader, see [Invoking EDB\*Loader](../).
+
+This example uses the `emp` table that's distributed with the EDB Postgres Advanced Server sample data. By default, the table contains:
+
+```sql
+edb=# select * from emp;
+__OUTPUT__
+empno|ename |   job   |  mgr |       hiredate     |   sal    | comm  | deptno
+-----+------+---------+------+--------------------+--------- +-------+--------
+7369 |SMITH |CLERK    | 7902 | 17-DEC-80 00:00:00 | 800.00   |       |   20
+7499 |ALLEN |SALESMAN | 7698 | 20-FEB-81 00:00:00 | 1600.00  |300.00 |   30
+7521 |WARD  |SALESMAN | 7698 | 22-FEB-81 00:00:00 | 1250.00  |500.00 |   30
+7566 |JONES |MANAGER  | 7839 | 02-APR-81 00:00:00 | 2975.00  |       |   20
+7654 |MARTIN|SALESMAN | 7698 | 28-SEP-81 00:00:00 | 1250.00  |1400.00|   30
+7698 |BLAKE |MANAGER  | 7839 | 01-MAY-81 00:00:00 | 2850.00  |       |   30
+7782 |CLARK |MANAGER  | 7839 | 09-JUN-81 00:00:00 | 2450.00  |       |   10
+7788 |SCOTT |ANALYST  | 7566 | 19-APR-87 00:00:00 | 3000.00  |       |   20
+7839 |KING  |PRESIDENT|      | 17-NOV-81 00:00:00 | 5000.00  |       |   10
+7844 |TURNER|SALESMAN | 7698 | 08-SEP-81 00:00:00 | 1500.00  | 0.00  |   30
+7876 |ADAMS |CLERK    | 7788 | 23-MAY-87 00:00:00 | 1100.00  |       |   20
+7900 |JAMES |CLERK    | 7698 | 03-DEC-81 00:00:00 | 950.00   |       |   30
+7902 |FORD  |ANALYST  | 7566 | 03-DEC-81 00:00:00 | 3000.00  |       |   20
+7934 |MILLER|CLERK    | 7782 | 23-JAN-82 00:00:00 | 1300.00  |       |   10
+(14 rows)
+```
+
+This control file (`emp_update.ctl`) specifies the fields in the table in a comma-delimited list. The control file performs an `UPDATE` on the `emp` table.
+
+```sql
+LOAD DATA
+  INFILE 'emp_update.dat'
+  BADFILE 'emp_update.bad'
+  DISCARDFILE 'emp_update.dsc'
+UPDATE INTO TABLE emp
+FIELDS TERMINATED BY ","
+(empno, ename, job, mgr, hiredate, sal, comm, deptno)
+```
+
+The data that's being updated or inserted is saved in the `emp_update.dat` file. `emp_update.dat` contains:
+
+```sql
+7521,WARD,MANAGER,7839,22-FEB-81 00:00:00,3000.00,0.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,3500.00,0.00,20
+7903,BAKER,SALESMAN,7521,10-JUN-13 00:00:00,1800.00,500.00,20
+7904,MILLS,SALESMAN,7839,13-JUN-13 00:00:00,1800.00,500.00,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1500.00,400.00,30
+```
+
+Invoke EDB\*Loader, specifying the name of the database (`edb`), the name of a database user and their associated password, and the name of the control file (`emp_update.ctl`):
+
+```shell
+edbldr -d edb userid=user_name/password control=emp_update.ctl
+```
+
+## Results of the update
+
+After performing the update, the `emp` table contains:
+
+```sql
+edb=# select * from emp;
+__OUTPUT__
+empno|ename |   job   |  mgr |      hiredate      |   sal   |  comm  | deptno
+-----+------+---------+------+--------------------+---------+--------+--------
+7369 |SMITH |CLERK    | 7902 | 17-DEC-80 00:00:00 | 800.00  |        |  20
+7499 |ALLEN |SALESMAN | 7698 | 20-FEB-81 00:00:00 | 1600.00 | 300.00 |  30
+7521 |WARD  |MANAGER  | 7839 | 22-FEB-81 00:00:00 | 3000.00 | 0.00   |  30
+7566 |JONES |MANAGER  | 7839 | 02-APR-81 00:00:00 | 3500.00 | 0.00   |  20
+7654 |MARTIN|SALESMAN | 7698 | 28-SEP-81 00:00:00 | 1500.00 | 400.00 |  30
+7698 |BLAKE |MANAGER  | 7839 | 01-MAY-81 00:00:00 | 2850.00 |        |  30
+7782 |CLARK |MANAGER  | 7839 | 09-JUN-81 00:00:00 | 2450.00 |        |  10
+7788 |SCOTT |ANALYST  | 7566 | 19-APR-87 00:00:00 | 3000.00 |        |  20
+7839 |KING  |PRESIDENT|      | 17-NOV-81 00:00:00 | 5000.00 |        |  10
+7844 |TURNER|SALESMAN | 7698 | 08-SEP-81 00:00:00 | 1500.00 | 0.00   |  30
+7876 |ADAMS |CLERK    | 7788 | 23-MAY-87 00:00:00 | 1100.00 |        |  20
+7900 |JAMES |CLERK    | 7698 | 03-DEC-81 00:00:00 | 950.00  |        |  30
+7902 |FORD  |ANALYST  | 7566 | 03-DEC-81 00:00:00 | 3000.00 |        |  20
+7903 |BAKER |SALESMAN | 7521 | 10-JUN-13 00:00:00 | 1800.00 | 500.00 |  20
+7904 |MILLS |SALESMAN | 7839 | 13-JUN-13 00:00:00 | 1800.00 | 500.00 |  20
+7934 |MILLER|CLERK    | 7782 | 23-JAN-82 00:00:00 | 1300.00 |        |  10
+(16 rows)
+```
+
+The rows containing information for the three employees that are currently in the `emp` table are updated, while rows are added for the new employees (`BAKER` and `MILLS`).
+
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx
new file mode 100644
index 00000000000..5f6f1037faf
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx
@@ -0,0 +1,45 @@
+---
+title: "Running a direct path load"
+navTitle: "Direct path load"
+description: "Describes how to use EDB*Loader to write data directly to the database pages"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/direct_path_load/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="direct_path_load" class="registered_link"></div>
+
+During a direct path load, EDB\*Loader writes the data directly to the database pages, which is then synchronized to disk. The insert processing associated with a conventional path load is bypassed, resulting in performance improvement. Bypassing insert processing reduces the types of constraints on the target table. The types of constraints permitted on the target table of a direct path load are:
+
+-   Primary key
+-   Not null constraints
+-   Indexes (unique or non-unique)
+
+## Restrictions
+
+The restrictions on the target table of a direct path load are:
+
+-   Triggers aren't permitted.
+-   Check constraints aren't permitted.
+-   Foreign key constraints on the target table referencing another table aren't permitted.
+-   Foreign key constraints on other tables referencing the target table aren't permitted.
+-   You must not partition the table.
+-   Rules can exist on the target table, but they aren't executed.
+
+!!! Note
+    Currently, a direct path load in EDB\*Loader is more restrictive than in Oracle SQL\*Loader. The preceding restrictions don't apply to Oracle SQL\*Loader in most cases. The following restrictions apply to a control file used in a direct path load:
+
+    -   Multiple table loads aren't supported. You can specify only one `INTO TABLE` clause in the control file.
+    -   You can't use SQL expressions in the data field definitions of the `INTO TABLE` clause.
+    -   The `FREEZE` option isn't supported for direct path loading.
+
+## Running the direct path load
+
+To run a direct path load, add the `DIRECT=TRUE` option:
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb USERID=enterprisedb/password
+CONTROL=emp.ctl DIRECT=TRUE
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+
+Successfully loaded (4) records
+```
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/index.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/index.mdx
new file mode 100644
index 00000000000..2b4b8a6a41e
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/index.mdx
@@ -0,0 +1,18 @@
+---
+title: "Invoking EDB*Loader"
+description: "Describes how to run EDB*Loader"
+indexCards: simple
+navigation:
+  - running_edb_loader
+  - conventional_path_load
+  - direct_path_load
+  - parallel_direct_path_load
+  - performing_remote_loading
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/invoking_edb_loader/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="invoking_edb_loader" class="registered_link"></div>
+
+You can run EDB\*Loader as superuser or as a normal user. 
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load.mdx
new file mode 100644
index 00000000000..2135fec87a8
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load.mdx
@@ -0,0 +1,153 @@
+---
+title: "Running a parallel direct path load"
+navTitle: "Parallel direct path load"
+description: "Describes how to run a parallel direct path load to distribute the loading process over two or more sessions"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/parallel_direct_path_load/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="parallel_direct_path_load" class="registered_link"></div>
+
+You can further improve the performance of a direct path load by distributing the loading process over two or more sessions running concurrently. Each session runs a direct path load into the same table.
+
+Since the same table is loaded from multiple sessions, the input records to load into the table must be divided among several data files. This way, each EDB\*Loader session uses its own data file, and the same record isn't loaded into the table more than once.
+
+## Restrictions
+
+The target table of a parallel direct path load is under the same restrictions as a direct path load run in a single session.
+
+The restrictions on the target table of a direct path load are:
+
+-   Triggers aren't permitted.
+-   Check constraints aren't permitted.
+-   Foreign key constraints on the target table referencing another table aren't permitted.
+-   Foreign key constraints on other tables referencing the target table aren't permitted.
+-   You must not partition the table.
+-   Rules can exist on the target table, but they aren't executed.
+
+In addition, you must specify the `APPEND` clause in the control file used by each EDB\*Loader session.
+
+## Running a parallel direct path load
+
+To run a parallel direct path load, run EDB\*Loader in a separate session for each participant of the parallel direct path load. You must include the `DIRECT=TRUE` and `PARALLEL=TRUE` parameters when invoking each such EDB\*Loader session.
+
+Each EDB\*Loader session runs as an independent transaction. Aborting and rolling back changes of one of the parallel sessions doesn't affect the loading done by the other parallel sessions.
+
+!!! Note
+    In a parallel direct path load, each EDB\*Loader session reserves a fixed number of blocks in the target table using turns. Some of the blocks in the last allocated chunk might not be used, and those blocks remain uninitialized. A later use of the `VACUUM` command on the target table might show warnings about these uninitialized blocks, such as the following:
+
+```text
+WARNING: relation "emp" page 98264 is uninitialized --- fixing
+
+WARNING: relation "emp" page 98265 is uninitialized --- fixing
+
+WARNING: relation "emp" page 98266 is uninitialized --- fixing
+```
+
+This behavior is expected and doesn't indicate data corruption.
+
+Indexes on the target table aren't updated during a parallel direct path load. They are therefore marked as invalid after the load is complete. You must use the `REINDEX` command to rebuild the indexes.
+
+This example shows the use of a parallel direct path load on the `emp` table.
+
+!!! Note
+    If you attempt a parallel direct path load on the sample `emp` table provided with EDB Postgres Advanced Server, you must first remove the triggers and constraints referencing the `emp` table. In addition, the primary key column, `empno`, was expanded from `NUMBER(4)` to `NUMBER` in this example to allow for inserting more rows.
+
+This is the control file used in the first session:
+
+```sql
+LOAD DATA
+  INFILE    '/home/user/loader/emp_parallel_1.dat'
+  APPEND
+  INTO TABLE emp
+    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
+    TRAILING NULLCOLS
+  (
+    empno,
+    ename,
+    job,
+    mgr,
+    hiredate,
+    sal,
+    deptno,
+    comm
+  )
+```
+
+You must specify the `APPEND` clause in the control file for a parallel direct path load.
+
+This example invokes EDB\*Loader in the first session. You must specify the `DIRECT=TRUE` and `PARALLEL=TRUE` parameters.
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb USERID=enterprisedb/password
+CONTROL=emp_parallel_1.ctl DIRECT=TRUE PARALLEL=TRUE
+WARNING: index maintenance will be skipped with PARALLEL load
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+```
+
+The control file used for the second session appears as follows. It's the same as the one used in the first session, but it uses a different data file.
+
+```sql
+LOAD DATA
+  INFILE '/home/user/loader/emp_parallel_2.dat'
+  APPEND
+  INTO TABLE emp
+    FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
+    TRAILING NULLCOLS
+  (
+    empno,
+    ename,
+    job,
+    mgr,
+    hiredate,
+    sal,
+    deptno,
+    comm
+  )
+```
+
+This control file is used in a second session:
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb USERID=enterprisedb/password
+CONTROL=emp_parallel_2.ctl DIRECT=TRUE PARALLEL=TRUE
+WARNING: index maintenance will be skipped with PARALLEL load
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+```
+
+EDB\*Loader displays a message in each session when the load operation completes:
+
+```text
+Successfully loaded (10000) records
+```
+
+This query shows that the index on the emp table was marked `INVALID`:
+
+```sql
+SELECT index_name, status FROM user_indexes WHERE table_name = 'EMP';
+__OUTPUT__
+  index_name | status
+-------------+---------
+   EMP_PK    | INVALID
+ (1 row)
+```
+
+!!! Note
+    `user_indexes` is the view of indexes compatible with Oracle databases owned by the current user.
+
+Queries on the `emp` table don't use the index unless you rebuild it using the `REINDEX` command:
+
+```sql
+REINDEX INDEX emp_pk;
+```
+
+A later query on `user_indexes` shows that the index is now marked as `VALID`:
+
+```sql
+SELECT index_name, status FROM user_indexes WHERE table_name = 'EMP';
+__OUTPUT__
+  index_name | status
+-------------+--------
+   EMP_PK    | VALID
+ (1 row)
+```
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx
new file mode 100644
index 00000000000..bc539ea9247
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/performing_remote_loading.mdx
@@ -0,0 +1,41 @@
+---
+title: "Performing remote loading"
+navTitle: "Remote loading"
+description: "Describes how to load a database running on a database server using data piped from a different source"
+redirects:
+  - /epas/latest/database_administration/02_edb_loader/performing_remote_loading/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="remote_loading" class="registered_link"></div>
+
+EDB\*Loader supports a feature called *remote loading*. In remote loading, the database containing the table to load is running on a database server on a host different from the one where EDB\*Loader is invoked with the input data source.
+
+This feature is useful if you have a large amount of data to load, and you don't want to create a large data file on the host running the database server.
+
+In addition, you can use the standard input feature to pipe the data from the data source, such as another program or script, directly to EDB\*Loader. EDB\*Loader then loads the table in the remote database. This feature bypasses having to create a data file on disk for EDB\*Loader.
+
+## Requirements 
+
+Performing remote loading using standard input requires:
+
+-   The `edbldr` program must be installed on the client host on which to invoke it with the data source for the EDB\*Loader session.
+-   The control file must contain the clause `INFILE 'stdin'` so you can pipe the data directly into EDB\*Loader’s standard input. For information on the `INFILE` clause and the EDB\*Loader control file, see [Building the EDB\*Loader control file](../building_the_control_file/).
+-   All files used by EDB\*Loader, such as the control file, bad file, discard file, and log file, must reside on or be created on the client host on which `edbldr` is invoked.
+-   When invoking EDB\*Loader, use the `-h` option to specify the IP address of the remote database server. For more information, see [Invoking EDB\*Loader](../).
+-   Use the operating system pipe operator (`|`) or input redirection operator (`<`) to supply the input data to EDB\*Loader.
+
+## Loading a database 
+
+This example loads a database running on a database server at `192.168.1.14` using data piped from a source named `datasource`:
+
+```shell
+datasource | ./edbldr -d edb -h 192.168.1.14 USERID=enterprisedb/password
+CONTROL=remote.ctl
+```
+
+This example also shows how you can use standard input:
+
+```shell
+./edbldr -d edb -h 192.168.1.14 USERID=enterprisedb/password
+CONTROL=remote.ctl < datasource
+```
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx
new file mode 100644
index 00000000000..171181e7a26
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/invoking_edb_loader/running_edb_loader.mdx
@@ -0,0 +1,292 @@
+---
+title: "Running EDB*Loader"
+description: "Describes how to run EDB*Loader from the command line"
+---
+
+Use the following command to invoke EDB\*Loader from the command line:
+
+```sql
+edbldr [ -d <dbname> ] [ -p <port> ] [ -h <host> ]
+[ USERID={ <username/password> | <username>/ | <username> | / } ]
+[ { -c | connstr= } <CONNECTION_STRING> ]
+  CONTROL=<control_file>
+[ DATA=<data_file> ]
+[ BAD=<bad_file>]
+[ DISCARD=<discard_file> ]
+[ DISCARDMAX=<max_discard_recs> ]
+[ HANDLE_CONFLICTS={ FALSE | TRUE } ]
+[ LOG=<log_file> ]
+[ PARFILE=<param_file> ]
+[ DIRECT={ FALSE | TRUE } ]
+[ FREEZE={ FALSE | TRUE } ]
+[ ERRORS=<error_count> ]
+[ PARALLEL={ FALSE | TRUE } ]
+[ ROWS=<n> ]
+[ SKIP=<skip_count> ]
+[ SKIP_INDEX_MAINTENANCE={ FALSE | TRUE } ]
+[ edb_resource_group=<group_name> ]
+```
+
+## Description
+
+You can specify parameters listed in the syntax diagram in a *parameter file*. Exeptions include the `-d` option, `-p` option, `-h` option, and the `PARFILE` parameter. Specify the parameter file on the command line when you invoke edbldr using `PARFILE=param_file`. You can specify some parameters in the `OPTIONS` clause in the control file. For more information on the control file, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+You can include the full directory path or a relative directory path to the file name when specifying `control_file`, `data_file`, `bad_file`, `discard_file`, `log_file`, and `param_file`. If you specify the file name alone or with a relative directory path, the file is assumed to exist in the case of `control_file`, `data_file`, or `param_file` relative to the current working directory from which edbldr is invoked. In the case of `bad_file`, `discard_file`, or `log_file`, the file is created.
+
+If you omit the `-d` option, the `-p` option, or the `-h` option, the defaults for the database, port, and host are determined by the same rules as other EDB Postgres Advanced Server utility programs, such as edb-psql.
+
+## Requirements
+
+- The control file must exist in the character set encoding of the client where edbldr is invoked. If the client is in an encoding different from the database encoding, then you must set the `PGCLIENTENCODING` environment variable on the client to the client’s encoding prior to invoking edbldr. This technique ensures character set conversion between the client and the database server is done correctly.
+
+- The file names must include these extensions:
+  - `control_file` must use the `.ctl` extension. 
+  - `data_file` must use the `.dat` extension. 
+  - `bad_file` must use the `.bad` extension 
+  - `discard_file` must use the `.dsc` extension 
+  - `log_file` must include the `.log` extension
+  
+  If the provided file name doesn't have an extension, EDB\*Loader assumes the actual file name includes the appropriate extension.
+
+- The operating system account used to invoke edbldr must have read permission on the directories and files specified by `control_file`, `data_file`, and `param_file`.
+
+- The operating system account enterprisedb must have write permission on the directories where `bad_file`, `discard_file`, and `log_file` are  written.
+
+## Parameters
+
+`dbname`
+
+ Name of the database containing the tables to load.
+
+`port`
+
+ Port number on which the database server is accepting connections.
+
+`host`
+
+ IP address of the host on which the database server is running.
+
+`USERID={ <username/password> | <username/> | <username> | / }`
+
+ EDB\*Loader connects to the database with `<username>`. `<username>` must be a superuser or a username with the required privileges. `<password>` is the password for `<username>`.
+
+ If you omit the `USERID` parameter, EDB\*Loader prompts for `username` and `password`. If you specify `USERID=username/`, then EDB\*Loader either:
+ -  Uses the password file specified by the environment variable `PGPASSFILE` if `PGPASSFILE` is set
+ -  Uses the `.pgpass` password file (`pgpass.conf` on Windows systems) if `PGPASSFILE` isn't set 
+ 
+ If you specify `USERID=username`, then EDB\*Loader prompts for `password`. If you specify `USERID=/`, the connection is attempted using the operating system account as the user name.
+
+ !!! Note
+     EDB\*Loader ignores the EDB Postgres Advanced Server connection environment variables `PGUSER` and `PGPASSWORD`. See the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/libpq-pgpass.html) for information on the `PGPASSFILE` environment variable and the password file.
+
+`-c CONNECTION_STRING`
+
+`connstr=CONNECTION_STRING`
+
+ The `-c` or `connstr=` option allows you to specify all the connection parameters supported by libpq. With this option, you can also specify SSL connection parameters or other connection parameters supported by libpq. If you provide connection options such as `-d`, `-h`, `-p`, or `userid=dbuser/dbpass` separately, they might override the values provided by the `-c` or `connstr=` option.
+
+`CONTROL=control_file`
+
+ `control_file` specifies the name of the control file containing EDB\*Loader directives. If you don't specify a file extension, an extension of `.ctl` is assumed.
+
+ For more information on the control file, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+`DATA=data_file`
+
+ `data_file` specifies the name of the file containing the data to load into the target table. If you don't specify a file extension, an extension of `.dat` is assumed. Specifying a `data_file` on the command line overrides the `INFILE` clause specified in the control file.
+
+ For more information about `data_file`, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+`BAD=bad_file`
+
+ `bad_file` specifies the name of a file that receives input data records that can't be loaded due to errors. Specifying `bad_file` on the command line overrides any `BADFILE` clause specified in the control file.
+
+ For more information about `bad_file`, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+`DISCARD=discard_file`
+
+ `discard_file` is the name of the file that receives input data records that don't meet any table’s selection criteria. Specifying `discard_file` on the command line overrides the `DISCARDFILE` clause in the control file.
+
+ For more information about `discard_file`, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+`DISCARDMAX=max_discard_recs`
+
+ `max_discard_recs` is the maximum number of discarded records that can be encountered from the input data records before terminating the EDB\*Loader session. Specifying `max_discard_recs` on the command line overrides the `DISCARDMAX` or `DISCARDS` clause in the control file.
+
+ For more information about `max_discard_recs`, see [Building the EDB\*Loader control file](../building_the_control_file/).
+
+`HANDLE_CONFLICTS={ FALSE | TRUE }`
+
+ If any record insertion fails due to a unique constraint violation, EDB\*Loader aborts the entire operation. You can instruct EDB\*Loader to instead move the duplicate record to the `BAD` file and continue processing by setting `HANDLE_CONFLICTS` to `TRUE`. This behavior applies only if indexes are present. By default, `HANDLE_CONFLICTS` is set to `FALSE`.
+
+ Setting `HANDLE_CONFLICTS` to `TRUE` isn't supported with direct path loading. If you set this parameter to `TRUE` when direct path loading, EDB\*Loader throws an error.
+
+`LOG=log_file`
+
+ `log_file` specifies the name of the file in which EDB\*Loader records the results of the EDB\*Loader session.
+
+ If you omit the `LOG` parameter, EDB\*Loader creates a log file with the name `control_file_base.log` in the directory from which edbldr is invoked. `control_file_base` is the base name of the control file used in the EDB\*Loader session. The operating system account `enterprisedb` must have write permission on the directory where the log file is written.
+
+`PARFILE=param_file`
+
+ `param_file` specifies the name of the file that contains command line parameters for the EDB\*Loader session. You can specify command line parameters listed in this section in `param_file` instead of on the command line. Exceptions are the `-d`, `-p`, and `-h` options, and the `PARFILE` parameter.
+
+ Any parameter given in `param_file` overrides the same parameter supplied on the command line before the `PARFILE` option. Any parameter given on the command line that appears after the `PARFILE` option overrides the same parameter given in `param_file`.
+
+ !!! Note
+    Unlike other EDB\*Loader files, there's no default file name or extension assumed for `param_file`. However, by Oracle SQL\*Loader convention, `.par` is typically used as an extension. It isn't required.
+
+`DIRECT= { FALSE | TRUE }`
+
+ If `DIRECT` is set to `TRUE`, EDB\*Loader performs a direct path load instead of a conventional path load. The default value of `DIRECT` is `FALSE`.
+
+ Don't set `DIRECT=true` when loading the data into a replicated table. If you're using EDB\*Loader to load data into a replicated table and set `DIRECT=true`, indexes might omit rows that are in a table or might contain references to rows that were deleted. EnterpriseDB doesn't support direct inserts to load data into replicated tables.
+
+ For information about direct path loads, see [Direct path load](direct_path_load).
+
+`FREEZE= { FALSE | TRUE }`
+
+ Set `FREEZE` to `TRUE` to copy the data with the rows *frozen*. A tuple guaranteed to be visible to all current and future transactions is marked as frozen to prevent transaction ID wraparound. For more information about frozen tuples, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/routine-vacuuming.html).
+
+ You must specify a data-loading type of `TRUNCATE` in the control file when using the `FREEZE` option. `FREEZE` isn't supported for direct loading.
+
+ By default, `FREEZE` is `FALSE`.
+
+`ERRORS=error_count`
+
+ `error_count` specifies the number of errors permitted before aborting the EDB\*Loader session. The default is `50`.
+
+`PARALLEL= { FALSE | TRUE }`
+
+ Set `PARALLEL` to `TRUE` to indicate that this EDB\*Loader session is one of a number of concurrent EDB\*Loader sessions participating in a parallel direct path load. The default value of `PARALLEL` is `FALSE`.
+
+ When `PARALLEL` is `TRUE`, the `DIRECT` parameter must also be set to `TRUE`.
+
+ For more information about parallel direct path loads, see [Parallel direct path load](parallel_direct_path_load).
+
+`ROWS=n`
+
+ `n` specifies the number of rows that EDB\*Loader commits before loading the next set of `n` rows.
+
+`SKIP=skip_count`
+
+ Number of records at the beginning of the input data file to skip before loading begins. The default is `0`.
+
+`SKIP_INDEX_MAINTENANCE= { FALSE | TRUE }`
+
+ If set to `TRUE`, index maintenance isn't performed as part of a direct path load, and indexes on the loaded table are marked as invalid. The default value of `SKIP_INDEX_MAINTENANCE` is `FALSE`.
+
+ During a parallel direct path load, target table indexes aren't updated. They're marked as invalid after the load is complete.
+
+ You can use the `REINDEX` command to rebuild an index. For more information about the `REINDEX` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-reindex.htm).
+
+`edb_resource_group=group_name`
+
+ `group_name` specifies the name of an EDB Resource Manager resource group to which to assign the EDB\*Loader session.
+
+ Any default resource group that was assigned to the session is overridden by the resource group given by the `edb_resource_group` parameter specified on the edbldr command line. An example of such a group is a database user running the EDB\*Loader session who was assigned a default resource group with the `ALTER ROLE ... SET` `edb_resource_group` command.
+
+## Examples
+
+This example invokes EDB\*Loader using a control file named `emp.ctl` to load a table in database `edb`. The file is located in the current working directory.
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb USERID=enterprisedb/password
+CONTROL=emp.ctl
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+
+Successfully loaded (4) records
+```
+
+In this example, EDB\*Loader prompts for the user name and password since they're omitted from the command line. In addition, the files for the bad file and log file are specified with the `BAD` and `LOG` command line parameters.
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb CONTROL=emp.ctl BAD=/tmp/emp.bad
+LOG=/tmp/emp.log
+Enter the user name : enterprisedb
+Enter the password :
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+
+Successfully loaded (4) records
+```
+
+This example runs EDB\*Loader using a parameter file located in the current working directory. The `SKIP` and `ERRORS` parameter default values are specified in the parameter file in addition the `CONTROL`, `BAD`, and `LOG` files. The parameter file, `emp.par`, contains:
+
+```ini
+CONTROL=emp.ctl
+BAD=/tmp/emp.bad
+LOG=/tmp/emp.log
+SKIP=1
+ERRORS=10
+```
+
+Invoke EDB\*Loader with the parameter file:
+
+```shell
+$ /usr/edb/as16/bin/edbldr -d edb PARFILE=emp.par
+Enter the user name : enterprisedb
+Enter the password :
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+
+Successfully loaded (3) records
+```
+
+This example invokes EDB\*Loader using a `connstr=` option that uses the `emp.ctl` control file located in the current working directory to load a table in a database named `edb`:
+
+```shell
+$ /usr/edb/as16/bin/edbldr connstr=\"sslmode=verify-ca sslcompression=0
+host=127.0.0.1 dbname=edb port=5444 user=enterprisedb\" CONTROL=emp.ctl
+EDB*Loader: Copyright (c) 2007-2021, EnterpriseDB Corporation.
+
+Successfully loaded (4) records
+```
+
+This example invokes EDB\*Loader using a normal user. For this example, one empty table `bar` is created and a normal user `bob` is created. The `bob` user is granted all privileges on the table `bar`. The CREATE TABLE command creates the empty table. The CREATE USER command creates the user, and the GRANT command gives required privileges to the user `bob` on the `bar` table:
+
+```sql
+CREATE TABLE bar(i int); 
+CREATE USER bob identified by '123';
+GRANT ALL on bar TO bob;
+```
+
+The control file and data file:
+
+```shell
+## Control file
+EDBAS/ - (master) $ cat /tmp/edbldr.ctl 
+LOAD DATA INFILE '/tmp/edbldr.dat'
+truncate into table bar
+(
+i position(1:1)
+)
+
+## Data file
+EDBAS/ - (master) $ cat /tmp/edbldr.dat 
+1
+2
+3
+5
+```
+
+Invoke EDB\*Loader:
+
+```shell
+EDBAS/ - (master) $ /usr/edb/as16/bin/edbldr -d edb userid=bob/123 control=/tmp/edbldr.ctl
+EDB*Loader: Copyright (c) 2007-2022, EnterpriseDB Corporation.
+
+Successfully loaded (4) records
+```
+
+<div id="exit_codes" class="registered_link"></div>
+
+## Exit codes
+
+When EDB\*Loader exits, it returns one of the following codes:
+
+| Exit code | Description                                                                                                                                                                 |
+| --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `0`       | All rows loaded successfully.                                                                                                                                |
+| `1`       | EDB\*Loader encountered command line or syntax errors or aborted the load operation due to an unrecoverable error.                                          |
+| `2`       | The load completed, but some or all rows were rejected or discarded.                                                                                       |
+| `3`       | EDB\*Loader encountered fatal errors, such as OS errors. This class of errors is equivalent to the `FATAL` or `PANIC` severity levels of PostgreSQL errors. |
+
diff --git a/product_docs/docs/epas/16/database_administration/02_edb_loader/using_edb_loader.mdx b/product_docs/docs/epas/16/database_administration/02_edb_loader/using_edb_loader.mdx
new file mode 100644
index 00000000000..e053521548d
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/02_edb_loader/using_edb_loader.mdx
@@ -0,0 +1,30 @@
+---
+title: "EDB*Loader error handling"
+description: "Describes the types of errors the EDB*Loader utility can encounter"
+---
+<div id="general_usage" class="registered_link"></div>
+
+EDB\*Loader can load data files with either delimiter-separated or fixed-width fields in single-byte or multibyte character sets. The delimiter can be a string consisting of one or more single-byte or multibyte characters. Data file encoding and the database encoding can differ. Character set conversion of the data file to the database encoding is supported.
+
+Each EDB\*Loader session runs as a single, independent transaction. If an error occurs during the EDB\*Loader session that aborts the transaction, all changes made during the session are rolled back.
+
+Generally, formatting errors in the data file don't result in an aborted transaction. Instead, the badly formatted records are written to a text file called the *bad file*. The reason for the error is recorded in the *log file*.
+
+Records causing database integrity errors result in an aborted transaction and rollback. As with formatting errors, the record causing the error is written to the bad file and the reason is recorded in the log file.
+
+!!! Note
+    EDB\*Loader differs from Oracle SQL\*Loader in that a database integrity error results in a rollback in EDB\*Loader. In Oracle SQL\*Loader, only the record causing the error is rejected. Records that were previously inserted into the table are retained, and loading continues after the rejected record.
+
+The following are examples of types of formatting errors that don't abort the transaction:
+
+-   Attempt to load non-numeric value into a numeric column
+-   Numeric value too large for a numeric column
+-   Character value too long for the maximum length of a character column
+-   Attempt to load improperly formatted date value into a date column
+
+The following are examples of types of database errors that abort the transaction and result in the rollback of all changes made in the EDB\*Loader session:
+
+-   Violating a unique constraint such as a primary key or unique index
+-   Violating a referential integrity constraint
+-   Violating a check constraint
+-   Error thrown by a trigger fired as a result of inserting rows
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/cpu_usage_throttling.mdx b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/cpu_usage_throttling.mdx
new file mode 100644
index 00000000000..bf816166131
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/cpu_usage_throttling.mdx
@@ -0,0 +1,325 @@
+---
+title: "CPU usage throttling"
+description: "How to use EDB Resource Manager to control the CPU use of a resource group"
+---
+
+EDB Resource Manager uses *CPU throttling* to keep the aggregate CPU usage of all processes in the group within the limit specified by the `cpu_rate_limit` parameter. A process in the group might be interrupted and put into sleep mode for a short time to maintain the defined limit. When and how such interruptions occur is defined by a proprietary algorithm used by EDB Resource Manager.
+
+To control CPU use of a resource group, set the `cpu_rate_limit` resource type parameter.
+
+- Set the `cpu_rate_limit` parameter to the fraction of CPU time over wall-clock time to which the combined, simultaneous CPU usage of all processes in the group must not exceed. The value assigned to `cpu_rate_limit` is typically less than or equal to 1.
+
+- On multicore systems, you can apply the `cpu_rate_limit` to more than one CPU core by setting it to greater than 1. For example, if `cpu_rate_limit` is set to 2.0, you use 100% of two CPUs. The valid range of the `cpu_rate_limit` parameter is 0 to 1.67772e+07. A setting of 0 means no CPU rate limit was set for the resource group.
+
+- When the value is multiplied by 100, you can also interpret the `cpu_rate_limit` as the CPU usage percentage for a resource group.
+
+## Setting the CPU rate limit for a resource group
+
+Use the `ALTER RESOURCE GROUP` command with the `SET cpu_rate_limit` clause to set the CPU rate limit for a resource group.
+
+In this example, the CPU usage limit is set to 50% for `resgrp_a`, 40% for `resgrp_b`, and 30% for `resgrp_c`. This means that the combined CPU usage of all processes assigned to `resgrp_a` is maintained at approximately 50%. Similarly, for all processes in `resgrp_b`, the combined CPU usage is kept to approximately 40%, and so on.
+
+```sql
+edb=# ALTER RESOURCE GROUP resgrp_a SET cpu_rate_limit TO .5;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_b SET cpu_rate_limit TO .4;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_c SET cpu_rate_limit TO .3;
+ALTER RESOURCE GROUP
+```
+
+This query shows the settings of `cpu_rate_limit` in the catalog:
+
+```sql
+edb=# SELECT rgrpname, rgrpcpuratelimit FROM edb_resource_group;
+__OUTPUT__
+ rgrpname | rgrpcpuratelimit
+----------+------------------
+ resgrp_a |              0.5
+ resgrp_b |              0.4
+ resgrp_c |              0.3
+(3 rows)
+```
+
+Changing the `cpu_rate_limit` of a resource group affects new processes that are assigned to the group. It also immediately affects any currently running processes that are members of the group. That is, if the `cpu_rate_limit` is changed from .5 to .3, currently running processes in the group are throttled downward so that the aggregate group CPU usage is near 30% instead of 50%.
+
+To show the effect of setting the CPU rate limit for resource groups, the following `psql` command-line examples use a CPU-intensive calculation of 20000 factorial (multiplication of 20000 \* 19999 \* 19998, and so on) performed by the query `SELECT 20000!`. 
+
+The resource groups with the CPU rate limit settings shown in the previous query are used in these examples.
+
+## Example: Single process in a single group
+
+This example shows that the current process is set to use resource group `resgrp_b`. The factorial calculation then starts.
+
+```sql
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+edb=# SELECT 20000!;
+```
+
+In a second session, the Linux `top` command is used to display the CPU usage under the `%CPU` column. Because the `top` command output periodically changes, it represents a snapshot at an arbitrary point in time:
+
+```shell
+$ top
+top - 16:37:03 up  4:15,  7 users,  load average: 0.49, 0.20, 0.38
+Tasks: 202 total,   1 running, 201 sleeping,   0 stopped,   0 zombie
+Cpu(s): 42.7%us,  2.3%sy,  0.0%ni, 55.0%id,  0.0%wa,  0.0%hi,  0.0%si,  0.0
+Mem:   1025624k total,   791160k used,   234464k free,    23400k buffers
+Swap:   103420k total,    13404k used,    90016k free,   373504k cached
+
+  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
+28915 enterpri  20   0  195m 5900 4212 S 39.9  0.6   3:36.98 edb-postgres
+ 1033 root      20   0  171m  77m 2960 S  1.0  7.8   3:43.96 Xorg
+ 3040 user      20   0  278m  22m  14m S  1.0  2.2   3:41.72 knotify4
+    .
+    .
+    .
+```
+
+The row where `edb-postgres` appears under the `COMMAND` column shows the `psql` session performing the factorial calculation. The CPU usage of the session shown under the `%CPU` column is 39.9, which is close to the 40% CPU limit set for resource group `resgrp_b`.
+
+By contrast, if the `psql` session is removed from the resource group and the factorial calculation is performed again, the CPU usage is much higher.
+
+```sql
+edb=# SET edb_resource_group TO DEFAULT;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+
+(1 row)
+
+edb=# SELECT 20000!;
+```
+
+Under the `%CPU` column for `edb-postgres`, the CPU usage is now 93.6, which is significantly higher than the 39.9 when the process was part of the resource group:
+
+```shell
+$ top
+top - 16:43:03 up 4:21, 7 users, load average: 0.66, 0.33, 0.37
+Tasks: 202 total, 5 running, 197 sleeping, 0 stopped, 0 zombie
+Cpu(s): 96.7%us, 3.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0
+Mem: 1025624k total, 791228k used, 234396k free, 23560k buffers
+Swap: 103420k total, 13404k used, 90016k free, 373508k cached
+
+  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+28915 enterpri 20 0 195m 5900 4212 R 93.6 0.6 5:01.56 edb-postgres
+ 1033 root 20 0 171m 77m 2960 S 1.0 7.8 3:48.15 Xorg
+ 2907 user 20 0 98.7m 11m 9100 S 0.3 1.2 0:46.51 vmware-user-lo
+    .
+    .
+    .
+```
+
+## Example: Multiple processes in a single group
+
+As stated previously, the CPU rate limit applies to the aggregate of all processes in the resource group. This concept is shown in the following example.
+
+The factorial calculation is performed simultaneously in two separate `psql` sessions, each of which was added to resource group `resgrp_b` that has `cpu_rate_limit` set to .4 (CPU usage of 40%).
+
+### Session 1
+
+```sql
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+
+edb=# SELECT 20000!;
+```
+
+### Session 2
+
+```sql
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+
+edb=# SELECT 20000!;
+```
+
+A third session monitors the CPU usage:
+
+```shell
+$ top
+top - 16:53:03 up 4:31, 7 users, load average: 0.31, 0.19, 0.27
+Tasks: 202 total, 1 running, 201 sleeping, 0 stopped, 0 zombie
+Cpu(s): 41.2%us, 3.0%sy, 0.0%ni, 55.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0
+Mem: 1025624k total, 792020k used, 233604k free, 23844k buffers
+Swap: 103420k total, 13404k used, 90016k free, 373508k cached
+
+  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
+29857 enterpri 20 0 195m 4708 3312 S 19.9 0.5 0:57.35 edb-postgres
+28915 enterpri 20 0 195m 5900 4212 S 19.6 0.6 5:35.49 edb-postgres
+ 3040 user 20 0 278m 22m 14m S 1.0 2.2 3:54.99 knotify4
+ 1033 root 20 0 171m 78m 2960 S 0.3 7.8 3:55.71 Xorg
+    .
+    .
+    .
+```
+
+Two new processes named `edb-postgres` have `%CPU` values of 19.9 and 19.6. The sum is close to the 40% CPU usage set for resource group `resgrp_b`.
+
+This command sequence displays the sum of all `edb-postgres` processes sampled over half-second time intervals. This example shows how the total CPU usage of the processes in the resource group changes over time as EDB Resource Manager throttles the processes to keep the total resource group CPU usage near 40%.
+
+```shell
+$ while [[ 1 -eq 1 ]]; do  top -d0.5 -b -n2 | grep edb-postgres | awk '{ SUM
++= $9} END { print SUM / 2 }'; done
+37.2
+39.1
+38.9
+38.3
+44.7
+39.2
+42.5
+39.1
+39.2
+39.2
+41
+42.85
+46.1
+    .
+    .
+    .
+```
+
+## Example: Multiple processes in multiple groups
+
+In this example, two additional `psql` sessions are used along with the previous two sessions. The third and fourth sessions perform the same factorial calculation in resource group `resgrp_c` with a `cpu_rate_limit` of `.3` (30% CPU usage).
+
+### Session 3
+
+```sql
+edb=# SET edb_resource_group TO resgrp_c;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_c
+(1 row)
+
+edb=# SELECT 20000!;
+```
+
+### Session 4
+
+```sql
+edb=# SET edb_resource_group TO resgrp_c;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_c
+(1 row)
+edb=# SELECT 20000!;
+```
+
+The `top` command displays the following output:
+
+```shell
+$ top
+top - 17:45:09 up 5:23, 8 users, load average: 0.47, 0.17, 0.26
+Tasks: 203 total, 4 running, 199 sleeping, 0 stopped, 0 zombie
+Cpu(s): 70.2%us, 0.0%sy, 0.0%ni, 29.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0
+Mem: 1025624k total, 806140k used, 219484k free, 25296k buffers
+Swap: 103420k total, 13404k used, 90016k free, 374092k cached
+
+  PID   USER     PR NI VIRT RES  SHR  S %CPU %MEM TIME+   COMMAND
+29857 enterpri 20 0  195m 4820 3324 S 19.9 0.5  4:25.02 edb-postgres
+28915 enterpri 20 0  195m 5900 4212 R 19.6 0.6  9:07.50 edb-postgres
+29023 enterpri 20 0  195m 4744 3248 R 16.3 0.5  4:01.73 edb-postgres
+11019 enterpri 20 0  195m 4120 2764 R 15.3 0.4  0:04.92 edb-postgres
+ 2907  user     20 0  98.7m 12m 9112 S  1.3 1.2  0:56.54 vmware-user-lo
+ 3040  user     20 0  278m  22m  14m S  1.3 2.2  4:38.73 knotify4
+```
+
+The two resource groups in use have CPU usage limits of 40% and 30%. The sum of the `%CPU` column for the first two `edb-postgres` processes is 39.5 (approximately 40%, which is the limit for `resgrp_b`). The sum of the `%CPU` column for the third and fourth `edb-postgres` processes is 31.6 (approximately 30%, which is the limit for `resgrp_c`).
+
+The sum of the CPU usage limits of the two resource groups to which these processes belong is 70%. The following output shows that the sum of the four processes borders around 70%:
+
+```shell
+$ while [[ 1 -eq 1 ]]; do  top -d0.5 -b -n2 | grep edb-postgres | awk '{ SUM
++= $9} END { print SUM / 2 }'; done
+61.8
+76.4
+72.6
+69.55
+64.55
+79.95
+68.55
+71.25
+74.85
+62
+74.85
+76.9
+72.4
+65.9
+74.9
+68.25
+```
+
+By contrast, if three sessions are processing. where two sessions remain in `resgrp_b` but the third session doesn't belong to any resource group, the `top` command shows the following output:
+
+```shell
+$ top
+top - 17:24:55 up 5:03, 7 users, load average: 1.00, 0.41, 0.38
+Tasks: 199 total, 3 running, 196 sleeping, 0 stopped, 0 zombie
+Cpu(s): 99.7%us, 0.3%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0
+Mem: 1025624k total, 797692k used, 227932k free, 24724k buffers
+Swap: 103420k total,  13404k used,  90016k free, 374068k cached
+
+  PID   USER     PR  NI  VIRT  RES  SHR  S  %CPU  %MEM TIME+   COMMAND
+29023 enterpri 20   0  195m  4744 3248 R  58.6  0.5  2:53.75 edb-postgres
+28915 enterpri 20   0  195m  5900 4212 S  18.9  0.6  7:58.45 edb-postgres
+29857 enterpri 20   0  195m  4820 3324 S  18.9  0.5  3:14.85 edb-postgres
+ 1033 root     20   0  174m   81m 2960 S   1.7  8.2  4:26.50 Xorg
+ 3040 user     20   0  278m   22m  14m S   1.0  2.2  4:21.20 knotify4
+```
+
+The second and third `edb-postgres` processes belonging to the resource group where the CPU usage is limited to 40% have a total CPU usage of 37.8. However, the first `edb-postgres` process has a 58.6% CPU usage, as it isn't within a resource group. It basically uses the remaining available CPU resources on the system.
+
+Likewise, the following output shows the sum of all three sessions is around 95%, since one of the sessions has no set limit on its CPU usage:
+
+```shell
+$ while [[ 1 -eq 1 ]]; do  top -d0.5 -b -n2 | grep edb-postgres | awk '{ SUM
++= $9} END { print SUM / 2 }'; done
+96
+90.35
+92.55
+96.4
+94.1
+90.7
+95.7
+95.45
+93.65
+87.95
+96.75
+94.25
+95.45
+97.35
+92.9
+96.05
+96.25
+94.95
+    .
+    .
+    .
+```
diff --git a/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/creating_resource_groups.mdx b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/creating_resource_groups.mdx
new file mode 100644
index 00000000000..0723a4a35b7
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/creating_resource_groups.mdx
@@ -0,0 +1,278 @@
+---
+title: "Working with resource groups"
+description: "How to use EDB Resource Manager to create and manage resource groups"
+---
+
+Use these data definition language commands to create and manage resource groups.
+
+## Creating a resource group
+
+Use the `CREATE RESOURCE GROUP` command to create a new resource group.
+
+```sql
+CREATE RESOURCE GROUP <group_name>;
+```
+
+### Description
+
+The `CREATE RESOURCE GROUP` command creates a resource group with the specified name. You can then define resource limits on the group with the `ALTER RESOURCE GROUP` command. The resource group is accessible from all databases in the EDB Postgres Advanced Server instance.
+
+To use the `CREATE RESOURCE GROUP` command, you must have superuser privileges.
+
+### Parameters
+
+`group_name`
+
+The name of the resource group.
+
+### Example
+
+This example creates three resource groups named `resgrp_a`, `resgrp_b`, and `resgrp_c`:
+
+```sql
+edb=# CREATE RESOURCE GROUP resgrp_a;
+CREATE RESOURCE GROUP
+edb=# CREATE RESOURCE GROUP resgrp_b;
+CREATE RESOURCE GROUP
+edb=# CREATE RESOURCE GROUP resgrp_c;
+CREATE RESOURCE GROUP
+```
+
+This query shows the entries for the resource groups in the `edb_resource_group` catalog:
+
+```sql
+edb=# SELECT * FROM edb_resource_group;
+__OUTPUT__
+ rgrpname  | rgrpcpuratelimit | rgrpdirtyratelimit
+-----------+------------------+--------------------
+ resgrp_a  |                0 | 0
+ resgrp_b  |                0 | 0
+ resgrp_c  |                0 | 0
+(3 rows)
+```
+
+## Modifying a resource group
+
+Use the `ALTER RESOURCE GROUP` command to change the attributes of an existing resource group. The command syntax comes in three forms.
+
+This form renames the resource group:
+
+```sql
+ALTER RESOURCE GROUP <group_name> RENAME TO <new_name>;
+```
+
+This form assigns a resource type to the resource group:
+
+```sql
+ALTER RESOURCE GROUP <group_name> SET
+  <resource_type> { TO | = } { <value> | DEFAULT };
+```
+
+This form resets the assignment of a resource type to its default in the group:
+
+```sql
+ALTER RESOURCE GROUP <group_name> RESET <resource_type>;
+```
+
+### Description
+
+The `ALTER RESOURCE GROUP` command changes certain attributes of an existing resource group.
+
+The form with the `RENAME TO` clause assigns a new name to an existing resource group.
+
+The form with the `SET resource_type TO` clause assigns the specified literal value to a resource type. Or, when you specify `DEFAULT`, it resets the resource type. Resetting a resource type means that the resource group has no defined limit on that resource type.
+
+The form with the `RESET resource_type` clause resets the resource type for the group.
+
+To use the `ALTER RESOURCE GROUP` command, you must have superuser privileges.
+
+### Parameters
+
+`group_name`
+
+The name of the resource group to alter.
+
+`new_name`
+
+The new name to assign to the resource group.
+
+`resource_type`
+
+Specifies the type of resource to which to set a usage value.
+
+`value | DEFAULT`
+
+When `value` is specified, the literal value to assign to `resource_type`. Specify `DEFAULT` to reset the assignment of `resource_type` for the resource group.
+
+### Example
+
+These examples show the use of the `ALTER RESOURCE GROUP` command:
+
+```sql
+edb=# ALTER RESOURCE GROUP resgrp_a RENAME TO newgrp;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_b SET cpu_rate_limit = .5;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_b SET dirty_rate_limit = 6144;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_c RESET cpu_rate_limit;
+ALTER RESOURCE GROUP
+```
+
+This query shows the results of the `ALTER RESOURCE GROUP` commands to the entries in the `edb_resource_group` catalog:
+
+```sql
+edb=# SELECT * FROM edb_resource_group;
+__OUTPUT__
+ rgrpname  | rgrpcpuratelimit | rgrpdirtyratelimit
+-----------+------------------+--------------------
+ newgrp    | 0                | 0
+ resgrp_b  | 0.5              | 6144
+ resgrp_c  | 0                | 0
+(3 rows)
+```
+
+## Removing a resource group
+
+Use the `DROP RESOURCE GROUP` command to remove a resource group.
+
+```sql
+DROP RESOURCE GROUP [ IF EXISTS ] <group_name>;
+```
+
+### Description
+
+The `DROP RESOURCE GROUP` command removes a resource group with the specified name.
+
+To use the `DROP RESOURCE GROUP` command, you must have superuser privileges.
+
+### Parameters
+
+`group_name`
+
+The name of the resource group to remove.
+
+`IF EXISTS`
+
+Don't throw an error if the resource group doesn't exist. Instead, issue a notice.
+
+### Example
+
+This example removes the resource group `newgrp`:
+
+```sql
+edb=# DROP RESOURCE GROUP newgrp;
+DROP RESOURCE GROUP
+```
+
+## Assigning a process to a resource group
+
+Use the `SET edb_resource_group TO group_name` command to assign the current process to a specified resource group:
+
+```sql
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+```
+
+The resource type settings of the group take effect on the current process immediately. If you use the command to change the resource group assigned to the current process, the resource type settings of the newly assigned group take effect immediately.
+
+You can include processes in a resource group by default by assigning a default resource group to roles, databases, or an entire database server instance.
+
+You can assign a default resource group to a role using the `ALTER ROLE ... SET` command. For more information about the `ALTER ROLE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-alterrole.html).
+
+You can assign a default resource group to a database by using the `ALTER DATABASE ... SET` command. For more information about the `ALTER DATABASE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-alterdatabase.html).
+
+You can assign the entire database server instance a default resource group by setting the `edb_resource_group` configuration parameter in the `postgresql.conf` file:
+
+```ini
+# - EDB Resource Manager -
+#edb_max_resource_groups = 16           # 0-65536 (change requires restart)
+edb_resource_group = 'resgrp_b'
+```
+
+If you change `edb_resource_group` in the `postgresql.conf` file, reload the configuration file to make it take effect on the database server instance.
+
+## Removing a process from a resource group
+
+Set `edb_resource_group` to `DEFAULT` or use `RESET edb_resource_group` to remove the current process from a resource group:
+
+```sql
+edb=# SET edb_resource_group TO DEFAULT;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+(1 row)
+```
+
+To remove a default resource group from a role, use the `ALTER ROLE ... RESET` form of the `ALTER ROLE` command.
+
+To remove a default resource group from a database, use the `ALTER DATABASE ... RESET` form of the `ALTER DATABASE` command.
+
+To remove a default resource group from the database server instance, set the `edb_resource_group` configuration parameter to an empty string in the `postgresql.conf` file. Then, reload the configuration file.
+
+## Monitoring processes in resource groups
+
+After you create resource groups, you can get the number of processes actively using these resource groups from the view `edb_all_resource_groups`.
+
+The following are the columns in `edb_all_resource_groups`:
+
+-   **group_name.** Name of the resource group.
+-   **active_processes.** Number of active processes in the resource group.
+-   **cpu_rate_limit.** The value of the CPU rate limit resource type assigned to the resource group.
+-   **per_process_cpu_rate_limit.** The CPU rate limit that applies to an individual active process in the resource group.
+-   **dirty_rate_limit.** The value of the dirty rate limit resource type assigned to the resource group.
+-   **per_process_dirty_rate_limit.** The dirty rate limit that applies to an individual active process in the resource group.
+
+!!! Note
+    Columns `per_process_cpu_rate_limit` and `per_process_dirty_rate_limit` don't show the actual resource consumption used by the processes. They indicate how `EDB Resource Manager` sets the resource limit for an individual process based on the number of active processes in the resource group.
+
+This example shows `edb_all_resource_groups` when resource group `resgrp_a` contains no active processes, resource group `resgrp_b` contains two active processes, and resource group `resgrp_c` contains one active process:
+
+```sql
+edb=# SELECT * FROM edb_all_resource_groups ORDER BY group_name;
+__OUTPUT__
+-[ RECORD 1 ]-----------------+------------------
+ group_name                   | resgrp_a
+ active_processes             | 0
+ cpu_rate_limit               | 0.5
+ per_process_cpu_rate_limit   |
+ dirty_rate_limit             | 12288
+ per_process_dirty_rate_limit |
+-[ RECORD 2 ]-----------------+------------------
+ group_name                   | resgrp_b
+ active_processes             | 2
+ cpu_rate_limit               | 0.4
+ per_process_cpu_rate_limit   | 0.195694289022895
+ dirty_rate_limit             | 6144
+ per_process_dirty_rate_limit | 3785.92924684337
+-[ RECORD 3 ]-----------------+------------------
+ group_name                   | resgrp_c
+ active_processes             | 1
+ cpu_rate_limit               | 0.3
+ per_process_cpu_rate_limit   | 0.292342129631091
+ dirty_rate_limit             | 3072
+ per_process_dirty_rate_limit | 3072
+```
+
+The CPU rate limit and dirty rate limit settings that are assigned to these resource groups are:
+
+```sql
+edb=# SELECT * FROM edb_resource_group;
+__OUTPUT__
+ rgrpname  | rgrpcpuratelimit | rgrpdirtyratelimit
+-----------+------------------+--------------------
+ resgrp_a  | 0.5              | 12288
+ resgrp_b  | 0.4              | 6144
+ resgrp_c  | 0.3              | 3072
+(3 rows)
+```
+
+In the `edb_all_resource_groups` view, the `per_process_cpu_rate_limit` and `per_process_dirty_rate_limit` values are roughly the corresponding CPU rate limit and dirty rate limit divided by the number of active processes.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx
new file mode 100644
index 00000000000..5f6ad2cf0ee
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/dirty_buffer_throttling.mdx
@@ -0,0 +1,397 @@
+---
+title: "Dirty buffer throttling"
+description: "How to use EDB Resource Manager to control writing to shared buffers"
+---
+
+EDB Resource Manager uses *dirty buffer throttling* to keep the aggregate shared buffer writing rate of all processes in the group near the limit specified by the `dirty_rate_limit` parameter. A process in the group might be interrupted and put into sleep mode for a short time to maintain the defined limit. When and how such interruptions occur is defined by a proprietary algorithm used by EDB Resource Manager.
+
+To control writing to shared buffers, set the `dirty_rate_limit` resource type parameter.
+
+- Set the `dirty_rate_limit` parameter to the number of kilobytes per second for the combined rate at which all the processes in the group write to, or “dirty”, the shared buffers. An example setting is 3072 kilobytes per seconds.
+
+- The valid range of the `dirty_rate_limit` parameter is 0 to 1.67772e+07. A setting of 0 means no dirty rate limit was set for the resource group.
+
+## Setting the dirty rate limit for a resource group
+
+Use the `ALTER RESOURCE GROUP` command with the `SET dirty_rate_limit` clause to set the dirty rate limit for a resource group.
+
+In this example, the dirty rate limit is set to 12288 kilobytes per second for `resgrp_a`, 6144 kilobytes per second for `resgrp_b`, and 3072 kilobytes per second for `resgrp_c`. This means that the combined writing rate to the shared buffer of all processes assigned to `resgrp_a` is maintained at approximately 12288 kilobytes per second. Similarly, for all processes in `resgrp_b`, the combined writing rate to the shared buffer is kept to approximately 6144 kilobytes per second, and so on.
+
+```sql
+edb=# ALTER RESOURCE GROUP resgrp_a SET dirty_rate_limit TO 12288;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_b SET dirty_rate_limit TO 6144;
+ALTER RESOURCE GROUP
+edb=# ALTER RESOURCE GROUP resgrp_c SET dirty_rate_limit TO 3072;
+ALTER RESOURCE GROUP
+```
+
+This query shows the settings of `dirty_rate_limit` in the catalog;
+
+```sql
+edb=# SELECT rgrpname, rgrpdirtyratelimit FROM edb_resource_group;
+__OUTPUT__
+ rgrpname  | rgrpdirtyratelimit
+-----------+--------------------
+ resgrp_a  |         12288
+ resgrp_b  |         6144
+ resgrp_c  |         3072
+(3 rows)
+```
+## Changing the dirty rate limit
+
+Changing the `dirty_rate_limit` of a resource group affects new processes that are assigned to the group. Any currently running processes that are members of the group are also immediately affected by the change. That is, if the `dirty_rate_limit` is changed from 12288 to 3072, currently running processes in the group are throttled downward so that the aggregate group dirty rate is near 3072 kilobytes per second instead of 12288 kilobytes per second.
+
+To show the effect of setting the dirty rate limit for resource groups, the examples use the following table for intensive I/O operations:
+
+```sql
+CREATE TABLE t1 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+```
+
+The `FILLFACTOR = 10` clause results in `INSERT` commands packing rows up to only 10% per page. The result is a larger sampling of dirty shared blocks for the purpose of these examples.
+
+## Displaying the number of dirty buffers
+
+The `pg_stat_statements` module is used to display the number of shared buffer blocks that are dirtied by a SQL command and the amount of time the command took to execute. This information is used to calculate the actual kilobytes per second writing rate for the SQL command and thus compare it to the dirty rate limit set for a resource group.
+
+To use the `pg_stat_statements` module:
+
+1.  In the `postgresql.conf` file, add `$libdir/pg_stat_statements` to the `shared_preload_libraries` configuration parameter:
+
+  ```ini
+  shared_preload_libraries = '$libdir/dbms_pipe,$libdir/edb_gen,$libdir/pg_stat_statements'
+  ```
+
+2.  Restart the database server.
+
+3.  Use the `CREATE EXTENSION` command to finish creating the `pg_stat_statements` module:
+
+  ```sql
+  edb=# CREATE EXTENSION pg_stat_statements SCHEMA public;
+  CREATE EXTENSION
+  ```
+
+  The `pg_stat_statements_reset()` function clears out the `pg_stat_statements` view for clarity of each example.
+
+The resource groups with the dirty rate limit settings shown in the previous query are used in these examples.
+
+<div id="example-single-process-in-a-single-group-1" class="registered_link"></div>
+
+## Example: Single process in a single group
+
+This sequence of commands creates table `t1`. The current process is set to use resource group `resgrp_b`. The `pg_stat_statements` view is cleared out by running the `pg_stat_statements_reset()` function.
+
+The `INSERT` command then generates a series of integers from 1 to 10,000 to populate the table and dirty approximately 10,000 blocks:
+
+```sql
+edb=# CREATE TABLE t1 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+```
+```sql
+edb=# SELECT pg_stat_statements_reset();
+__OUTPUT__
+ pg_stat_statements_reset
+--------------------------
+
+(1 row)
+
+edb=# INSERT INTO t1 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+This example shows the results from the `INSERT` command:
+
+```sql
+edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM
+pg_stat_statements;
+__OUTPUT__
+-[ RECORD 1 ]--------+--------------------------------------------------
+ query               | INSERT INTO t1 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 13496.184
+ shared_blks_dirtied | 10003
+```
+
+The actual dirty rate is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 13496.184 ms, which yields 0.74117247 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 741.17247 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 6072 kilobytes per second.
+
+The actual dirty rate of 6072 kilobytes per second is close to the dirty rate limit for the resource group, which is 6144 kilobytes per second.
+
+By contrast, if you repeat the steps without the process belonging to any resource group, the dirty buffer rate is much higher:
+
+```sql
+edb=# CREATE TABLE t1 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+
+(1 row)
+```
+```sql
+edb=# SELECT pg_stat_statements_reset();
+__OUTPUT__
+ pg_stat_statements_reset
+--------------------------
+
+(1 row)
+
+edb=# INSERT INTO t1 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+This example shows the results from the `INSERT` command without the use of a resource group:
+
+```sql
+edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM
+pg_stat_statements;
+__OUTPUT__
+-[ RECORD 1 ]--------+--------------------------------------------------
+ query               | INSERT INTO t1 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 2432.165
+ shared_blks_dirtied | 10003
+```
+
+The total time was only 2432.165 milliseconds, compared to 13496.184 milliseconds when using a resource group with a dirty rate limit set to 6144 kilobytes per second.
+
+The actual dirty rate without the use of a resource group is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 2432.165 ms, which yields 4.112797 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 4112.797 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 33692 kilobytes per second.
+
+The actual dirty rate of 33692 kilobytes per second is much higher than when the resource group with a dirty rate limit of 6144 kilobytes per second was used.
+
+<div id="example-multiple-processes-in-a-single-group-1" class="registered_link"></div>
+
+## Example: Multiple processes in a single group
+
+As stated previously, the dirty rate limit applies to the aggregate of all processes in the resource group. This concept is illustrated in the following example.
+
+For this example, the inserts are performed simultaneously on two different tables in two separate `psql` sessions, each of which was added to resource group `resgrp_b` that has a `dirty_rate_limit` set to 6144 kilobytes per second.
+
+### Session 1
+
+```sql
+edb=# CREATE TABLE t1 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+
+edb=# INSERT INTO t1 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+### Session 2
+
+```sql
+edb=# CREATE TABLE t2 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SET edb_resource_group TO resgrp_b;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_b
+(1 row)
+```
+```sql
+edb=# SELECT pg_stat_statements_reset();
+__OUTPUT__
+ pg_stat_statements_reset
+--------------------------
+(1 row)
+
+edb=# INSERT INTO t2 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+!!! Note
+    The `INSERT` commands in session 1 and session 2 started after the `SELECT pg_stat_statements_reset()` command in session 2 ran.
+
+This example shows the results from the `INSERT` commands in the two sessions. `RECORD 3` shows the results from session 1. `RECORD 2` shows the results from session 2.
+
+```sql
+edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM
+pg_stat_statements;
+__OUTPUT__
+-[ RECORD 1 ]--------+--------------------------------------------------
+ query               | SELECT pg_stat_statements_reset();
+ rows                | 1
+ total_time          | 0.43
+ shared_blks_dirtied | 0
+-[ RECORD 2 ]--------+--------------------------------------------------
+ query               | INSERT INTO t2 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 30591.551
+ shared_blks_dirtied | 10003
+-[ RECORD 3 ]--------+--------------------------------------------------
+ query               | INSERT INTO t1 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 33215.334
+ shared_blks_dirtied | 10003
+```
+
+The total time was 33215.334 milliseconds for session 1 and 30591.551 milliseconds for session 2. When only one session was active in the same resource group, the time was 13496.184 milliseconds. Thus, more active processes in the resource group result in a slower dirty rate for each active process in the group. The following calculations show this.
+
+The actual dirty rate for session 1 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 33215.334 ms, which yields 0.30115609 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 301.15609 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2467 kilobytes per second.
+
+The actual dirty rate for session 2 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 30591.551 ms, which yields 0.32698571 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 326.98571 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2679 kilobytes per second.
+
+The combined dirty rate from session 1 (2467 kilobytes per second) and from session 2 (2679 kilobytes per second) yields 5146 kilobytes per second, which is below the set dirty rate limit of the resource group (6144 kilobytes per seconds).
+
+<div id="example-multiple-processes-in-multiple-groups-1" class="registered_link"></div>
+
+## Example: Multiple processes in multiple groups
+
+In this example, two additional `psql` sessions are used along with the previous two sessions. The third and fourth sessions perform the same `INSERT` command in resource group `resgrp_c` with a `dirty_rate_limit` of 3072 kilobytes per second.
+
+Repeat sessions 1 and 2 from the prior example using resource group `resgrp_b` with a `dirty_rate_limit` of 6144 kilobytes per second:
+
+### Session 3
+
+```sql
+edb=# CREATE TABLE t3 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SET edb_resource_group TO resgrp_c;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+
+
+resgrp_c
+(1 row)
+
+edb=# INSERT INTO t3 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+### Session 4
+
+```sql
+edb=# CREATE TABLE t4 (c1 INTEGER, c2 CHARACTER(500)) WITH (FILLFACTOR = 10);
+CREATE TABLE
+edb=# SET edb_resource_group TO resgrp_c;
+SET
+edb=# SHOW edb_resource_group;
+__OUTPUT__
+ edb_resource_group
+--------------------
+ resgrp_c
+(1 row)
+```
+```sql
+edb=# SELECT pg_stat_statements_reset();
+__OUTPUT__
+ pg_stat_statements_reset
+--------------------------
+
+(1 row)
+
+edb=# INSERT INTO t4 VALUES (generate_series (1,10000), 'aaa');
+INSERT 0 10000
+```
+
+!!! Note
+    The `INSERT` commands in all four sessions started after the `SELECT pg_stat_statements_reset()` command in session 4 ran.
+
+This example shows the results from the `INSERT` commands in the four sessions:
+
+-  `RECORD 3` shows the results from session 1. `RECORD 2` shows the results from session 2.
+
+-  `RECORD 4` shows the results from session 3. `RECORD 5` shows the results from session 4.
+
+```sql
+edb=# SELECT query, rows, total_time, shared_blks_dirtied FROM
+pg_stat_statements;
+__OUTPUT__
+-[ RECORD 1 ]--------+--------------------------------------------------
+ query               | SELECT pg_stat_statements_reset();
+ rows                | 1
+ total_time          | 0.467
+ shared_blks_dirtied | 0
+-[ RECORD 2 ]--------+--------------------------------------------------
+ query               | INSERT INTO t2 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 31343.458
+ shared_blks_dirtied | 10003
+-[ RECORD 3 ]--------+--------------------------------------------------
+ query               | INSERT INTO t1 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 28407.435
+ shared_blks_dirtied | 10003
+-[ RECORD 4 ]--------+--------------------------------------------------
+ query               | INSERT INTO t3 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 52727.846
+ shared_blks_dirtied | 10003
+-[ RECORD 5 ]--------+--------------------------------------------------
+ query               | INSERT INTO t4 VALUES (generate_series (?,?), ?);
+ rows                | 10000
+ total_time          | 56063.697
+ shared_blks_dirtied | 10003
+```
+
+The times of session 1 (28407.435) and session 2 (31343.458) are close to each other, as they are both in the same resource group with `dirty_rate_limit` set to 6144. These times differe from the times of session 3 (52727.846) and session 4 (56063.697), which are in the resource group with `dirty_rate_limit` set to 3072. The latter group has a slower dirty rate limit, so the expected processing time is longer, as is the case for sessions 3 and 4.
+
+The actual dirty rate for session 1 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 28407.435 ms, which yields 0.35212612 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 352.12612 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2885 kilobytes per second.
+
+The actual dirty rate for session 2 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 31343.458 ms, which yields 0.31914156 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 319.14156 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 2614 kilobytes per second.
+
+The combined dirty rate from session 1 (2885 kilobytes per second) and from session 2 (2614 kilobytes per second) yields 5499 kilobytes per second, which is near the set dirty rate limit of the resource group (6144 kilobytes per seconds).
+
+The actual dirty rate for session 3 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 52727.846 ms, which yields 0.18971001 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 189.71001 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 1554 kilobytes per second.
+
+The actual dirty rate for session 4 is calculated as follows:
+
+-   The number of blocks dirtied per millisecond (ms) is 10003 blocks / 56063.697 ms, which yields 0.17842205 blocks per millisecond.
+-   Multiply the result by 1000 to give the number of shared blocks dirtied per second (1 second = 1000 ms), which yields 178.42205 blocks per second.
+-   Multiply the result by 8.192 to give the number of kilobytes dirtied per second (1 block = 8.192 kilobytes), which yields approximately 1462 kilobytes per second.
+
+The combined dirty rate from session 3 (1554 kilobytes per second) and from session 4 (1462 kilobytes per second) yields 3016 kilobytes per second, which is near the set dirty rate limit of the resource group (3072 kilobytes per seconds).
+
+This example shows how EDB Resource Manager keeps the aggregate dirty rate of the active processes in its groups close to the dirty rate limit set for each group.
+
+<div id="system-catalogs-1" class="registered_link"></div>
diff --git a/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/edb_resource_manager_key_concepts.mdx b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/edb_resource_manager_key_concepts.mdx
new file mode 100644
index 00000000000..873501369b8
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/edb_resource_manager_key_concepts.mdx
@@ -0,0 +1,20 @@
+---
+title: "EDB Resource Manager key concepts"
+navTitle: "Key concepts"
+description: "Describes key points about using EDB Resource Manager"
+---
+
+You use EDB Resource Manager to control the use of operating system resources used by EDB Postgres Advanced Server processes.
+
+Some key points about using EDB Resource Manager are:
+
+-   The basic component of EDB Resource Manager is a *resource group*. A resource group is a named, global group. It's available to all databases in an EDB Postgres Advanced Server instance, and you can define various resource usage limits on it. EDB Postgres Advanced Server processes that are assigned as members of a given resource group are then controlled by EDB Resource Manager. This configuration keeps the aggregate resource use of all processes in the group near the limits defined on the group.
+-   Data definition language commands are used to create, alter, and drop resource groups. Only a database user with superuser privileges can use these commands.
+-   *Resource type parameters* define the desired aggregate consumption level of all processes belonging to a resource group. You use different resource type parameters for the different types of system resources currently supported by EDB Resource Manager.
+-   You can create multiple resource groups, each with different settings for its resource type parameters, which defines different consumption levels for each resource group.
+-   EDB Resource Manager throttles processes in a resource group to keep resource consumption near the limits defined by the resource type parameters. If multiple resource type parameters have defined settings in a resource group, the actual resource consumption might be significantly lower for certain resource types than their defined resource type parameter settings. This lower consumption happens because EDB Resource Manager throttles processes, attempting to keep all resources with defined resource type settings within their defined limits.
+-   The definitions of available resource groups and their resource type settings are stored in a shared global system catalog. Thus, all databases in a given EDB Postgres Advanced Server instance can use resource groups.
+-   The `edb_max_resource_groups` configuration parameter sets the maximum number of resource groups that can be active at the same time as running processes. The default setting is 16 resource groups. Changes to this parameter take effect when you restart the database server.
+-   Use the `SET edb_resource_group TO group_name` command to assign the current process to a specified resource group. Use the `RESET edb_resource_group` command or `SET edb_resource_group` to `DEFAULT` to remove the current process from a resource group.
+-   You can assign a default resource group to a role using the `ALTER ROLE ... SET` command or to a database using the `ALTER DATABASE ... SET` command. You can assign the entire database server instance a default resource group by setting the parameter in the `postgresql.conf` file.
+-   To include resource groups in a backup file of the database server instance, use the `pg_dumpall` backup utility with default settings. That is, don't specify any of the `--globals-only`, `--roles-only`, or `--tablespaces-only` options.
diff --git a/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/index.mdx b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/index.mdx
new file mode 100644
index 00000000000..4c059c256a4
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/10_edb_resource_manager/index.mdx
@@ -0,0 +1,32 @@
+---
+title: "Throttling CPU and I/O at the process level"
+navTitle: "EDB Resource Manager"
+indexCards: simple
+description: "How to use EDB Resource Manager to control the use of operating system resources used by EDB Postgres Advanced Server processes"
+navigation:
+  - edb_resource_manager_key_concepts
+  - creating_resource_groups
+  - cpu_usage_throttling
+  - dirty_buffer_throttling
+  - edb_resource_manager_system_catalogs
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.37.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.35.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.34.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.33.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.36.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.083.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.082.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.079.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.081.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.080.html"
+---
+
+<div id="edb_resource_manager" class="registered_link"></div>
+
+EDB Resource Manager is an EDB Postgres Advanced Server feature that lets you control the use of operating system resources used by EDB Postgres Advanced Server processes.
+
+This capability allows you to protect the system from processes that might uncontrollably overuse and monopolize certain system resources. 
+
+
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/checking_the_status.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/checking_the_status.mdx
new file mode 100644
index 00000000000..b5a9e7eadb3
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/checking_the_status.mdx
@@ -0,0 +1,45 @@
+---
+title: "Checking the status of the cloning process"
+navTitle: "Checking status"
+description: "Describes how to obtain the status of the cloning function"
+---
+
+<div id="process_status_from_log" class="registered_link"></div>
+
+The `process_status_from_log` function provides the status of a cloning function from its log file:
+
+```sql
+process_status_from_log (
+  <log_file> TEXT
+)
+```
+
+The function returns the following fields from the log file:
+
+| Field name       | Description                                                                                               |
+| ---------------- | --------------------------------------------------------------------------------------------------------- |
+| `status`         | Displays either `STARTING`, `RUNNING`, `FINISH`, or `FAILED`.                                             |
+| `execution_time` | When the command was executed. Displayed in timestamp format.                                             |
+| `pid`            | Session process ID in which clone schema is getting called.                                               |
+| `level`          | Displays either `INFO`, `ERROR`, or `SUCCESSFUL`.                                                         |
+| `stage`          | Displays either `STARTUP`, `INITIAL`, `DDL-COLLECTION`, `PRE-DATA`, `DATA-COPY`, `POST-DATA`, or `FINAL`. |
+| `message`        | Information respective to each command or failure.                                                        |
+
+## Parameters
+
+`log_file`
+
+Name of the log file recording the cloning of a schema as specified when the cloning function was invoked.
+
+## Example
+
+The following shows the use of the `process_status_from_log` function:
+
+```sql
+edb=# SELECT edb_util.process_status_from_log('clone_edb_edbcopy');
+__OUTPUT__
+                                      process_status_from_log
+---------------------------------------------------------------------------------------------------
+ (FINISH,"26-JUN-17 11:57:03.214458 -04:00",3691,INFO,"STAGE: FINAL","successfully cloned schema")
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx
new file mode 100644
index 00000000000..36110b453dd
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_remote_schema.mdx
@@ -0,0 +1,327 @@
+---
+title: "Copying database objcts from a remote source"
+navTitle: "Copying a remote database"
+description: "Describes how to copy a database when the source schema and the copy will reside in separate databases"
+---
+
+There are two functions you can use with EDB Clone Schema to perform a remote copy of a schema and its database objects:
+
+-   `remotecopyschema` &mdash; This function copies a schema and its database objects from a source database to a different target database. Use this function when the source schema and the copy will reside in separate databases. The separate databases can reside in the same EDB Postgres Advanced Server database clusters or in different ones. See [remotecopyschema](#remotecopyschema) for more information.
+-   `remotecopyschema_nb` &mdash; This function performs the same purpose as `remotecopyschema` but as a background job, which frees up the terminal from which the function was initiated. This function is a non-blocking function. See [remotecopyschema_nb](#remotecopyschema_nb) for more information.
+
+## Copying a remote schema
+
+<div id="remotecopyschema" class="registered_link"></div>
+
+The `remotecopyschema` function copies a schema and its database objects from a source schema in the remote source database specified in the `source_fdw` foreign server to a target schema in the local target database specified in the `target_fdw` foreign server:
+
+```sql
+remotecopyschema(
+  <source_fdw> TEXT,
+  <target_fdw> TEXT,
+  <source_schema> TEXT,
+  <target_schema> TEXT,
+  <log_filename> TEXT
+  [, <on_tblspace> BOOLEAN
+  [, <verbose_on> BOOLEAN
+  [, <copy_acls> BOOLEAN
+  [, <worker_count> INTEGER ]]]]
+)
+```
+
+The function returns a Boolean value. If the function succeeds, then `true` is returned. If the function fails, then `false` is returned.
+
+The `source_fdw`, `target_fdw`, `source_schema`, `target_schema`, and `log_filename` are required parameters. All other parameters are optional.
+
+### Parameters
+
+`source_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper from which to clone database objects.
+
+`target_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper to which to clone database objects.
+
+`source_schema`
+
+Name of the schema from which to clone database objects.
+
+`target_schema`
+
+Name of the schema into which to clone database objects from the source schema.
+
+`log_filename`
+
+Name of the log file in which information from the function is recorded. The log file is created under the directory specified by the `log_directory` configuration parameter in the `postgresql.conf` file.
+
+`on_tblspace`
+
+Boolean value to specify whether to create database objects in their tablespaces. If `false`, then the `TABLESPACE` clause isn't included in the applicable `CREATE` DDL statement when added to the target schema. If `true`, then the `TABLESPACE` clause is included in the `CREATE` DDL statement when added to the target schema. The default value is `false`.
+
+!!! Note
+    If you specify `true` and a database object has a `TABLESPACE` clause, the tablespace must exist in the target database cluseter. Otherwise, the cloning function fails.
+
+`verbose_on`
+
+Boolean value to specify whether to print the DDLs in `log_filename` when creating objects in the target schema. If `false`, then DDLs aren't printed. If `true`, then DDLs are printed. The default value is `false`.
+
+`copy_acls`
+
+Boolean value to specify whether to include the access control list (ACL) while creating objects in the target schema. The access control list is the set of `GRANT` privilege statements. If `false`, then the access control list isn't included for the target schema. If `true`, then the access control list is included for the target schema. The default value is `false`.
+
+!!! Note
+    If you specify `true`, a role with `GRANT` privilege must exist in the target database cluster. Otherwise, the cloning function fails.
+
+`worker_count`
+
+Number of background workers to perform the clone in parallel. The default value is `1`.
+
+### Example
+
+This example shows cloning schema `srcschema` in database `srcdb` (as defined by `src_server`) to target schema `tgtschema` in database `tgtdb` (as defined by `tgt_server`).
+
+The source server environment:
+
+-   Host on which the source database server is running: `192.168.2.28`
+-   Port of the source database server: `5444`
+-   Database source of the clone: `srcdb`
+-   Foreign server (`src_server`) and user mapping with the information of the preceding bullet points
+-   Source schema: `srcschema`
+
+The target server environment:
+
+-   Host on which the target database server is running: `localhost`
+-   Port of the target database server: `5444`
+-   Database target of the clone: `tgtdb`
+-   Foreign server (`tgt_server`) and user mapping with the information of the preceding bullet points
+-   Target schema: `tgtschema`
+-   Database superuser to invoke `remotecopyschema: enterprisedb`
+
+Before invoking the function, the connection database user `enterprisedb` connects to database `tgtdb`. A `worker_count` of `4` is specified for this function.
+
+```sql
+tgtdb=# SELECT edb_util.remotecopyschema
+('src_server','tgt_server','srcschema','tgtschema','clone_rmt_src_tgt',worker_count => 4);
+__OUTPUT__
+ remotecopyschema
+------------------
+ t
+(1 row)
+```
+
+This example displays the status from the log file during various points in the cloning process:
+
+```sql
+tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt');
+__OUTPUT__
+                                                      process_status_from_log
+
+-----------------------------------------------------------------------------------------------------
+--------------------------------------
+ (RUNNING,"28-JUN-17 13:18:05.299953 -04:00",4021,INFO,"STAGE: DATA-COPY","[0][0] successfully 
+ copied data in [tgtschema.pgbench_tellers]
+")
+ (1 row)
+```
+```sql
+tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt');
+__OUTPUT__
+                                                      process_status_from_log
+
+-----------------------------------------------------------------------------------------------------
+---------------------------------------
+ (RUNNING,"28-JUN-17 13:18:06.634364 -04:00",4022,INFO,"STAGE: DATA-COPY","[0][1] successfully 
+ copied data in [tgtschema.pgbench_history]
+")
+ (1 row)
+```
+```sql
+tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt');
+__OUTPUT__
+                                                      process_status_from_log
+
+------------------------------------------------------------------------------------------------------
+-------------------------------------
+ (RUNNING,"28-JUN-17 13:18:10.550393 -04:00",4039,INFO,"STAGE: POST-DATA","CREATE PRIMARY KEY 
+ CONSTRAINT pgbench_tellers_pkey successful"
+)
+ (1 row)
+```
+```sql
+tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt');
+__OUTPUT__
+                                                      process_status_from_log
+-------------------------------------------------------------------------------------------------------
+---------------------------------
+ (FINISH,"28-JUN-17 13:18:12.019627 -04:00",4039,INFO,"STAGE: FINAL","successfully clone 
+ schema into tgtschema")
+ (1 row)
+```
+
+### Results
+
+The following shows the cloned tables:
+
+```sql
+tgtdb=# \dt+
+__OUTPUT__
+                             List of relations
+  Schema   |       Name       | Type  |    Owner     |    Size    | Description
+-----------+------------------+-------+--------------+------------+-------------
+ tgtschema | pgbench_accounts | table | enterprisedb | 256 MB     |
+ tgtschema | pgbench_branches | table | enterprisedb | 8192 bytes |
+ tgtschema | pgbench_history  | table | enterprisedb | 25 MB      |
+ tgtschema | pgbench_tellers  | table | enterprisedb | 16 kB      |
+(4 rows)
+```
+
+When the `remotecopyschema` function was invoked, four background workers were specified.
+
+The following portion of the log file `clone_rmt_src_tgt` shows the status of the parallel data copying operation using four background workers:
+
+```text
+Wed Jun 28 13:18:05.232949 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0] table count [4]
+Wed Jun 28 13:18:05.233321 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0][0] worker started to
+copy data
+Wed Jun 28 13:18:05.233640 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0][1] worker started to
+copy data
+Wed Jun 28 13:18:05.233919 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0][2] worker started to
+copy data
+Wed Jun 28 13:18:05.234231 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0][3] worker started to
+copy data
+Wed Jun 28 13:18:05.298174 2017 EDT: [4024] INFO: [STAGE: DATA-COPY] [0][3] successfully
+copied data in [tgtschema.pgbench_branches]
+Wed Jun 28 13:18:05.299913 2017 EDT: [4021] INFO: [STAGE: DATA-COPY] [0][0] successfully
+copied data in [tgtschema.pgbench_tellers]
+Wed Jun 28 13:18:06.634310 2017 EDT: [4022] INFO: [STAGE: DATA-COPY] [0][1] successfully
+copied data in [tgtschema.pgbench_history]
+Wed Jun 28 13:18:10.477333 2017 EDT: [4023] INFO: [STAGE: DATA-COPY] [0][2] successfully
+copied data in [tgtschema.pgbench_accounts]
+Wed Jun 28 13:18:10.477609 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0] all workers finished
+[4]
+Wed Jun 28 13:18:10.477654 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] [0] copy done [4] tables
+Wed Jun 28 13:18:10.493938 2017 EDT: [4019] INFO: [STAGE: DATA-COPY] successfully copied data
+into tgtschema
+```
+
+The `DATA-COPY` log message includes two square-bracket numbers, for example, `[0][3]`. The first number is the job index. The second number is the worker index. The worker index values range from 0 to 3 for the four background workers.
+
+In case two clone schema jobs are running in parallel, the first log file has `0` as the job index, and the second has `1` as the job index.
+
+## Copying a remote schema using a batch job
+
+<div id="remotecopyschema_nb" class="registered_link"></div>
+
+The `remotecopyschema_nb` function copies a schema and its database objects from a source schema in the remote source database specified in the `source_fdw` foreign server to a target schema in the local target database specified in the `target_fdw` foreign server. Copying occurs in a non-blocking manner as a job submitted to pgAgent.
+
+```sql
+remotecopyschema_nb(
+  <source_fdw> TEXT,
+  <target_fdw> TEXT,
+  <source> TEXT,
+  <target> TEXT,
+  <log_filename> TEXT
+  [, <on_tblspace> BOOLEAN
+  [, <verbose_on> BOOLEAN
+  [, <copy_acls> BOOLEAN
+  [, <worker_count> INTEGER ]]]]
+)
+```
+
+The function returns an `INTEGER` value job ID for the job submitted to pgAgent. If the function fails, then null is returned.
+
+The `source_fdw`, `target_fdw`, `source`, `target`, and `log_filename` parameters are required. All other parameters are optional.
+
+After the pgAgent job is complete, remove it with the `remove_log_file_and_job` function.
+
+### Parameters
+
+`source_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper from which to clone database objects.
+
+`target_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper to which to clone database objects.
+
+`source`
+
+Name of the schema from which to clone database objects.
+
+`target`
+
+Name of the schema into which to clone database objects from the source schema.
+
+`log_filename`
+
+Name of the log file in which to record information from the function. The log file is created under the directory specified by the `log_directory` configuration parameter in the `postgresql.conf` file.
+
+`on_tblspace`
+
+Boolean value to specify whether to create database objects in their tablespaces. If `false`, then the `TABLESPACE` clause isn't included in the applicable `CREATE` DDL statement when added to the target schema. If `true`, then the `TABLESPACE` clause is included in the `CREATE` DDL statement when added to the target schema. The default value is `false`.
+
+!!! Note
+    If you specify `true` is specified and a database object has a `TABLESPACE` clause, that tablespace must exist in the target database cluster. Otherwise, the cloning function fails.
+
+`verbose_on`
+
+Boolean value to specify whether to print the DDLs in `log_filename` when creating objects in the target schema. If `false`, then DDLs aren't printed. If `true`, then DDLs are printed. The default value is `false`.
+
+`copy_acls`
+
+Boolean value to specify whether to include the access control list (ACL) while creating objects in the target schema. The access control list is the set of `GRANT` privilege statements. If `false`, then the access control list isn't included for the target schema. If `true`, then the access control list is included for the target schema. The default value is `false`.
+
+!!! Note
+    If you specify `true`, a role with `GRANT` privilege must exist in the target database cluster. Otherwise the cloning function fails.
+
+`worker_count`
+
+Number of background workers to perform the clone in parallel. The default value is `1`.
+
+### Example
+
+The same cloning operation is performed as the example in [`remotecopyschema`](#remotecopyschema) but using the non-blocking function `remotecopyschema_nb`.
+
+This command starts pgAgent on the target database `tgtdb`. The `pgagent` program file is located in the `bin` subdirectory of the EDB Postgres Advanced Server installation directory.
+
+```shell
+[root@localhost bin]# ./pgagent -l 1 -s /tmp/pgagent_tgtdb_log hostaddr=127.0.0.1 port=5444 
+user=enterprisedb dbname=tgtdb password=password
+```
+### Results 
+
+The `remotecopyschema_nb` function returns the job ID shown as `2` in the example:
+
+```sql
+tgtdb=# SELECT edb_util.remotecopyschema_nb
+('src_server','tgt_server','srcschema','tgtschema','clone_rmt_src_tgt',worker_count => 4);
+__OUTPUT__
+ remotecopyschema_nb
+---------------------
+                2
+(1 row)
+```
+
+The following shows the completed status of the job:
+
+```sql
+tgtdb=# SELECT edb_util.process_status_from_log('clone_rmt_src_tgt');
+__OUTPUT__
+                                             process_status_from_log
+--------------------------------------------------------------------------------------------------------------------
+ (FINISH,"29-JUN-17 current:16:00.100284 -04:00",3849,INFO,"STAGE: FINAL","successfully clone schema into tgtschema")
+(1 row)
+```
+
+The following command removes the log file and the pgAgent job:
+
+```sql
+tgtdb=# SELECT edb_util.remove_log_file_and_job ('clone_rmt_src_tgt',2);
+__OUTPUT__
+ remove_log_file_and_job
+-------------------------
+ t
+(1 row)
+```
+
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_schema.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_schema.mdx
new file mode 100644
index 00000000000..427ae7ffed0
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/copying_a_schema.mdx
@@ -0,0 +1,307 @@
+---
+title: "Copying database objects from a local source to a target"
+navTitle: "Copying a local database"
+description: "Describes how to copy database objects from a source database into the same database but with a different schema name"
+---
+
+There are two functions you can use with EDB Clone Schema to perform a local copy of a schema and its database objects:
+
+-   `localcopyschema` &mdash; This function copies a schema and its database objects from a source database into the same database (the target) but with a different schema name from the original. Use this function when the source schema and the copy will reside within the same database. See [localcopyschema](#localcopyschema) for more information.
+-   `localcopyschema_nb` &mdash; This function performs the same purpose as `localcopyschema` but as a background job, which frees up the terminal from which the function was initiated. This function is referred to as a *non-blocking* function. See [localcopyschema_nb](#localcopyschema_nb) for more information.
+
+## Performing a local copy of a schema
+
+<div id="localcopyschema" class="registered_link"></div>
+
+The `localcopyschema` function copies a schema and its database objects in a local database specified in the `source_fdw` foreign server from the source schema to the specified target schema in the same database.
+
+```sql
+localcopyschema(
+  <source_fdw> TEXT,
+  <source_schema> TEXT,
+  <target_schema> TEXT,
+  <log_filename> TEXT
+  [, <on_tblspace> BOOLEAN
+  [, <verbose_on> BOOLEAN
+  [, <copy_acls> BOOLEAN
+  [, <worker_count> INTEGER ]]]]
+)
+```
+
+The function returns a Boolean value. If the function succeeds, then `true` is returned. If the function fails, then `false` is returned.
+
+The `source_fdw, source_schema, target_schema`, and `log_filename` are required parameters while all other parameters are optional.
+
+### Parameters
+
+`source_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper from which to clone database objects.
+
+`source_schema`
+
+Name of the schema from which to clone database objects.
+
+`target_schema`
+
+Name of the schema into which to clone database objects from the source schema.
+
+`log_filename`
+
+Name of the log file in which information from the function is recorded. The log file is created under the directory specified by the `log_directory` configuration parameter in the `postgresql.conf` file.
+
+`on_tblspace`
+
+Boolean value to specify whether to create database objects in their tablespaces. If `false`, then the `TABLESPACE` clause isn't included in the applicable `CREATE` DDL statement when added to the target schema. If `true`, then the `TABLESPACE` clause is included in the `CREATE` DDL statement when added to the target schema. The default value is `false`.
+
+`verbose_on`
+
+Boolean value to specify whether to print the DDLs in `log_filename` when creating objects in the target schema. If `false`, then DDLs aren't printed. If `true`, then DDLs are printed. The default value is `false`.
+
+`copy_acls`
+
+Boolean value to specify whether to include the access control list (ACL) while creating objects in the target schema. The access control list is the set of `GRANT` privilege statements. If `false`, then the access control list isn't included for the target schema. If `true`, then the access control list is included for the target schema. The default value is `false`.
+
+`worker_count`
+
+Number of background workers to perform the clone in parallel. The default value is `1`.
+
+### Example
+
+This example shows the cloning of schema `edb` containing a set of database objects to target schema `edbcopy`. Both schemas are in database `edb` as defined by `local_server`.
+
+The example is for the following environment:
+
+-   Host on which the database server is running: `localhost`
+-   Port of the database server: `5444`
+-   Database source/target of the clone: `edb`
+-   Foreign server (`local_server`) and user mapping with the information of the preceding bullet points
+-   Source schema: `edb`
+-   Target schema: `edbcopy`
+-   Database superuser to invoke `localcopyschema: enterprisedb`
+
+Before invoking the function, database user `enterprisedb` connects to to database `edb`:
+
+```sql
+edb=# SET search_path TO "$user",public,edb_util;
+SET
+edb=# SHOW search_path;
+__OUTPUT__
+        search_path
+---------------------------
+ "$user", public, edb_util
+(1 row)
+```
+```sql
+edb=# SELECT localcopyschema ('local_server','edb','edbcopy','clone_edb_edbcopy');
+__OUTPUT__
+ localcopyschema
+-----------------
+ t
+(1 row)
+```
+
+The following displays the logging status using the `process_status_from_log` function:
+
+```sql
+edb=# SELECT process_status_from_log('clone_edb_edbcopy');
+__OUTPUT__
+                                    process_status_from_log
+------------------------------------------------------------------------------------------------
+ (FINISH,"2017-06-29 11:07:36.830783-04",3855,INFO,"STAGE: FINAL","successfully cloned schema")
+(1 row)
+```
+## Results 
+
+After the clone is complete, the following shows some of the database objects copied to the `edbcopy` schema:
+
+```sql
+edb=# SET search_path TO edbcopy;
+SET
+edb=# \dt+
+__OUTPUT__
+                       List of relations
+ Schema  |  Name   | Type  |    Owner     |    Size    | Description
+---------+---------+-------+--------------+------------+-------------
+ edbcopy | dept    | table | enterprisedb | 8192 bytes |
+ edbcopy | emp     | table | enterprisedb | 8192 bytes |
+ edbcopy | jobhist | table | enterprisedb | 8192 bytes |
+(3 rows)
+```
+```sql
+edb=# \dv
+__OUTPUT__
+         List of relations
+ Schema  |   Name   | Type |    Owner
+---------+----------+------+--------------
+ edbcopy | salesemp | view | enterprisedb
+(1 row)
+```
+```sql
+edb=# \di
+__OUTPUT__
+                 List of relations
+ Schema  |     Name      | Type  |    Owner     |  Table
+---------+---------------+-------+--------------+---------
+ edbcopy | dept_dname_uq | index | enterprisedb | dept
+ edbcopy | dept_pk       | index | enterprisedb | dept
+ edbcopy | emp_pk        | index | enterprisedb | emp
+ edbcopy | jobhist_pk    | index | enterprisedb | jobhist
+(4 rows)
+```
+```sql
+edb=# \ds
+__OUTPUT__
+            List of relations
+ Schema  |    Name    |   Type   |    Owner
+---------+------------+----------+--------------
+ edbcopy | next_empno | sequence | enterprisedb
+(1 row)
+```
+```sql
+edb=# SELECT DISTINCT schema_name, name, type FROM user_source WHERE
+schema_name = 'EDBCOPY' ORDER BY type, name;
+__OUTPUT__
+ schema_name |              name              |     type
+-------------+--------------------------------+--------------
+ EDBCOPY     | EMP_COMP                       | FUNCTION
+ EDBCOPY     | HIRE_CLERK                     | FUNCTION
+ EDBCOPY     | HIRE_SALESMAN                  | FUNCTION
+ EDBCOPY     | NEW_EMPNO                      | FUNCTION
+ EDBCOPY     | EMP_ADMIN                      | PACKAGE
+ EDBCOPY     | EMP_ADMIN                      | PACKAGE BODY
+ EDBCOPY     | EMP_QUERY                      | PROCEDURE
+ EDBCOPY     | EMP_QUERY_CALLER               | PROCEDURE
+ EDBCOPY     | LIST_EMP                       | PROCEDURE
+ EDBCOPY     | SELECT_EMP                     | PROCEDURE
+ EDBCOPY     | EMP_SAL_TRIG                   | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_19991" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_19992" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_19999" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_20000" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_20004" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_a_20005" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_19993" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_19994" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_20001" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_20002" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_20006" | TRIGGER
+ EDBCOPY     | "RI_ConstraintTrigger_c_20007" | TRIGGER
+ EDBCOPY     | USER_AUDIT_TRIG                | TRIGGER
+(24 rows)
+```
+
+## Performing a local copy of a schema as a batch job
+
+<div id="localcopyschema_nb" class="registered_link"></div>
+
+The `localcopyschema_nb` function copies a schema and its database objects in a local database specified in the `source_fdw` foreign server from the source schema to the specified target schema in the same database. The copy occurs in a non-blocking manner as a job submitted to pgAgent.
+
+```sql
+localcopyschema_nb(
+  <source_fdw> TEXT,
+  <source> TEXT,
+  <target> TEXT,
+  <log_filename> TEXT
+  [, <on_tblspace> BOOLEAN
+  [, <verbose_on> BOOLEAN
+  [, <copy_acls> BOOLEAN
+  [, <worker_count> INTEGER ]]]]
+)
+```
+
+The function returns an `INTEGER` value job ID for the job submitted to pgAgent. If the function fails, then null is returned.
+
+The `source_fdw`, `source`, `target`, and `log_filename` parameters are required. All other parameters are optional.
+
+After the pgAgent job completes, remove it with the `remove_log_file_and_job` function.
+
+### Parameters
+
+`source_fdw`
+
+Name of the foreign server managed by the `postgres_fdw` foreign data wrapper from which to clone database objects.
+
+`source`
+
+Name of the schema from which to clone database objects.
+
+`target`
+
+Name of the schema into which to clone database objects from the source schema.
+
+`log_filename`
+
+Name of the log file in which to record information from the function. The log file is created under the directory specified by the `log_directory` configuration parameter in the `postgresql.conf` file.
+
+`on_tblspace`
+
+Boolean value to specify whether to create database objects in their tablespaces. If `false`, then the `TABLESPACE` clause isn't included in the applicable `CREATE` DDL statement when added to the target schema. If `true`, then the `TABLESPACE` clause is included in the `CREATE` DDL statement when added to the target schema. The default value is `false`.
+
+`verbose_on`
+
+Boolean value to specify whether to print the DDLs in `log_filename` when creating objects in the target schema. If `false`, then DDLs aren't printed. If `true`, then DDLs are printed. The default value is `false`.
+
+`copy_acls`
+
+Boolean value to specify whether to include the access control list (ACL) while creating objects in the target schema. The access control list is the set of `GRANT` privilege statements. If `false`, then the access control list isn't included for the target schema. If `true`, then the access control list is included for the target schema. The default value is `false`.
+
+`worker_count`
+
+Number of background workers to perform the clone in parallel. The default value is `1`.
+
+### Example
+
+The same cloning operation is performed as the example in [`localcopyschema`](#localcopyschema) but using the non-blocking function `localcopyschema_nb`.
+
+You can use this command to see whether pgAgent is running on the appropriate local database:
+
+```shell
+[root@localhost ~]# ps -ef | grep pgagent
+root       4518      1  0 11:35 pts/1    00:00:00 pgagent -s /tmp/pgagent_edb_log 
+hostaddr=127.0.0.1 port=5444 dbname=edb user=enterprisedb password=password
+root       4525   4399  0 11:35 pts/1    00:00:00 grep --color=auto pgagent
+```
+
+If pgAgent isn't running, start it by executing the `pgagent` option. The `pgagent` program file is located in the `bin` subdirectory of the EDB Postgres Advanced Server installation directory.
+
+```shell
+[root@localhost bin]# ./pgagent -l 2 -s /tmp/pgagent_edb_log hostaddr=127.0.0.1 port=5444 
+dbname=edb user=enterprisedb password=password
+```
+
+!!! Note
+    The `pgagent -l 2` option starts pgAgent in `DEBUG` mode, which logs continuous debugging information into the log file specified with the `-s` option. Use a lower value for the `-l` option, or omit it entirely to record less information.
+
+The `localcopyschema_nb` function returns the job ID shown as `4` in the example.
+
+```sql
+edb=# SELECT edb_util.localcopyschema_nb ('local_server','edb','edbcopy','clone_edb_edbcopy');
+__OUTPUT__
+ localcopyschema_nb
+--------------------
+               4
+(1 row)
+```
+
+The following displays the job status:
+
+```sql
+edb=# SELECT edb_util.process_status_from_log('clone_edb_edbcopy');
+__OUTPUT__
+                                   process_status_from_log
+---------------------------------------------------------------------------------------------------
+ (FINISH,"29-JUN-17 11:39:11.620093 -04:00",4618,INFO,"STAGE: FINAL","successfully cloned schema")
+(1 row)
+```
+
+The following removes the pgAgent job:
+
+```sql
+edb=# SELECT edb_util.remove_log_file_and_job (4);
+__OUTPUT__
+ remove_log_file_and_job
+-------------------------
+ t
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx
new file mode 100644
index 00000000000..d293972d470
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/edb_clone_schema_overview.mdx
@@ -0,0 +1,80 @@
+---
+title: "EDB Clone Schema key concepts and limitations"
+navTitle: "Overview and limitations"
+description: "Provides an overview of the key features of EDB Clone Schema as well as important information about limitations"
+---
+
+## EDB Clone Schema functions
+
+The EDB Clone Schema functions are created in the `edb_util` schema when the `parallel_clone` and `edb_cloneschema` extensions are installed.
+
+## Prerequisites
+
+Verify the following conditions before using an EDB Clone Schema function:
+
+-   You're connected to the target or local database as the database superuser defined in the `CREATE USER MAPPING` command for the foreign server of the target or local database.
+-   The `edb_util` schema is in the search path, or invoke the cloning function with the `edb_util` prefix.
+-   The target schema doesn't exist in the target database.
+-   When using the remote copy functions, if the `on_tblspace` parameter is set to `true`, then the target database cluster contains all tablespaces that are referenced by objects in the source schema. Otherwise, creating the DDL statements for those database objects fails in the target schema, which causes a failure of the cloning process.
+-   When using the remote copy functions, if you set the `copy_acls` parameter to `true`, then all roles that have `GRANT` privileges on objects in the source schema exist in the target database cluster. Otherwise granting privileges to those roles fails in the target schema, which causes a failure of the cloning process.
+-   pgAgent is running against the target database if you're using the non-blocking form of the function.
+
+EDB Postgres Advanced Server includes pgAgent as a component. For information about pgAgent, see the [pgAdmin documentation](https://www.pgadmin.org/docs/pgadmin4/dev/pgagent.html).
+
+## Overview of the functions
+
+Use the following functions with EDB Clone Schema:
+
+-   `localcopyschema`. This function copies a schema and its database objects from a source database into the same database (the target) but with a different schema name from the original. Use this function when the source schema and the copy will reside within the same database. See [localcopyschema](copying_a_schema) for more information.
+-   `localcopyschema_nb`. This function performs the same purpose as `localcopyschema` but as a background job, which frees up the terminal from which the function was initiated. This function is referred to as a *non-blocking* function. See [localcopyschema_nb](copying_a_schema) for more information.
+-   `remotecopyschema`. This function copies a schema and its database objects from a source database to a different target database. Use this function when the source schema and the copy will reside in separate databases. The separate databases can reside in the same EDB Postgres Advanced Server database clusters or in different ones. See [remotecopyschema](copying_a_remote_schema) for more information.
+-   `remotecopyschema_nb`. This function performs the same purpose as `remotecopyschema` but as a background job, which frees up the terminal from which the function was initiated. This function is a non-blocking function. See [remotecopyschema_nb](copying_a_remote_schema) for more information.
+-   `process_status_from_log`. This function displays the status of the cloning functions. The information is obtained from a log file you specify when invoking a cloning function. See [process_status_from_log](checking_the_status) for more information.
+-   `remove_log_file_and_job`. This function deletes the log file created by a cloning function. You can also use this function to delete a job created by the non-blocking form of the function. See [remove_log_file_and_job](performing_cleanup_tasks) for more information.
+
+## List of supported database objects
+
+You can clone these database objects from one schema to another:
+
+-   Data types
+-   Tables including partitioned tables, excluding foreign tables
+-   Indexes
+-   Constraints
+-   Sequences
+-   View definitions
+-   Materialized views
+-   Private synonyms
+-   Table triggers, but excluding event triggers
+-   Rules
+-   Functions
+-   Procedures
+-   Packages
+-   Comments for all supported object types
+-   Access control lists (ACLs) for all supported object types
+
+You can't clone the following database objects:
+
+-   Large objects (Postgres `LOBs` and `BFILEs`)
+-   Logical replication attributes for a table
+-   Database links
+-   Foreign data wrappers
+-   Foreign tables
+-   Event triggers
+-   Extensions 
+
+For cloning objects that rely on extensions, see the limitations that follow.
+
+-   Row-level security
+-   Policies
+-   Operator class
+
+## Limitations
+
+The following limitations apply:
+
+-   EDB Clone Schema is supported on EDB Postgres Advanced Server when you specify a dialect of **Compatible with Oracle** on the EDB Postgres Advanced Server Dialect dialog box during installation. It's also supported when you include the `--redwood-like` keywords during a text-mode installation or cluster initialization.
+-   The source code in functions, procedures, triggers, packages, and so on, aren't modified after being copied to the target schema. If such programs contain coded references to objects with schema names, the programs might fail when invoked in the target schema if such schema names are no longer consistent in the target schema.
+-   Cross-schema object dependencies aren't resolved. If an object in the target schema depends on an object in another schema, this dependency isn't resolved by the cloning functions.
+-   For remote cloning, if an object in the source schema depends on an extension, then you must create this extension in the public schema of the remote database before invoking the remote cloning function.
+-   At most, 16 copy jobs can run in parallel to clone schemas. Each job can have at most 16 worker processes to copy table data in parallel.
+-   You can't cancel queries run by background workers.
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/index.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/index.mdx
new file mode 100644
index 00000000000..a5755f91ddf
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "Copying a database"
+navTitle: "EDB Clone Schema"
+indexCards: simple
+description: "How to use the EDB Clone Schema module to copy a schema and its database objects from a source database to a target database"
+navigation:
+  - edb_clone_schema_overview
+  - setting_up_edb_clone_schema
+  - copying_a_schema
+  - copying_a_remote_schema
+  - checking_the_status
+  - performing_cleanup_tasks
+---
+
+<div id="edb_clone_schema" class="registered_link"></div>
+
+EDB Clone Schema is an extension module for EDB Postgres Advanced Server that allows you to copy a schema and its database objects from a local or remote database (the source database) to a receiving database (the target database).
+
+The source and target databases can be either:
+
+-  The same physical database 
+-  Different databases in the same database cluster
+-  Separate databases running under different database clusters on separate database server hosts
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/performing_cleanup_tasks.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/performing_cleanup_tasks.mdx
new file mode 100644
index 00000000000..dd2784bd469
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/performing_cleanup_tasks.mdx
@@ -0,0 +1,68 @@
+---
+title: "Performing cleanup tasks"
+description: "Describes how to cleanup log files"
+---
+
+<div id="remove_log_file_and_job" class="registered_link"></div>
+
+The `remove_log_file_and_job` function performs cleanup tasks by removing the log files created by the schema cloning functions and the jobs created by the non-blocking functions.
+
+```sql
+remove_log_file_and_job (
+  { <log_file> TEXT |
+    <job_id> INTEGER |
+    <log_file> TEXT, <job_id> INTEGER
+  }
+)
+```
+
+You can specify values for either or both of the two parameters when invoking the `remove_log_file_and_job` function:
+
+-   If you specify only `log_file`, then the function removes only the log file.
+-   If you specify only `job_id`, then the function removes only the job.
+-   If you specify both, then the function removes only the log file and the job.
+
+## Parameters
+
+`log_file`
+
+Name of the log file to remove.
+
+`job_id`
+
+Job ID of the job to remove.
+
+## Example
+
+This example removes only the log file, given the log file name:
+
+```sql
+edb=# SELECT edb_util.remove_log_file_and_job ('clone_edb_edbcopy');
+__OUTPUT__
+ remove_log_file_and_job
+-------------------------
+ t
+(1 row)
+```
+
+This example removes only the job, given the job ID:
+
+```sql
+edb=# SELECT edb_util.remove_log_file_and_job (3);
+__OUTPUT__
+ remove_log_file_and_job
+-------------------------
+ t
+(1 row)
+```
+
+This example removes the log file and the job, given both values:
+
+```sql
+tgtdb=# SELECT edb_util.remove_log_file_and_job ('clone_rmt_src_tgt',2);
+__OUTPUT__
+ remove_log_file_and_job
+-------------------------
+ t
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx
new file mode 100644
index 00000000000..796546f1933
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/14_edb_clone_schema/setting_up_edb_clone_schema.mdx
@@ -0,0 +1,291 @@
+---
+title: "Setting up EDB Clone Schema"
+description: "Describes how to install and configure the EDB Clone Schema extension"
+---
+
+To use EDB Clone Schema, you must first install several extensions along with the PL/Perl language on any database used as the source or target database by an EDB Clone Schema function.
+
+In addition, it might help to modify some configuration parameters in the `postgresql.conf` file of the database servers.
+
+## Installing extensions
+
+Perform this installation on any database to be used as the source or target database by an EDB Clone Schema function.
+
+1. Install the following extensions on the database: `postgres_fdw`, `dblink`, `adminpack` and `pgagent`.
+1. Ensure that pgAgent is installed before creating the `pgagent` extension. On Linux, you can use the `edb-as<xx>-pgagent` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number to install pgAgent. On Windows, use StackBuilder Plus to download and install pgAgent.
+
+  Install the extensions:
+
+  ```sql
+  CREATE EXTENSION postgres_fdw SCHEMA public;
+  CREATE EXTENSION dblink SCHEMA public;
+  CREATE EXTENSION adminpack;
+  CREATE EXTENSION pgagent;
+  ```
+
+  For more information about using the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
+
+## Modifying the configuration file
+
+Modify the `postgresql.conf` file by adding `$libdir/parallel_clone` to the `shared_preload_libraries` configuration parameter:
+
+  ```ini
+  shared_preload_libraries = '$libdir/dbms_pipe,$libdir/dbms_aq,$libdir/parallel_clone'
+  ```
+
+## Installing PL/Perl
+
+1.  Install the Perl procedural language (PL/Perl) on the database, and run the `CREATE TRUSTED LANGUAGE plperl` command. For Linux, install PL/Perl using the `edb-as<xx>-server-plperl` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number. For Windows, use the EDB Postgres Language Pack. For information on EDB Language Pack, see the [EDB Postgres Language Pack](/language_pack/latest).
+
+1. Connect to the database as a superuser and run the following command:
+
+  ```sql
+  CREATE TRUSTED LANGUAGE plperl;
+  ```
+
+For more information about using the `CREATE LANGUAGE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createlanguage.html).
+
+<div id="setting-configuration-parameters-1" class="registered_link"></div>
+
+## Setting configuration parameters
+
+You might need to modify configuration parameters in the `postgresql.conf` file.
+
+### Performance configuration parameters
+
+You might need to tune the system for copying a large schema as part of one transaction. Tuning of configuration parameters is for the source database server referenced in a cloning function.
+
+You might need to tune the following configuration parameters in the `postgresql.conf` file:
+
+-   `work_mem`. Specifies the amount of memory for internal sort operations and hash tables to use before writing to temporary disk files.
+-   `maintenance_work_mem`. Specifies the maximum amount of memory for maintenance operations such as `VACUUM`, `CREATE INDEX`, and `ALTER TABLE ADD FOREIGN KEY` to use.
+-   `max_worker_processes`. Sets the maximum number of background processes that the system can support.
+-   `checkpoint_timeout`. Maximum time between automatic WAL checkpoints, in seconds.
+-   `checkpoint_completion_target`. Specifies the target of checkpoint completion as a fraction of total time between checkpoints.
+-   `checkpoint_flush_after`. Whenever more than `checkpoint_flush_after` bytes are written while performing a checkpoint, attempt to force the OS to issue these writes to the underlying storage.
+-   `max_wal_size`. Maximum size to let the WAL grow to between automatic WAL checkpoints.
+-   `max_locks_per_transaction`. Controls the average number of object locks allocated for each transaction. Individual transactions can lock more objects as long as the locks of all transactions fit in the lock table.
+
+For information about the configuration parameters, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/runtime-config.html).
+
+### Status logging
+
+Status logging by the cloning functions creates log files in the directory specified by the `log_directory` parameter in the `postgresql.conf` file for the database server to which you're connected when invoking the cloning function.
+
+The default location is `PGDATA/log`:
+
+```ini
+#log_directory = 'log'        # directory where log files are written,
+                              # can be absolute or relative to PGDATA
+```
+
+This directory must exist before running a cloning function.
+
+The name of the log file is determined by what you specify in the parameter list when invoking the cloning function.
+
+To display the status from a log file, use the `process_status_from_log` function.
+
+To delete a log file, use the `remove_log_file_and_job` function, or delete it manually from the log directory.
+
+## Installing EDB Clone Schema
+
+Install the EDB Clone Schema on any database to be used as the source or target database by an EDB Clone Schema function.
+
+1.  If you previously installed an older version of the `edb_cloneschema` extension, run the following command:  
+
+  ```sql
+  DROP EXTENSION parallel_clone CASCADE;
+  ```
+
+  This command also drops the `edb_cloneschema` extension.
+
+1.  Install the extensions. Make sure that you create the `parallel_clone` extension before creating the `edb_cloneschema` extension.
+
+  ```sql
+  CREATE EXTENSION parallel_clone SCHEMA public;
+
+  CREATE EXTENSION edb_cloneschema;
+  ```
+
+## Creating the foreign servers and user mappings
+
+When using one of the local cloning functions `localcopyschema` or `localcopyschema_nb`, one of the required parameters includes a single, foreign server. This server is for identifying the database server and its database that's the source and receiver of the cloned schema.
+
+When using one of the remote cloning functions `remotecopyschema` or `remotecopyschema_nb`, two of the required parameters include two foreign servers. The foreign server specified as the first parameter identifies the source database server and its database that's the provider of the cloned schema. The foreign server specified as the second parameter identifies the target database server and its database that's the receiver of the cloned schema.
+
+For each foreign server, you must create a user mapping. When a selected database superuser invokes a cloning function, that superuser must be mapped to a database user name and password that has access to the foreign server that's specified as a parameter in the cloning function.
+
+For general information about foreign data, foreign servers, and user mappings, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/ddl-foreign-data.html).
+
+### Foreign server and user mapping for local cloning functions
+
+For the `localcopyschema` and `localcopyschema_nb` functions, the source and target schemas are both in the same database of the same database server. You must define and specify only one foreign server for these functions. This foreign server is also referred to as the *local server* because this server is the one to which you must be connected when invoking the `localcopyschema` or `localcopyschema_nb` function.
+
+The user mapping defines the connection and authentication information for the foreign server. You must create this foreign server and user mapping in the database of the local server in which the cloning occurs.
+
+The database user for whom the user mapping is defined must be a superuser and connected to the local server when invoking an EDB Clone Schema function.
+
+This example creates the foreign server for the database containing the schema to clone and to receive the cloned schema:
+
+```sql
+CREATE SERVER local_server FOREIGN DATA WRAPPER postgres_fdw
+  OPTIONS(
+    host 'localhost',
+    port '5444',
+    dbname 'edb'
+);
+```
+
+For more information about using the `CREATE SERVER` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createserver.html).
+
+The user mapping for this server is:
+
+```sql
+CREATE USER MAPPING FOR enterprisedb SERVER local_server
+  OPTIONS (
+    user 'enterprisedb',
+    password 'password'
+);
+```
+
+For more information about using the `CREATE USER MAPPING` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-createusermapping.html).
+
+These psql commands show the foreign server and user mapping:
+
+```sql
+edb=# \des+
+__OUTPUT__
+List of foreign servers
+-[ RECORD 1 ]--------+----------------------------------------------
+Name                 | local_server
+Owner                | enterprisedb
+Foreign-data wrapper | postgres_fdw
+Access privileges    |
+Type                 |
+Version              |
+FDW options          | (host 'localhost', port '5444', dbname 'edb')
+Description          |
+```
+```sql
+edb=# \deu+
+__OUTPUT__
+                        List of user mappings
+    Server    |  User name   |                 FDW options
+--------------+--------------+----------------------------------------------
+ local_server | enterprisedb | ("user" 'enterprisedb', password 'password')
+(1 row)
+```
+
+When database superuser `enterprisedb` invokes a cloning function, the database user `enterprisedb` with its password is used to connect to `local_server` on the `localhost` with port `5444` to database `edb`.
+
+In this case, the mapped database user, `enterprisedb`, and the database user, `enterprisedb`, used to connect to the local `edb` database are the same database user. However, that's not required.
+
+For specific use of these foreign server and user mapping examples, see the example given in [`localcopyschema`](copying_a_schema).
+
+### Foreign server and user mapping for remote cloning functions
+
+For the `remotecopyschema` and `remotecopyschema_nb` functions, the source and target schemas are in different databases of either the same or different database servers. You must define and specify two foreign servers for these functions.
+
+The foreign server defining the originating database server and its database containing the source schema to clone is referred to as the *source server* or the *remote server*.
+
+The foreign server defining the database server and its database to receive the schema to clone is referred to as the *target server* or the *local server*. The target server is also referred to as the local server because this server is the one to which you must be connected when invoking the `remotecopyschema` or `remotecopyschema_nb` function.
+
+The user mappings define the connection and authentication information for the foreign servers. You must create all of these foreign servers and user mappings in the target database of the target/local server. The database user for whom the user mappings are defined must be a superuser and the user connected to the local server when invoking an EDB Clone Schema function.
+
+This example creates the foreign server for the local, target database that receives the cloned schema:
+
+```sql
+CREATE SERVER tgt_server FOREIGN DATA WRAPPER postgres_fdw
+  OPTIONS(
+    host 'localhost',
+    port '5444',
+    dbname 'tgtdb'
+);
+```
+
+The user mapping for this server is:
+
+```sql
+CREATE USER MAPPING FOR enterprisedb SERVER tgt_server
+  OPTIONS (
+    user 'tgtuser',
+    password 'tgtpassword'
+);
+```
+
+This example creates the foreign server for the remote, source database that's the source for the cloned schema:
+
+```sql
+CREATE SERVER src_server FOREIGN DATA WRAPPER postgres_fdw
+  OPTIONS(
+    host '192.168.2.28',
+    port '5444',
+    dbname 'srcdb'
+);
+```
+
+The user mapping for this server is:
+
+```sql
+CREATE USER MAPPING FOR enterprisedb SERVER src_server
+  OPTIONS (
+    user 'srcuser',
+    password 'srcpassword'
+);
+```
+## Displaying foreign servers and user mappings
+
+These psql commands show the foreign servers and user mappings:
+
+```sql
+tgtdb=# \des+
+__OUTPUT__
+List of foreign servers
+-[ RECORD 1 ]--------+---------------------------------------------------
+Name                 | src_server
+Owner                | tgtuser
+Foreign-data wrapper | postgres_fdw
+Access privileges    |
+Type                 |
+Version              |
+FDW options          | (host '192.168.2.28', port '5444', dbname 'srcdb')
+Description          |
+-[ RECORD 2 ]--------+---------------------------------------------------
+Name                 | tgt_server
+Owner                | tgtuser
+Foreign-data wrapper | postgres_fdw
+Access privileges    |
+Type                 |
+Version              |
+FDW options          | (host 'localhost', port '5444', dbname 'tgtdb')
+Description          |
+```
+```sql
+tgtdb=# \deu+
+__OUTPUT__
+                      List of user mappings
+   Server   |  User name   |                FDW options
+------------+--------------+--------------------------------------------
+ src_server | enterprisedb | ("user" 'srcuser', password 'srcpassword')
+ tgt_server | enterprisedb | ("user" 'tgtuser', password 'tgtpassword')
+(2 rows)
+```
+
+When database superuser `enterprisedb` invokes a cloning function, the database user `tgtuser` with password `tgtpassword` is used to connect to `tgt_server` on the `localhost` with port `5444` to database `tgtdb`.
+
+In addition, database user `srcuser` with password `srcpassword` connects to `src_server` on host `192.168.2.28` with port `5444` to database `srcdb`.
+
+!!! Note
+    Be sure the `pg_hba.conf` file of the database server running the source database `srcdb` has an appropriate entry. This entry must permit connection from the target server location (address `192.168.2.27` in the following example) with the database user `srcuser` that was included in the user mapping for the foreign server `src_server` defining the source server and database.
+
+```shell
+# TYPE  DATABASE        USER            ADDRESS                 METHOD
+
+# "local" is for Unix domain socket connections only
+local   all             all                                     md5
+# IPv4 local connections:
+host    srcdb           srcuser         192.168.2.27/32         md5
+```
+
+For specific use of these foreign server and user mapping examples, see the example given in [`remotecopyschema`](copying_a_remote_schema).
+
diff --git a/product_docs/docs/epas/16/database_administration/index.mdx b/product_docs/docs/epas/16/database_administration/index.mdx
new file mode 100644
index 00000000000..48712593d96
--- /dev/null
+++ b/product_docs/docs/epas/16/database_administration/index.mdx
@@ -0,0 +1,11 @@
+---
+title: "Database administration"
+indexCards: simple
+navigation:
+- 01_configuration_parameters
+- 10_edb_resource_manager
+- 02_edb_loader
+- 14_edb_clone_schema
+---
+
+EDB Postgres Advanced Server includes features to help you to maintain, secure, and operate EDB Postgres Advanced Server databases.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_platform_support/index.mdx b/product_docs/docs/epas/16/epas_platform_support/index.mdx
new file mode 100644
index 00000000000..ce54e41ab45
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_platform_support/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Supported platforms"
+description: "Provides information for determining the platform support for EDB Postgres Advanced Server"
+redirects:
+  - ../epas_inst_linux/02_supported_platforms
+  - /epas/latest/epas_platform_support/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server supports installations on Linux and Windows platforms. 
+
+To learn about the platform support for EDB Postgres Advanced Server, you can refer either to the platform support for EDB Postgres Advanced Server on the [Platform Compatibility page](https://www.enterprisedb.com/platform-compatibility#epas) on the EDB website or [Installing EDB Postgres Advanced Server](../installing).
+
+
+
+
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx
new file mode 100644
index 00000000000..d4980a2eed6
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_2_0_rel_notes.mdx
@@ -0,0 +1,12 @@
+---
+title: EDB Postgres Advanced Server 16.2 release notes
+navTitle: "Version 16.2"
+---
+
+Released: 8 Feb 2024
+
+EDB Postgres Advanced Server 16.2 includes the following enhancements and bug fixes:
+
+|      Type      |                                                                                                                                                                                 Description                                                                                                                                                                                 | Category |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| Upstream merge | Merged with community PostgreSQL 16.2. Important: Although not vulnerable to the recent 8.0 scoring CVE, CVE-2024-0985, this release includes tightened security restrictions which address the same issues. See the [PostgreSQL 16.2 Release Notes](https://www.postgresql.org/docs/16/release-16-2.html) for more information.                                                                  
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_3_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_3_0_rel_notes.mdx
new file mode 100644
index 00000000000..4a7e46d417f
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_3_0_rel_notes.mdx
@@ -0,0 +1,21 @@
+---
+title: EDB Postgres Advanced Server 16.3.0 release notes
+navTitle: "Version 16.3.0"
+---
+
+Released: 9 May 2024
+
+EDB Postgres Advanced Server 16.3.0 includes the following enhancements and bug fixes:
+
+| Type              | Description                                                                                                                                                                                         | Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
+| Upstream merge    | Merged with community PostgreSQL 16.3. This release includes a fix for [CVE-2024-4317](/security/assessments/cve-2024-4317). See the [PostgreSQL 16.3 Release Notes](https://www.postgresql.org/docs/release/16.3/) for more information. | [CVE-2024-4317](/security/assessments/cve-2024-4317) |
+| Security&nbsp;fix | Fixed an issue for `edbldr`. Now `edbldr` checks the `pg_read_server_files` privilege before accessing the data files.                                                                              | #35906, [CVE-2024-4545](/security/advisories/cve20244545/)                                           |
+| Bug&nbsp;fix      | Fixed an issue for `edb_filter_log`. Now it correctly redacts the password when the tab is used before the keyword.                                                                                 | #36220                                                                                              |
+| Bug&nbsp;fix      | Fixed an issue for `edb_audit` on Windows. Now it correctly rotates the log files based on days configured in `edb_audit_rotation_day`.                                                             | #99282                                                                                              |
+| Bug&nbsp;fix      | Fixed an issue to fetch all the attributes correctly from the sublink in `CONNECT BY` processing to avoid the server crash.                                                                         | #102746                                                                                             |
+| Bug&nbsp;fix      | Added conditional free path in `add_path()` to avoid the rare possible server crashes when the freed path is still in use, specially in FDWs.                                                       | #86497                                                                                              |
+| Bug&nbsp;fix      | Fixed an crash issue for `edbldr`. Now `edbldr` loads data into multiple tables with different encodings from the target database.                                                                  |                                                                                                     |
+| Bug&nbsp;fix      | Fixed an issue with possible data loss and `pg_dump` failures when using rowids.                                                                                                                    | #35901                                                                                              |
+| Bug&nbsp;fix      | Fixed an issue with assertion in `DROP ROLE` statement having duplicate names.                                                                                                                      |                                                                                                     |
+| Bug&nbsp;fix      | Fixed server crash with `edb_dblink_oci` in left join with whole row reference.                                                                                                                     |                                                                                                     |
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_4_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_4_0_rel_notes.mdx
new file mode 100644
index 00000000000..e2cb3fdce51
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_4_0_rel_notes.mdx
@@ -0,0 +1,20 @@
+---
+title: EDB Postgres Advanced Server 16.4.0 release notes
+navTitle: "Version 16.4.0"
+---
+
+Released: 8 Aug 2024
+
+EDB Postgres Advanced Server 16.4.0 includes the following enhancements and bug fixes:
+
+| Type           | Description                                                                                                                                         | Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
+|----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
+| Upstream merge | Merged with community PostgreSQL 16.4. This release includes a fix for [CVE-2024-7348](https://www.postgresql.org/support/security/CVE-2024-7348/). See the [PostgreSQL 16.4 Release Notes](https://www.postgresql.org/docs/release/16.4/) for more information. |      [CVE-2024-7348](https://www.postgresql.org/support/security/CVE-2024-7348/) |                                                                                               |
+| Feature        | Added `alteruser` utility to alter the user details. It allows to modify an existing role in your database clusters.                                |                                                                                                     |
+| Bug&nbsp;fix   | Fixed an issue for EDB*Loader. Now when multiple duplicate key errors occur during the load it doesn't slow down and memory doesn't overflow.       | #37017                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue for replication connections. Now it correctly displays the authentication failure error message.                                     | #101591                                                                                             |
+| Bug&nbsp;fix   | Fixed an issue for `ecpg`. Now it supports `do..while()` in Pro*C mode (`-C PROC`).                                                                 | #35988                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue for `edb_dblink_oci`. Now it correctly push downs `ANY` and `ALL` operators when used with scalar array.                             |                                                                                               |
+| Bug&nbsp;fix   | Fixed an issue for `to_number()` function. Now it correctly accepts the `"+"` sign.                                                                 | #92903                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue with incomplete transactions clean up after a crash. Now the incomplete transactions are cleaned up in reorder buffer after a crash. | #99636                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue with `edb_dblink_oci`. Now it uses SHA256 instead of MD5 for password obfuscation.                                                   | #38240                                                                                              |
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_4_1_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_4_1_rel_notes.mdx
new file mode 100644
index 00000000000..970726d7999
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_4_1_rel_notes.mdx
@@ -0,0 +1,12 @@
+---
+title: EDB Postgres Advanced Server 16.4.1 release notes
+navTitle: "Version 16.4.1 "
+---
+
+Released: 16 Aug 2024
+
+EDB Postgres Advanced Server 16.4.1  includes the following enhancements and bug fixes:
+
+| Type         | Description                                                                                                                                                                                                                                                                                                                             | Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
+|--------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
+| Bug&nbsp;fix | A previous release introduced a new `in_create` field to the LogicalDecodingContext structure and changed its memory layout. This means that any code that expects the old layout will no longer be compatible. The release fixed the issue to ensure the old layout is still compatible with the creation of a logical replication slot. |                                                                                                     |
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx
new file mode 100644
index 00000000000..150677ac410
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_6_0_rel_notes.mdx
@@ -0,0 +1,19 @@
+---
+title: EDB Postgres Advanced Server 16.6.0 release notes
+navTitle: "Version 16.6.0 "
+---
+
+Released: 21 Nov 2024
+
+EDB Postgres Advanced Server 16.6.0  includes the following enhancements and bug fixes:
+
+| Type           | Description                                                                                                                                                                                                                                                        | Addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
+|----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------|
+| Upstream merge | Merged with community PostgreSQL 16.6. This release includes a fix for [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/). See the [PostgreSQL 16.6 Release Notes](https://www.postgresql.org/docs/release/16.6/) for more information. | [CVE-2024-10978](https://www.postgresql.org/support/security/CVE-2024-10978/)                       |
+| Bug&nbsp;fix   | Fixed an issue for Auditing. With `edb_audit`, now you can audit the initial connection process or authentication messages as well.                                                                                                                                | #39540                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue for `EDB*Loader`. Now the `negative bitmapset member not allowed` error is resolved for partitioned tables.                                                                                                                                         | #39562                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue for `Oracle Proc*c`and `ecpg with PROC` . Corrected the macro definition in `sqlda-proc.h` to fix the compilation errors when used.                                                                                                                 | #40573                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue for replication. Now the login of locked account on the physical replica is not allowed.                                                                                                                                                            |                                                                                                     |
+| Bug&nbsp;fix   | Fixed an issue for `COPY` and `EDB*Loader`. Now the server is not crashed while using dynamic partitioning in `COPY` and `EDB*Loader`.                                                                                                                             | #38963                                                                                              |
+| Bug&nbsp;fix   | Fixed an issue with tab completion for the object names while using in SQL statements.                                                                                                                                                                             |                                                                                                     |
+| Bug&nbsp;fix   | Fixed an issue with `ecpg`. Now it supports `EXEC SQL INCLUDE` in Pro*C (`-C PROC`) mode.                                                                                                                                                                          | #41438                                                                                              |
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_rel_notes/epas16_rel_notes.mdx b/product_docs/docs/epas/16/epas_rel_notes/epas16_rel_notes.mdx
new file mode 100644
index 00000000000..f094b5532af
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/epas16_rel_notes.mdx
@@ -0,0 +1,34 @@
+---
+title: EDB Postgres Advanced Server 16.1 release notes
+navTitle: "Version 16.1"
+---
+
+Released: 09 Nov 2023
+
+EDB Postgres Advanced Server 16.1 includes the following enhancements and bug fixes:
+
+!!! Note Deprecation
+This release removes support for Index Advisor and `edb_enable_pruning` GUC parameter.
+Index Advisor features are now included in the [EDB Query Advisor](/pg_extensions/query_advisor/).
+!!!
+
+|      Type      |                                                                                                                                                                                 Description                                                                                                                                                                                 | Category |
+| -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
+| Upstream merge | Merged with community PostgreSQL 16.1. See the [PostgreSQL 16 Release Notes](https://www.postgresql.org/docs/16/release-16-1.html) for more information.                                                                                                                                                                                                                   |          |
+| Feature        | Added support for Oracle-compatible `DBMS_PRIVILEGE_CAPTURE` package and the SQL commands to define the capture privilege policy. See the [DBMS_PRIVILEGE_CAPTURE](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_privilege_capture/) for more information.                                                                 |          |
+| Feature        | Added support for two timezone functions: `DBTIMEZONE` and `SESSIONTIMEZONE`. See the [TIMEZONE functions](../reference/sql_reference/03_functions_and_operators/08_date_time_functions_and_operators/#timezone-functions) for more information.                                                                                                                              |          |
+| Feature        | Added support for the Oracle-compatible `NANVL` function. See the [NANVL function](../reference/sql_reference/03_functions_and_operators/10_conditional_expressions/#nanvl) for more information.                                                                                                                                                                           |          |
+| Feature        | Added support for the Oracle-equivalent `LNNVL()` function. See the [LNNVL function](../reference/sql_reference/03_functions_and_operators/10_conditional_expressions/#lnnvl) for more information.                                                                                                                                                                         |          |
+| Feature        | Added support for the Oracle-compatible `DUMP` SQL function. See the [DUMP function](../reference/sql_reference/03_functions_and_operators/dump_function/) for more information.                                                                                                                                                                                            |          |
+| Feature        | Added support for the Oracle-compatible `NLS CHARSET` functions. See the [NLS functions](../reference/sql_reference/03_functions_and_operators/04_string_functions_and_operators/) for more information.                                                                                                                                                                    |          |
+| Feature        | Added support for few more subprograms of `DBMS_SQL` package to ease the migrations. See the [DBMS_SQL package](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/) for more information.                                                                                                                                  |          |
+| Feature        | Added `spl_check` extension to check and report errors for the EDB SPL language. See the [spl_check](/pg_extensions/spl_check/) for more information.                                                                                                                                                                                                                  |          |
+| Enhancement    | Added support for `UTL_FILE` subprograms to ease the migrations. See the [utl_file](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/20_utl_file.mdx) for more information.                                                                                                                                                           |          |
+| Enhancement    | Transparent data encryption (TDE) now supports the AES key length 256 option to TDE.                                                                                                                                                                                                                                                                                        |          |
+| Enhancement    | Added the `edb_job_scheduler` extension, which provides a background process that does the job scheduling for the `DBMS_SCHEDULER` and `DBMS_JOB` packages. Before, these packages were dependent on pgAgent. With this extension, packages don't have that dependency. See the [EDB Job Scheduler extension](/pg_extensions/edb_job_scheduler/) for more information. |          |
+| Enhancement    | The (`ORDERED, NULL`) upperrel operations are now performed remotely through OCI DBlink, which is responsible for evaluating the query’s `ORDER BY` ordering.                                                                                                                                                                                                               |          |
+| Enhancement    | Implemented `MULTISET INTERSECT UNIQUE/DISTINCT` and `MULTISET EXCEPT UNIQUE/DISTINCT` now for SPL collection types.                                                                                                                                                                                                                                                        |          |
+| Enhancement    | You can now use the `BULK COLLECT` clause with a `FETCH` statement.                                                                                                                                                                                                                                                                                                         |          |
+| Enhancement    | Added synonym support for packages.                                                                                                                                                                                                                                                                                                                                         |          |
+| Enhancement    | The `TO_TIMESTAMP_TZ()` function now takes a single argument that converts a string to `TIMESTAMPTZ` in the default format.                                                                                                                                                                                                                                                 |          |
+| Enhancement    | The `EXPAND_SQL_TEXT` procedure of the `DBMS_UTILITY` package is now supported. It returns an expanded version of a given SQL query by replacing view references with its definition.                                                                                                                                                                                       |          |
diff --git a/product_docs/docs/epas/16/epas_rel_notes/index.mdx b/product_docs/docs/epas/16/epas_rel_notes/index.mdx
new file mode 100644
index 00000000000..32afb7c9134
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_rel_notes/index.mdx
@@ -0,0 +1,46 @@
+---
+navTitle: Release notes
+title: "EDB Postgres Advanced Server release notes"
+navigation:
+- epas16_6_0_rel_notes
+- epas16_4_1_rel_notes
+- epas16_4_0_rel_notes
+- epas16_3_0_rel_notes
+- epas16_2_0_rel_notes
+- epas16_rel_notes
+
+---
+
+EDB Postgres Advanced Server 16 is built on open-source PostgreSQL 16, which introduces myriad enhancements that enable databases to scale up and scale out in more efficient ways. 
+
+The EDB Postgres Advanced Server documentation describes the latest version of EDB Postgres Advanced Server 16 including minor releases and patches. These release notes provide information on what was new in each release. 
+
+| Version                        | Release date | Upstream merges                                                                                                  |
+|--------------------------------|--------------|------------------------------------------------------------------------------------------------------------------|
+| [16.6.0](epas16_6_0_rel_notes) | 21 Nov 2024  | [16.6](https://www.postgresql.org/docs/16/release-16-6.html)                                                     |
+| [16.4.1](epas16_4_1_rel_notes) | 16 Aug 2024  |                                                                                                                  |
+| [16.4.0](epas16_4_0_rel_notes) | 08 Aug 2024  | [16.4](https://www.postgresql.org/docs/16/release-16-4.html)                                                     |
+| [16.3.0](epas16_3_0_rel_notes) | 09 May 2024  | [16.3](https://www.postgresql.org/docs/16/release-16-3.html)                                                     |
+| [16.2](epas16_2_0_rel_notes)   | 08 Feb 2024  | [16.2](https://www.postgresql.org/docs/16/release-16-2.html)                                                     |
+| [16.1](epas16_rel_notes)       | 09 Nov 2023  | [16.0](https://www.postgresql.org/docs/16/release-16.html),[16.1](https://www.postgresql.org/docs/release/16.1/) |
+
+## Component certification
+
+This components are included in the EDB Postgres Advanced Server v16.1 release:
+
+-   pgAgent 4.4.2
+-   PL Debugger 1.5.1
+-   pg_catcheck 1.4.0
+-   EDB Query Advisor 1.0.1
+-   EDB Wait States 1.1.0
+-   EDB Clone Schema
+-   EDB Parallelcone
+-   EDB EDB*Plus 41.2.0
+-   SQL Profiler 4.1.1
+-   SPL Check
+
+## Support announcements
+
+### Backup and Recovery Tool (BART) incompatibility
+
+The EDB Backup and Recovery Tool (BART) isn't supported by EDB Postgres Advanced Server or PostgreSQL version 14 and later. We strongly recommend that you move to [Barman](/supported-open-source/barman/) or [PgBackRest](/supported-open-source/pgbackrest/) as your backup recovery tool. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/01_sql_protect_overview.mdx b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/01_sql_protect_overview.mdx
new file mode 100644
index 00000000000..87bbbfee77f
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/01_sql_protect_overview.mdx
@@ -0,0 +1,99 @@
+---
+title: "SQL/Protect overview"
+description: "Provides an overview about how SQL/Protect guards against different types of SQL injection attacks"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.28.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.073.html"
+---
+
+<div id="sql_protect_overview" class="registered_link"></div>
+
+SQL/Protect guards against different types of SQL injection attacks.
+
+## Types of SQL injection attacks
+
+A number of different techniques are used to perpetrate SQL injection attacks. Each technique is characterized by a certain *signature*. SQL/Protect examines queries for the following signatures.
+
+### Unauthorized relations
+
+While EDB Postgres Advanced Server allows administrators to restrict access to relations (such as tables and views), many administrators don't perform this tedious task. SQL/Protect provides a *learn* mode that tracks the relations a user accesses.
+
+This mode allows administrators to examine the workload of an application and for SQL/Protect to learn the relations an application is allowed to access for a given user or group of users in a role.
+
+When SQL/Protect is switched to *passive* or *active* mode, the incoming queries are checked against the list of learned relations.
+
+### Utility commands
+
+A common technique used in SQL injection attacks is to run utility commands, which are typically SQL data definition language (DDL) statements. An example is creating a user-defined function that can access other system resources.
+
+SQL/Protect can block running all utility commands that aren't normally needed during standard application processing.
+
+### SQL tautology
+
+The most frequent technique used in SQL injection attacks is issuing a tautological `WHERE` clause condition (that is, using a condition that is always true).
+
+The following is an example:
+
+ `WHERE password = 'x' OR 'x'='x'`
+
+Attackers usually start identifying security weaknesses using this technique. SQL/Protect can block queries that use a tautological conditional clause.
+
+### Unbounded DML statements
+
+A dangerous action taken during SQL injection attacks is running unbounded DML statements. These are `UPDATE` and `DELETE` statements with no `WHERE` clause. For example, an attacker might update all users’ passwords to a known value or initiate a denial of service attack by deleting all of the data in a key table.
+
+## Monitoring SQL injection attacks
+
+SQL/Protect can monitor and report on SQL injection attacks.
+
+### Protected roles
+
+Monitoring for SQL injection attacks involves analyzing SQL statements originating in database sessions where the current user of the session is a *protected role*. A protected role is an EDB Postgres Advanced Server user or group that the database administrator chooses to monitor using SQL/Protect. (In EDB Postgres Advanced Server, users and groups are collectively referred to as *roles*.)
+
+You can customize each protected role for the types of SQL injection attacks it's being monitored for, This approach provides different levels of protection by role and significantly reduces the user-maintenance load for DBAs.
+
+You can't make a role with the superuser privilege a protected role. If a protected non-superuser role later becomes a superuser, certain behaviors occur when that superuser tries to issue any command:
+
+-   SQL/Protect issues a warning message for every command issued by the protected superuser.
+-   The statistic in the column superusers of `edb_sql_protect_stats` is incremented with every command issued by the protected superuser. See [Attack attempt statistics](#attack-attempt-statistics) for information on the `edb_sql_protect_stats` view.
+-   SQL/Protect in active mode prevents all commands issued by the protected superuser from running.
+
+Either alter a protected role that has the superuser privilege so that it's no longer a superuser, or revert it to an unprotected role.
+
+### Attack attempt statistics
+
+SQL/Protect records each use of a command by a protected role that's considered an attack. It collects statistics by type of SQL injection attack, as discussed in [Types of SQL injection attacks](../02_protecting_against_sql_injection_attacks/01_sql_protect_overview/#types-of-sql-injection-attacks).
+
+You can access these statistics from the view `edb_sql_protect_stats`. You can easily monitor this view to identify the start of a potential attack.
+
+The columns in `edb_sql_protect_stats` monitor the following:
+
+-   **username.** Name of the protected role.
+-   **superusers.** Number of SQL statements issued when the protected role is a superuser. In effect, any SQL statement issued by a protected superuser increases this statistic. See [Protected roles](#protected-roles) for information about protected superusers.
+-   **relations.** Number of SQL statements issued referencing relations that weren't learned by a protected role. (These relations aren't in a role’s protected relations list.)
+-   **commands.** Number of DDL statements issued by a protected role.
+-   **tautology.** Number of SQL statements issued by a protected role that contained a tautological condition.
+-   **dml.** Number of `UPDATE` and `DELETE` statements issued by a protected role that didn't contain a `WHERE` clause.
+
+These statistics give database administrators the chance to react proactively in preventing theft of valuable data or other malicious actions.
+
+If a role is protected in more than one database, the role’s statistics for attacks in each database are maintained separately and are viewable only when connected to the respective database.
+
+!!! Note
+    SQL/Protect statistics are maintained in memory while the database server is running. When the database server is shut down, the statistics are saved to a binary file named `edb_sqlprotect.stat` in the `data/global` subdirectory of the EDB Postgres Advanced Server home directory.
+
+### Attack attempt queries
+
+Each use of a command by a protected role that's considered an attack by SQL/Protect is recorded in the `edb_sql_protect_queries` view, which contains the following columns:
+
+-   **username.** Database user name of the attacker used to log into the database server.
+-   **ip_address.** IP address of the machine from which the attack was initiated.
+-   **port.** Port number from which the attack originated.
+-   **machine_name.** Name of the machine from which the attack originated, if known.
+-   **date_time.** Date and time when the database server received the query. The time is stored to the precision of a minute.
+-   **query.** The query string sent by the attacker.
+
+The maximum number of offending queries that are saved in `edb_sql_protect_queries` is controlled by the `edb_sql_protect.max_queries_to_save` configuration parameter.
+
+If a role is protected in more than one database, the role’s queries for attacks in each database are maintained separately. They are viewable only when connected to the respective database.
diff --git a/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/02_configuring_sql_protect.mdx b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/02_configuring_sql_protect.mdx
new file mode 100644
index 00000000000..42249779a02
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/02_configuring_sql_protect.mdx
@@ -0,0 +1,510 @@
+---
+title: "Configuring SQL/Protect"
+description: "Describes the various ways you can configure SQL/Protect"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.29.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.074.html"
+---
+
+<div id="configuring_sql_protect" class="registered_link"></div>
+
+You can configure how SQL/Protect operates.
+
+## Prerequisites
+
+Meet the following prerequisites before configuring SQL/Protect:
+
+-   The library file (`sqlprotect.so` on Linux, `sqlprotect.dll` on Windows) needed to run SQL/Protect is installed in the `lib` subdirectory of your EDB Postgres Advanced Server home directory. For Windows, the EDB Postgres Advanced Server installer does this. For Linux, install the `edb-as<xx>-server-sqlprotect` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number.
+
+-   You need the SQL script file `sqlprotect.sql` located in the `share/contrib` subdirectory of your EDB Postgres Advanced Server home directory.
+
+-   You must configure the database server to use SQL/Protect, and you must configure each database that you want SQL/Protect to monitor:
+
+    -   You must modify the database server configuration file `postgresql.conf` by adding and enabling configuration parameters used by SQL/Protect.
+    -   Install database objects used by SQL/Protect in each database that you want SQL/Protect to monitor.
+
+## Configuring the module
+
+1.  Edit the following configuration parameters in the `postgresql.conf` file located in the `data` subdirectory of your EDB Postgres Advanced Server home directory:
+
+  -   `shared_preload_libraries`. Add `$libdir/sqlprotect` to the list of libraries.
+
+  -   `edb_sql_protect.enabled`. Controls whether SQL/Protect is actively monitoring protected roles by analyzing SQL statements issued by those roles and reacting according to the setting of `edb_sql_protect.level`. When you're ready to begin monitoring with SQL/Protect, set this parameter to `on`. The default is `off`.
+
+  -   `edb_sql_protect.level`. Sets the action taken by SQL/Protect when a SQL statement is issued by a protected role. The default behavior is `passive`. Initially, set this parameter to `learn`. See [Setting the protection level](#setting-the-protection-level) for more information.
+
+  -   `edb_sql_protect.max_protected_roles`. Sets the maximum number of roles to protect. The default is `64`.
+
+  -   `edb_sql_protect.max_protected_relations`. Sets the maximum number of relations to protect per role. The default is `1024`.
+
+    The total number of protected relations for the server is the number of protected relations times the number of protected roles. Every protected relation consumes space in shared memory. The space for the maximum possible protected relations is reserved during database server startup.
+
+  -   `edb_sql_protect.max_queries_to_save`. Sets the maximum number of offending queries to save in the `edb_sql_protect_queries` view. The default is `5000`. If the number of offending queries reaches the limit, additional queries aren't saved in the view but are accessible in the database server log file.
+
+    The minimum valid value for this parameter is `100`. If you specify a value less than `100`, the database server starts using the default setting of `5000`. A warning message is recorded in the database server log file.
+
+  This example shows the settings of these parameters in the `postgresql.conf` file:
+
+```ini
+shared_preload_libraries = '$libdir/dbms_pipe,$libdir/edb_gen,$libdir/sqlprotect'
+                                        # (change requires restart)
+                          .
+                          .
+                          .
+edb_sql_protect.enabled = off
+edb_sql_protect.level = learn
+edb_sql_protect.max_protected_roles = 64
+edb_sql_protect.max_protected_relations = 1024
+edb_sql_protect.max_queries_to_save = 5000
+```
+
+2.  After you modify the `postgresql.conf` file, restart the database server.
+
+  -  **On Linux:** Invoke the EDB Postgres Advanced Server service script with the `restart` option.
+
+    On a Redhat or CentOS 7.x installation, use the command:
+
+  ```shell
+  systemctl restart edb-as-16
+  ```
+
+  -  **On Windows:** Use the Windows Services applet to restart the service named `edb-as-14`.
+
+3.  For each database that you want to protect from SQL injection attacks, connect to the database as a superuser (either `enterprisedb` or `postgres`, depending on your installation options). Then run the script `sqlprotect.sql`, located in the `share/contrib` subdirectory of your EDB Postgres Advanced Server home directory. The script creates the SQL/Protect database objects in a schema named `sqlprotect`.
+
+This example shows the process to set up protection for a database named `edb`:
+
+<!-- Consider replacing -->
+
+```sql
+$ /usr/edb/as16/bin/psql -d edb -U enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0, server 16.1.0)
+Type "help" for help.
+
+edb=# \i /usr/edb/as16/share/contrib/sqlprotect.sql
+CREATE SCHEMA
+GRANT
+SET
+CREATE TABLE
+GRANT
+CREATE TABLE
+GRANT
+CREATE FUNCTION
+CREATE FUNCTION
+CREATE FUNCTION
+CREATE FUNCTION
+CREATE FUNCTION
+CREATE FUNCTION
+CREATE FUNCTION
+DO
+CREATE FUNCTION
+CREATE FUNCTION
+DO
+CREATE VIEW
+GRANT
+DO
+CREATE VIEW
+GRANT
+CREATE VIEW
+GRANT
+CREATE FUNCTION
+CREATE FUNCTION
+SET
+```
+
+## Selecting roles to protect
+
+After you create the SQL/Protect database objects in a database, you can select the roles for which to monitor SQL queries for protection and the level of protection to assign to each role.
+
+### Setting the protected roles list
+
+For each database that you want to protect, you must determine the roles you want to monitor and then add those roles to the *protected roles list* of that database.
+
+1.  Connect as a superuser to a database that you want to protect with either `psql` or the Postgres Enterprise Manager client:
+
+<!-- Consider replacing -->
+
+```sql
+$ /usr/edb/as16/bin/psql -d edb -U enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0, server 16.1.0)
+Type "help" for help.
+
+edb=#
+```
+
+2.  Since the SQL/Protect tables, functions, and views are built under the `sqlprotect` schema, use the `SET search_path` command to include the `sqlprotect` schema in your search path. Doing so eliminates the need to schema-qualify any operation or query involving SQL/Protect database objects:
+
+```sql
+edb=# SET search_path TO sqlprotect;
+SET
+```
+
+3.  You must add each role that you want to protect to the protected roles list. This list is maintained in the table `edb_sql_protect`.
+
+  To add a role, use the function `protect_role('rolename')`. This example protects a role named `appuser`:
+
+```sql
+edb=# SELECT protect_role('appuser');
+__OUTPUT__
+ protect_role
+--------------
+
+(1 row)
+```
+
+You can list the roles that were added to the protected roles list with the following query:
+
+```sql
+edb=# SELECT * FROM edb_sql_protect;
+__OUTPUT__
+ dbid  | roleid | protect_relations | allow_utility_cmds | allow_tautology |
+ allow_empty_dml
+-------+--------+-------------------+--------------------+-----------------+--
+-------------
+ 13917 |  16671 | t                 | f                  | f               | f
+(1 row)
+```
+
+A view is also provided that gives the same information using the object names instead of the object identification numbers (OIDs):
+
+```sql
+edb=# \x
+Expanded display is on.
+edb=# SELECT * FROM list_protected_users;
+__OUTPUT__
+-[ RECORD 1 ]------+--------
+dbname             | edb
+username           | appuser
+protect_relations  | t
+allow_utility_cmds | f
+allow_tautology    | f
+allow_empty_dml    | f
+```
+
+<div id="setting_the_protection_level" class="registered_link"></div>
+
+### Setting the protection level
+
+The `edb_sql_protect.level` configuration parameter sets the protection level, which defines the behavior of SQL/Protect when a protected role issues a SQL statement. The defined behavior applies to all roles in the protected roles lists of all databases configured with SQL/Protect in the database server.
+
+You can set the `edb_sql_protect.level` configuration parameter in the `postgresql.conf` file to one of the following values to specify learn, passive, or active mode:
+
+-   `learn`. Tracks the activities of protected roles and records the relations used by the roles. Use this mode when first configuring SQL/Protect so the expected behaviors of the protected applications are learned.
+-   `passive`. Issues warnings if protected roles are breaking the defined rules but doesn't stop any SQL statements from executing. This mode is the next step after SQL/Protect learns the expected behavior of the protected roles. It essentially behaves in intrusion detection mode. You can run this mode in production when proper monitoring is in place.
+-   `active`. Stops all invalid statements for a protected role. This mode behaves as a SQL firewall, preventing dangerous queries from running. This approach is particularly effective against early penetration testing when the attacker is trying to find the vulnerability point and the type of database behind the application. Not only does SQL/Protect close those vulnerability points, it tracks the blocked queries. This tracking can alert administrators before the attacker finds another way to penetrate the system.
+
+The default mode is `passive`.
+
+If you're using SQL/Protect for the first time, set `edb_sql_protect.level` to `learn`.
+
+## Monitoring protected roles
+
+After you configure SQL/Protect in a database, add roles to the protected roles list, and set the desired protection level, you can activate SQL/Protect in `learn`, `passive`, or `active` mode. You can then start running your applications.
+
+With a new SQL/Protect installation, the first step is to determine the relations that protected roles are allowed to access during normal operation. Learn mode allows a role to run applications during which time SQL/Protect is recording the relations that are accessed. These are added to the role’s *protected relations list* stored in table `edb_sql_protect_rel`.
+
+Monitoring for protection against attack begins when you run SQL/Protect in passive or active mode. In passive and active modes, the role is permitted to access the relations in its protected relations list. These are the specified relations the role can access during typical usage.
+
+However, if a role attempts to access a relation that isn't in its protected relations list, SQL/Protect returns a `WARNING` or `ERROR` severity-level message. The role’s attempted action on the relation might not be carried out, depending on whether the mode is passive or active.
+
+<div id="learn_mode" class="registered_link"></div>
+
+### Learn mode
+
+To activate SQL/Protect in learn mode:
+
+1.  Set the parameters in the `postgresql.conf` file:
+
+```ini
+edb_sql_protect.enabled = on
+edb_sql_protect.level = learn
+```
+
+2.  Reload the `postgresql.conf` file. From the EDB Postgres Advanced Server application menu, select **Reload Configuration > Expert Configuration**.
+
+  For an alternative method of reloading the configuration file, use the `pg_reload_conf` function. Be sure you're connected to a database as a superuser, and execute `function pg_reload_conf`:
+
+```sql
+edb=# SELECT pg_reload_conf();
+__OUTPUT__
+ pg_reload_conf
+----------------
+ t
+(1 row)
+```
+
+3.  Allow the protected roles to run their applications.
+
+  For example, the following queries are issued in the `psql` application by the protected role `appuser`:
+
+```sql
+edb=> SELECT * FROM dept;
+__OUTPUT__
+NOTICE:  SQLPROTECT: Learned relation: 16384
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BOSTON
+(4 rows)
+```
+```sql
+edb=> SELECT empno, ename, job FROM emp WHERE deptno = 10;
+__OUTPUT__
+NOTICE:  SQLPROTECT: Learned relation: 16391
+ empno | ename  |    job
+-------+--------+-----------
+  7782 | CLARK  | MANAGER
+  7839 | KING   | PRESIDENT
+  7934 | MILLER | CLERK
+(3 rows)
+```
+
+  SQL/Protect generates a `NOTICE` severity-level message, indicating the relation was added to the role’s protected relations list.
+
+  In SQL/Protect learn mode, SQL statements that are cause for suspicion aren't prevented from executing. However, a message is issued to alert the user to potentially dangerous statements:
+
+```sql
+edb=> CREATE TABLE appuser_tab (f1 INTEGER);
+NOTICE: SQLPROTECT: This command type is illegal for this user
+CREATE TABLE
+edb=> DELETE FROM appuser_tab;
+NOTICE: SQLPROTECT: Learned relation: 16672
+NOTICE: SQLPROTECT: Illegal Query: empty DML
+DELETE 0
+```
+
+4.  As a protected role runs applications, you can query the SQL/Protect tables to see that relations were added to the role’s protected relations list. Connect as a superuser to the database you're monitoring, and set the search path to include the `sqlprotect` schema:
+
+```sql
+edb=# SET search_path TO sqlprotect;
+SET
+```
+
+  Query the `edb_sql_protect_rel` table to see the relations added to the protected relations list:
+
+```sql
+edb=# SELECT * FROM edb_sql_protect_rel;
+__OUTPUT__
+ dbid   | roleid | relid
+--------+--------+-------
+ 13917  | 16671  | 16384
+ 13917  | 16671  | 16391
+ 13917  | 16671  | 16672
+(3 rows)
+```
+
+  The `list_protected_rels` view provides more comprehensive information along with the object names instead of the OIDs:
+
+```sql
+edb=# SELECT * FROM list_protected_rels;
+__OUTPUT__
+ Database | Protected User | Schema |    Name     | Type  |    Owner
+----------+----------------+--------+-------------+-------+------------
+ edb      | appuser        | public | dept        | Table | enterprisedb
+ edb      | appuser        | public | emp         | Table | enterprisedb
+ edb      | appuser        | public | appuser_tab | Table | appuser
+(3 rows)
+```
+
+### Passive mode
+
+After a role’s applications have accessed all relations they need, you can change the protection level so that SQL/Protect can actively monitor the incoming SQL queries and protect against SQL injection attacks.
+
+Passive mode is a less restrictive protection mode than active.
+
+1.  To activate SQL/Protect in passive mode, set the following parameters in the `postgresql.conf` file:
+
+```ini
+edb_sql_protect.enabled = on
+edb_sql_protect.level = passive
+```
+
+2.  Reload the configuration file as shown in Step 2 of [Learn mode](#learn-mode).
+
+  Now SQL/Protect is in passive mode. For relations that were learned, such as the `dept` and `emp` tables of the prior examples, SQL statements are permitted. No special notification to the client by SQL/Protect is required, as shown by the following queries run by user `appuser`:
+
+```sql
+edb=> SELECT * FROM dept;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+    10  | ACCOUNTING | NEW YORK
+    20  | RESEARCH   | DALLAS
+    30  | SALES      | CHICAGO
+    40  | OPERATIONS | BOSTON
+(4 rows)
+```
+```sql
+edb=> SELECT empno, ename, job FROM emp WHERE deptno = 10;
+__OUTPUT__
+ empno | ename  |    job
+-------+--------+-----------
+  7782 | CLARK  | MANAGER
+  7839 | KING   | PRESIDENT
+  7934 | MILLER | CLERK
+(3 rows)
+```
+
+  SQL/Protect doesn't prevent any SQL statement from executing. However, it issues a message of `WARNING` severity level for SQL statements executed against relations that weren't learned. It also issues a warning for SQL statements that contain a prohibited signature:
+
+```sql
+edb=> CREATE TABLE appuser_tab_2 (f1 INTEGER);
+WARNING: SQLPROTECT: This command type is illegal for this user
+CREATE TABLE
+edb=> INSERT INTO appuser_tab_2 VALUES (1);
+WARNING: SQLPROTECT: Illegal Query: relations
+INSERT 0 1
+edb=> INSERT INTO appuser_tab_2 VALUES (2);
+WARNING: SQLPROTECT: Illegal Query: relations
+INSERT 0 1
+edb=> SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+WARNING: SQLPROTECT: Illegal Query: relations
+WARNING: SQLPROTECT: Illegal Query: tautology
+__OUTPUT__
+f1
+----
+  1
+  2
+(2 rows)
+```
+
+3.  Monitor the statistics for suspicious activity.
+
+  By querying the view `edb_sql_protect_stats`, you can see the number of times SQL statements executed that referenced relations that weren't in a role’s protected relations list or contained SQL injection attack signatures. 
+
+  The following is a query on `edb_sql_protect_stats`:
+
+```sql
+edb=# SET search_path TO sqlprotect;
+SET
+edb=# SELECT * FROM edb_sql_protect_stats;
+__OUTPUT__
+ username  | superusers | relations | commands | tautology | dml
+-----------+------------+-----------+----------+-----------+-----
+ appuser   |     0      |     3     |    1     |     1     | 0
+(1 row)
+```
+
+4.  View information on specific attacks.
+
+  By querying the `edb_sql_protect_queries` view, you can see the SQL statements that were executed that referenced relations that weren't in a role’s protected relations list or that contained SQL injection attack signatures.
+
+  The following code sample shows a query on `edb_sql_protect_queries`:
+
+```sql
+edb=# SELECT * FROM edb_sql_protect_queries;
+__OUTPUT__
+-[ RECORD 1 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:21:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (1);
+-[ RECORD 2 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:21:00 -04:00
+ query        | CREATE TABLE appuser_tab_2 (f1 INTEGER);
+-[ RECORD 3 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:22:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (2);
+-[ RECORD 4 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:22:00 -04:00
+ query        | SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+```
+
+!!! Note
+    The `ip_address` and `port` columns don't return any information if the attack originated on the same host as the database server using the Unix-domain socket (that is, `pg_hba.conf` connection type `local`).
+
+### Active mode
+
+In active mode, disallowed SQL statements are prevented from executing. Also, the message issued by SQL/Protect has a higher severity level of `ERROR` instead of `WARNING`.
+
+1.  To activate SQL/Protect in active mode, set the following parameters in the `postgresql.conf` file:
+
+```ini
+edb_sql_protect.enabled = on
+edb_sql_protect.level = active
+```
+
+2.  Reload the configuration file as shown in Step 2 of [Learn mode](#learn-mode).
+
+This example shows SQL statements similar to those given in the examples of Step 2 in [Passive mode](#passive-mode). These statements are executed by the user `appuser` when `edb_sql_protect.level` is set to `active`:
+
+```sql
+edb=> CREATE TABLE appuser_tab_3 (f1 INTEGER);
+ERROR: SQLPROTECT: This command type is illegal for this user
+edb=> INSERT INTO appuser_tab_2 VALUES (1);
+ERROR: SQLPROTECT: Illegal Query: relations
+edb=> SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+ERROR: SQLPROTECT: Illegal Query: relations
+```
+
+The following shows the resulting statistics:
+
+```sql
+edb=# SELECT * FROM sqlprotect.edb_sql_protect_stats;
+__OUTPUT__
+ username  | superusers | relations | commands | tautology | dml
+-----------+------------+-----------+----------+-----------+-----
+ appuser   |      0     |     5     |     2    |     1     | 0
+(1 row)
+```
+
+The following is a query on `edb_sql_protect_queries`:
+
+```sql
+edb=# SELECT * FROM sqlprotect.edb_sql_protect_queries;
+__OUTPUT__
+-[ RECORD 1 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:21:00 -04:00
+ query        | CREATE TABLE appuser_tab_2 (f1 INTEGER);
+-[ RECORD 2 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:22:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (2);
+-[ RECORD 3 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | CREATE TABLE appuser_tab_3 (f1 INTEGER);
+-[ RECORD 4 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (1);
+-[ RECORD 5 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/03_common_maintenance_operations.mdx b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/03_common_maintenance_operations.mdx
new file mode 100644
index 00000000000..e49bb163f79
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/03_common_maintenance_operations.mdx
@@ -0,0 +1,260 @@
+---
+title: "Common maintenance operations"
+description: "Describes how to perform routine maintenance tasks using SQL/Protect"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.30.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.075.html"
+---
+
+<div id="common_maintenance_operations" class="registered_link"></div>
+
+You must be connected as a superuser to perform these operations. Include the `sqlprotect` schema in your search path.
+
+## Adding a role to the protected roles list
+
+Add a role to the protected roles list. Run `protect_role('rolename')`, as shown in this example:
+
+```sql
+edb=# SELECT protect_role('newuser');
+__OUTPUT__
+ protect_role
+--------------
+(1 row)
+```
+
+## Removing a role from the protected roles list
+
+To remove a role from the protected roles list, use either of the following functions:
+
+```sql
+unprotect_role('rolename')
+
+unprotect_role(roleoid)
+```
+
+The variation of the function using the OID is useful if you remove the role using the `DROP ROLE` or `DROP USER` SQL statement before removing the role from the protected roles list. If a query on a SQL/Protect relation returns a value such as `unknown (OID=16458)` for the user name, use the `unprotect_role(roleoid)` form of the function to remove the entry for the deleted role from the protected roles list.
+
+Removing a role using these functions also removes the role’s protected relations list.
+
+To delete the statistics for a role that was removed, use the [drop_stats function](#drop_stats).
+
+To delete the offending queries for a role that was removed, use the [drop_queries function](#drop_queries).
+
+This example shows the `unprotect_role` function:
+
+```sql
+edb=# SELECT unprotect_role('newuser');
+__OUTPUT__
+ unprotect_role
+----------------
+(1 row)
+```
+
+Alternatively, you can remove the role by giving its OID of `16693`:
+
+```sql
+edb=# SELECT unprotect_role(16693);
+__OUTPUT__
+ unprotect_role
+----------------
+(1 row)
+```
+
+## Setting the types of protection for a role
+
+You can change whether a role is protected from a certain type of SQL injection attack.
+
+Change the Boolean value for the column in `edb_sql_protect` corresponding to the type of SQL injection attack for which you want to enable or disable protection of a role.
+
+Be sure to qualify the following columns in your `WHERE` clause of the statement that updates `edb_sql_protect`:
+
+-   **dbid.** OID of the database for which you're making the change.
+-   **roleid.** OID of the role for which you're changing the Boolean settings
+
+For example, to allow a given role to issue utility commands, update the `allow_utility_cmds` column:
+
+```sql
+UPDATE edb_sql_protect SET allow_utility_cmds = TRUE WHERE dbid =
+13917 AND roleid = 16671;
+```
+
+You can verify the change was made by querying `edb_sql_protect` or `list_protected_users`. In the following query, note that column `allow_utility_cmds` now contains `t`:
+
+```sql
+edb=# SELECT dbid, roleid, allow_utility_cmds FROM edb_sql_protect;
+__OUTPUT__
+ dbid   | roleid | allow_utility_cmds
+--------+--------+--------------------
+ 13917  | 16671  | t
+(1 row)
+```
+
+The updated rules take effect on new sessions started by the role since the change was made.
+
+## Removing a relation from the protected relations list
+
+If SQL/Protect learns that a given relation is accessible for a given role, you can later remove that relation from the role’s protected relations list.
+
+Delete the entry from the `edb_sql_protect_rel` table using any of the following functions:
+
+```sql
+unprotect_rel('rolename', 'relname') 
+unprotect_rel('rolename', 'schema', 'relname') 
+unprotect_rel(roleoid, reloid)
+```
+
+If the relation given by `relname` isn't in your current search path, specify the relation’s schema using the second function format.
+
+The third function format allows you to specify the OIDs of the role and relation, respectively, instead of their text names.
+
+This example removes the `public.emp` relation from the protected relations list of the role `appuser`:
+
+```sql
+edb=# SELECT unprotect_rel('appuser', 'public', 'emp');
+__OUTPUT__
+ unprotect_rel
+---------------
+(1 row)
+```
+
+This query shows there's no longer an entry for the `emp` relation:
+
+```sql
+edb=# SELECT * FROM list_protected_rels;
+__OUTPUT__
+ Database | Protected User | Schema |    Name     | Type  |    Owner
+----------+----------------+--------+-------------+-------+--------------
+ edb      | appuser        | public | dept        | Table | enterprisedb
+ edb      | appuser        | public | appuser_tab | Table | appuser
+(2 rows)
+```
+
+SQL/Protect now issues a warning or completely blocks access (depending on the setting of `edb_sql_protect.level`) when the role attempts to use that relation.
+
+<div id="drop_stats" class="registered_link"></div>
+
+## Deleting statistics
+
+You can delete statistics from the view `edb_sql_protect_stats` using either of the following functions:
+
+```sql
+drop_stats('rolename')
+
+drop_stats(roleoid)
+```
+
+The form of the function using the OID is useful if you remove the role using the `DROP ROLE` or `DROP USER` SQL statement before deleting the role’s statistics using `drop_stats('rolename')`. If a query on `edb_sql_protect_stats` returns a value such as `unknown (OID=16458)` for the user name, use the `drop_stats(roleoid)` form of the function to remove the deleted role’s statistics from `edb_sql_protect_stats`.
+
+This example shows the `drop_stats` function:
+
+```sql
+edb=# SELECT drop_stats('appuser');
+__OUTPUT__
+ drop_stats
+------------
+(1 row)
+```
+```sql
+edb=# SELECT * FROM edb_sql_protect_stats;
+__OUTPUT__
+ username  | superusers | relations | commands | tautology | dml
+-----------+------------+-----------+----------+-----------+-----
+(0 rows)
+```
+
+This example uses the `drop_stats(roleoid)` form of the function when a role is dropped before deleting its statistics:
+
+```sql
+edb=# SELECT * FROM edb_sql_protect_stats;
+__OUTPUT__
+      username       | superusers | relations | commands | tautology | dml
+---------------------+------------+-----------+----------+-----------+-----
+ unknown (OID=16693) |          0 |         5 |        3 |         1 |   0
+ appuser             |          0 |         5 |        2 |         1 |   0
+(2 rows)
+```
+```sql
+edb=# SELECT drop_stats(16693);
+__OUTPUT__
+ drop_stats
+------------
+
+(1 row)
+```
+```sql
+edb=# SELECT * FROM edb_sql_protect_stats;
+__OUTPUT__
+ username | superusers | relations | commands | tautology | dml
+----------+------------+-----------+----------+-----------+-----
+ appuser  |          0 |         5 |        2 |         1 |   0
+(1 row)
+```
+
+<div id="drop_queries" class="registered_link"></div>
+
+## Deleting offending queries
+
+You can delete offending queries from the view `edb_sql_protect_queries` using either of the following functions:
+
+```sql
+drop_queries('rolename')
+
+drop_queries(roleoid)
+```
+
+The variation of the function using the OID is useful if you remove the role using the `DROP ROLE` or `DROP USER` SQL statement before deleting the role’s offending queries using `drop_queries('rolename')`. If a query on `edb_sql_protect_queries` returns a value such as `unknown (OID=16454)` for the user name, use the `drop_queries(roleoid)` form of the function to remove the deleted role’s offending queries from `edb_sql_protect_queries`.
+
+This example shows the `drop_queries` function:
+
+```sql
+edb=# SELECT drop_queries('appuser');
+__OUTPUT__
+ drop_queries
+--------------
+           5
+(1 row)
+```
+```sql
+edb=# SELECT * FROM edb_sql_protect_queries;
+__OUTPUT__
+ username  | ip_address | port | machine_name | date_time | query
+-----------+------------+------+--------------+-----------+-------
+(0 rows)
+```
+
+This example uses the `drop_queries(roleoid)` form of the function when a role is dropped before deleting its queries:
+
+```sql
+edb=# SELECT username, query FROM edb_sql_protect_queries;
+__OUTPUT__
+      username       |                    query
+---------------------+----------------------------------------------
+ unknown (OID=16454) | CREATE TABLE appuser_tab_2 (f1 INTEGER);
+ unknown (OID=16454) | INSERT INTO appuser_tab_2 VALUES (2);
+ unknown (OID=16454) | CREATE TABLE appuser_tab_3 (f1 INTEGER);
+ unknown (OID=16454) | INSERT INTO appuser_tab_2 VALUES (1);
+ unknown (OID=16454) | SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+(5 rows)
+```
+```sql
+edb=# SELECT drop_queries(16454);
+__OUTPUT__
+ drop_queries
+--------------
+          5
+(1 row)
+```
+```sql
+edb=# SELECT * FROM edb_sql_protect_queries;
+__OUTPUT__
+ username | ip_address | port | machine_name | date_time | query
+----------+------------+------+--------------+-----------+-------
+(0 rows)
+```
+
+## Disabling and enabling monitoring
+
+If you want to turn off SQL/Protect monitoring, modify the `postgresql.conf` file, setting the `edb_sql_protect.enabled` parameter to `off`. After saving the file, reload the server configuration to apply the settings.
+
+If you want to turn on SQL/Protect monitoring, modify the `postgresql.conf` file, setting the `edb_sql_protect.enabled` parameter to `on`. Save the file, and then reload the server configuration to apply the settings.
diff --git a/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/04_backing_up_restoring_sql_protect.mdx b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/04_backing_up_restoring_sql_protect.mdx
new file mode 100644
index 00000000000..c8806ad753a
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/04_backing_up_restoring_sql_protect.mdx
@@ -0,0 +1,276 @@
+---
+title: "Backing up and restoring a SQL/Protect database"
+description: "Describes how to back up and then restore databases configured with SQL/Protect"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.31.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.076.html"
+---
+
+<div id="backing_up_restoring_sql_protect" class="registered_link"></div>
+
+Backing up a database that's configured with SQL/Protect and then restoring the backup file to a new database requires considerations in addition to those normally associated with backup and restore procedures. These added considerations are mainly due to the use of object identification numbers (OIDs) in the SQL/Protect tables.
+
+!!! Note
+    This information applies if your backup and restore procedures result in re-creating database objects in the new database with new OIDs, such as when using the `pg_dump` backup program.
+
+    If you're backing up your EDB Postgres Advanced Server database server by using the operating system’s copy utility to create a binary image of the EDB Postgres Advanced Server data files (file system backup method), then this information doesn't apply.
+
+## Object identification numbers in SQL/Protect tables
+
+SQL/Protect uses two tables, `edb_sql_protect` and `edb_sql_protect_rel`, to store information on database objects such as databases, roles, and relations. References to these database objects in these tables are done using the objects’ OIDs, not their text names. The OID is a numeric data type used by EDB Postgres Advanced Server to uniquely identify each database object.
+
+When a database object is created, EDB Postgres Advanced Server assigns an OID to the object, which is then used when a reference to the object is needed in the database catalogs. If you create the same database object in two databases, such as a table with the same `CREATE TABLE` statement, each table is assigned a different OID in each database.
+
+In a backup and restore operation that results in re-creating the backed-up database objects, the restored objects end up with different OIDs in the new database from what they were assigned in the original database. As a result, the OIDs referencing databases, roles, and relations stored in the `edb_sql_protect` and `edb_sql_protect_rel` tables are no longer valid when these tables are dumped to a backup file and then restored to a new database.
+
+Two functions, `export_sqlprotect` and `import_sqlprotect`, are used specifically for backing up and restoring SQL/Protect tables to ensure the OIDs in the SQL/Protect tables reference the correct database objects after the tables are restored.
+
+## Backing up the database
+
+Back up a database that was configured with SQL/Protect.
+
+1.  Create a backup file using `pg_dump`.
+
+  This example shows a plain-text backup file named `/tmp/edb.dmp` created from database `edb` using the `pg_dump` utility program:
+
+```shell
+$ cd /usr/edb/as16/bin
+$ ./pg_dump -U enterprisedb -Fp -f /tmp/edb.dmp edb
+Password:
+$
+```
+
+2.  Connect to the database as a superuser, and export the SQL/Protect data using the `export_sqlprotect('sqlprotect_file')` function. `sqlprotect_file` is the fully qualified path to a file where the SQL/Protect data is saved.
+
+  The `enterprisedb` operating system account (`postgres` if you installed EDB Postgres Advanced Server in PostgreSQL compatibility mode) must have read and write access to the directory specified in `sqlprotect_file`.
+
+```sql
+edb=# SELECT sqlprotect.export_sqlprotect('/tmp/sqlprotect.dmp');
+__OUTPUT__
+ export_sqlprotect
+-------------------
+(1 row)
+```
+
+The files `/tmp/edb.dmp` and `/tmp/sqlprotect.dmp` comprise your total database backup.
+
+## Restoring from the backup files
+
+1.  Restore the backup file to the new database.
+
+  This example uses the `psql` utility program to restore the plain-text backup file `/tmp/edb.dmp` to a newly created database named `newdb`:
+
+```sql
+$ /usr/edb/as16/bin/psql -d newdb -U enterprisedb -f /tmp/edb.dmp
+Password for user enterprisedb:
+SET
+SET
+SET
+SET
+SET
+COMMENT
+CREATE SCHEMA
+    .
+    .
+    .
+```
+
+2.  Connect to the new database as a superuser, and delete all rows from the `edb_sql_protect_rel` table.
+
+  This deletion removes any existing rows in the `edb_sql_protect_rel` table that were backed up from the original database. These rows don't contain the correct OIDs relative to the database where the backup file was restored.
+<!--Consider replacing -->
+```sql
+$ /usr/edb/as16/bin/psql -d newdb -U enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0, server 16.1.0)
+Type "help" for help.
+
+newdb=# DELETE FROM sqlprotect.edb_sql_protect_rel;
+DELETE 2
+```
+
+3.  Delete all rows from the `edb_sql_protect` table.
+
+  This deletion removes any existing rows in the `edb_sql_protect` table that were backed up from the original database. These rows don't contain the correct OIDs relative to the database where the backup file was restored.
+
+```sql
+newdb=# DELETE FROM sqlprotect.edb_sql_protect;
+DELETE 1
+```
+
+4.  Delete any of the database's statistics.
+
+  This deletion removes any existing statistics for the database to which you're restoring the backup. The following query displays any existing statistics:
+
+```sql
+newdb=# SELECT * FROM sqlprotect.edb_sql_protect_stats;
+__OUTPUT__
+ username  | superusers | relations | commands | tautology | dml
+-----------+------------+-----------+----------+-----------+-----
+(0 rows)
+```
+
+  For each row that appears in the preceding query, use the `drop_stats` function, specifying the role name of the entry.
+
+  For example, if a row appeared with `appuser` in the `username` column, issue the following command to remove it:
+
+```sql
+newdb=# SELECT sqlprotect.drop_stats('appuser');
+__OUTPUT__
+ drop_stats
+------------
+(1 row)
+```
+
+5.  Delete any of the database's offending queries.
+
+  This deletion removes any existing queries for the database to which you're restoring the backup. This query displays any existing queries:
+
+```sql
+edb=# SELECT * FROM sqlprotect.edb_sql_protect_queries;
+__OUTPUT__
+ username  | ip_address | port | machine_name | date_time | query
+-----------+------------+------+--------------+-----------+-------
+(0 rows)
+```
+
+  For each row that appears in the preceding query, use the `drop_queries` function, specifying the role name of the entry. For example, if a row appeared with `appuser` in the `username` column, issue the following command to remove it:
+
+```sql
+edb=# SELECT sqlprotect.drop_queries('appuser');
+__OUTPUT__
+ drop_queries
+--------------
+(1 row)
+```
+
+6.  Make sure the role names that were protected by SQL/Protect in the original database are in the database server where the new database resides.
+
+  If the original and new databases reside in the same database server, then you don't need to do anything if you didn't delete any of these roles from the database server.
+
+7.  Run the function `import_sqlprotect('sqlprotect_file')`, where `sqlprotect_file` is the fully qualified path to the file you created in Step 2 of [Backing up the database](#backing-up-the-database).
+
+```sql
+newdb=# SELECT sqlprotect.import_sqlprotect('/tmp/sqlprotect.dmp');
+__OUTPUT__
+ import_sqlprotect
+-------------------
+(1 row)
+```
+
+  Tables `edb_sql_protect` and `edb_sql_protect_rel` are populated with entries containing the OIDs of the database objects as assigned in the new database. The statistics view `edb_sql_protect_stats` also displays the statistics imported from the original database.
+
+  The SQL/Protect tables and statistics are properly restored for this database. Use the following queries on the EDB Postgres Advanced Server system catalogs to verify:
+
+```sql
+newdb=# SELECT datname, oid FROM pg_database;
+__OUTPUT__
+  datname  |  oid
+-----------+-------
+ template1 |     1
+ template0 | 13909
+ edb       | 13917
+ newdb     | 16679
+(4 rows)
+```
+```sql
+newdb=# SELECT rolname, oid FROM pg_roles;
+__OUTPUT__
+   rolname    |  oid
+--------------+-------
+ enterprisedb |    10
+ appuser      | 16671
+ newuser      | 16678
+(3 rows)
+```
+```sql
+newdb=# SELECT relname, oid FROM pg_class WHERE relname IN
+('dept','emp','appuser_tab');
+__OUTPUT__
+   relname   |  oid
+-------------+-------
+ appuser_tab | 16803
+ dept        | 16809
+ emp         | 16812
+(3 rows)
+```
+```sql
+newdb=# SELECT * FROM sqlprotect.edb_sql_protect;
+__OUTPUT__
+ dbid  | roleid | protect_relations | allow_utility_cmds | allow_tautology |
+ allow_empty_dml
+-------+--------+-------------------+--------------------+-----------------+--
+---------------
+ 16679 |  16671 | t                 | t                  | f               | f
+(1 row)
+```
+```sql
+newdb=# SELECT * FROM sqlprotect.edb_sql_protect_rel;
+__OUTPUT__
+ dbid  | roleid | relid
+-------+--------+-------
+ 16679 |  16671 | 16809
+ 16679 |  16671 | 16803
+(2 rows)
+```
+```sql
+newdb=# SELECT * FROM sqlprotect.edb_sql_protect_stats;
+__OUTPUT__
+ username | superusers | relations | commands | tautology | dml
+----------+------------+-----------+----------+-----------+-----
+ appuser  |          0 |         5 |        2 |         1 |   0
+(1 row)
+```
+```sql
+newedb=# \x
+Expanded display is on.
+nwedb=# SELECT * FROM sqlprotect.edb_sql_protect_queries;
+__OUTPUT__
+-[ RECORD 1 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:21:00 -04:00
+ query        | CREATE TABLE appuser_tab_2 (f1 INTEGER);
+-[ RECORD 2 ]+---------------------------------------------
+ username     | appuser
+ ip_address   |
+ port         |
+ machine_name |
+ date_time    | 20-JUN-14 13:22:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (2);
+-[ RECORD 3 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | CREATE TABLE appuser_tab_3 (f1 INTEGER);
+-[ RECORD 4 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | INSERT INTO appuser_tab_2 VALUES (1);
+-[ RECORD 5 ]+---------------------------------------------
+ username     | appuser
+ ip_address   | 192.168.2.6
+ port         | 50098
+ machine_name |
+ date_time    | 20-JUN-14 13:39:00 -04:00
+ query        | SELECT * FROM appuser_tab_2 WHERE 'x' = 'x';
+```
+
+  Note the following about the columns in tables `edb_sql_protect` and `edb_sql_protect_rel`:
+
+  -   **dbid.** Matches the value in the `oid` column from `pg_database` for `newdb`.
+  -   **roleid.** Matches the value in the `oid` column from `pg_roles` for `appuser`.
+
+  Also, in table `edb_sql_protect_rel`, the values in the `relid` column match the values in the `oid` column of `pg_class` for relations `dept` and `appuser_tab`.
+
+8.  Verify that the SQL/Protect configuration parameters are set as desired in the `postgresql.conf` file for the database server running the new database. Restart the database server or reload the configuration file as appropriate.
+
+You can now monitor the database using SQL/Protect.
diff --git a/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/index.mdx b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/index.mdx
new file mode 100644
index 00000000000..414aac2bf02
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/02_protecting_against_sql_injection_attacks/index.mdx
@@ -0,0 +1,27 @@
+---
+title: "Protecting against SQL injection attacks"
+indexCards: simple
+description: "With the SQL/Protect feature, EDB Postgres Advanced Server offers protection against SQL injection attacks by examining incoming queries for common SQL injection profiles."
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.27.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.072.html"
+---
+
+<div id="protecting_against_sql_injection_attacks" class="registered_link"></div>
+
+EDB Postgres Advanced Server provides protection against *SQL injection attacks*. A SQL injection attack is an attempt to compromise a database by running SQL statements whose results provide clues to the attacker as to the content, structure, or security of that database.
+
+Preventing a SQL injection attack is normally the responsibility of the application developer. The database administrator typically has little or no control over the potential threat. The difficulty for database administrators is that the application must have access to the data to function properly.
+
+SQL/Protect:
+
+- Allows a database administrator to protect a database from SQL injection attacks 
+- Provides a layer of security in addition to the normal database security policies by examining incoming queries for common SQL injection profiles
+- Gives the control back to the database administrator by alerting the administrator to potentially dangerous queries and by blocking these queries.
+
+<div class="toctree" maxdepth="3">
+
+sql_protect_overview configuring_sql_protect common_maintenance_operations backing_up_restoring_sql_protect
+
+</div>
diff --git a/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/edb_wrap_key_concepts.mdx b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/edb_wrap_key_concepts.mdx
new file mode 100644
index 00000000000..7bfde479819
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/edb_wrap_key_concepts.mdx
@@ -0,0 +1,17 @@
+---
+title: "EDB*Wrap key concepts"
+description: "Describes the benefits and basic operation of the EDB*Wrap feature"
+---
+
+The EDB\*Wrap program translates a plaintext file that contains SPL or PL/pgSQL source code into a file that contains the same code in a form that's nearly impossible to read. Once you have the obfuscated form of the code, you can send that code to the PostgreSQL server, and the server stores those programs in obfuscated form. While EDB\*Wrap does obscure code, table definitions are still exposed.
+
+Everything you wrap is stored in obfuscated form. If you wrap an entire package, the package body source, as well as the prototypes contained in the package header and the functions and procedures contained in the package body, are stored in obfuscated form.
+
+If you wrap a `CREATE PACKAGE` statement, you hide the package API from other developers. You might want to wrap the package body but not the package header so users can see the package prototypes and other public variables that are defined in the package body. To allow users to see the prototypes the package contains, use EDBWrap to obfuscate only the `CREATE PACKAGE BODY` statement in the `edbwrap` input file, omitting the `CREATE PACKAGE` statement. The package header source is stored as plaintext, while the package body source and package functions and procedures are obfuscated.
+
+![image](../../images/epas_tools_utility_edb_wrap.png)
+
+You can't unwrap or debug wrapped source code and programs. Reverse engineering is possible but very difficult.
+
+The entire source file is wrapped into one unit. Any `psql` meta-commands included in the wrapped file aren't recognized when the file is executed. Executing an obfuscated file that contains a psql meta-command causes a syntax error. `edbwrap` doesn't validate SQL source code. If the plaintext form contains a syntax error, `edbwrap` doesn't report it. Instead, the server reports an error and aborts the entire file when you try to execute the obfuscated form.
+
diff --git a/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/index.mdx b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/index.mdx
new file mode 100644
index 00000000000..a8586191575
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Protecting proprietary source code"
+description: "Describes how to use the EDB*Wrap utility to obfuscate proprietary source code and programs"
+indexCards: simple
+navigation:
+  - edb_wrap_key_concepts
+  - obfuscating_source_code
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.17.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.18.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.316.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.317.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.077.html"
+---
+
+<div id="edb_wrap" class="registered_link"></div>
+
+The EDB\*Wrap utility protects proprietary source code and programs like functions, stored procedures, triggers, and packages from unauthorized scrutiny. 
+
+<div id="using_edbwrap_to_obfuscate_source_code" class="registered_link"></div>
diff --git a/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/obfuscating_source_code.mdx b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/obfuscating_source_code.mdx
new file mode 100644
index 00000000000..1986ccb4a16
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/03_edb_wrap/obfuscating_source_code.mdx
@@ -0,0 +1,211 @@
+---
+title: "Obfuscating source code"
+description: "Describes how to use the EDB*Wrap utility protects proprietary source code and programs"
+redirects:
+  - /epas/latest/epas_compat_tools_guide/03_edb_wrap/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB\*Wrap is a command line utility that accepts a single input source file, obfuscates the contents, and returns a single output file. When you invoke the `edbwrap` utility, you must provide the name of the file that contains the source code to obfuscate. You can also specify the name of the file where `edbwrap` writes the obfuscated form of the code. 
+
+## Overview of the command-line styles
+
+`edbwrap` offers three different command-line styles. The first style is compatible with Oracle's `wrap` utility:
+
+```shell
+edbwrap iname=<input_file> [oname=<output_file>]
+```
+
+The `iname=input_file` argument specifies the name of the input file. If `input_file` doesn't contain an extension, `edbwrap` searches for a file named `input_file.sql`.
+
+The optional `oname=output_file` argument specifies the name of the output file. If `output_file` doesn't contain an extension, `edbwrap` appends `.plb` to the name.
+
+If you don't specify an output file name, `edbwrap` writes to a file whose name is derived from the input file name. `edbwrap` strips the suffix (typically `.sql`) from the input file name and adds `.plb`.
+
+`edbwrap` offers two other command-line styles:
+
+```shell
+edbwrap --iname <input_file> [--oname <output_file>]
+edbwrap -i <input_file> [-o <output_file>]
+```
+
+You can mix command-line styles. The rules for deriving input and output file names are the same regardless of the style you use.
+
+Once `edbwrap` produces a file that contains obfuscated code, you typically feed that file into the PostgreSQL server using a client application such as `edb-psql`. The server executes the obfuscated code line by line and stores the source code for SPL and PL/pgSQL programs in wrapped form.
+
+In summary, to obfuscate code with EDB\*Wrap, you:
+
+1.  Create the source code file.
+2.  Invoke EDB\*Wrap to obfuscate the code.
+3.  Import the file as if it were in plaintext form.
+
+## Creating the source code file 
+
+To use the EDB\*Wrap utility, create the source code for the `list_emp` procedure in plaintext form:
+
+```sql
+[bash] cat listemp.sql
+CREATE OR REPLACE PROCEDURE list_emp
+IS                                  
+     v_empno         NUMBER(4);      
+     v_ename         VARCHAR2(10);   
+     CURSOR emp_cur IS               
+         SELECT empno, ename FROM emp ORDER BY empno;
+BEGIN                                               
+     OPEN emp_cur;                                   
+     DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');         
+     DBMS_OUTPUT.PUT_LINE('-----    -------');       
+     LOOP                                            
+         FETCH emp_cur INTO v_empno, v_ename;        
+         EXIT WHEN emp_cur%NOTFOUND;                 
+         DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+     END LOOP;                                               
+     CLOSE emp_cur;                                          
+END;                                                        
+/                                                           
+```
+
+Import the `list_emp` procedure with a client application such as `edb-psql`:
+
+```sql
+[bash] edb-psql edb
+Welcome to edb-psql 8.4.3.2, the EnterpriseDB interactive terminal.
+Type:  \copyright for distribution terms
+       \h for help with SQL commands    
+       \? for help with edb-psql commands
+       \g or terminate with semicolon to execute query
+       \q to quit                                     
+
+edb=# \i listemp.sql
+CREATE PROCEDURE
+```
+
+View the plaintext source code stored in the server by examining the `pg_proc` system table:
+
+```sql
+edb=# SELECT prosrc FROM pg_proc WHERE proname = 'list_emp';
+__EDBwrapped__
+                             prosrc                            
+--------------------------------------------------------------                                                    
+
+     v_empno         NUMBER(4);                               
+      v_ename         VARCHAR2(10);                            
+      CURSOR emp_cur IS                                        
+          SELECT empno, ename FROM emp ORDER BY empno;         
+  BEGIN                                                        
+      OPEN emp_cur;                                            
+      DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');                  
+      DBMS_OUTPUT.PUT_LINE('-----    -------');                
+      LOOP                                                     
+          FETCH emp_cur INTO v_empno, v_ename;                 
+          EXIT WHEN emp_cur%NOTFOUND;                          
+          DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename); 
+      END LOOP;                                                
+      CLOSE emp_cur;                                           
+  END                                                          
+(1 row)                                                       
+
+edb=# quit
+```
+## Invoking EDB\*Wrap
+
+Ofuscate the plaintext file with EDB\*Wrap:
+
+```shell
+[bash] edbwrap -i listemp.sql                                        
+EDB*Wrap Utility: Release 8.4.3.2
+
+Copyright (c) 2004-2021 EnterpriseDB Corporation.  All Rights Reserved.
+
+Using encoding UTF8 for input
+Processing listemp.sql to listemp.plb
+
+Examining the contents of the output file (listemp.plb) file reveals
+that the code is obfuscated:
+
+[bash] cat listemp.plb 
+$__EDBwrapped__$                     
+UTF8                                 
+d+6DL30RVaGjYMIzkuoSzAQgtBw7MhYFuAFkBsfYfhdJ0rjwBv+bHr1FCyH6j9SgH
+movU+bYI+jR+hR2jbzq3sovHKEyZIp9y3/GckbQgualRhIlGpyWfE0dltDUpkYRLN
+/OUXmk0/P4H6EI98sAHevGDhOWI+58DjJ44qhZ+l5NNEVxbWDztpb/s5sdx4660qQ
+Ozx3/gh8VkqS2JbcxYMpjmrwVr6fAXfb68Ml9mW2Hl7fNtxcb5kjSzXvfWR2XYzJf
+KFNrEhbL1DTVlSEC5wE6lGlwhYvXOf22m1R2IFns0MtF9fwcnBWAs1YqjR00j6+fc
+er/f/efAFh4=
+$__EDBwrapped__$
+```
+
+The second line of the wrapped file contains an encoding name. In this case, the encoding is UTF8. When you obfuscate a file, `edbwrap` infers the encoding of the input file by examining the locale. For example, if you're running `edbwrap` while your locale is set to `en_US.utf8`, `edbwrap` assumes that the input file is encoded in UTF8. Be sure to examine the output file after running `edbwrap`. If the locale contained in the wrapped file doesn't match the encoding of the input file, change your locale and rewrap the input file.
+
+## Importing the obfuscated code to the PostgreSQL server
+
+You can import the obfuscated code to the PostgreSQL server using the same tools that work with plaintext code:
+
+```sql
+[bash] edb-psql edb
+Welcome to edb-psql 8.4.3.2, the EnterpriseDB interactive terminal.
+Type:  \copyright for distribution terms
+       \h for help with SQL commands
+       \? for help with edb-psql commands
+       \g or terminate with semicolon to execute query
+       \q to quit
+
+edb=# \i listemp.plb
+CREATE PROCEDURE
+```
+
+The pg_proc system table contains the obfuscated code:
+
+```text
+edb=# SELECT prosrc FROM pg_proc WHERE proname = 'list_emp';
+__OUTPUT__
+                                     prosrc
+----------------------------------------------------------------
+  $__EDBwrapped__$
+  UTF8
+  dw4B9Tz69J3WOsy0GgYJQa+G2sLZ3IOyxS8pDyuOTFuiYe/EXiEatwwG3h3tdJk
+  ea+AIp35dS/4idbN8wpegM3s994dQ3R97NgNHfvTQnO2vtd4wQtsQ/Zc4v4Lhfj
+  nlV+A4UpHI5oQEnXeAch2LcRD87hkU0uo1ESeQV8IrXaj9BsZr+ueROnwhGs/Ec
+  pva/tRV4m9RusFn0wyr38u4Z8w4dfnPW184Y3o6It4b3aH07WxTkWrMLmOZW1jJ
+  Nu6u4o+ezO64G9QKPazgehslv4JB9NQnuocActfDSPMY7R7anmgw
+  $__EDBwrapped__$
+(1 row)
+```
+
+Invoke the obfuscated code in the same way that you invoke the plaintext form:
+
+```sql
+edb=# exec list_emp;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+
+EDB-SPL Procedure successfully completed
+edb=# quit
+```
+
+When you use `pg_dump` to back up a database, wrapped programs remain obfuscated in the archive file.
+
+Be aware that audit logs produced by the Postgres server show wrapped programs in plaintext form. Source code is also displayed in plaintext in SQL error messages generated when the program executes.
+
+!!! Note
+    The bodies of the objects created by the following statements aren't stored in obfuscated form:
+
+     ```sql
+     CREATE [OR REPLACE] TYPE type_name AS OBJECT
+     CREATE [OR REPLACE] TYPE type_name UNDER type_name
+     CREATE [OR REPLACE] TYPE BODY type_name
+     ```
diff --git a/product_docs/docs/epas/16/epas_security_guide/03_virtual_private_database.mdx b/product_docs/docs/epas/16/epas_security_guide/03_virtual_private_database.mdx
new file mode 100644
index 00000000000..54dbe92c8df
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/03_virtual_private_database.mdx
@@ -0,0 +1,33 @@
+---
+navTitle: Controlling data access
+title: "Controlling data access (Virtual Private Database)"
+description: "Virtual Private Database offers fine-grained access control to data down to specific rows, as defined by the security policy"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.32.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.078.html"
+---
+
+<div id="virtual_private_database" class="registered_link"></div>
+
+Virtual Private Database is a type of *fine-grained access control* using security policies. Fine-grained access control means that you can control access to data down to specific rows as defined by the security policy.
+
+The rules that encode a *security policy* are defined in a *policy function*. A policy function is an SPL function with certain input parameters and return value. The security policy is the named association of the policy function to a particular database object, typically a table.
+
+In EDB Postgres Advanced Server, you can write the policy function in any language it supports, such as SQL and PL/pgSQL, in addition to SPL.
+
+!!! Note
+    The database objects currently supported by EDB Postgres Advanced Server Virtual Private Database are tables. You can apply policies to views or synonyms.
+
+The following are advantages of using Virtual Private Database:
+
+-   It provides a fine-grained level of security. Database-object-level privileges given by the `GRANT` command determine access privileges to the entire instance of a database object. Virtual Private Database provides access control for the individual rows of a database object instance.
+-   You can apply a different security policy depending on the type of SQL command (`INSERT`, `UPDATE`, `DELETE`, or `SELECT`).
+-   The security policy can vary dynamically for each applicable SQL command affecting the database object. Factors such as the session user of the application accessing the database object affect the security policy.
+-   Invoking the security policy is transparent to all applications that access the database object. You don't have to modify individual applications to apply the security policy.
+-   After you enable a security policy, no application (including new applications) can circumvent the security policy except by the system privilege described in the note that follows. Even superusers can't circumvent the security policy except by the noted system privilege.
+
+!!! Note
+    The only way you can circumvent security policies is if the user is granted `EXEMPT ACCESS POLICY` system privilege. Use extreme care when granting the `EXEMPT ACCESS POLICY` privilege. A user with this privilege is exempted from all policies in the database.
+
+The `DBMS_RLS` package provides procedures to create policies, remove policies, enable policies, and disable policies.
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/01_creating_a_password_function.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/01_creating_a_password_function.mdx
new file mode 100644
index 00000000000..77eb426db17
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/01_creating_a_password_function.mdx
@@ -0,0 +1,135 @@
+---
+title: "Creating a password function"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/01_creating_a_new_profile/01_creating_a_password_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_password_function" class="registered_link"></div>
+
+When specifying `PASSWORD_VERIFY_FUNCTION`, you can provide a customized function that specifies the security rules to apply when your users change their password. For example, you can specify rules that stipulate that the new password must be at least *n* characters long and can't contain a specific value.
+
+The password function has the following signature:
+
+```sql
+<function_name> (<user_name> VARCHAR2,
+                 <new_password> VARCHAR2,
+                 <old_password> VARCHAR2) RETURN boolean
+```
+
+Where:
+
+-   `user_name` is the name of the user.
+
+-   `new_password` is the new password.
+
+-   `old_password` is the user's previous password. If you reference this parameter in your function:
+
+    -  When a database superuser changes their password, the third parameter is always `NULL`.
+    -  When a user with the `CREATEROLE` attribute changes their password, the parameter passes the previous password if the statement includes the `REPLACE` clause. The `REPLACE` clause is optional syntax for a user with the `CREATEROLE` privilege.
+    -  When a user that isn't a database superuser and doesn't have the `CREATEROLE` attribute changes their password, the third parameter contains the previous password for the role.
+
+The function returns a Boolean value. If the function returns `true` and doesn't raise an exception, the password is accepted. If the function returns `false` or raises an exception, the password is rejected. If the function raises an exception, the specified error message is displayed to the user. If the function doesn't raise an exception but returns `false`, the following error message is displayed:
+
+`ERROR: password verification for the specified password failed`
+
+The function must be owned by a database superuser and reside in the `sys` schema.
+
+## Example
+
+This example creates a profile and a custom function. Then, the function is associated with the profile. 
+
+This `CREATE PROFILE` command creates a profile named `acctg_pwd_profile`:
+
+```sql
+CREATE PROFILE acctg_pwd_profile;
+```
+
+The following commands create a schema-qualified function named `verify_password`:
+
+```sql
+CREATE OR REPLACE FUNCTION sys.verify_password(user_name varchar2,
+new_password varchar2, old_password varchar2)
+RETURN boolean IMMUTABLE
+IS
+BEGIN
+  IF (length(new_password) < 5)
+  THEN
+    raise_application_error(-20001, 'too short');
+  END IF;
+
+  IF substring(new_password FROM old_password) IS NOT NULL
+  THEN
+    raise_application_error(-20002, 'includes old password');
+  END IF;
+
+  RETURN true;
+END;
+```
+
+The function first ensures that the password is at least five characters long and then compares the new password to the old password. If the new password contains fewer than five characters or contains the old password, the function raises an error.
+
+The following statement sets the ownership of the `verify_password` function to the `enterprisedb` database superuser:
+
+```sql
+ALTER FUNCTION verify_password(varchar2, varchar2, varchar2) OWNER TO
+enterprisedb;
+```
+
+Then, the `verify_password` function is associated with the profile:
+
+```sql
+ALTER PROFILE acctg_pwd_profile LIMIT PASSWORD_VERIFY_FUNCTION
+verify_password;
+```
+
+The following statements confirm that the function is working by first creating a test user (`alice`), and then attempting to associate invalid and valid passwords with her role:
+
+```sql
+CREATE ROLE alice WITH LOGIN PASSWORD 'temp_password' PROFILE
+acctg_pwd_profile;
+```
+
+Then, when `alice` connects to the database and attempts to change her password, she must adhere to the rules established by the profile function. A non-superuser without `CREATEROLE` must include the `REPLACE` clause when changing a password:
+
+```sql
+edb=> ALTER ROLE alice PASSWORD 'hey';
+ERROR:  missing REPLACE clause
+```
+
+The new password must be at least five characters long:
+
+```sql
+edb=> ALTER USER alice PASSWORD 'hey' REPLACE 'temp_password';
+ERROR:  EDB-20001: too short
+CONTEXT:  edb-spl function verify_password(character varying,character
+varying,character varying) line 5 at procedure/function invocation statement
+```
+
+If the new password is acceptable, the command completes without error:
+
+```sql
+edb=> ALTER USER alice PASSWORD 'hello' REPLACE 'temp_password';
+ALTER ROLE
+```
+
+If `alice` decides to change her password, the new password must not contain the old password:
+
+```sql
+edb=> ALTER USER alice PASSWORD 'helloworld' REPLACE 'hello';
+ERROR:  EDB-20002: includes old password
+CONTEXT:  edb-spl function verify_password(character varying,character
+varying,character varying) line 10 at procedure/function invocation statement
+```
+
+To remove the verify function, set `password_verify_function` to `NULL`:
+
+```sql
+ALTER PROFILE acctg_pwd_profile LIMIT password_verify_function NULL;
+```
+
+Then, all password constraints are lifted:
+
+```sql
+edb=# ALTER ROLE alice PASSWORD 'hey';
+ALTER ROLE
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/index.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/index.mdx
new file mode 100644
index 00000000000..109fdfd0b74
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/01_creating_a_new_profile/index.mdx
@@ -0,0 +1,124 @@
+---
+title: "Creating a new profile"
+description: "Describes how to create a new profile"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.030.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.027.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.030.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/01_creating_a_new_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_new_profile" class="registered_link"></div>
+
+Use the `CREATE PROFILE` command to create a new profile. The syntax is:
+
+```sql
+CREATE PROFILE <profile_name>
+       [LIMIT {<parameter value>} ... ];
+```
+
+Include the `LIMIT` clause and one or more space-delimited parameter/value pairs to specify the rules enforced by EDB Postgres Advanced Server.
+
+## Parameters
+
+-  `profile_name` specifies the name of the profile.
+
+-  `parameter` specifies the attribute limited by the profile.
+
+-  `value` specifies the parameter limit.
+
+EDB Postgres Advanced Server supports the vollowing `value` for each `parameter`:
+
+`FAILED_LOGIN_ATTEMPTS` specifies the number of failed login attempts that a user can make before the server locks them out of their account for the length of time specified by `PASSWORD_LOCK_TIME`. Supported values are:
+
+-   An `INTEGER` value greater than `0`.
+-   `DEFAULT` &mdash; The value of `FAILED_LOGIN_ATTEMPTS` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The connecting user can make an unlimited number of failed login attempts.
+
+`PASSWORD_LOCK_TIME` specifies the length of time that must pass before the server unlocks an account that was locked because of `FAILED_LOGIN_ATTEMPTS`. Supported values are:
+
+-   A `NUMERIC` value greater than or equal to 0. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LOCK_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The account is locked until a database superuser manually unlocks it.
+
+`PASSWORD_LIFE_TIME` specifies the number of days that the current password can be used before the user is prompted to provide a new password. Include the `PASSWORD_GRACE_TIME` clause when using the `PASSWORD_LIFE_TIME` clause to specify the number of days that pass after the password expires before connections by the role are rejected. If you don't specify `PASSWORD_GRACE_TIME`, the password expires on the day specified by the default value of `PASSWORD_GRACE_TIME`, and the user can't execute any command until they provide a new password. Supported values are:
+
+-   A `NUMERIC` value greater than or equal to 0. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LIFE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password doesn't have an expiration date.
+
+`PASSWORD_GRACE_TIME` specifies the length of the grace period after a password expires until the user is forced to change their password. When the grace period expires, a user can connect but can't execute any command until they update their expired password. Supported values are:
+
+-   A `NUMERIC` value greater than or equal to 0. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_GRACE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The grace period is infinite.
+
+`PASSWORD_REUSE_TIME` specifies the number of days a user must wait before reusing a password. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED`, there are no restrictions on password reuse. Supported values are:
+
+-   A `NUMERIC` value greater than or equal to 0. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_REUSE_MAX` specifies the number of password changes that must occur before a password can be reused. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED`, there are no restrictions on password reuse. Supported values are:
+
+-   An `INTEGER` value greater than or equal to 0.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_MAX` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_VERIFY_FUNCTION` specifies password complexity. Supported values are:
+
+-   The name of a PL/SQL function.
+-   `DEFAULT` &mdash; The value of `PASSWORD_VERIFY_FUNCTION` specified in the `DEFAULT` profile.
+-   `NULL`
+
+`PASSWORD_ALLOW_HASHED` specifies whether an encrypted password is allowed. If you specify `TRUE`, the system allows a user to change the password by specifying a hash-computed encrypted password on the client side. If you specify `FALSE`, then a password must be specified in a plain-text form to validate. Otherwise, an error is thrown if a server receives an encrypted password. Supported values are:
+
+-   A Boolean value `TRUE/ON/YES/1` or `FALSE/OFF/NO/0`.
+-   `DEFAULT` &mdash; The value of `PASSWORD_ALLOW_HASHED` specified in the `DEFAULT` profile.
+
+!!! Note
+    -   The `PASSWORD_ALLOW_HASHED` isn't an Oracle-compatible parameter.
+    -   Use `DROP PROFILE` command to remove the profile.
+
+## Examples
+
+The following command creates a profile named `acctg`. The profile specifies that if a user doesn't authenticate with the correct password in five attempts, the account is locked for one day:
+
+```sql
+CREATE PROFILE acctg LIMIT
+       FAILED_LOGIN_ATTEMPTS 5
+       PASSWORD_LOCK_TIME 1;
+```
+
+The following command creates a profile named `sales`. The profile specifies that a user must change their password every 90 days:
+
+```sql
+CREATE PROFILE sales LIMIT
+       PASSWORD_LIFE_TIME 90
+       PASSWORD_GRACE_TIME 3;
+```
+
+If the user doesn't change their password before the 90 days specified in the profile has passed, a warning appears at login. After a grace period of their days, their account can't invoke any commands until they change their password.
+
+The following command creates a profile named `accts`. The profile specifies that a user can't reuse a password within 180 days of the last use of the password and must change their password at least five times before reusing the password:
+
+```sql
+CREATE PROFILE accts LIMIT
+       PASSWORD_REUSE_TIME 180
+       PASSWORD_REUSE_MAX 5;
+```
+
+The following command creates a profile named `resources`. The profile calls a user-defined function named `password_rules` that verifies that the password provided meets their standards for complexity:
+
+```sql
+CREATE PROFILE resources LIMIT
+       PASSWORD_VERIFY_FUNCTION password_rules;
+```
+
+<div class="toctree" maxdepth="3">
+
+creating_a_password_function
+
+</div>
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/02_altering_a_profile.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/02_altering_a_profile.mdx
new file mode 100644
index 00000000000..50c9dc338f4
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/02_altering_a_profile.mdx
@@ -0,0 +1,50 @@
+---
+title: "Altering a profile"
+description: "Describes how to use the ALTER PROFILE command to modify a user-defined profile"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.031.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.031.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.028.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/02_altering_a_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="altering_a_profile" class="registered_link"></div>
+
+Use the `ALTER PROFILE` command to modify a user-defined profile. EDB Postgres Advanced Server supports two forms of the command:
+
+```sql
+ALTER PROFILE <profile_name> RENAME TO <new_name>;
+
+ALTER PROFILE <profile_name>
+      LIMIT {<parameter value>}[...];
+```
+
+Include the `LIMIT` clause and one or more space-delimited parameter/value pairs to specify the rules enforced by EDB Postgres Advanced Server. Or use `ALTER PROFILE...RENAME TO` to change the name of a profile.
+
+## Parameters
+
+-  `profile_name` specifies the name of the profile.
+-  `new_name` specifies the new name of the profile.
+-  `parameter` specifies the attribute limited by the profile.
+-  `value` specifies the parameter limit.
+
+See the table in [Creating a new profile](01_creating_a_new_profile/#creating_a_new_profile) for a complete list of accepted parameter/value pairs.
+
+## Examples
+
+The following example modifies a profile named `acctg_profile`:
+
+```sql
+ALTER PROFILE acctg_profile
+       LIMIT FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LOCK_TIME 1;
+```
+
+`acctg_profile` counts failed connection attempts when a login role attempts to connect to the server. The profile specifies that if a user doesn't authenticate with the correct password in three attempts, the account is locked for one day.
+
+The following example changes the name of `acctg_profile` to `payables_profile`:
+
+```sql
+ALTER PROFILE acctg_profile RENAME TO payables_profile;
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/03_dropping_a_profile.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/03_dropping_a_profile.mdx
new file mode 100644
index 00000000000..01d269adc97
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/03_dropping_a_profile.mdx
@@ -0,0 +1,47 @@
+---
+title: "Dropping a profile"
+description: "Describes how to use the DROP PROFILE command to drop a profile"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.032.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.029.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.032.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/03_dropping_a_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dropping_a_profile" class="registered_link"></div>
+
+Use the `DROP PROFILE` command to drop a profile. The syntax is:
+
+```sql
+DROP PROFILE [IF EXISTS] <profile_name> [CASCADE|RESTRICT];
+```
+
+Include the `IF EXISTS` clause to instruct the server not to throw an error if the specified profile doesn't exist. The server issues a notice if the profile doesn't exist.
+
+Include the optional `CASCADE` clause to reassign any users that are currently associated with the profile to the `default` profile and then drop the profile. Include the optional `RESTRICT` clause to instruct the server not to drop any profile that's associated with a role. This is the default behavior.
+
+## Parameters
+
+`profile_name`
+
+The name of the profile being dropped.
+
+## Examples
+
+This example drops a profile named `acctg_profile`:
+
+```sql
+DROP PROFILE acctg_profile CASCADE;
+```
+
+The command first reassociates any roles associated with the `acctg_profile` profile with the `default` profile and then drops the `acctg_profile` profile.
+
+The following example drops a profile named `acctg_profile`:
+
+```sql
+DROP PROFILE acctg_profile RESTRICT;
+```
+
+The `RESTRICT` clause in the command instructs the server not to drop `acctg_profile` if any roles are associated with the profile.
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/04_associating_a_profile_with_an_existing_role.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/04_associating_a_profile_with_an_existing_role.mdx
new file mode 100644
index 00000000000..6ff02ca4085
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/04_associating_a_profile_with_an_existing_role.mdx
@@ -0,0 +1,85 @@
+---
+title: "Associating a profile with an existing role"
+description: "Describes how to use commands to associate the profile with a role"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.033.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.033.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.030.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/04_associating_a_profile_with_an_existing_role/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="associating_a_profile_with_an_existing_role" class="registered_link"></div>
+
+After creating a profile, you can use the `ALTER USER... PROFILE` or `ALTER ROLE... PROFILE` command to associate the profile with a role. The command syntax related to profile management functionality is:
+
+```sql
+ALTER USER|ROLE <name> [[WITH] option[…]
+```
+
+where `option` can be the following compatible clauses:
+
+```sql
+   PROFILE <profile_name>
+| ACCOUNT {LOCK|UNLOCK}
+| PASSWORD EXPIRE [AT '<timestamp>']
+```
+
+Or, `option` can be the following noncompatible clauses:
+
+```sql
+| PASSWORD SET AT '<timestamp>'
+| LOCK TIME '<timestamp>'
+| STORE PRIOR PASSWORD {'<password>' '<timestamp>} [, ...]
+```
+
+For information about the administrative clauses of the `ALTER USER` or `ALTER ROLE` command that are supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+Only a database superuser can use the `ALTER USER|ROLE` clauses that enforce profile management. The clauses enforce the following behaviors:
+
+-   Include the `PROFILE` clause and a `profile_name` to associate a predefined profile with a role or to change the predefined profile associated with a user.
+
+-   Include the `ACCOUNT` clause and the `LOCK` or `UNLOCK` keyword to place the user account in a locked or unlocked state.
+
+-   Include the `LOCK TIME 'timestamp'` clause and a date/time value to lock the role at the specified time and unlock the role at the time indicated by the `PASSWORD_LOCK_TIME` parameter of the profile assigned to this role. If `LOCK TIME` is used with the `ACCOUNT LOCK` clause, only a database superuser can unlock the role with the `ACCOUNT UNLOCK` clause.
+
+-   Include the `PASSWORD EXPIRE` clause with the `AT 'timestamp'` keywords to specify a date/time when the password associated with the role expires. If you omit the `AT 'timestamp'` keywords, the password expires immediately.
+
+-   Include the `PASSWORD SET AT 'timestamp'` keywords to set the password modification date to the time specified.
+
+-   Include the `STORE PRIOR PASSWORD {'password' 'timestamp} [, ...]` clause to modify the password history, adding the new password and the time the password was set.
+
+Each login role can have only one profile. To discover the profile that's currently associated with a login role, query the `profile` column of the `DBA_USERS` view.
+
+## Parameters
+
+`name`
+
+  The name of the role with which to associate the specified profile.
+
+`password`
+
+  The password associated with the role.
+
+`profile_name`
+
+  The name of the profile to associate with the role.
+
+`timestamp`
+
+  The date and time at which to enforce the clause. When specifying a value for `timestamp`, enclose the value in single quotes.
+
+## Examples
+
+This command uses the `ALTER USER... PROFILE` command to associate a profile named `acctg` with a user named `john`:
+
+```sql
+ALTER USER john PROFILE acctg_profile;
+```
+
+The following command uses the `ALTER ROLE... PROFILE` command to associate a profile named `acctg` with a user named `john`:
+
+```sql
+ALTER ROLE john PROFILE acctg_profile;
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/05_unlocking_a_locked_account.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/05_unlocking_a_locked_account.mdx
new file mode 100644
index 00000000000..4ff718019b9
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/05_unlocking_a_locked_account.mdx
@@ -0,0 +1,72 @@
+---
+title: "Unlocking a locked account"
+description: "Describes how to use specific clauses in the ALTER USER|ROLE command to lock or unlock a user role"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.034.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.034.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.031.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/05_unlocking_a_locked_account/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="unlocking_a_locked_account" class="registered_link"></div>
+
+A database superuser can use clauses of the `ALTER USER|ROLE...` command to lock or unlock a role. The syntax is:
+
+```sql
+ALTER USER|ROLE <name>
+       ACCOUNT {LOCK|UNLOCK}
+       LOCK TIME '<timestamp>'
+```
+
+Include the `ACCOUNT LOCK` clause to lock a role immediately. When locked, a role’s `LOGIN` functionality is disabled. When you specify the `ACCOUNT LOCK` clause without the `LOCK TIME` clause, the state of the role doesn't change until a superuser uses the `ACCOUNT UNLOCK` clause to unlock the role.
+
+Use the `ACCOUNT UNLOCK` clause to unlock a role.
+
+Use the `LOCK TIME 'timestamp'` clause to lock the account at the time specified by the given timestamp for the length of time specified by the `PASSWORD_LOCK_TIME` parameter of the profile associated with this role.
+
+Combine the `LOCK TIME 'timestamp'` clause and the `ACCOUNT LOCK` clause to lock an account at a specified time until the account is unlocked by a superuser invoking the `ACCOUNT UNLOCK` clause.
+
+## Parameters
+
+`name`
+
+  The name of the role that's being locked or unlocked.
+
+`timestamp`
+
+  The date and time when the role is locked. When specifying a value for `timestamp`, enclose the value in single quotes.
+
+!!! Note
+    This command (available only in EDB Postgres Advanced Server) is implemented to support Oracle-styled profile management.
+
+## Examples
+
+This example uses the `ACCOUNT LOCK` clause to lock the role named `john`. The account remains locked until the account is unlocked with the `ACCOUNT UNLOCK` clause.
+
+```sql
+ALTER ROLE john ACCOUNT LOCK;
+```
+
+This example uses the `ACCOUNT UNLOCK` clause to unlock the role named `john`:
+
+```sql
+ALTER USER john ACCOUNT UNLOCK;
+```
+
+This example uses the `LOCK TIME 'timestamp'` clause to lock the role named `john` on September 4, 2015:
+
+```sql
+ALTER ROLE john LOCK TIME ‘September 4 12:00:00 2015’;
+```
+
+The role remains locked for the length of time specified by the `PASSWORD_LOCK_TIME` parameter.
+
+This example combines the `LOCK TIME 'timestamp'` clause and the `ACCOUNT LOCK` clause to lock the role named `john` on September 4, 2015:
+
+```sql
+ALTER ROLE john LOCK TIME ‘September 4 12:00:00 2015’ ACCOUNT LOCK;
+```
+
+The role remains locked until a database superuser uses the `ACCOUNT UNLOCK` command to unlock the role.
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/06_creating_a_new_role_associated_with_a_profile.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/06_creating_a_new_role_associated_with_a_profile.mdx
new file mode 100644
index 00000000000..aaf695f3d6e
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/06_creating_a_new_role_associated_with_a_profile.mdx
@@ -0,0 +1,83 @@
+---
+title: "Creating a new role associated with a profile"
+description: "Describes how to assign a profile to a new role"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.035.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.035.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.032.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/06_creating_a_new_role_associated_with_a_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_new_role_associated_with_a_profile" class="registered_link"></div>
+
+A database superuser can use clauses of the `CREATE USER|ROLE` command to assign a named profile to a role when creating the role or to specify profile management details for a role. The command syntax related to profile management functionality is:
+
+```sql
+CREATE USER|ROLE <name> [[WITH] <option> […]]
+```
+
+where `option` can be the following compatible clauses:
+
+```sql
+   PROFILE <profile_name>
+|  ACCOUNT {LOCK|UNLOCK}
+|  PASSWORD EXPIRE [AT '<timestamp>']
+```
+
+Or, `option` can be the following noncompatible clauses:
+
+```sql
+|  LOCK TIME '<timestamp>'
+```
+
+For information about the administrative clauses of the `CREATE USER` or `CREATE ROLE` command that are supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+`CREATE ROLE|USER... PROFILE` adds a role with an associated profile to an EDB Postgres Advanced Server database cluster.
+
+Roles created with the `CREATE USER` command are by default login roles. Roles created with the `CREATE ROLE` command are by default not login roles. To create a login account with the `CREATE ROLE` command, you must include the `LOGIN` keyword.
+
+Only a database superuser can use the `CREATE USER|ROLE` clauses that enforce profile management. These clauses enforce the following behaviors:
+
+-   Include the `PROFILE` clause and a `profile_name` to associate a predefined profile with a role or to change the predefined profile associated with a user.
+
+-   Include the `ACCOUNT` clause and the `LOCK` or `UNLOCK` keyword to place the user account in a locked or unlocked state.
+
+-   Include the `LOCK TIME 'timestamp'` clause and a date/time value to lock the role at the specified time and unlock the role at the time indicated by the `PASSWORD_LOCK_TIME` parameter of the profile assigned to this role. If `LOCK TIME` is used with the `ACCOUNT LOCK` clause, only a database superuser can unlock the role with the `ACCOUNT UNLOCK` clause.
+
+-   Include the `PASSWORD EXPIRE` clause with the optional `AT 'timestamp'` keywords to specify a date/time when the password associated with the role expires. If you omit the `AT 'timestamp'` keywords, the password expires immediately.
+
+Each login role can have only one profile. To discover the profile that's currently associated with a login role, query the `profile` column of the `DBA_USERS` view.
+
+## Parameters
+
+`name`
+
+  The name of the role.
+
+`profile_name`
+
+  The name of the profile associated with the role.
+
+`timestamp`
+
+  The date and time when the clause is enforced. When specifying a value for `timestamp`, enclose the value in single quotes.
+
+## Examples
+
+This example uses `CREATE USER` to create a login role named `john` associated with the `acctg_profile` profile:
+
+```sql
+CREATE USER john PROFILE acctg_profile IDENTIFIED BY “1safepwd”;
+```
+
+`john` can log in to the server using the password `1safepwd`.
+
+This example uses `CREATE ROLE` to create a login role named `john` associated with the `acctg_profile` profile:
+
+```sql
+CREATE ROLE john PROFILE acctg_profile LOGIN PASSWORD “1safepwd”;
+```
+
+`john` can log in to the server using the password `1safepwd`.
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/07_backing_up_profile_management_functions.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/07_backing_up_profile_management_functions.mdx
new file mode 100644
index 00000000000..be5d04b7994
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/07_backing_up_profile_management_functions.mdx
@@ -0,0 +1,25 @@
+---
+title: "Backing up profile management functions"
+description: "Describes how to use the profile backup functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.036.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.036.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.033.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/07_backing_up_profile_management_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="backing_up_profile_management_functions" class="registered_link"></div>
+
+A profile can include a `PASSWORD_VERIFY_FUNCTION` clause that refers to a user-defined function that specifies the behavior enforced by EDB Postgres Advanced Server. Profiles are global objects. They are shared by all of the databases in a cluster. While profiles are global objects, user-defined functions are database objects.
+
+Invoking `pg_dumpall` with the `–g` or `–r` option creates a script that re-creates the definition of any existing profiles but that doesn't re-create the user-defined functions that are referred to by the `PASSWORD_VERIFY_FUNCTION` clause. Use the `pg_dump` utility to explicitly dump, and later restore, the database in which those functions reside.
+
+The script created by `pg_dump` contains a command that includes the clause and function name to associate the restored function with the profile with which it was previously associated:
+
+```sql
+ALTER PROFILE… LIMIT PASSWORD_VERIFY_FUNCTION <function_name>
+```
+
+If the `PASSWORD_VERIFY_FUNCTION` clause is set to `DEFAULT` or `NULL`, the behavior is replicated by the script generated by the `pg_dumpall –g` or `pg_dumpall –r` command.
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/index.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/index.mdx
new file mode 100644
index 00000000000..081a1b28955
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/index.mdx
@@ -0,0 +1,31 @@
+---
+title: "Managing user profiles"
+navTitle: Managing user profiles
+indexCards: simple
+description: "How to create and manage profiles that specify database access for users"
+navigation:
+  - profile_overview
+  - 01_creating_a_new_profile
+  - 02_altering_a_profile
+  - 03_dropping_a_profile
+  - 04_associating_a_profile_with_an_existing_role
+  - 05_unlocking_a_locked_account
+  - 06_creating_a_new_role_associated_with_a_profile
+  - 07_backing_up_profile_management_functions
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.029.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.029.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/04_profile_management/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="profile_management" class="registered_link"></div>
+
+EDB Postgres Advanced Server allows a database superuser to create named *profiles*. The following sections describe how to manage profiles with EDB Postgres Advanced Server .
+
+<div class="toctree" maxdepth="3">
+
+creating_a_new_profile altering_a_profile dropping_a_profile associating_a_profile_with_an_existing_role unlocking_a_locked_account creating_a_new_role_associated_with_a_profile backing_up_profile_management_functions
+
+</div>
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_profile_management/profile_overview.mdx b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/profile_overview.mdx
new file mode 100644
index 00000000000..c400f84cabc
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_profile_management/profile_overview.mdx
@@ -0,0 +1,33 @@
+---
+title: "Profile management key concepts"
+description: "Provides an overview of how to manage user profiles"
+---
+
+A profile is a set of password attributes that allow you to easily manage a group of roles that share comparable authentication requirements. Each profile defines rules for password management that augment `password` and `md5` authentication. The rules in a profile can:
+
+-   Count failed login attempts
+-   Lock an account due to excessive failed login attempts
+-   Mark a password for expiration
+-   Define a grace period after a password expiration
+-   Define rules for password complexity
+-   Define rules that limit password reuse
+
+If the password requirements change, you can modify the profile to apply the new requirements to each user associated with that profile.
+
+After creating the profile, you can associate the profile with one or more users. When a user connects to the server, the server enforces the profile that's associated with their login role. Profiles are shared by all databases in a cluster, but each cluster can have multiple profiles. A single user with access to multiple databases uses the same profile when connecting to each database in the cluster.
+
+EDB Postgres Advanced Server creates a profile named `default` that's associated with a new role when the role is created unless you specify an alternative profile. If you upgrade to EDB Postgres Advanced Server from a previous server version, existing roles are automatically assigned to the `default` profile. You can't delete the `default` profile.
+
+The `default` profile specifies the following attributes:
+
+| `FAILED_LOGIN_ATTEMPTS`    | `UNLIMITED` | 
+| -------------------------- | ----------- | 
+| `PASSWORD_LOCK_TIME`       | `UNLIMITED` | 
+| `PASSWORD_LIFE_TIME`       | `UNLIMITED` | 
+| `PASSWORD_GRACE_TIME`      | `UNLIMITED` | 
+| `PASSWORD_REUSE_TIME`      | `UNLIMITED` | 
+| `PASSWORD_REUSE_MAX`       | `UNLIMITED` | 
+| `PASSWORD_VERIFY_FUNCTION` | `NULL`      | 
+| `PASSWORD_ALLOW_HASHED`    | `TRUE`      | 
+
+A database superuser can use the `ALTER PROFILE` command to modify the values specified by the `default` profile. For more information about modifying a profile, see [Altering a profile](02_altering_a_profile/#altering_a_profile).
diff --git a/product_docs/docs/epas/16/epas_security_guide/04_sslutils.mdx b/product_docs/docs/epas/16/epas_security_guide/04_sslutils.mdx
new file mode 100644
index 00000000000..095b96135e9
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/04_sslutils.mdx
@@ -0,0 +1,109 @@
+---
+title: "Generating SSL certificates"
+description: "The sslutils Postgres extension provides SSL certificate generation functions to EDB Postgres Advanced Server for use by the EDB Postgres Enterprise Manager server"
+---
+
+<div id="sslutils" class="registered_link"></div>
+
+`sslutils` is a Postgres extension that provides SSL certificate generation functions to EDB Postgres Advanced Server for use by the EDB Postgres Enterprise Manager server. 
+
+## Installing the extension
+
+You install `sslutils` by using the `edb-as<xx>-server-sslutils` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number.
+
+Each parameter in the function’s parameter list is described by `parameter n`, where `n` refers to the `nth` ordinal position (for example, first, second, or third) in the function’s parameter list.
+
+## openssl_rsa_generate_key
+
+The `openssl_rsa_generate_key` function generates an RSA private key. The function signature is:
+
+```sql
+openssl_rsa_generate_key(<integer>) RETURNS <text>
+```
+
+When invoking the function, pass the number of bits as an integer value. The function returns the generated key.
+
+## openssl_rsa_key_to_csr
+
+The `openssl_rsa_key_to_csr` function generates a certificate signing request (CSR). The signature is:
+
+```sql
+openssl_rsa_key_to_csr(<text>, <text>, <text>, <text>, <text>, <text>,
+<text>) RETURNS <text>
+```
+
+The function generates and returns the certificate signing request.
+
+### Parameters
+
+`parameter 1`
+
+ The name of the RSA key file.
+
+`parameter 2`
+
+ The common name (e.g., `agentN`) of the agent to use the signing request.
+
+`parameter 3`
+
+ The name of the country where the server resides.
+
+`parameter 4`
+
+ The name of the state where the server resides.
+
+`parameter 5`
+
+ The location (city) in the state where the server resides.
+
+`parameter 6`
+
+ The name of the organization unit requesting the certificate.
+
+`parameter 7`
+
+ The email address of the user requesting the certificate.
+
+## openssl_csr_to_crt
+
+The `openssl_csr_to_crt` function generates a self-signed certificate or a certificate authority certificate. The signature is:
+
+```sql
+openssl_csr_to_crt(<text>, <text>, <text>) RETURNS <text>
+```
+
+The function returns the self-signed certificate or certificate authority certificate.
+
+### Parameters
+
+`parameter 1`
+
+ The name of the certificate signing the request.
+
+`parameter 2`
+
+ The path to the certificate authority certificate, or `NULL` if generating a certificate authority certificate.
+
+`parameter 3`
+
+ The path to the certificate authority’s private key or, if argument `2` is `NULL`, the path to a private key.
+
+## openssl_rsa_generate_crl
+
+The `openssl_rsa_generate_crl` function generates a default certificate revocation list. The signature is:
+
+```sql
+openssl_rsa_generate_crl(<text>, <text>) RETURNS <text>
+```
+
+The function returns the certificate revocation list.
+
+### Parameters
+
+`parameter 1`
+
+ The path to the certificate authority certificate.
+
+`parameter 2`
+
+ The path to the certificate authority private key.
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/creating_a_data_redaction_policy.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/creating_a_data_redaction_policy.mdx
new file mode 100644
index 00000000000..03b3f1656fb
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/creating_a_data_redaction_policy.mdx
@@ -0,0 +1,200 @@
+---
+title: "Creating a data redaction policy"
+description: "How to use the CREATE REDACTION POLICY command to define a new data redaction policy for a table"
+---
+
+The `CREATE REDACTION POLICY` command defines a new data redaction policy for a table.
+
+## Synopsis
+
+```sql
+CREATE REDACTION POLICY <name> ON <table_name>
+  [ FOR ( <expression> ) ]
+  [ ADD [ COLUMN ] <column_name> USING <funcname_clause>
+    [ WITH OPTIONS ( [ <redaction_option> ]
+      [, <redaction_option> ] )
+    ]
+  ] [, ...]
+```
+
+Where `redaction_option` is:
+
+```sql
+{ SCOPE <scope_value> |
+  EXCEPTION <exception_value> }
+```
+
+## Description
+
+The `CREATE REDACTION POLICY` command defines a new column-level security policy for a table by redacting column data using a redaction function. A newly created data redaction policy is enabled by default. You can disable the policy using `ALTER REDACTION POLICY ... DISABLE`.
+
+`FOR ( expression )`
+
+ This form adds a redaction policy expression.
+
+`ADD [ COLUMN ]`
+
+ This optional form adds a column of the table to the data redaction policy. The `USING` clause specifies a redaction function expression. You can use multiple `ADD [ COLUMN ]` forms if you want to add multiple columns of the table to the data redaction policy being created. The optional `WITH OPTIONS ( ... )` clause specifies a scope or an exception to the data redaction policy to apply. If you don't specify the scope or exception, the default value for scope is `query` and for exception is `none`.
+
+## Parameters
+
+`name`
+
+ The name of the data redaction policy to create. This must be distinct from the name of any other existing data redaction policy for the table.
+
+`table_name`
+
+ The optionally schema-qualified name of the table the data redaction policy applies to.
+
+`expression`
+
+ The data redaction policy expression. No redaction is applied if this expression evaluates to false.
+
+`column_name`
+
+ Name of the existing column of the table on which the data redaction policy is being created.
+
+`funcname_clause`
+
+ The data redaction function that decides how to compute the redacted column value. Return type of the redaction function must be the same as the column type on which the data redaction policy is being added.
+
+`scope_value`
+
+ The scope identifies the query part to apply redaction for the column. Scope value can be `query`, `top_tlist`, or `top_tlist_or_error`. If the scope is `query`, then the redaction is applied on the column regardless of where it appears in the query. If the scope is `top_tlist`, then the redaction is applied on the column only when it appears in the query’s top target list. If the scope is `top_tlist_or_error`, the behavior is the same as the `top_tlist` but throws an errors when the column appears anywhere else in the query.
+
+`exception_value`
+
+ The exception identifies the query part where redaction is exempted. Exception value can be `none`, `equal`, or `leakproof`. If exception is `none`, then there's no exemption. If exception is `equal`, then the column isn't redacted when used in an equality test. If exception is `leakproof`, the column isn't redacted when a leakproof function is applied to it.
+
+## Notes
+
+You must be the owner of a table to create or change data redaction policies for it.
+
+The superuser and the table owner are exempt from the data redaction policy.
+
+## Examples
+
+This example shows how you can use this feature in production environments. 
+
+Create the components for a data redaction policy on the `employees` table:
+
+```sql
+CREATE TABLE employees (
+ id          integer GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
+ name        varchar(40) NOT NULL,
+ ssn         varchar(11) NOT NULL,
+ phone       varchar(10),
+ birthday    date,
+ salary      money,
+ email       varchar(100)
+);
+
+-- Insert some data
+INSERT INTO employees (name, ssn, phone, birthday, salary, email)
+VALUES
+( 'Sally Sample', '020-78-9345', '5081234567', '1961-02-02', 51234.34,
+'sally.sample@enterprisedb.com'),
+( 'Jane Doe', '123-33-9345', '6171234567', '1963-02-14', 62500.00,
+'jane.doe@gmail.com'),
+( 'Bill Foo', '123-89-9345', '9781234567','1963-02-14', 45350,
+'william.foe@hotmail.com');
+
+-- Create a user hr who can see all the data in employees
+CREATE USER hr;
+-- Create a normal user
+CREATE USER alice;
+GRANT ALL ON employees TO hr, alice;
+
+-- Create redaction function in which actual redaction logic resides
+CREATE OR REPLACE FUNCTION redact_ssn (ssn varchar(11)) RETURN varchar(11) IS
+BEGIN
+   /* replaces 020-12-9876 with xxx-xx-9876 */
+   return overlay (ssn placing 'xxx-xx' from 1) ;
+END;
+
+CREATE OR REPLACE FUNCTION redact_salary () RETURN money IS BEGIN return
+0::money;
+END;
+```
+
+Create a data redaction policy on `employees` to redact column `ssn` and `salary` with default scope and exception. Column `ssn` must be accessible in equality condition. The redaction policy is exempt for the `hr` user.
+
+```sql
+CREATE REDACTION POLICY redact_policy_personal_info ON employees FOR (session_user != 'hr')
+ADD COLUMN ssn USING redact_ssn(ssn) WITH OPTIONS (SCOPE query, EXCEPTION equal),
+ADD COLUMN salary USING redact_salary();
+```
+
+The visible data for the `hr` user is:
+
+```sql
+-- hr can view all columns data
+edb=# \c edb hr
+edb=> SELECT * FROM employees;
+__OUTPUT__
+ id | name         | ssn         | phone      | birthday           |
+ salary     | email
+----+--------------+-------------+------------+--------------------+---
+--+---------------------
+  1 | Sally Sample | 020-78-9345 | 5081234567 | 02-FEB-61 00:00:00 |
+  $51,234.34 | sally.sample@enterprisedb.com
+  2 | Jane Doe     | 123-33-9345 | 6171234567 | 14-FEB-63 00:00:00 |
+  $62,500.00 | jane.doe@gmail.com
+  3 | Bill Foo     | 123-89-9345 | 9781234567 | 14-FEB-63 00:00:00 |
+  $45,350.00 | william.foe@hotmail.com
+(3 rows)
+```
+
+The visible data for the normal user `alice` is:
+
+```sql
+-- Normal user cannot see salary and ssn number.
+edb=> \c edb alice
+edb=> SELECT * FROM employees;
+__OUTPUT__
+id  | name         | ssn         | phone      | birthday           | salary |
+email
+----+--------------+-------------+------------+--------------------+--------+-
+------------------------------
+  1 | Sally Sample | xxx-xx-9345 | 5081234567 | 02-FEB-61 00:00:00 |  $0.00 |
+  sally.sample@enterprisedb.com
+  2 | Jane Doe     | xxx-xx-9345 | 6171234567 | 14-FEB-63 00:00:00 |  $0.00 |
+  jane.doe@gmail.com
+  3 | Bill Foo     | xxx-xx-9345 | 9781234567 | 14-FEB-63 00:00:00 |  $0.00 |
+  william.foe@hotmail.com
+(3 rows)
+```
+
+But `ssn` data is accessible when used for equality check due to the `exception_value` setting:
+
+```sql
+-- Get ssn number starting from 123
+edb=> SELECT * FROM employees WHERE substring(ssn from 0 for 4) = '123';
+__OUTPUT__
+ id | name     | ssn         | phone      | birthday           | salary |
+ email
+----+----------+-------------+------------+--------------------+--------+-----
+--------------------
+  2 | Jane Doe | xxx-xx-9345 | 6171234567 | 14-FEB-63 00:00:00 |  $0.00 |
+  jane.doe@gmail.com
+  3 | Bill Foo | xxx-xx-9345 | 9781234567 | 14-FEB-63 00:00:00 |  $0.00 |
+  william.foe@hotmail.com
+(2 rows)
+```
+
+## Caveats
+
+-  The data redaction policies created on inheritance hierarchies aren't cascaded. For example, if the data redaction policy is created for a parent, it isn't applied to the child table that inherits it, and vice versa. A user with access to these child tables can see the non-redacted data. For information about inheritance hierarchies, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/ddl-inherit.html).
+
+-  If the superuser or the table owner created any materialized view on the table and provided the access rights `GRANT SELECT` on the table and the materialized view to any non-superuser, then the non-superuser can access the non-redacted data through the materialized view.
+
+-  The objects accessed in the redaction function body must be schema qualified. Otherwise `pg_dump` might fail.
+
+## Compatibility
+
+`CREATE REDACTION POLICY` is an EDB extension.
+
+## See also
+
+[`ALTER REDACTION POLICY`](modifying_a_data_redaction_policy), [`DROP REDACTION POLICY`](removing_a_data_redaction_policy)
+
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_key_concepts.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_key_concepts.mdx
new file mode 100644
index 00000000000..813064e46ef
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_key_concepts.mdx
@@ -0,0 +1,36 @@
+---
+title: "Data redaction key concepts"
+description: "Describes the benefits and basic operation of the data redaction feature"
+---
+
+<div id="data_redaction" class="registered_link"></div>
+
+The EDB Postgres Advanced Server *Data redaction* feature limits sensitive data exposure by dynamically changing data as it's displayed for certain users.
+
+For example, a social security number (SSN) is stored as `021-23-9567`. Privileged users can see the full SSN, while other users see only the last four digits: `xxx-xx-9567`.
+
+You implement data redaction by defining a function for each field to which to apply redaction. The function returns the value to display to the users subject to the data redaction.
+
+For example, for the SSN field, the redaction function returns `xxx-xx-9567` for an input SSN of `021-23-9567`.
+
+For a salary field, a redaction function always returns `$0.00`, regardless of the input salary value.
+
+These functions are then incorporated into a redaction policy by using the `CREATE REDACTION POLICY` command. In addition to other options, this command specifies:
+
+-  The table on which the policy applies 
+-  The table columns affected by the specified redaction functions 
+-  Expressions to determine the affect session users
+
+The `edb_data_redaction` parameter in the `postgresql.conf` file then determines whether to apply data redaction.
+
+By default, the parameter is enabled, so the redaction policy is in effect. The following occurs:
+
+-   Superusers and the table owner bypass data redaction and see the original data.
+-   All other users have the redaction policy applied and see the reformatted data.
+
+If the parameter is disabled by having it set to `FALSE` during the session, then the following occurs:
+
+-   Superusers and the table owner bypass data redaction and see the original data.
+-   All other users get an error.
+
+You can change a redaction policy using the `ALTER REDACTION POLICY` command. Or, you can eliminate it using the `DROP REDACTION POLICY` command.
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_system_catalogs.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_system_catalogs.mdx
new file mode 100644
index 00000000000..e3ccc9b047d
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/data_redaction_system_catalogs.mdx
@@ -0,0 +1,39 @@
+---
+title: "Data redaction system catalogs"
+description: "Describes the system catalogs related to the data redaction feature"
+---
+
+System catalogs store the redaction policy information.
+
+## edb_redaction_column
+
+The `edb_redaction_column` system catalog stores information about the data redaction policy attached to the columns of a table.
+
+| Column        | Type           | References                 | Description                                                                 |
+| ------------- | -------------- | -------------------------- | --------------------------------------------------------------------------- |
+| `oid`         | `oid`          |                            | Row identifier (hidden attribute, must be explicitly selected)              |
+| `rdpolicyid`  | `oid`          | `edb_redaction_policy.oid` | The data redaction policy that applies to the described column                   |
+| `rdrelid`     | `oid`          | `pg_class.oid`             | The table that the described column belongs to                              |
+| `rdattnum`    | `int2`         | `pg_attribute.attnum`      | The number of the described column                                          |
+| `rdscope`     | `int2`         |                            | The redaction scope: `1` = query, `2` = top_tlist, `4` = top_tlist_or_error |
+| `rdexception` | `int2`         |                            | The redaction exception: `8` = none, `16` = equal, `32` = leakproof         |
+| `rdfuncexpr`  | `pg_node_tree` |                            | Data redaction function expression                                          |
+
+!!! Note
+    The described column is redacted if the redaction policy `edb_redaction_column.rdpolicyid` on the table is enabled and the redaction policy expression `edb_redaction_policy.rdexpr` evaluates to `true`.
+
+## edb_redaction_policy
+
+The catalog `edb_redaction_policy` stores information about the redaction policies for tables.
+
+| Column     | Type           | References     | Description                                                    |
+| ---------- | -------------- | -------------- | -------------------------------------------------------------- |
+| `oid`      | `oid`          |                | Row identifier (hidden attribute, must be explicitly selected) |
+| `rdname`   | `name`         |                | The name of the data redaction policy                          |
+| `rdrelid`  | `oid`          | `pg_class.oid` | The table to which the data redaction policy applies           |
+| `rdenable` | `boolean`      |                | Is the data redaction policy enabled?                          |
+| `rdexpr`   | `pg_node_tree` |                | The data redaction policy expression                           |
+
+!!! Note
+    The data redaction policy applies for the table if it's enabled and the expression ever evaluated true.
+
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/index.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/index.mdx
new file mode 100644
index 00000000000..bba0f1a69f5
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Redacting data"
+description: "Use the EDB Postgres Advanced Server data redaction feature to limit exposure to sensitive data by dynamically changing the data as it is displayed for certain users"
+indexCards: simple
+navigation:
+- data_redaction_key_concepts
+- creating_a_data_redaction_policy
+- modifying_a_data_redaction_policy
+- removing_a_data_redaction_policy
+- data_redaction_system_catalogs
+---
+
+EDB Postgres Advanced Server includes features to help you to maintain, secure, and operate EDB Postgres Advanced Server databases. The DB Postgres Advanced Server *Data redaction* feature limits sensitive data exposure by dynamically changing data as it's displayed for certain users.
+
+
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/modifying_a_data_redaction_policy.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/modifying_a_data_redaction_policy.mdx
new file mode 100644
index 00000000000..45d45b3013c
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/modifying_a_data_redaction_policy.mdx
@@ -0,0 +1,130 @@
+---
+title: "Modifying a data redaction policy"
+description: "How to use the ALTER REDACTION POLICY command to change the definition of a data redaction policy for a table"
+---
+
+The `ALTER REDACTION POLICY` command changes the definition of data redaction policy for a table.
+
+## Synopsis
+
+```sql
+ALTER REDACTION POLICY <name> ON <table_name> RENAME TO <new_name>
+
+ALTER REDACTION POLICY <name> ON <table_name> FOR ( <expression> )
+
+ALTER REDACTION POLICY <name> ON <table_name> { ENABLE | DISABLE}
+
+ALTER REDACTION POLICY <name> ON <table_name>
+  ADD [ COLUMN ] <column_name> USING <funcname_clause>
+    [ WITH OPTIONS ( [ <redaction_option> ]
+      [, <redaction_option> ] )
+    ]
+
+ALTER REDACTION POLICY <name> ON <table_name>
+  MODIFY [ COLUMN ] <column_name>
+  {
+    [ USING <funcname_clause> ]
+  |
+    [ WITH OPTIONS ( [ <redaction_option> ]
+      [, <redaction_option> ] )
+    ]
+  }
+
+ALTER REDACTION POLICY <name> ON <table_name>
+  DROP [ COLUMN ] <column_name>
+```
+
+Where `redaction_option` is:
+
+```sql
+{ SCOPE <scope_value> |
+  EXCEPTION <exception_value> }
+```
+
+## Description
+
+`ALTER REDACTION POLICY` changes the definition of an existing data redaction policy.
+
+To use `ALTER REDACTION POLICY`, you must own the table that the data redaction policy applies to.
+
+`FOR ( expression )`
+
+ This form adds or replaces the data redaction policy expression.
+
+`ENABLE`
+
+ Enables the previously disabled data redaction policy for a table.
+
+`DISABLE`
+
+ Disables the data redaction policy for a table.
+
+`ADD [ COLUMN ]`
+
+ This form adds a column of the table to the existing redaction policy. See [`CREATE REDACTION POLICY`](creating_a_data_redaction_policy) for details.
+
+`MODIFY [ COLUMN ]`
+
+ This form modifies the data redaction policy on the column of the table. You can update the redaction function clause or the redaction options for the column. The `USING` clause specifies the redaction function expression to update. The `WITH OPTIONS ( ... )` clause specifies the scope or the exception. For more details on the redaction function clause, the redaction scope, and the redaction exception, see [`CREATE REDACTION POLICY`](creating_a_data_redaction_policy).
+
+`DROP [ COLUMN ]`
+
+ This form removes the column of the table from the data redaction policy.
+
+## Parameters
+
+`name`
+
+ The name of an existing data redaction policy to alter.
+
+`table_name`
+
+ The optionally schema-qualified name of the table that the data redaction policy is on.
+
+`new_name`
+
+ The new name for the data redaction policy. This must be distinct from the name of any other existing data redaction policy for the table.
+
+`expression`
+
+ The data redaction policy expression.
+
+`column_name`
+
+ Name of existing column of the table on which the data redaction policy is being altered or dropped.
+
+`funcname_clause`
+
+ The data redaction function expression for the column. See [`CREATE REDACTION POLICY`](creating_a_data_redaction_policy) for details.
+
+`scope_value`
+
+ The scope identifies the query part to apply redaction for the column. See [`CREATE REDACTION POLICY`](creating_a_data_redaction_policy) for the details.
+
+`exception_value`
+
+ The exception identifies the query part where redaction are exempted. See [`CREATE REDACTION POLICY`](creating_a_data_redaction_policy) for the details.
+
+## Examples
+
+Update the data redaction policy called `redact_policy_personal_info` on the table named `employees`:
+
+```sql
+ALTER REDACTION POLICY redact_policy_personal_info ON employees
+FOR (session_user != 'hr' AND session_user != 'manager');
+```
+
+To update the data redaction function for the column `ssn` in the same policy:
+
+```sql
+ALTER REDACTION POLICY redact_policy_personal_info ON employees
+MODIFY COLUMN ssn USING redact_ssn_new(ssn);
+```
+
+## Compatibility
+
+`ALTER REDACTION POLICY` is an EDB extension.
+
+## See also
+
+[`CREATE REDACTION POLICY`](creating_a_data_redaction_policy), [`DROP REDACTION POLICY`](removing_a_data_redaction_policy)
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/removing_a_data_redaction_policy.mdx b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/removing_a_data_redaction_policy.mdx
new file mode 100644
index 00000000000..60509c6b1ac
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_data_redaction/removing_a_data_redaction_policy.mdx
@@ -0,0 +1,55 @@
+---
+title: "Removing a data redaction policy"
+description: "How to use the DROP REDACTION POLICY command to remove a data redaction policy from a table"
+---
+
+The `DROP REDACTION POLICY` command removes a data redaction policy from a table.
+
+## Synopsis
+
+```sql
+DROP REDACTION POLICY [ IF EXISTS ] <name> ON <table_name>
+  [ CASCADE | RESTRICT ]
+```
+
+## Description
+
+`DROP REDACTION POLICY` removes the specified data redaction policy from the table.
+
+To use `DROP REDACTION POLICY`, you must own the table that the redaction policy applies to.
+
+## Parameters
+
+`IF EXISTS`
+
+ Don't throw an error if the data redaction policy doesn't exist. A notice is issued in this case.
+
+`name`
+
+ The name of the data redaction policy to drop.
+
+`table_name`
+
+ The optionally schema-qualified name of the table that the data redaction policy is on.
+
+`CASCADE`
+
+`RESTRICT`
+
+ These keywords don't have any effect, as there are no dependencies on the data redaction policies.
+
+## Examples
+
+To drop the data redaction policy called `redact_policy_personal_info` on the table named `employees`:
+
+```sql
+DROP REDACTION POLICY redact_policy_personal_info ON employees;
+```
+
+## Compatibility
+
+`DROP REDACTION POLICY` is an EDB extension.
+
+## See also
+
+[`CREATE REDACTION POLICY`](creating_a_data_redaction_policy), [`ALTER REDACTION POLICY`](modifying_a_data_redaction_policy)
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx
new file mode 100644
index 00000000000..b724fd7cd0c
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit.mdx
@@ -0,0 +1,702 @@
+---
+title: "Selecting SQL statements to audit"
+description: "How to use the edb_audit_statement to include comma-separated values to control the SQL statements to audit"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/02_selecting_sql_statements_to_audit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="selecting_sql_statements_to_audit" class="registered_link"></div>
+
+The `edb_audit_statement` permits inclusion of one or more comma-separated values to control the SQL statements to audit. The following is the general format:
+
+```ini
+edb_audit_statement = 'value_1[, value_2]...'
+```
+
+The comma-separated values can include or omit space characters following the comma. You can specify the values in any combination of lowercase or uppercase letters.
+
+## Overview of the parameters
+
+The basic parameter values are the following:
+
+-   `all` &mdash; Audit and log every statement including any error messages on statements.
+-   `none` &mdash; Disable all auditing and logging. A value of `none` overrides any other value included in the list.
+-   `ddl` &mdash; Audit all data definition language (DDL) statements (`CREATE`, `ALTER`, and `DROP`) as well as `GRANT` and `REVOKE` data control language (DCL) statements.
+-   `dml` &mdash; Audit all data manipulation language (DML) statements (`INSERT`, `UPDATE`, `DELETE`, and `TRUNCATE`).
+-   `select` &mdash; Audit `SELECT` statements.
+-   `set` &mdash; Audit `SET` statements.
+-   `rollback` &mdash; Audit `ROLLBACK` statements.
+-   `error` &mdash; Log all error messages that occur. Otherwise, no messages about errors that occur on SQL statements related to any of the other preceding parameter values are logged except when `all` is used.
+-   `{ select | update | delete | insert }@groupname` &mdash; Selectively audit objects for specific DML statements (`SELECT`, `UPDATE`, `DELETE`, and `INSERT`) including `(@)` and excluding `(-)` groups on a given table. For more information, see [Object auditing](09_object_auditing).
+
+[DDL and DCL statements](#ddl-and-dcl-statements) describes additional parameter values for selecting particular DDL or DCL statements for auditing. [DML statements](#dml-statements) describes additional parameter values for selecting particular DML statements for auditing.
+
+If an unsupported value is included in the `edb_audit_statement` parameter, then an error occurs when applying the setting to the database server. See the database server log file for the error such as in the following example in which `create materialized vw` results in the error. The correct value is `create materialized view`.
+
+```text
+2017-07-16 11:20:39 EDT LOG:  invalid value for parameter
+"edb_audit_statement": "create materialized vw, create sequence, grant"
+2017-07-16 11:20:39 EDT FATAL:  configuration file "/var/lib/edb/as16/data/
+postgresql.conf" contains errors
+```
+
+## DDL and DCL statements
+
+When auditing DDL and DCL statements, the following general rules apply to the values that can be included in the `edb_audit_statement` parameter:
+
+-   If the `edb_audit_statement` parameter includes `ddl` or `all`, then all DDL statements are audited. In addition, the DCL statements `GRANT` and `REVOKE` are audited.
+-   If the `edb_audit_statement` is set to `none`, then no DDL nor DCL statements are audited.
+-   You can choose specific types of DDL and DCL statements for auditing by including a combination of values in the `edb_audit_statement` parameter.
+
+Use the following syntax to specify an `edb_audit_statement` parameter value for DDL statements:
+
+```text
+{ create | alter | drop } [ <object_type> ]
+```
+
+`object_type` is any of the following:
+
+ -  `ACCESS METHOD`
+
+ -  `AGGREGATE`
+
+ -  `CAST`
+
+ -  `COLLATION`
+
+ -  `CONVERSION`
+
+ -  `DATABASE`
+
+ -  `EVENT TRIGGER`
+
+ -  `EXTENSION`
+
+ -  `FOREIGN TABLE`
+
+ -  `FUNCTION`
+
+ -  `INDEX`
+
+ -  `LANGUAGE`
+
+ -  `LARGE OBJECT`
+
+ -  `MATERIALIZED VIEW`
+
+ -  `OPERATOR`
+
+ -  `OPERATOR CLASS`
+
+ -  `OPERATOR FAMILY`
+
+ -  `POLICY`
+
+ -  `PUBLICATION`
+
+ -  `ROLE`
+
+ -  `RULE`
+
+ -  `SCHEMA`
+
+ -  `SEQUENCE`
+
+ -  `SERVER`
+
+ -  `SUBSCRIPTION`
+
+ -  `TABLE`
+
+ -  `TABLESPACE`
+
+ -  `TEXT SEARCH CONFIGURATION`
+
+ -  `TEXT SEARCH DICTIONARY`
+
+ -  `TEXT SEARCH PARSER`
+
+ -  `TEXT SEARCH TEMPLATE`
+
+ -  `TRANSFORM`
+
+ -  `TRIGGER`
+
+ -  `TYPE`
+
+ -  `USER MAPPING`
+
+ -  `VIEW`
+
+Descriptions of object types as used in SQL commands can be found in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+If `object_type` is omitted from the parameter value, then all of the specified command statements (`create`, `alter`, or `drop`) are audited.
+
+Use the following syntax to specify an `edb_audit_statement` parameter value for DCL statements:
+
+```text
+{ grant | revoke }
+```
+
+### Examples
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit_statement = 'create, alter, error'
+```
+
+Thus, only SQL statements invoked by the `CREATE` and `ALTER` commands are audited. Error messages are also included in the audit log.
+
+The following is the database session that occurs:
+
+```sql
+$ psql edb enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0)
+Type "help" for help.
+
+edb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect
+-------------------
+ all
+(1 row)
+```
+```sql
+edb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement
+----------------------
+ create, alter, error
+(1 row)
+```
+```sql
+edb=# CREATE ROLE adminuser;
+CREATE ROLE
+edb=# ALTER ROLE adminuser WITH LOGIN, SUPERUSER, PASSWORD 'password';
+ERROR:  syntax error at or near ","
+LINE 1: ALTER ROLE adminuser WITH LOGIN, SUPERUSER, PASSWORD 'passwo...
+                                    ^
+edb=# ALTER ROLE adminuser WITH LOGIN SUPERUSER PASSWORD 'password';
+ALTER ROLE
+edb=# CREATE DATABASE auditdb;
+CREATE DATABASE
+edb=# ALTER DATABASE auditdb OWNER TO adminuser;
+ALTER DATABASE
+edb=# \c auditdb adminuser
+Password for user adminuser:
+You are now connected to database "auditdb" as user "adminuser".
+auditdb=# CREATE SCHEMA edb;
+CREATE SCHEMA
+auditdb=# SET search_path TO edb;
+SET
+auditdb=# CREATE TABLE department (
+auditdb(#  deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+auditdb(#  dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+auditdb(#  loc             VARCHAR2(13)
+auditdb(# );
+CREATE TABLE
+auditdb=# DROP TABLE department;
+DROP TABLE
+auditdb=# CREATE TABLE dept (
+auditdb(#  deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+auditdb(#  dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+auditdb(#  loc             VARCHAR2(13)
+auditdb(# );
+CREATE TABLE
+```
+
+The resulting audit log file contains the following. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2020-05-25 12:32:22.799 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,1,"authentication",2020-05-25 12:32:22 IST,4/19,0,AUDIT,00000,
+"connection authorized:user=enterprisedb database=edb",,,,,,,,,"","client
+backend","","connect"
+
+2020-05-25 12:34:05.843 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,2,"idle",2020-05-25 12:32:22 IST,4/23,0,AUDIT,00000,"statement: CREATE
+ROLE adminuser;",,,,,,,,,"psql","client backend","CREATE ROLE","create"
+
+2020-05-25 12:34:16.617 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,3,"idle",2020-05-25 12:32:22 IST,4/24,0,ERROR,42601,"syntax error at or
+near "",""",,,,,,"ALTER ROLE adminuser WITH LOGIN, SUPERUSER, PASSWORD
+'password';",32,,"psql","client backend","","error"
+
+2020-05-25 12:34:29.954 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,4,"idle",2020-05-25 12:32:22 IST,4/25,0,AUDIT,00000,"statement: ALTER
+ROLE adminuser WITH LOGIN SUPERUSER PASSWORD 'password';",,,,,,,,,"psql",
+"client backend","ALTER ROLE","alter"
+
+2020-05-25 12:34:40.114 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,5,"idle",2020-05-25 12:32:22 IST,4/26,0,AUDIT,00000,"statement: CREATE
+DATABASE auditdb;",,,,,,,,,"psql","client backend","CREATE DATABASE","create"
+
+2020-05-25 12:34:50.591 IST,"enterprisedb","edb",72518,"[local]",5ecb6d7e.
+11b46,6,"idle",2020-05-25 12:32:22 IST,4/27,0,AUDIT,00000,"statement: ALTER
+DATABASE auditdb OWNER TO adminuser;",,,,,,,,,"psql","client backend","ALTER
+DATABASE","alter"
+
+2020-05-25 12:35:01.554 IST,"adminuser","auditdb",75531,"[local]",5ecb6e1d.
+1270b,1,"authentication",2020-05-25 12:35:01 IST,5/11,0,AUDIT,00000,
+"connection authorized:user=adminuser database=auditdb",,,,,,,,,"","client
+backend","","connect"
+
+2020-05-25 12:35:12.931 IST,"adminuser","auditdb",75531,"[local]",5ecb6e1d.
+1270b,2,"idle",2020-05-25 12:35:01 IST,5/13,0,AUDIT,00000,"statement: CREATE
+SCHEMA edb;",,,,,,,,,"psql","client backend","CREATE SCHEMA","create"
+
+2020-05-25 12:37:18.547 IST,"adminuser","auditdb",75531,"[local]",5ecb6e1d.
+1270b,3,"idle",2020-05-25 12:35:01 IST,5/15,0,AUDIT,00000,"statement: CREATE
+TABLE department
+(
+     deptno   NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+     dname    VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+     loc      VARCHAR2(13)
+);",,,,,,,,,"psql","client backend","CREATE TABLE","create"
+
+2020-05-25 12:39:09.065 IST,"adminuser","auditdb",75531,"[local]",5ecb6e1d.
+1270b,4,"idle",2020-05-25 12:35:01 IST,5/17,0,AUDIT,00000,"statement: CREATE
+TABLE dept (
+     deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+     dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+     loc             VARCHAR2(13)
+);",,,,,,,,,"psql","client backend","CREATE TABLE","create"
+```
+
+The `CREATE` and `ALTER` statements for the `adminuser` role and `auditdb` database are audited. Because `error` is included in the `edb_audit_statement` parameter, the error for the `ALTER ROLE adminuser` statement is also logged.
+
+Similarly, the `CREATE` statements for schema `edb` and tables `department` and `dept` are audited.
+
+There's no `edb_audit_statement` setting that results in auditing successfully processed `DROP` statements such as `ddl`, `all`, or `drop`. Thus the `DROP TABLE department` statement isn't in the audit log. 
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit_statement = 'create view,create materialized view,create sequence,grant'
+```
+
+Thus, only SQL statements invoked by the `CREATE VIEW`, `CREATE MATERIALIZED VIEW`, `CREATE SEQUENCE` and `GRANT` commands are audited.
+
+The following is the database session that occurs:
+
+```sql
+$ psql auditdb adminuser
+Password for user adminuser:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect
+-------------------
+ all
+(1 row)
+```
+```sql
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+                 edb_audit_statement
+------------------------------------------------------------
+ create view,create materialized view,create sequence,grant
+(1 row)
+```
+```sql
+auditdb=# SET search_path TO edb;
+SET
+auditdb=# CREATE TABLE emp (
+auditdb(#   empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+auditdb(#   ename           VARCHAR2(10),
+auditdb(#   job             VARCHAR2(9),
+auditdb(#   mgr             NUMBER(4),
+auditdb(#   hiredate        DATE,
+auditdb(#   sal             NUMBER(7,2) CONSTRAINT emp_sal_ck CHECK (sal > 0),
+auditdb(#   comm            NUMBER(7,2),
+auditdb(#   deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+auditdb(#                       REFERENCES dept(deptno)
+auditdb(# );
+CREATE TABLE
+auditdb=# CREATE VIEW salesemp AS
+auditdb-#     SELECT empno, ename, hiredate, sal, comm FROM emp WHERE job =
+'SALESMAN';
+CREATE VIEW
+auditdb=# CREATE MATERIALIZED VIEW managers AS
+auditdb-#     SELECT empno, ename, hiredate, sal, comm FROM emp WHERE job =
+'MANAGER';
+SELECT 0
+auditdb=# CREATE SEQUENCE next_empno START WITH 8000 INCREMENT BY 1;
+CREATE SEQUENCE
+auditdb=# GRANT ALL ON dept TO PUBLIC;
+GRANT
+auditdb=# GRANT ALL ON emp TO PUBLIC;
+GRANT
+```
+
+The resulting audit log file contains the following. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2020-05-25 14:05:29.163 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,1,"authentication",2020-05-25 14:05:29 IST,4/28,0,AUDIT,00000,
+"connection authorized:user=adminuser database=auditdb",,,,,,,,,"","client
+backend","","connect"
+
+2020-05-25 14:12:06.318 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,2,"idle",2020-05-25 14:05:29 IST,4/34,0,AUDIT,00000,"statement: CREATE
+VIEW salesemp AS SELECT empno, ename, hiredate, sal, comm FROM emp WHERE job
+= 'SALESMAN';",,,,,,,,,"psql","client backend","CREATE VIEW","create"
+
+2020-05-25 14:13:26.657 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,3,"idle",2020-05-25 14:05:29 IST,4/36,0,AUDIT,00000,"statement: CREATE
+MATERIALIZED VIEW managers AS SELECT empno, ename, hiredate, sal, comm FROM
+emp WHERE job = 'MANAGER';",,,,,,,,,"psql","client backend","CREATE
+MATERIALIZED VIEW","create"
+
+2020-05-25 14:13:38.928 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,4,"idle",2020-05-25 14:05:29 IST,4/37,0,AUDIT,00000,"statement: CREATE
+SEQUENCE next_empno START WITH 8000 INCREMENT BY 1;",,,,,,,,,"psql","client
+backend","CREATE SEQUENCE","create"
+
+2020-05-25 14:13:51.434 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,5,"idle",2020-05-25 14:05:29 IST,4/38,0,AUDIT,00000,"statement: GRANT
+ALL ON dept TO PUBLIC;",,,,,,,,,"psql","client backend","GRANT","grant"
+
+2020-05-25 14:14:03.737 IST,"adminuser","auditdb",40810,"[local]",5ecb8351.
+9f6a,6,"idle",2020-05-25 14:05:29 IST,4/39,0,AUDIT,00000,"statement: GRANT
+ALL ON emp TO PUBLIC;",,,,,,,,,"psql","client backend","GRANT","grant"
+```
+
+The `CREATE VIEW` and `CREATE MATERIALIZED VIEW` statements are audited. The prior `CREATE TABLE emp` statement isn't audited because none of the values `create`, `create table`, `ddl`, nor `all` are included in the `edb_audit_statement` parameter.
+
+The `CREATE SEQUENCE` and `GRANT` statements are audited because those values are included in the `edb_audit_statement` parameter.
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit_statement = 'none'
+```
+
+The session for users who connect as `ADMIN` or `SYSDBA` can be fully audited. An admin user is connected to a database `auditdb` as `ADMINUSER`. The following `ALTER USER` command specifies to audit `ADMINUSER`.
+
+```sql
+ALTER USER adminuser SET edb_audit_statement = "all";
+```
+
+Setting the `edb_audit_statement` parameter to `all` allows auditing of all of the SQL statements for an admin user.
+
+The following is the database session that occurs:
+
+```sql
+$ psql auditdb adminuser
+Password for user adminuser:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect
+-------------------
+ all
+(1 row)
+```
+```sql
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement 
+---------------------
+ all
+(1 row)
+```
+```sql
+auditdb=# SET search_path TO edb;
+SET
+auditdb=> CREATE TABLE dept
+auditdb->        (deptno NUMBER(2),
+auditdb(>         dname VARCHAR2(14),
+auditdb(>         loc VARCHAR2(13) );
+CREATE TABLE
+auditdb=> INSERT INTO dept VALUES (10, 'ACCOUNTING', 'NEW YORK');
+INSERT 0 1
+auditdb=> INSERT INTO dept VALUES (20, 'RESEARCH', 'DALLAS');
+INSERT 0 1
+auditdb=> INSERT INTO dept VALUES (30, 'SALES', 'CHICAGO');
+INSERT 0 1
+auditdb=>  UPDATE dept SET loc = 'BEDFORD' WHERE deptno = 20;
+UPDATE 1
+auditdb=> SELECT * FROM dept;
+__OUTPUT__
+ deptno |   dname    |   loc    
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     30 | SALES      | CHICAGO
+     20 | RESEARCH   | BEDFORD
+(3 rows)
+```
+```sql
+auditdb=> DELETE FROM emp WHERE deptno = 40;
+ERROR:  relation "emp" does not exist
+LINE 1: DELETE FROM emp WHERE deptno = 40;
+                    ^
+auditdb=> DELETE FROM dept WHERE deptno = 10;
+DELETE 1
+auditdb=> SELECT * FROM dept;
+__OUTPUT__
+ deptno |  dname   |   loc   
+--------+----------+---------
+     30 | SALES    | CHICAGO
+     20 | RESEARCH | BEDFORD
+(2 rows)
+```
+
+The resulting audit log file contains the following. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2021-06-23 06:06:59.027 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,1,"authentication",2021-06-23 06:06:59 IST,4/19,0,AUDIT,00000,"connection authorized: 
+user=adminuser database=auditdb",,,,,,,,,"","client backend",,"","","connect"
+
+2021-06-23 06:07:33.192 IST,"adminuser","auditdb",66316,"[local]",60daab0c.
+1030c,2,"idle",2021-06-23 06:07:33 IST,4/16,0,AUDIT,00000,"statement: SHOW edb_audit_connect;
+",,,,,,,,,"psql","client backend",,"SHOW","","sql statement"
+
+2021-06-23 06:08:12.474 IST,"adminuser","auditdb",66316,"[local]",60daab0c.
+1030c,3,"idle",2021-06-23 06:08:12 IST,4/17,0,AUDIT,00000,"statement: SHOW edb_audit_statement;
+",,,,,,,,,"psql","client backend",,"SHOW","","sql statement"
+
+2021-06-23 06:08:20.519 IST,"adminuser","auditdb",66922,"[local]",60dab036.
+1056a,4,"idle",2021-06-23 06:08:20 IST,4/15,0,AUDIT,00000,"statement: SET search_path TO edb;
+",,,,,,,,,"psql","client backend",,"SET","","set"
+
+2021-06-23 06:09:27.613 IST,"adminuser","auditdb",60218,"[local]",60dab117.
+10602,5,"idle",2021-06-23 06:09:59 IST,4/21,0,AUDIT,00000,"statement: CREATE TABLE dept
+       (deptno NUMBER(2),
+        dname VARCHAR2(14),
+        loc VARCHAR2(13) );",,,,,,,,,"psql","client backend",,"CREATE TABLE","","create"
+
+2021-06-23 06:09:39.238 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,6,"idle",2021-06-23 06:09:29 IST,4/22,0,AUDIT,00000,"statement: INSERT INTO 
+dept VALUES (10, 'ACCOUNTING', 'NEW YORK');",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-06-23 06:09:39.242 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,7,"idle",2021-06-23 06:09:29 IST,4/23,0,AUDIT,00000,"statement: INSERT INTO 
+dept VALUES (20, 'RESEARCH', 'DALLAS');",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-06-23 06:09:39.247 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,8,"idle",2021-06-23 06:08:35 IST,4/24,0,AUDIT,00000,"statement: INSERT INTO 
+dept VALUES (30, 'SALES', 'CHICAGO');",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-06-23 06:10:04.849 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,9,"idle",2021-06-23 06:08:59 IST,4/25,0,AUDIT,00000,"statement: UPDATE dept SET loc = 'BEDFORD' 
+WHERE deptno = 20;",,,,,,,,,"psql","client backend",,"UPDATE","","update"
+
+2021-06-23 06:10:16.045 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,10,"idle",2021-06-23 06:08:59 IST,4/26,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+
+2021-06-23 06:10:40.593 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,11,"idle",2021-06-23 06:08:59 IST,4/27,0,AUDIT,00000,"statement: DELETE FROM emp WHERE deptno = 40;
+",,,,,,,,,"psql","client backend",,"DELETE","","delete"
+
+2021-06-23 06:10:40.594 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,12,"DELETE",2021-06-23 06:08:59 IST,4/27,0,ERROR,42P01,"relation ""emp"" does not exist",,,,,,
+"DELETE FROM emp WHERE deptno = 40;",13,,"psql","client backend",,"DELETE","","error"
+
+2021-06-23 06:11:02.563 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,13,"idle",2021-06-23 06:08:59 IST,4/28,0,AUDIT,00000,"statement: DELETE FROM dept WHERE deptno = 10;
+",,,,,,,,,"psql","client backend",,"DELETE","","delete"
+
+2021-06-23 06:11:14.585 IST,"adminuser","auditdb",60218,"[local]",60d3083b.
+eb3a,14,"idle",2021-06-23 06:08:59 IST,4/29,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+```
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit_statement = 'all'
+```
+
+The audit session for a user `carol` can be fully blocked by the database administrators using the `ALTER USER` command:
+
+```sql
+ALTER USER carol SET edb_audit_statement = "none";
+```
+
+!!! Note
+    The database administrator can allow a specific user to audit any SQL statements by specifying the `ALTER USER` command and setting the `edb_audit_statement` parameter to any value.
+    
+The following is the database session that occurs:
+
+```sql
+$ psql auditdb carol
+Password for user carol:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect
+-------------------
+ all
+(1 row)
+```
+```sql
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement 
+---------------------
+ none
+(1 row)
+```
+```sql
+auditdb=# SET search_path TO edb;
+SET
+auditdb=> CREATE TABLE salgrade
+auditdb->         (grade NUMBER,
+auditdb(>          losal NUMBER,
+auditdb(>          hisal NUMBER);
+CREATE TABLE
+INSERT INTO salgrade VALUES (1,  700, 1200);
+INSERT INTO salgrade VALUES (2, 1201, 1400);
+INSERT INTO salgrade VALUES (3, 1401, 2000);
+```
+
+The resulting audit log file contains only the connection authentication information. Setting the `edb_audit_statement` parameter to `none` doesn't allow the auditing of SQL statements for `carol`, so no audit logs are generated.
+
+(Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2021-06-29 02:27:26.240 IST,"carol","auditdb",68072,"[local]",60dabd4e.
+109e8,1,"authentication",2021-06-29 02:27:26 IST,4/13,0,AUDIT,00000,"connection authorized: user=carol 
+database=auditdb",,,,,,,,,"","client backend",,"","","connect"
+```
+
+## DML statements
+
+When auditing DML statements, the following general rules apply to the values that can be included in the `edb_audit_statement` parameter:
+
+-   If the `edb_audit_statement` parameter includes `dml` or `all`, then all DML statements are audited.
+-   If the `edb_audit_statement` is set to `none`, then no DML statements are audited.
+-   You can choose specific types of DML statements for auditing by including a combination of values in the `edb_audit_statement` parameter.
+
+Use the following syntax to specify an `edb_audit_statement` parameter value for `SQL INSERT`, `UPDATE`, `DELETE`, or `TRUNCATE` statements:
+
+```text
+{ insert | update | delete | truncate }
+```
+
+### Example
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit_statement = 'UPDATE, DELETE, error'
+```
+
+Thus, only SQL statements invoked by the `UPDATE` and `DELETE` commands are audited. All errors are also included in the audit log, including errors not related to the `UPDATE` and `DELETE` commands.
+
+The following is the database session that occurs:
+
+```sql
+$ psql auditdb adminuser
+Password for user adminuser:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect
+-------------------
+ all
+(1 row)
+```
+```sql
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement
+-----------------------
+ UPDATE, DELETE, error
+(1 row)
+```
+```sql
+auditdb=# SET search_path TO edb;
+SET
+auditdb=# INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+INSERT 0 1
+auditdb=# INSERT INTO dept VALUES (20,'RESEARCH','DALLAS');
+INSERT 0 1
+auditdb=# INSERT INTO dept VALUES (30,'SALES','CHICAGO');
+INSERT 0 1
+auditdb=# INSERT INTO dept VALUES (40,'OPERATIONS','BOSTON');
+INSERT 0 1
+auditdb=# INSERT INTO emp VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
+INSERT 0 1
+auditdb=# INSERT INTO emp VALUES (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
+INSERT 0 1
+auditdb=# INSERT INTO emp VALUES (7521,'WARD','SALESMAN',7698,'22-FEB-81',1250,500,30);
+INSERT 0 1
+                 .
+                 .
+                 .
+auditdb=# INSERT INTO emp VALUES (7934,'MILLER','CLERK',7782,'23-JAN-82',1300,NULL,10);
+INSERT 0 1
+auditdb=# UPDATE dept SET loc = 'BEDFORD' WHERE deptno = 40;
+UPDATE 1
+auditdb=# SELECT * FROM dept;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+     40 | OPERATIONS | BEDFORD
+(4 rows)
+```
+```sql
+auditdb=# DELETE FROM emp WHERE deptno = 10;
+DELETE 3
+auditdb=# TRUNCATE employee;
+ERROR:  relation "employee" does not exist
+auditdb=# TRUNCATE emp;
+TRUNCATE TABLE
+auditdb=# \q
+```
+
+The resulting audit log file contains the following. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2020-05-25 15:17:16.392 IST,"adminuser","auditdb",123420,"[local]",5ecb9424.
+1e21c,1,"authentication",2020-05-25 15:17:16 IST,5/3,0,AUDIT,00000,
+"connection authorized:user=adminuser database=auditdb",,,,,,,,,"","client
+backend","",connect"
+
+2020-05-25 15:19:18.066 IST,"adminuser","auditdb",123420,"[local]",5ecb9424.
+1e21c,2,"idle",2020-05-25 15:17:16 IST,5/14,0,AUDIT,00000,"statement: UPDATE
+dept SET loc = 'BEDFORD' WHERE deptno = 40;",,,,,,,,,"psql","client backend",
+"UPDATE","update"
+
+2020-05-25 15:19:38.524 IST,"adminuser","auditdb",123420,"[local]",5ecb9424.
+1e21c,3,"idle",2020-05-25 15:17:16 IST,5/16,0,AUDIT,00000,"statement: DELETE
+FROM emp WHERE deptno = 10;",,,,,,,,,"psql","client backend","DELETE","delete"
+
+2020-05-25 15:19:48.149 IST,"adminuser","auditdb",123420,"[local]",5ecb9424.
+1e21c,4,"TRUNCATE TABLE",2020-05-25 15:17:16 IST,5/17,0,ERROR,42P01,"relation
+""employee""does not exist",,,,,,"TRUNCATE employee;",,,"psql","client backend
+","TRUNCATE TABLE","error"
+```
+
+The `UPDATE dept` and `DELETE FROM emp` statements are audited. All of the prior `INSERT` statements aren't audited because the values `insert`, `dml`, or `all` aren't included in the `edb_audit_statement` parameter.
+
+The `SELECT * FROM dept` statement isn't audited because `select` and `all` aren't included in the `edb_audit_statement` parameter.
+
+Because `error` is specified in the `edb_audit_statement` parameter but not the `truncate` value, the error on the `TRUNCATE employee` statement is logged in the audit file. But the successful `TRUNCATE emp` statement isn't.
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/03_enabling_audit_logging.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/03_enabling_audit_logging.mdx
new file mode 100644
index 00000000000..a9edd53b5ab
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/03_enabling_audit_logging.mdx
@@ -0,0 +1,263 @@
+---
+title: "Enabling audit logging"
+description: "How to configure EDB Postgres Advanced Server to log the items you want to audit"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/03_enabling_audit_logging/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="enabling_audit_logging" class="registered_link"></div>
+
+You can configure EDB Postgres Advanced Server to log all connections, disconnections, DDL statements, DCL statements, DML statements, and any statements resulting in an error.
+
+-  Enable auditing by setting the `edb_audit` parameter to `xml` or `csv`.
+-  Set the file rotation day when the new file is created by setting the parameter `edb_audit_rotation_day` to the desired value.
+-  To audit all connections, set the parameter `edb_audit_connect` to `all`.
+-  To audit all disconnections, set the parameter `edb_audit_disconnect` to `all`.
+-  To audit DDL, DCL, DML and other statements, set the parameter `edb_audit_statement` according to the instructions in [Selecting SQL statements to audit](02_selecting_sql_statements_to_audit/#selecting_sql_statements_to_audit).
+-  To specify the desired location of audit files, set the `edb_audit_directory` parameter.
+
+Setting the `edb_audit_statement` parameter in the configuration file affects the entire database cluster.
+
+You can further refine the type of statements that are audited. The type is controlled by the `edb_audit_statement` parameter according to the database in use as well as the database role running the session:
+
+-   You can set the `edb_audit_statement` parameter as an attribute of a specified database with the `ALTER DATABASE dbname SET edb_audit_statement` command. This setting overrides the `edb_audit_statement` parameter in the configuration file for statements executed when connected to database `dbname`.
+-   You can set the `edb_audit_statement` parameter as an attribute of a specified role with the `ALTER ROLE rolename SET edb_audit_statement` command. This setting overrides the `edb_audit_statement` parameter in the configuration file as well as any setting assigned to the database by the `ALTER DATABASE` command when the specified role is running the current session.
+-   You can set the `edb_audit_statement` parameter as an attribute of a specified role when using a specified database with the `ALTER ROLE rolename IN DATABASE dbname SET edb_audit_statement` command. This setting overrides the `edb_audit_statement` parameter in the configuration file. It also overrides any setting assigned to the database by the `ALTER DATABASE` command and as any setting assigned to the role with the `ALTER ROLE` command without the `IN DATABASE` clause.
+
+## Examples
+
+The following are examples of this technique.
+
+The database cluster is established with `edb_audit_statement` set to `all` as shown in its `postgresql.conf` file:
+
+```ini
+logging_collector = 'on'
+edb_audit_statement = 'all'     # Statement type to be audited:
+                                # none, dml, insert, update, delete, truncate,
+                                # select, error, rollback, ddl, create, drop,
+                                # alter, grant, revoke, set, all
+                                # {select | update | delete | insert}@groupname
+```
+
+A database and role are established with the following settings for the `edb_audit_statement` parameter:
+
+-   Database `auditdb` with `ddl`, `insert`, `update`, and `delete`
+-   Role `admin` with `select`, `truncate`, and `set`
+-   Role `admin` in database `auditdb` with `create table`, `insert`, and `update`
+
+The following shows creating and altering the database and role:
+
+```sql
+$ psql edb enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0)
+Type "help" for help.
+
+edb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement
+---------------------
+ all
+(1 row)
+```
+```sql
+edb=# CREATE DATABASE auditdb;
+CREATE DATABASE
+edb=# ALTER DATABASE auditdb SET edb_audit_statement TO 'ddl, insert, update, delete';
+ALTER DATABASE
+edb=# CREATE ROLE admin WITH LOGIN SUPERUSER PASSWORD 'password';
+CREATE ROLE
+edb=# ALTER ROLE admin SET edb_audit_statement TO 'select, truncate';
+ALTER ROLE
+edb=# ALTER ROLE admin IN DATABASE auditdb SET edb_audit_statement TO 'create table, insert, update';
+ALTER ROLE
+```
+
+The following shows the changes made and the resulting audit log file for three cases.
+
+### Case 1: Changes made in database `auditdb` by role `enterprisedb`
+
+Only `ddl`, `insert`, `update`, and `delete` statements are audited:
+
+```sql
+$ psql auditdb enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+     edb_audit_statement
+-----------------------------
+ ddl, insert, update, delete
+(1 row)
+```
+```sql
+auditdb=# CREATE TABLE audit_tbl (f1 INTEGER PRIMARY KEY, f2 TEXT);
+CREATE TABLE
+auditdb=# INSERT INTO audit_tbl VALUES (1, 'Row 1');
+INSERT 0 1
+auditdb=# UPDATE audit_tbl SET f2 = 'Row A' WHERE f1 = 1;
+UPDATE 1
+auditdb=# SELECT * FROM audit_tbl;                  <== Should not be audited
+__OUTPUT__
+ f1 |  f2
+----+-------
+  1 | Row A
+(1 row)
+```
+```sql
+auditdb=# TRUNCATE audit_tbl;                       <== Should not be audited
+TRUNCATE TABLE
+```
+
+The following audit log file shows entries only for the `CREATE TABLE`, `INSERT INTO audit_tbl`, and `UPDATE audit_tbl` statements. The `SELECT * FROM audit_tbl` and `TRUNCATE audit_tbl` statements weren't audited. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2020-05-25 15:59:12.332 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,2,
+"idle",2020-05-25 15:59:02 IST,5/7,0,AUDIT,00000,"statement: CREATE TABLE 
+audit_tbl(f1 INTEGER PRIMARY KEY, f2 TEXT);",,,,,,,,,"psql","client backend","CREATE TABLE","","create"
+
+2020-05-25 15:59:22.419 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,3,
+"idle",2020-05-25 15:59:02 IST,5/8,0,AUDIT,00000,"statement: INSERT INTO 
+audit_tbl VALUES (1, 'Row 1');",,,,,,,,,"psql","client backend","INSERT","","insert"
+
+2020-05-25 15:59:32.180 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,4,
+"idle",2020-05-25 15:59:02 IST,5/9,0,AUDIT,00000,"statement: UPDATE
+audit_tbl SET f2 = 'Row A' WHERE f1 = 1;",,,,,,,,,"psql","client backend","UPDATE","","update"
+```
+
+### Case 2: Changes made in database `edb` by role `admin`
+
+Only `select`, `truncate`, and `set` statements are audited:
+
+```sql
+$ psql edb admin
+Password for user admin:
+psql.bin (16.1.0)
+Type "help" for help.
+
+edb=# SHOW edb_audit_statement;
+__OUTPUT__
+ edb_audit_statement
+-----------------------
+ select, truncate, set
+(1 row)
+```
+```sql
+edb=# SET default_with_rowids TO TRUE;
+SET
+
+edb=# CREATE TABLE edb_tbl (f1 INTEGER PRIMARY KEY, f2 TEXT); <== Should not be audited
+CREATE TABLE
+edb=# INSERT INTO edb_tbl VALUES (1, 'Row 1');                <== Should not be audited
+INSERT 0 1
+edb=# SELECT * FROM edb_tbl;
+__OUTPUT__
+ f1 |  f2
+----+-------
+  1 | Row 1
+(1 row)
+```
+```sql
+edb=# TRUNCATE edb_tbl;
+TRUNCATE TABLE
+```
+
+Continuation of the audit log file now appears as follows. The last two entries representing the second case show only the `SET default_with_rowids TO TRUE`, `SELECT * FROM edb_tbl`, and `TRUNCATE edb_tbl` statements. The `CREATE TABLE edb_tbl` and `INSERT INTO edb_tbl` statements weren't audited.
+
+```text
+2020-05-25 15:59:12.332 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,2,
+"idle",2020-05-25 15:59:02 IST,5/7,0,AUDIT,00000,"statement: CREATE TABLE 
+audit_tbl(f1 INTEGER PRIMARY KEY, f2 TEXT);",,,,,,,,,"psql","client backend","CREATE TABLE","","create"
+
+2020-05-25 15:59:22.419 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,3,
+"idle",2020-05-25 15:59:02 IST,5/8,0,AUDIT,00000,"statement: INSERT INTO 
+audit_tbl VALUES (1, 'Row 1');",,,,,,,,,"psql","client backend","INSERT","","insert"
+
+2020-05-25 15:59:32.180 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,4,
+"idle",2020-05-25 15:59:02 IST,5/9,0,AUDIT,00000,"statement: UPDATE
+audit_tbl SET f2 = 'Row A' WHERE f1 = 1;",,,,,,,,,"psql","client backend","UPDATE","","update"
+
+2021-02-18 08:04:57.434 IST,"admin","edb",3182,"[local]",602e65dc.c6e,1,
+"idle",2021-02-18 08:04:28 IST,4/22,0,AUDIT,00000,"statement: SET default_with_rowids TO TRUE;
+",,,,,,,,,"psql","client backend","SET","","set"
+
+2021-02-18 08:06:01.662 IST,"admin","edb",3182,"[local]",602e65dc.c6e,2,
+"idle",2021-02-18 08:04:28 IST,4/27,0,AUDIT,00000,"statement: SELECT * FROM edb_tbl;
+",,,,,,,,,"psql","client backend","SELECT","","select"
+
+2021-02-18 08:06:11.125 IST,"admin","edb",3182,"[local]",602e65dc.c6e,3,
+"idle",2021-02-18 08:04:28 IST,4/28,0,AUDIT,00000,"statement: TRUNCATE edb_tbl;
+",,,,,,,,,"psql","client backend","TRUNCATE TABLE","","truncate"
+```
+
+### Case 3: Changes made in database `auditdb` by role `admin` 
+
+Only `create table`, `insert`, and `update` statements are audited:
+
+```sql
+$ psql auditdb admin
+Password for user admin:
+psql.bin (16.1.0)
+Type "help" for help.
+
+auditdb=# SHOW edb_audit_statement;
+__OUTPUT__
+     edb_audit_statement
+------------------------------
+ create table, insert, update
+(1 row)
+```
+```sql
+auditdb=# CREATE TABLE audit_tbl_2 (f1 INTEGER PRIMARY KEY, f2 TEXT);
+CREATE TABLE
+auditdb=# INSERT INTO audit_tbl_2 VALUES (1, 'Row 1');
+INSERT 0 1
+auditdb=# SELECT * FROM audit_tbl_2;                <== Should not be audited
+__OUTPUT__
+ f1 |  f2
+----+-------
+  1 | Row 1
+(1 row)
+```
+```sql
+auditdb=# TRUNCATE audit_tbl_2;                     <== Should not be audited
+TRUNCATE TABLE
+```
+
+Continuation of the audit log file now appears as follows. The next-to-last two entries representing the third case show only `CREATE TABLE audit_tbl_2` and `INSERT INTO audit_tbl_2` statements. The `SELECT * FROM audit_tbl_2` and `TRUNCATE audit_tbl_2` statements weren't audited.
+
+```text
+2020-05-25 15:59:12.332 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,2,
+"idle",2020-05-25 15:59:02 IST,5/7,0,AUDIT,00000,"statement: CREATE TABLE 
+audit_tbl(f1 INTEGER PRIMARY KEY, f2 TEXT);",,,,,,,,,"psql","client backend","CREATE TABLE","","create"
+
+2020-05-25 15:59:22.419 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,3,
+"idle",2020-05-25 15:59:02 IST,5/8,0,AUDIT,00000,"statement: INSERT INTO 
+audit_tbl VALUES (1, 'Row 1');",,,,,,,,,"psql","client backend","INSERT","","insert"
+
+2020-05-25 15:59:32.180 IST,"enterprisedb","auditdb",41837,"[local]",5ecb9dee.a36d,4,
+"idle",2020-05-25 15:59:02 IST,5/9,0,AUDIT,00000,"statement: UPDATE
+audit_tbl SET f2 = 'Row A' WHERE f1 = 1;",,,,,,,,,"psql","client backend","UPDATE","","update"
+
+2021-02-18 08:04:57.434 IST,"admin","edb",3182,"[local]",602e65dc.c6e,1,
+"idle",2021-02-18 08:04:28 IST,4/22,0,AUDIT,00000,"statement: SET default_with_rowids TO TRUE;
+",,,,,,,,,"psql","client backend","SET","","set"
+
+2021-02-18 08:06:01.662 IST,"admin","edb",3182,"[local]",602e65dc.c6e,2,
+"idle",2021-02-18 08:04:28 IST,4/27,0,AUDIT,00000,"statement: SELECT * FROM edb_tbl;
+",,,,,,,,,"psql","client backend","SELECT","","select"
+
+2021-02-18 08:06:11.125 IST,"admin","edb",3182,"[local]",602e65dc.c6e,3,
+"idle",2021-02-18 08:04:28 IST,4/28,0,AUDIT,00000,"statement: TRUNCATE edb_tbl;
+",,,,,,,,,"psql","client backend","TRUNCATE TABLE","","truncate"
+
+2020-05-25 17:30:59.057 IST,"admin","auditdb",122093,"[local]",5ecbb370.1dced,2,
+"idle",2020-05-25 17:30:48 IST,5/11,0,AUDIT,00000,"statement: CREATE TABLE
+audit_tbl_2 (f1 INTEGER PRIMARY KEY, f2 TEXT);",,,,,,,,,"psql","client backend","CREATE TABLE","","create"
+
+2020-05-25 17:31:08.866 IST,"admin","auditdb",122093,"[local]",5ecbb370.1dced,3,
+"idle",2020-05-25 17:30:48 IST,5/12,0,AUDIT,00000,"statement: INSERT INTO
+audit_tbl_2 VALUES (1, 'Row 1');",,,,,,,,,"psql","client backend","INSERT","","insert"
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/05_using_error_codes_to_filter_audit_logs.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/05_using_error_codes_to_filter_audit_logs.mdx
new file mode 100644
index 00000000000..edc29d85868
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/05_using_error_codes_to_filter_audit_logs.mdx
@@ -0,0 +1,32 @@
+---
+title: "Using error codes to filter audit logs"
+description: "Describes how to filter the audit logs based on specific error codes"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/05_using_error_codes_to_filter_audit_logs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_error_codes_to_filter_audit_logs" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes an extension that you can use to exclude from the EDB Postgres Advanced Server log files entries that include a user-specified error code. To filter audit log entries, you must first enable the extension by modifying the `postgresql.conf` file. Add the following value to those specified in the `shared_preload_libraries` parameter:
+
+```text
+$libdir/edb_filter_log
+```
+
+Then, use the `edb_filter_log.errcodes` parameter to specify any error codes you want to omit from the log files:
+
+```ini
+edb_filter_log.errcode = 'error_code'
+```
+
+Where `error_code` specifies one or more error codes that you want to omit from the log file. Provide multiple error codes in a comma-delimited list.
+
+For example, if `edb_filter_log` is enabled, and `edb_filter_log.errcode` is set to `'23505,23502,22012'`, any log entries that return one of the following `SQLSTATE` errors are omitted from the log file:
+
+- `23505` (for violating a unique constraint)
+
+- `23502` (for violating a not-null constraint)
+
+- `22012` (for dividing by zero)
+
+For a complete list of the error codes supported by EDB Postgres Advanced Server audit log filtering, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/errcodes-appendix.html).
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/06_using_command_tags_to_filter_audit_logs.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/06_using_command_tags_to_filter_audit_logs.mdx
new file mode 100644
index 00000000000..867eac6c8c6
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/06_using_command_tags_to_filter_audit_logs.mdx
@@ -0,0 +1,82 @@
+---
+title: "Using command tags to filter audit logs"
+description: "Describes how to use command tags to find log file entries related to a SQL command"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/06_using_command_tags_to_filter_audit_logs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="using_command_tags_to_filter_audit_logs" class="registered_link"></div>
+
+Each entry in the log file contains a *command tag*, except for entries that display an error message. A command tag is the SQL command executed for that log entry. The command tag makes it possible to use tools later to scan the log file to find entries related to a SQL command.
+
+This example is in XML form, formatted for easier review. The command tag is displayed as the `command_tag` attribute of the `event` element with values `CREATE ROLE`, `ALTER ROLE`, and `DROP ROLE`.
+
+```xml
+<event user="enterprisedb" database="edb" process_id="64234" remote_host=
+"[local]"
+       session_id="5ecbc7e6.faea" session_line_num="2" process_status="idle"
+       session_start_time="2020-05-25 18:58:06 IST" log_time="2020-05-25
+       18:58:21.147 IST"
+       virtual_transaction_id="4/30" type="create" command_tag="CREATE ROLE"
+       application_name="psql" backend_type="client backend">
+           <error_severity>AUDIT</error_severity>
+           <message>statement: CREATE ROLE newuser WITH LOGIN;</message>
+</event>
+<event user="enterprisedb" database="edb" process_id="64234" remote_host=
+"[local]"
+       session_id="5ecbc7e6.faea" session_line_num="3" process_status="idle"
+       session_start_time="2020-05-25 18:58:06 IST" log_time="2020-05-25
+       18:58:34.142 IST"
+       virtual_transaction_id="4/31" type="error" sql_state_code="42601"
+       application_name="psql" backend_type="client backend">
+           <error_severity>ERROR</error_severity>
+           <message>unrecognized role option &quot;super&quot;</message>
+           <query>ALTER ROLE newuser WITH SUPER USER;</query>
+           <query_pos>25</query_pos>
+</event>
+<event user="enterprisedb" database="edb" process_id="64234" remote_host=
+"[local]"
+       session_id="5ecbc7e6.faea" session_line_num="4" process_status="idle"
+       session_start_time="2020-05-25 18:58:06 IST" log_time="2020-05-25
+       18:58:44.680 IST"
+       virtual_transaction_id="4/32" type="alter" command_tag="ALTER ROLE"
+       application_name="psql" backend_type="client backend">
+           <error_severity>AUDIT</error_severity>
+           <message>statement: ALTER ROLE newuser WITH SUPERUSER;</message>
+</event>
+<event user="enterprisedb" database="edb" process_id="64234" remote_host=
+"[local]"
+       session_id="5ecbc7e6.faea" session_line_num="5" process_status="idle"
+       session_start_time="2020-05-25 18:58:06 IST" log_time="2020-05-25
+       18:58:58.173 IST"
+       virtual_transaction_id="4/33" type="drop" command_tag="DROP ROLE"
+       application_name="psql" backend_type="client backend">
+           <error_severity>AUDIT</error_severity>
+           <message>statement: DROP ROLE newuser;</message>
+</event>
+```
+
+The following is the same example in CSV form. The command tag is the next-to-last column of each entry. In the listing, the column that appears empty (""), is the value of the `edb_audit_tag` parameter, if provided.
+
+(Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2020-05-25 19:09:32.105 IST,"enterprisedb","edb",77212,"[local]",5ecbca7b.
+12d9c,2,"idle",2020-05-25 19:09:07 IST,4/30,0,AUDIT,00000,"statement: CREATE
+ROLE newuser WITH LOGIN;",,,,,,,,,"psql","client backend","CREATE ROLE","",
+"create"
+
+2020-05-25 19:09:50.975 IST,"enterprisedb","edb",77212,"[local]",5ecbca7b.
+12d9c,3,"idle",2020-05-25 19:09:07 IST,4/31,0,ERROR,42601,"unrecognized role
+option ""super""",,,,,,"ALTER ROLE newuser WITH SUPER USER;",25,,"psql",
+"client backend","","","error"
+
+2020-05-25 19:10:04.128 IST,"enterprisedb","edb",77212,"[local]",5ecbca7b.
+12d9c,4,"idle",2020-05-25 19:09:07 IST,4/32,0,AUDIT,00000,"statement: ALTER
+ROLE newuser WITH SUPERUSER;",,,,,,,,,"psql","client backend","ALTER ROLE","",
+"alter"
+
+2020-05-25 19:10:15.959 IST,"enterprisedb","edb",77212,"[local]",5ecbca7b.
+12d9c,5,"idle",2020-05-25 19:09:07 IST,4/33,0,AUDIT,00000,"statement: DROP
+ROLE newuser;",,,,,,,,,"psql","client backend","DROP ROLE","","drop"
+```
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/07_redacting_passwords_from_audit_logs.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/07_redacting_passwords_from_audit_logs.mdx
new file mode 100644
index 00000000000..3d83730f6f6
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/07_redacting_passwords_from_audit_logs.mdx
@@ -0,0 +1,63 @@
+---
+title: "Redacting passwords in audit logs"
+description: "Describes how to redact stored passwords in the audit log file"
+hideToC: true
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/07_redacting_passwords_from_audit_logs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="redacting_passwords_from_audit_logs" class="registered_link"></div>
+
+You can use the GUC parameter `edb_filter_log.redact_password_commands` under the `postgresql.conf` file to redact stored passwords in the log file. 
+
+The syntax is:
+
+```sql
+{CREATE|ALTER} {USER|ROLE|GROUP} identifier 
+   { [WITH] [ENCRYPTED] PASSWORD 'nonempty_string_literal' 
+    | IDENTIFIED BY { 'nonempty_string_literal' 
+    | bareword } } 
+    [ REPLACE { 'nonempty_string_literal' | bareword } ]
+```
+
+To enable password redaction, you must first enable the parameter by modifying the `postgresql.conf` file. Add the following value to those specified in the `shared_preload_libraries` parameter:
+
+```text
+$libdir/edb_filter_log
+```
+
+Then, set `edb_filter_log.redact_password_commands` to `true`:
+
+```ini
+edb_filter_log.redact_password_commands = true
+```
+
+After modifying the `postgresql.conf` file, you must restart the server for the changes to take effect.
+
+## Examples
+
+When the following statement is logged by `log_statement`, the server redacts the password to `x`. For example, this command is added to the log file:
+
+```sql
+CREATE USER carol with login PASSWORD '1safepwd';
+```
+
+It appears as:
+
+```text
+2021-05-17 05:01:46.841 IST,"enterprisedb","edb",18415,"[local]",60a230f0.47ef,1,"idle",2021-05-17 05:01:36 IST,3/3,0,AUDIT,00000,"statement: CREATE USER carol with login PASSWORD 'x';",,,,,,,,,"psql","client backend","CREATE ROLE","","create"
+```
+
+When the following statement is logged by `log_statement`, the server identifies the new password, replace, and redact the password to `x`. For example, this command is added to the log file:
+ 
+```sql
+ALTER USER carol IDENTIFIED BY 'new_pass' REPLACE '1safepwd'; 
+```
+
+It appears as:
+
+```text
+2021-05-19 04:41:45.718 IST,"enterprisedb","edb",19354,"[local]",60a23a72.4b9a,1,"idle",2021-05-19 04:41:23 IST,3/3,0,AUDIT,00000,"statement: ALTER USER carol IDENTIFIED BY 'x' REPLACE 'x';",,,,,,,,,"psql","client backend","ALTER ROLE","","alter"
+```
+
+The statement that includes a password is logged. The server redacts the password text to `x`. When the statement is logged as context for some other message, the server omits the statement from the context.
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx
new file mode 100644
index 00000000000..70d8eab002a
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/08_audit_log_archiving.mdx
@@ -0,0 +1,139 @@
+---
+title: "Archiving audit logs"
+description: "Describes how to use the Audit Archiver to manage audit log files"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/08_audit_log_archiving/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="audit_log_archiving" class="registered_link"></div>
+
+EDB audit log archiving enables database administrators to control the space consumed by the audit log directory and helps manage the audit log files. The Audit Archiver is responsible for the compression, execution, and expiration of log files with `edb_audit_archiver_filename_prefix` present in the audit directory. The `edb_audit_archiver_timeout` parameter triggers the compression or expiration of audit log files at an appropriate time. For more information about audit archiving configuration parameters, see [Audit logging configuration parameters](/epas/latest/reference/database_administrator_reference/01_audit_logging_configuration_parameters/).
+
+The audit archiver helps to:
+
+-  Prepare a list of log files from the audit log directory for compression.
+-  Determine the log files for compression based on the parameters `edb_audit_archiver_compress_time_limit` and `edb_audit_archiver_compress_size_limit`. 
+-  Perform compression of the log files by specifying the compression command based on the `edb_audit_archiver_compress_command` parameter.
+-  Determine the log files to remove based on the `edb_audit_archiver_expire_time_limit` and `edb_audit_archiver_expire_size_limit` parameter. 
+-  Execute the expiration command specified in the `edb_audit_archiver_expire_command` parameter to remove the log files.
+
+## Rotating out older audit log files
+
+To rotate out the older audit log files, you can set the log file rotation day when the new file is created. To do so, set the parameter `edb_audit_rotation_day` to the desired value. The audit log records are overwritten on a first-in, first-out basis if space isn't available for more audit log records.
+
+## Enabling compression and expiration of log files
+
+To configure EDB Postgres Advanced Server to enable compression and expiration of the log files:
+
+1.  Enable audit log archiving by setting the `edb_audit_archiver` parameter to `on` in the `postgresql.conf` file.
+1.  To enable compression of log files, set the parameter `edb_audit_archiver_compress_size_limit` and `edb_audit_archiver_compress_time_limit` to the values you want.
+1.  To enable expiration of log files, set the parameter `edb_audit_archiver_expire_size_limit` and `edb_audit_archiver_expire_time_limit` to the values you want. 
+1.  To enable both compression and expiration, set the parameters `edb_audit_archiver_compress_size_limit`, `edb_audit_archiver_compress_time_limit`, `edb_audit_archiver_expire_size_limit`, `edb_audit_archiver_expire_time_limit`, and `edb_audit_archiver_expire_command` to the values you want.
+
+The following is an example of the configuration parameter settings in the `postgresql.conf` file.
+
+Setting the `edb_audit_archiver` parameter in the configuration file affects the entire database cluster. The database cluster is established with `edb_audit_archiver` set to `on`, as shown in the `postgresql.conf` file. The audit log file is generated in CSV format based on the setting of the `edb_audit` configuration parameter.
+
+```ini
+logging_collector = 'on'
+edb_audit = 'csv'
+edb_audit_archiver = 'on'  # (Change requires restart)
+```
+
+## Examples
+
+In this example, `edb_audit_archiver`, `edb_audit_archiver_compress_size_limit`, and `edb_audit_archiver_compress_time_limit` are set to enable compression of the audit log files greater than 10MB.
+
+```ini
+edb_audit_archiver = 'on'
+edb_audit_archiver_compress_size_limit = 10
+edb_audit_archiver_compress_time_limit = 0
+```
+
+Before compression, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 2097276 Jun 4 11:42 audit-20200811_114237.csv   <== Shows non-compressed audit log files 
+-rw-------. 1 enterprisedb edb 2097278 Jun 4 11:42 audit-20200811_114243.csv
+-rw-------. 1 enterprisedb edb 2097289 Jun 4 11:42 audit-20200811_114245.csv
+-rw-------. 1 enterprisedb edb 2097330 Jun 4 11:42 audit-20200811_114246.csv
+-rw-------. 1 enterprisedb edb 2097343 Jun 4 11:42 audit-20200811_114248.csv
+-rw-------. 1 enterprisedb edb 2097338 Jun 4 11:42 audit-20200811_114249.csv
+```
+
+The `edb_audit_archiver` parameter checks the log files, excluding the latest file. It retains at least 10MB of log files in the audit log directory and compresses the remaining log files. The `.gz` specifies the name of an already compressed log file. After compression, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 64119 Jun 4 11:42 audit-20200811_114237.csv.gz   <== Shows compressed audit log files 
+-rw-------. 1 enterprisedb edb 64323 Jun 4 11:42 audit-20200811_114243.csv.gz
+-rw-------. 1 enterprisedb edb 64091 Jun 4 11:42 audit-20200811_114245.csv.gz
+-rw-------. 1 enterprisedb edb 64152 Jun 4 11:42 audit-20200811_114246.csv.gz      
+-rw-------. 1 enterprisedb edb 2097343 Jun 4 11:42 audit-20200811_114248.csv    <== Shows non-compressed audit log files 
+-rw-------. 1 enterprisedb edb 2097338 Jun 4 11:42 audit-20200811_114249.csv
+```
+
+In this example, `edb_audit_archiver`, `edb_audit_archiver_expire_size_limit`, and `edb_audit_archiver_expire_time_limit` are set to enable expiration of the audit log files older than one hour.
+
+```ini
+edb_audit_archiver = 'on'
+edb_audit_archiver_expire_size_limit = 0
+edb_audit_archiver_expire_time_limit = 3600
+```
+
+Before compression, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 2097367 Jun 4 13:23 audit-20200811_132352.csv   <== Shows non-compressed audit log files scheduled for expiration/removal
+-rw-------. 1 enterprisedb edb 2097395 Jun 4 13:24 audit-20200811_132353.csv
+-rw-------. 1 enterprisedb edb 2097328 Jun 4 14:35 audit-20200811_143438.csv
+-rw-------. 1 enterprisedb edb 2097276 Jun 4 14:35 audit-20200811_143502.csv
+-rw-------. 1 enterprisedb edb 2097211 Jun 4 14:35 audit-20200811_143503.csv
+-rw-------. 1 enterprisedb edb 2097152 Jun 4 14:35 audit-20200811_143504.csv
+```
+
+The `edb_audit_archiver` parameter checks the log files, excluding the latest file. It removes the log files older than one hour. After expiration, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 2097328 Jun 4 14:35 audit-20200811_143438.csv
+-rw-------. 1 enterprisedb edb 2097276 Jun 4 14:35 audit-20200811_143502.csv
+-rw-------. 1 enterprisedb edb 2097211 Jun 4 14:35 audit-20200811_143503.csv
+-rw-------. 1 enterprisedb edb 2097152 Jun 4 14:35 audit-20200811_143504.csv
+```
+
+In this example, `edb_audit_archiver`, `edb_audit_archiver_compress_size_limit`, `edb_audit_archiver_compress_time_limit`, `edb_audit_archiver_expire_size_limit`, `edb_audit_archiver_expire_time_limit`, and `edb_audit_archiver_expire_command` are set to enable both compression and expiration of the audit log files.
+
+```ini
+edb_audit_archiver = 'on'
+edb_audit_archiver_compress_size_limit = 4
+edb_audit_archiver_compress_time_limit = 0
+edb_audit_archiver_expire_size_limit = 5
+edb_audit_archiver_expire_time_limit = 0
+edb_audit_archiver_expire_command = 'cp %p /home/edb_audit/backup-log/'
+```
+
+Before compression, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 2097522 Jun 4 13:02 audit-20200811_125816.csv   <== Shows non-compressed audit log files ready to be removed/expired
+-rw-------. 1 enterprisedb edb 2097510 Jun 4 13:02 audit-20200811_130215.csv
+-rw-------. 1 enterprisedb edb 2097336 Jun 4 13:10 audit-20200811_130947.csv
+-rw-------. 1 enterprisedb edb 2097271 Jun 4 13:10 audit-20200811_131034.csv
+-rw-------. 1 enterprisedb edb 2097246 Jun 4 13:10 audit-20200811_131035.csv
+-rw-------. 1 enterprisedb edb 2097289 Jun 4 13:10 audit-20200811_131036.csv
+```
+
+The `edb_audit_archiver` parameter checks the log files, excluding the latest file. It retains at least 4MB of log files in the audit log directory and compresses the remaining log files. While checking the log files for expiration, `edb_audit_archiver` retains at least 5MB of log files in the audit log directory and removes the remaining log files. After compression and expiration, the audit log file appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 63854 Jun 4 13:10 audit-20200811_131034.csv.gz
+-rw-------. 1 enterprisedb edb 63513 Jun 4 13:10 audit-20200811_131035.csv.gz
+-rw-------. 1 enterprisedb edb 63738 Jun 4 13:10 audit-20200811_131036.csv.gz
+```
+
+The expiration command is specified as `edb_audit_archiver_expire_command = 'cp %p /home/edb_audit/backup-log/'` in the `postgresql.conf` file. The `edb_audit_archiver` executes this command and copies the log files to a backup log directory before deleting them from the audit log directory. After compression and expiration, the backup log directory appears as follows:
+
+```text
+-rw-------. 1 enterprisedb edb 2097522 Jun 4 13:02 audit-20200811_125816.csv.gz
+-rw-------. 1 enterprisedb edb 2097510 Jun 4 13:02 audit-20200811_130215.csv.gz
+-rw-------. 1 enterprisedb edb 2097336 Jun 4 13:10 audit-20200811_130947.csv.gz
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/09_object_auditing.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/09_object_auditing.mdx
new file mode 100644
index 00000000000..a6866b00d04
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/09_object_auditing.mdx
@@ -0,0 +1,258 @@
+---
+title: "Auditing objects"
+description: "Describes how to selectively audit objects for specific DML statements"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/09_object_auditing/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="object_auditing" class="registered_link"></div>
+
+Object-level auditing allows selective auditing of objects for specific data manipulation language (DML) statements, such as `SELECT`, `UPDATE`, `DELETE`, and `INSERT`, on a given table. Object-level auditing also lets you include or exclude specific groups by specifying `(@)` or `(-)` with the `edb_audit_statement` parameter. For more information about DML statements, see [Selecting SQL statements to audit](02_selecting_sql_statements_to_audit/#selecting_sql_statements_to_audit).
+
+Use the following syntax to specify an `edb_audit_statement` parameter value for `SELECT`, `UPDATE`, `DELETE`, or `INSERT` statements:
+
+```text
+{ select | update | delete | insert }{@ | -}groupname
+```
+
+## Example
+
+In this example, `edb_audit_connect` and `edb_audit_statement` are set with the following non-default values:
+
+```ini
+logging_collector = 'on'
+edb_audit_connect = 'all'
+edb_audit = 'csv'
+edb_audit_statement = 'select, insert, update, delete'
+```
+
+The SQL statements invoked by the `SELECT`, `INSERT`, `UPDATE`, and `DELETE` commands are audited.
+
+The following is the database session that occurs:
+
+```sql
+$ psql edb enterprisedb
+Password for user enterprisedb:
+psql.bin (16.1.0)
+Type "help" for help.
+
+edb=# SHOW edb_audit_connect;
+__OUTPUT__
+ edb_audit_connect 
+-------------------
+ all
+(1 row)
+```
+```sql
+edb=# SHOW edb_audit_statement;
+__OUTPUT__
+      edb_audit_statement       
+--------------------------------
+ select, insert, update, delete
+(1 row)
+
+edb=# CREATE TABLE emp
+edb-#        (empno NUMBER(4) NOT NULL,
+edb(#         ename VARCHAR2(10),
+edb(#         job VARCHAR2(9),
+edb(#         mgr NUMBER(4),
+edb(#         hiredate DATE,
+edb(#         sal NUMBER(7, 2),
+edb(#         comm NUMBER(7, 2),
+edb(#         deptno NUMBER(2));
+CREATE TABLE
+
+edb=# ALTER TABLE emp SET (edb_audit_group = 'low_security');
+ALTER TABLE
+
+edb=# CREATE TABLE dept
+edb-#         (deptno NUMBER(2),
+edb(#          dname VARCHAR2(14),
+edb(#          loc VARCHAR2(13) ) with (edb_audit_group = 'low_security');
+CREATE TABLE
+
+edb=# CREATE TABLE bonus
+edb-#         (ename VARCHAR2(10),
+edb(#          job   VARCHAR2(9),
+edb(#          sal   NUMBER,
+edb(#          comm  NUMBER) with (edb_audit_group = 'high_security'); 
+CREATE TABLE
+
+edb=# CREATE TABLE sal
+edb-#         (grade NUMBER,
+edb(#          losal NUMBER,
+edb(#          hisal NUMBER) with (edb_audit_group = 'high_security');  
+CREATE TABLE
+    
+edb=# SET edb_audit_statement = 'select@low_security@high_security, insert@high_security-low_security, update-low_security@high_security, delete@low_security-high_security';
+SET
+```
+```sql
+edb=# SELECT reloptions FROM pg_class WHERE relname IN('emp', 'dept', 'bonus', 'sal');
+__OUTPUT__
+           reloptions            
+---------------------------------
+ {edb_audit_group=low_security}
+ {edb_audit_group=low_security}
+ {edb_audit_group=high_security}
+ {edb_audit_group=high_security}
+(4 rows)
+```
+```sql
+edb=# SELECT setting FROM pg_settings WHERE name = 'edb_audit_statement';
+__OUTPUT__
+                                                                  setting                                                                   
+--------------------------------------------------------------------------------------------------------------------------------------------
+ select@low_security@high_security, insert@high_security-low_security, update-low_security@high_security, delete@low_security-high_security
+(1 row)
+```
+```sql
+edb=# SELECT * FROM emp;
+__OUTPUT__
+ empno | ename | job | mgr | hiredate | sal | comm | deptno 
+-------+-------+-----+-----+----------+-----+------+--------
+(0 rows)
+```
+```sql
+edb=# SELECT * FROM dept;
+__OUTPUT__
+ deptno | dname | loc 
+--------+-------+-----
+(0 rows)
+```
+```sql
+edb=# SELECT * FROM bonus;
+__OUTPUT__
+ ename | job | sal | comm 
+-------+-----+-----+------
+(0 rows)
+```
+```sql
+edb=# SELECT * FROM sal;
+__OUTPUT__
+ grade | losal | hisal 
+-------+-------+-------
+(0 rows)
+```
+```sql
+edb=# INSERT INTO emp VALUES (7369, 'SMITH', 'CLERK', 7902, TO_DATE('17-DEC-1980', 'DD-MON-YYYY'), 800, NULL, 10);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES (7788, 'SCOTT', 'ANALYST', 7566, TO_DATE('09-DEC-1982', 'DD-MON-YYYY'), 3000, NULL, 20);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES (7566, 'JONES', 'MANAGER', 7839, TO_DATE('2-APR-1981', 'DD-MON-YYYY'), 2975, NULL, 30);
+INSERT 0 1
+
+edb=# INSERT INTO dept VALUES (10, 'ACCOUNTING', 'NEW YORK');
+INSERT 0 1
+edb=# INSERT INTO dept VALUES (20, 'RESEARCH', 'DALLAS');
+INSERT 0 1
+edb=# INSERT INTO dept VALUES (30, 'SALES', 'CHICAGO');
+INSERT 0 1
+edb=# INSERT INTO dept VALUES (40, 'OPERATIONS', 'BOSTON');
+INSERT 0 1
+
+edb=# INSERT INTO bonus VALUES ('SMITH', 'CLERK', 800, NULL);
+INSERT 0 1
+edb=# INSERT INTO bonus VALUES ('SCOTT', 'ANALYST', 3000, NULL);
+INSERT 0 1
+edb=# INSERT INTO bonus VALUES ('JONES', 'MANAGER', 2975, 300);
+INSERT 0 1
+
+edb=# INSERT INTO sal VALUES (3, 800, 1500);
+INSERT 0 1
+edb=# INSERT INTO sal VALUES (2, 2975, 4000);
+INSERT 0 1
+edb=# INSERT INTO sal VALUES (1, 3000, 5000);
+INSERT 0 1
+
+edb=# UPDATE emp SET sal = '5500' WHERE deptno = 10;
+UPDATE 1
+edb=# UPDATE dept SET loc = 'BEDFORD' WHERE deptno = 20;
+UPDATE 1
+edb=# UPDATE bonus SET sal = '4000' WHERE ename = 'SMITH';
+UPDATE 1
+edb=# UPDATE sal SET losal = '5000';
+UPDATE 3
+
+edb=# DELETE FROM emp WHERE deptno = 10;
+DELETE 1
+edb=# DELETE FROM dept WHERE deptno = 20;
+DELETE 1
+edb=# DELETE FROM bonus WHERE sal = 4000;
+DELETE 1
+edb=# DELETE FROM sal WHERE losal = 5000;
+DELETE 3
+```
+
+Setting the `edb_audit_statement` parameter to `'select@low_security@high_security, insert@high_security-low_security, update-low_security@high_security, delete@low_security-high_security'` for the `enterprisedb` user and `edb` database allows auditing of `SELECT`, `INSERT`, `UPDATE` or `DELETE` statements including `(@)` and excluding `-` for a group in the audit log file. 
+
+For a table in the log file:
+
+-  `select@low_security@high_security` audits `SELECT` statements of the `low_security` and `high_security` audit groups. 
+-  `insert@high_security-low_security` audits `INSERT` statements of `high_security` and excludes the insert statements of `low_security` audit group. 
+-  `update-low_security@high_security` audits `UPDATE` statements of `high_security` and excludes the update statements of the `low_security` audit group. 
+-  `delete@low_security-high_security` audits `DELETE` statements of `low_security` and excludes the delete statements of `high_security` audit group for a table in the log file.
+
+The resulting audit log file contains the following. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2021-07-20 01:45:27.077 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,1,"authentication",2021-07-20 01:45:27 IST,5/1,0,AUDIT,00000,"connection authorized: user=enterprisedb 
+database=edb",,,,,,,,,"","client backend",,"","","connect"
+
+2021-07-20 01:50:40.125 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,2,"SELECT",2021-07-20 01:45:27 IST,5/13,0,AUDIT,00000,"statement: SELECT * FROM emp;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+
+2021-07-20 01:50:53.778 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,3,"SELECT",2021-07-20 01:45:27 IST,5/14,0,AUDIT,00000,"statement: SELECT * FROM dept;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+
+2021-07-20 01:51:05.306 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,4,"SELECT",2021-07-20 01:45:27 IST,5/15,0,AUDIT,00000,"statement: SELECT * FROM bonus;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+
+2021-07-20 01:51:14.874 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,5,"SELECT",2021-07-20 01:45:27 IST,5/16,0,AUDIT,00000,"statement: SELECT * FROM sal;",,,,,,,,,
+"psql","client backend",,"SELECT","","select"
+
+2021-07-20 01:52:53.413 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,6,"INSERT",2021-07-20 01:45:27 IST,5/24,0,AUDIT,00000,"statement: INSERT INTO bonus VALUES ('SMITH', 'CLERK', 800, NULL);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:53:02.945 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,7,"INSERT",2021-07-20 01:45:27 IST,5/25,0,AUDIT,00000,"statement: INSERT INTO bonus VALUES ('SCOTT', 'ANALYST', 3000, NULL);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:53:12.064 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,8,"INSERT",2021-07-20 01:45:27 IST,5/26,0,AUDIT,00000,"statement: INSERT INTO bonus VALUES ('JONES', 'MANAGER', 2975, 300);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:53:23.836 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,9,"INSERT",2021-07-20 01:45:27 IST,5/27,0,AUDIT,00000,"statement: INSERT INTO sal VALUES (3, 800, 1500);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:53:33.280 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,10,"INSERT",2021-07-20 01:45:27 IST,5/28,0,AUDIT,00000,"statement: INSERT INTO sal VALUES (2, 2975, 4000);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:53:42.388 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,11,"INSERT",2021-07-20 01:45:27 IST,5/29,0,AUDIT,00000,"statement: INSERT INTO sal VALUES (1, 3000, 5000);
+",,,,,,,,,"psql","client backend",,"INSERT","","insert"
+
+2021-07-20 01:54:17.126 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,12,"UPDATE",2021-07-20 01:45:27 IST,5/32,0,AUDIT,00000,"statement: UPDATE bonus SET sal = '4000' WHERE ename = 'SMITH';
+",,,,,,,,,"psql","client backend",,"UPDATE","","update"
+
+2021-07-20 01:54:34.344 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,13,"UPDATE",2021-07-20 01:45:27 IST,5/33,0,AUDIT,00000,"statement: UPDATE sal SET losal = '5000';
+",,,,,,,,,"psql","client backend",,"UPDATE","","update"
+
+2021-07-20 01:54:45.887 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,14,"DELETE",2021-07-20 01:45:27 IST,5/34,0,AUDIT,00000,"statement: DELETE FROM emp WHERE deptno = 10;
+",,,,,,,,,"psql","client backend",,"DELETE","","delete"
+
+2021-07-20 01:54:54.513 IST,"enterprisedb","edb",87490,"[local]",60f662f7.
+155c2,15,"DELETE",2021-07-20 01:45:27 IST,5/35,0,AUDIT,00000,"statement: DELETE FROM dept WHERE deptno = 20;
+",,,,,,,,,"psql","client backend",,"DELETE","","delete"
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/index.mdx b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/index.mdx
new file mode 100644
index 00000000000..032a65cb292
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/05_edb_audit_logging/index.mdx
@@ -0,0 +1,24 @@
+---
+title: Using EDB audit logging
+navTitle: "EDB audit logging"
+indexCards: simple
+description: "Enables database and security administrators, auditors, and operators to track and analyze database activities"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_audit_logging" class="registered_link"></div>
+
+EDB Postgres Advanced Server allows database and security administrators, auditors, and operators to track and analyze database activities using EDB *audit logging*. EDB audit logging generates audit log files, which  can be  configured to record information such as:
+
+-   When a role establishes a connection to an EDB Postgres Advanced Server database
+-   The database objects a role creates, modifies, or deletes when connected to EDB Postgres Advanced Server
+-   When any failed authentication attempts occur
+
+The parameters specified in the configuration files `postgresql.conf` or `postgresql.auto.conf` control the information included in the audit logs.
+
+<div class="toctree" maxdepth="3">
+
+audit_logging_configuration_parameters selecting_sql_statements_to_audit enabling_audit_logging audit_log_file using_error_codes_to_filter_audit_logs using_command_tags_to_filter_audit_logs redacting_passwords_from_audit_logs audit_log_archiving object_auditing
+
+</div>
diff --git a/product_docs/docs/epas/16/epas_security_guide/index.mdx b/product_docs/docs/epas/16/epas_security_guide/index.mdx
new file mode 100644
index 00000000000..bb416ee7d99
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/index.mdx
@@ -0,0 +1,16 @@
+---
+navTitle: Implementing security features
+title: "EDB Postgres Advanced Server security features"
+indexCards: simple
+navigation:
+- tde_feature
+- 05_edb_audit_logging
+- 02_protecting_against_sql_injection_attacks
+- 04_sslutils
+- 03_edb_wrap
+- 04_profile_management
+- 05_data_redaction
+- 03_virtual_private_database
+---
+
+EDB Postgres Advanced Server extends Postgres security with features designed to limit unauthorized access. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx b/product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx
new file mode 100644
index 00000000000..cbcaaf5ce69
--- /dev/null
+++ b/product_docs/docs/epas/16/epas_security_guide/tde_feature.mdx
@@ -0,0 +1,12 @@
+---
+title: "Transparent Data Encryption overview"
+description: "Provides an overview of the benefits of the Transparent Data Encryption feature"
+---
+
+Transparent Data Encryption (TDE) is an optional encryption method that protects data in the database by encrypting the underlying files.
+
+TDE is transparent to authorized users of the database, as no change is required in the applications or existing access policies. It's supported by EDB Postgres Advanced Server and EDB Postgres Extended Server, in versions 15 and above, with high availability.
+
+TDE hardens your organization’s data security with minimum performance overhead and doesn't require additional storage. TDE also enables developers to secure their data using secure encryption algorithms without changing their applications. The feature securely stores individual tablespaces and logs encrypted with their own encryption keys, ensuring security of user data while preserving ease of management for database administrators.
+
+For information about how to enable transparent data encryption and work with the encrypted files, see the [Transparent Data Encryption](/tde/latest/) documentation.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/fundamentals/epas_fundamentals/benefits_epas.mdx b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/benefits_epas.mdx
new file mode 100644
index 00000000000..9bde8de3fc0
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/benefits_epas.mdx
@@ -0,0 +1,23 @@
+---
+title: "Benefits of EDB Postgres Advanced Server"
+description: "Describes the functionality included in EDB Postgres Advanced Server that bring value to your installation"
+---
+
+EDB Postgres Advanced Server is a stand-alone proprietary database server that adds extended functionality to the open-source PostgreSQL database. 
+
+EDB Postgres Advanced Server is designed to provide enterprise capabilities on top of the features present in community Postgres. These capabilities:
+
+- [Help database administrators to maintain and operate EDB Postgres Advanced Server databases](../../database_administration)
+- [Include enhanced SQL functionality and other features that add flexibility and convenience](../../application_programming/15_enhanced_sql_and_other_misc_features/)
+- [Extend Postgres security with features designed to limit unauthorized access](../../epas_security_guide)
+- [Assist with performance monitoring and analysis](../../managing_performance)
+- [Include multiple features designed to increase application programmer productivity](../../application_programming)
+- [Advanced replication support (version 14 and higher)](https://www.enterprisedb.com/docs/pgd/latest/). 
+
+EDB Postgres Advanced Server also has a significant amount of [Oracle compatibility features](../../working_with_oracle_data) which facilitate Oracle to Postgres migrations. 
+
+EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications, as well as compatible procedural logic, data types, system catalog views and other features that enable EDB’s Oracle compatible connectors, EDB\*Plus, EDB\*Loader and many other tools and functionality. 
+
+Major versions of EDB Postgres Advanced Server are released yearly in line with the major version release of PostgreSQL. EDB Postgres Advanced Server is normally released one to two months after PostgreSQL major version releases. 
+
+EDB Postgres Advanced Server is supported on [Linux x86-64](../../installing/linux_x86_64/), Linux on [IBM Power](../../installing/linux_ppc64le/) and [Windows x86-64](../../installing/windows/).
diff --git a/product_docs/docs/epas/16/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx
new file mode 100644
index 00000000000..3db9a225605
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/index.mdx
@@ -0,0 +1,32 @@
+---
+navTitle: Overview of Oracle compatibility
+title: "Database compatibility for Oracle developers"
+description: "Provides a high-level view of Oracle compatibility features"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/toc.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.001.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/toc.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="introduction" class="registered_link"></div>
+
+EDB Postgres Advanced Server makes Postgres look, feel, and operate more like Oracle, so when you migrate, there is less code to rewrite, and you can be up and running quickly. The Oracle compatibility features allow you to run many applications written for Oracle in EDB Postgres Advanced Server with minimal to no changes. 
+
+EDB Postgres Advanced Server provides Oracle compatible:
+- [Stored procedure language (SPL)](../../../application_programming/epas_compat_spl/) when creating database server-side application logic for stored procedures, functions, triggers, and packages   
+- [Data types that are compatible with Oracle databases](../../../reference/sql_reference/02_data_types/)
+- [SQL statements](../../../reference/sql_reference/01_sql_syntax/) that are compatible with Oracle SQL
+- [System and built-in functions](../../../reference/sql_reference/03_functions_and_operators/) for use in SQL statements and procedural logic
+- [System catalog views](../../../reference/oracle_compatibility_reference/epas_compat_cat_views/)  that are compatible with Oracle’s data dictionary
+- [Additional compatibility with Oracle MERGE](../../../reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx). 
+
+
+!!!SeeAlso "Further reading"
+   - Compatible SQL syntax, data types, and views in [SQL reference](../../../reference/oracle_compatibility_reference/epas_compat_sql/).
+   - Compatibility offered by the procedures and functions that are part of the built-in packages in [Built-in packages](../../../reference/oracle_compatibility_reference/epas_compat_bip_guide/).
+   - Compatible tools and utilities (EDB\*Plus, EDB\*Loader, DRITA, and EDB\*Wrap) that are included with an EDB Postgres Advanced Server installation in [Tools, utilities, and components](../../../tools_utilities_and_components/database_administration_tools/09_tools_and_utilities/).
+   - For applications written using the Oracle Call Interface (OCI), EDB’s Open Client Library (OCL) provides interoperability with these applications. See [EDB OCL Connector](/ocl_connector/latest/).
+
diff --git a/product_docs/docs/epas/16/fundamentals/epas_fundamentals/index.mdx b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/index.mdx
new file mode 100644
index 00000000000..36e39dfbcb4
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "EDB Postgres Advanced Server fundamentals"
+description: "Describes the key concepts to help you successfully deploy and manage EDB Postgres Advanced Server"
+indexCards: simple
+---
+
+EDB Postgres Advanced Server provides tools you can use to administer enterprise-scale data solutions. These essential concepts help you to design, implement, and manage EDB Postgres Advanced Server. 
diff --git a/product_docs/docs/epas/16/fundamentals/epas_fundamentals/terminology.mdx b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/terminology.mdx
new file mode 100644
index 00000000000..2fc781acd6d
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/epas_fundamentals/terminology.mdx
@@ -0,0 +1,19 @@
+---
+title: "Terminology"
+navTitle: "Terminology"
+description: "Introduces some terminology essential to understanding EDB Postgres Advanced Server"
+redirects:
+  - /epas/latest/terminology/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The terminology that follows is important for understanding EDB Postgres Advanced Server's functionality and its components.
+
+## Database server (postmaster) 
+The server process that provides the key functionality that allows you to store and manage data. It manages the database files, accepts connections to the database from client applications, and performs database actions on behalf of the clients. The database server process is called *postgres*.
+
+## Database cluster 
+A set of on-disk structures that comprise a collection of databases. A cluster is serviced by a single-instance of the database server. A database cluster is stored in the `data` directory. Don't store the `data` directory of a production database on an NFS file system.
+
+## Configuration files
+You can use the parameters listed in Postgres configuration files to manage deployment preferences, security preferences, connection behaviors, and logging preferences.
+
diff --git a/product_docs/docs/epas/16/fundamentals/index.mdx b/product_docs/docs/epas/16/fundamentals/index.mdx
new file mode 100644
index 00000000000..f4c1c853f3a
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Fundamentals"
+navigation:
+- epas_fundamentals
+- sql_fundamentals
+indexCards: simple
+---
+
+The key concepts of EDB Postgres Advanced Server include its features, benefits, and terminology. The SQL tutorial uses a sample database and explains important database concepts. 
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_about_the_examples_used_in_this_guide.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_about_the_examples_used_in_this_guide.mdx
new file mode 100644
index 00000000000..2a60aca5a3f
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_about_the_examples_used_in_this_guide.mdx
@@ -0,0 +1,54 @@
+---
+title: "About the examples"
+description: "Provides information about the presentation and usage of the examples used in the documentation"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.007.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.007.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_about_the_examples_used_in_this_guide/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="about_the_examples_used_in_this_guide" class="registered_link"></div>
+
+The examples shown in the documentation use the PSQL program. PSQL is a terminal-based command line interface for Postgres. The prompt that normally appears when using PSQL is omitted in these examples to provide extra clarity for the point being shown.
+
+```text
+Examples and output from examples are shown in a fixed-width, white font on a dark background.
+```
+
+Consider the following key points related to the examples:
+
+-   During installation of the EDB Postgres Advanced Server, you must make selections for configuration and defaults compatible with Oracle databases to reproduce the same results as the examples. You can verify a default compatible configuration by issuing the following commands in PSQL and returning the results shown:
+
+    ```sql
+    SHOW edb_redwood_date;
+
+     edb_redwood_date
+    ------------------
+     on
+
+    SHOW datestyle;
+
+     DateStyle
+    --------------
+     Redwood, DMY
+
+    SHOW edb_redwood_strings;
+
+     edb_redwood_strings
+    ---------------------
+     on
+    ```
+
+-   The examples use the sample tables, `dept`, `emp`, and `jobhist`, created and loaded when EDB Postgres Advanced Server was installed. The `emp` table is installed with triggers that you must disable to reproduce the same results as the examples. Log in to EDB Postgres Advanced Server as the enterprisedb superuser, and disable the triggers by issuing the following command:
+-   
+    ```sql
+    ALTER TABLE emp DISABLE TRIGGER USER;
+    ```
+    
+    You can later reactivate the triggers on the `emp` table with the following command:
+    
+    ```sql
+    ALTER TABLE emp ENABLE TRIGGER USER;
+    ```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_conventions.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_conventions.mdx
new file mode 100644
index 00000000000..1d2fb03e95c
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_conventions.mdx
@@ -0,0 +1,20 @@
+---
+title: "Conventions used"
+description: "Provides information about the conventions used in the documentation"
+redirects:
+  - /epas/latest/epas_guide/01_introduction/02_conventions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="conventions" class="registered_link"></div>
+
+The conventions used in the documentation described here apply to both Linux and Windows systems. 
+
+Directory paths are presented in the Linux format with forward slashes. When working on Windows systems, start the directory path with the drive letter followed by a colon, and substitute back slashes for forward slashes.
+
+Some of this information might apply interchangeably to the PostgreSQL and EDB Postgres Advanced Server database systems. The term *EDB Postgres Advanced Server* is used to refer to EDB Postgres Advanced Server. The term *Postgres* is used to generically refer to both PostgreSQL and EDB Postgres Advanced Server. When a distinction must be made between these two database systems, the specific names&mdash;PostgreSQL or EDB Postgres Advanced Server&mdash;are used.
+
+The installation directory path of the PostgreSQL or EDB Postgres Advanced Server products is referred to as *POSTGRES_INSTALL_HOME*.
+
+-   For EDB Postgres Advanced Server Linux installations performed using the interactive installer for version 10 and earlier, the default is `/opt/edb/asx.x`.
+-   For EDB Postgres Advanced Server Linux installations performed using an RPM package, the default is `/usr/edb/as<xx>` where `<xx>` is the EDB Postgres Advanced Server version number.
+-   For EDB Postgres Advanced Server Windows installations, the default is `C:\Program Files\edb\as<xx>`. The product version number is represented by `x.x` or by `xx` for version 10 and later.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/01_sample_database_installation.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/01_sample_database_installation.mdx
new file mode 100644
index 00000000000..9806fc21e42
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/01_sample_database_installation.mdx
@@ -0,0 +1,23 @@
+---
+title: "Accessing the sample database"
+description: "Describes the characteristics of the sample database installation"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/01_sample_database/01_sample_database_installation/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sample_database_installation" class="registered_link"></div>
+
+When EDB Postgres Advanced Server is installed, a sample database named `edb` is automatically created. This sample database contains the tables and programs used in this tutorial after you execute the script `edb-sample.sql`, located in the `/usr/edb/as16/share` directory.
+
+This script does the following:
+
+-   Creates the sample tables and programs in the currently connected database
+-   Grants all permissions on the tables to the `PUBLIC` group
+
+The tables and programs are created in the first schema of the search path in which the current user has permission to create tables and procedures. You can display the search path by issuing the command:
+
+```sql
+SHOW SEARCH_PATH;
+```
+
+You can alter the search path using commands in PSQL, a terminal-based front end to Postgres.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/02_sample_database_description.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/02_sample_database_description.mdx
new file mode 100644
index 00000000000..95b6899c775
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/02_sample_database_description.mdx
@@ -0,0 +1,560 @@
+---
+title: "Overview of the sample database"
+description: "Describes the key elements of the sample database"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/01_sample_database/02_sample_database_description/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sample_database_description" class="registered_link"></div>
+
+The sample database represents employees in an organization. It contains three types of records: employees, departments, and historical records of employees.
+
+Each employee has an identification number, name, hire date, salary, and manager. Some employees earn a commission in addition to their salary. All employee-related information is stored in the `emp` table.
+
+The sample company is regionally diverse, so the database keeps track of the location of the departments. Each company employee is assigned to a department. Each department is identified by a unique department number and a short name. Each department is associated with one location. All department-related information is stored in the `dept` table.
+
+The company also tracks information about jobs held by the employees. Some employees have been with the company for a long time and have held different positions, received raises, switched departments, and so on. When a change in employee status occurs, the company records the end date of the former position. A new job record is added with the start date and the new job title, department, salary, and the reason for the status change. All employee history is maintained in the `jobhist` table.
+
+The following is an entity relationship diagram of the sample database tables.
+
+![Sample Database Tables](../../../../images/sample_database_tables.png)
+
+<div style="text-align: center"> Fig. 1: Sample Database Tables </div>
+
+
+The `edb-sample.sql` script is:
+
+```sql
+--
+--  Script that creates the 'sample' tables, views, procedures,
+--  functions, triggers, etc.
+--
+--  Start new transaction - commit all or nothing
+--
+BEGIN;
+/
+--
+--  Create and load tables used in the documentation examples.
+--
+--  Create the 'dept' table
+--
+CREATE TABLE dept (
+   deptno           NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+   dname            VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+   loc              VARCHAR2(13)
+);
+--
+--  Create the 'emp' table
+--
+CREATE TABLE emp (
+   empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+   ename           VARCHAR2(10),
+   job             VARCHAR2(9),
+   mgr             NUMBER(4),
+   hiredate        DATE,
+   sal             NUMBER(7,2) CONSTRAINT emp_sal_ck CHECK (sal > 0),
+   comm            NUMBER(7,2),
+   deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                       REFERENCES dept(deptno)
+);
+--
+--  Create the 'jobhist' table
+--
+CREATE TABLE jobhist (
+   empno           NUMBER(4) NOT NULL,
+   startdate       DATE NOT NULL,
+   enddate         DATE,
+   job             VARCHAR2(9),
+   sal             NUMBER(7,2),
+   comm            NUMBER(7,2),
+   deptno          NUMBER(2),
+   chgdesc         VARCHAR2(80),
+   CONSTRAINT jobhist_pk PRIMARY KEY (empno, startdate),
+   CONSTRAINT jobhist_ref_emp_fk FOREIGN KEY (empno)
+       REFERENCES emp(empno) ON DELETE CASCADE,
+   CONSTRAINT jobhist_ref_dept_fk FOREIGN KEY (deptno)
+       REFERENCES dept (deptno) ON DELETE SET NULL,
+   CONSTRAINT jobhist_date_chk CHECK (startdate <= enddate)
+);
+--
+--  Create the 'salesemp' view
+--
+CREATE OR REPLACE VIEW salesemp AS
+   SELECT empno, ename, hiredate, sal, comm FROM emp WHERE job = 'SALESMAN';
+--
+--  Sequence to generate values for function 'new_empno'.
+--
+CREATE SEQUENCE next_empno START WITH 8000 INCREMENT BY 1;
+--
+--  Issue PUBLIC grants
+--
+GRANT ALL ON emp TO PUBLIC;
+GRANT ALL ON dept TO PUBLIC;
+GRANT ALL ON jobhist TO PUBLIC;
+GRANT ALL ON salesemp TO PUBLIC;
+GRANT ALL ON next_empno TO PUBLIC;
+--
+--  Load the 'dept' table
+--
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+INSERT INTO dept VALUES (20,'RESEARCH','DALLAS');
+INSERT INTO dept VALUES (30,'SALES','CHICAGO');
+INSERT INTO dept VALUES (40,'OPERATIONS','BOSTON');
+--
+--  Load the 'emp' table
+--
+INSERT INTO emp VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
+INSERT INTO emp VALUES (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
+INSERT INTO emp VALUES (7521,'WARD','SALESMAN',7698,'22-FEB-81',1250,500,30);
+INSERT INTO emp VALUES (7566,'JONES','MANAGER',7839,'02-APR-81',2975,NULL,20);
+INSERT INTO emp VALUES (7654,'MARTIN','SALESMAN',7698,'28-SEP-81',1250,1400,30);
+INSERT INTO emp VALUES (7698,'BLAKE','MANAGER',7839,'01-MAY-81',2850,NULL,30);
+INSERT INTO emp VALUES (7782,'CLARK','MANAGER',7839,'09-JUN-81',2450,NULL,10);
+INSERT INTO emp VALUES (7788,'SCOTT','ANALYST',7566,'19-APR-87',3000,NULL,20);
+INSERT INTO emp VALUES (7839,'KING','PRESIDENT',NULL,'17-NOV-81',5000,NULL,10);
+INSERT INTO emp VALUES (7844,'TURNER','SALESMAN',7698,'08-SEP-81',1500,0,30);
+INSERT INTO emp VALUES (7876,'ADAMS','CLERK',7788,'23-MAY-87',1100,NULL,20);
+INSERT INTO emp VALUES (7900,'JAMES','CLERK',7698,'03-DEC-81',950,NULL,30);
+INSERT INTO emp VALUES (7902,'FORD','ANALYST',7566,'03-DEC-81',3000,NULL,20);
+INSERT INTO emp VALUES (7934,'MILLER','CLERK',7782,'23-JAN-82',1300,NULL,10);
+--
+--  Load the 'jobhist' table
+--
+INSERT INTO jobhist VALUES (7369,'17-DEC-80',NULL,'CLERK',800,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7499,'20-FEB-81',NULL,'SALESMAN',1600,300,30,'New Hire');
+INSERT INTO jobhist VALUES (7521,'22-FEB-81',NULL,'SALESMAN',1250,500,30,'New Hire');
+INSERT INTO jobhist VALUES (7566,'02-APR-81',NULL,'MANAGER',2975,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7654,'28-SEP-81',NULL,'SALESMAN',1250,1400,30,'New Hire');
+INSERT INTO jobhist VALUES (7698,'01-MAY-81',NULL,'MANAGER',2850,NULL,30,'New Hire');
+INSERT INTO jobhist VALUES (7782,'09-JUN-81',NULL,'MANAGER',2450,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7788,'19-APR-87','12-APR-88','CLERK',1000,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7788,'13-APR-88','04-MAY-89','CLERK',1040,NULL,20,'Raise');
+INSERT INTO jobhist VALUES (7788,'05-MAY-90',NULL,'ANALYST',3000,NULL,20,'Promoted to Analyst');
+INSERT INTO jobhist VALUES (7839,'17-NOV-81',NULL,'PRESIDENT',5000,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7844,'08-SEP-81',NULL,'SALESMAN',1500,0,30,'New Hire');
+INSERT INTO jobhist VALUES (7876,'23-MAY-87',NULL,'CLERK',1100,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7900,'03-DEC-81','14-JAN-83','CLERK',950,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7900,'15-JAN-83',NULL,'CLERK',950,NULL,30,'Changed to Dept 30');
+INSERT INTO jobhist VALUES (7902,'03-DEC-81',NULL,'ANALYST',3000,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7934,'23-JAN-82',NULL,'CLERK',1300,NULL,10,'New Hire');
+--
+--  Populate statistics table and view (pg_statistic/pg_stats)
+--
+ANALYZE dept;
+ANALYZE emp;
+ANALYZE jobhist;
+--
+--  Procedure that lists all employees' numbers and names
+--  from the 'emp' table using a cursor.
+--
+CREATE OR REPLACE PROCEDURE list_emp
+IS
+   v_empno         NUMBER(4);
+   v_ename         VARCHAR2(10);
+   CURSOR emp_cur IS
+       SELECT empno, ename FROM emp ORDER BY empno;
+BEGIN
+   OPEN emp_cur;
+   DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+   DBMS_OUTPUT.PUT_LINE('-----    -------');
+   LOOP
+       FETCH emp_cur INTO v_empno, v_ename;
+       EXIT WHEN emp_cur%NOTFOUND;
+       DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+   END LOOP;
+   CLOSE emp_cur;
+END;
+/
+--
+--  Procedure that selects an employee row given the employee
+--  number and displays certain columns.
+--
+CREATE OR REPLACE PROCEDURE select_emp (
+   p_empno         IN  NUMBER
+)
+IS
+   v_ename         emp.ename%TYPE;
+   v_hiredate      emp.hiredate%TYPE;
+   v_sal           emp.sal%TYPE;
+   v_comm          emp.comm%TYPE;
+   v_dname         dept.dname%TYPE;
+   v_disp_date     VARCHAR2(10);
+BEGIN
+   SELECT ename, hiredate, sal, NVL(comm, 0), dname
+       INTO v_ename, v_hiredate, v_sal, v_comm, v_dname
+       FROM emp e, dept d
+       WHERE empno = p_empno
+       AND e.deptno = d.deptno;
+   v_disp_date := TO_CHAR(v_hiredate, 'MM/DD/YYYY');
+   DBMS_OUTPUT.PUT_LINE('Number    : ' || p_empno);
+   DBMS_OUTPUT.PUT_LINE('Name      : ' || v_ename);
+   DBMS_OUTPUT.PUT_LINE('Hire Date : ' || v_disp_date);
+   DBMS_OUTPUT.PUT_LINE('Salary    : ' || v_sal);
+   DBMS_OUTPUT.PUT_LINE('Commission: ' || v_comm);
+   DBMS_OUTPUT.PUT_LINE('Department: ' || v_dname);
+EXCEPTION
+   WHEN NO_DATA_FOUND THEN
+       DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno || ' not found');
+   WHEN OTHERS THEN
+       DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+       DBMS_OUTPUT.PUT_LINE(SQLERRM);
+       DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+       DBMS_OUTPUT.PUT_LINE(SQLCODE);
+END;
+/
+--
+--  Procedure that queries the 'emp' table based on
+--  department number and employee number or name.  Returns
+--  employee number and name as IN OUT parameters and job,
+--  hire date, and salary as OUT parameters.
+--
+CREATE OR REPLACE PROCEDURE emp_query (
+   p_deptno        IN     NUMBER,
+   p_empno         IN OUT NUMBER,
+   p_ename         IN OUT VARCHAR2,
+   p_job           OUT    VARCHAR2,
+   p_hiredate      OUT    DATE,
+   p_sal           OUT    NUMBER
+)
+IS
+BEGIN
+   SELECT empno, ename, job, hiredate, sal
+       INTO p_empno, p_ename, p_job, p_hiredate, p_sal
+       FROM emp
+       WHERE deptno = p_deptno
+         AND (empno = p_empno
+          OR  ename = UPPER(p_ename));
+END;
+/
+--
+--  Procedure to call 'emp_query_caller' with IN and IN OUT
+--  parameters.  Displays the results received from IN OUT and
+--  OUT parameters.
+--
+CREATE OR REPLACE PROCEDURE emp_query_caller
+IS
+   v_deptno        NUMBER(2);
+   v_empno         NUMBER(4);
+   v_ename         VARCHAR2(10);
+   v_job           VARCHAR2(9);
+   v_hiredate      DATE;
+   v_sal           NUMBER;
+BEGIN
+   v_deptno := 30;
+   v_empno  := 0;
+   v_ename  := 'Martin';
+   emp_query(v_deptno, v_empno, v_ename, v_job, v_hiredate, v_sal);
+   DBMS_OUTPUT.PUT_LINE('Department : ' || v_deptno);
+   DBMS_OUTPUT.PUT_LINE('Employee No: ' || v_empno);
+   DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+   DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+   DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+   DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+EXCEPTION
+   WHEN TOO_MANY_ROWS THEN
+       DBMS_OUTPUT.PUT_LINE('More than one employee was selected');
+   WHEN NO_DATA_FOUND THEN
+       DBMS_OUTPUT.PUT_LINE('No employees were selected');
+END;
+/
+--
+--  Function to compute yearly compensation based on semimonthly
+--  salary.
+--
+CREATE OR REPLACE FUNCTION emp_comp (
+   p_sal           NUMBER,
+   p_comm          NUMBER
+) RETURN NUMBER
+IS
+BEGIN
+   RETURN (p_sal + NVL(p_comm, 0)) * 24;
+END;
+/
+--
+--  Function that gets the next number from sequence, 'next_empno',
+--  and ensures it is not already in use as an employee number.
+--
+CREATE OR REPLACE FUNCTION new_empno RETURN NUMBER
+IS
+   v_cnt           INTEGER := 1;
+   v_new_empno     NUMBER;
+BEGIN
+   WHILE v_cnt > 0 LOOP
+       SELECT next_empno.nextval INTO v_new_empno FROM dual;
+       SELECT COUNT(*) INTO v_cnt FROM emp WHERE empno = v_new_empno;
+   END LOOP;
+   RETURN v_new_empno;
+END;
+/
+--
+--  EDB-SPL function that adds a new clerk to table 'emp'.  This function
+--  uses package 'emp_admin'.
+--
+CREATE OR REPLACE FUNCTION hire_clerk (
+   p_ename         VARCHAR2,
+   p_deptno        NUMBER
+) RETURN NUMBER
+IS
+   v_empno         NUMBER(4);
+   v_ename         VARCHAR2(10);
+   v_job           VARCHAR2(9);
+   v_mgr           NUMBER(4);
+   v_hiredate      DATE;
+   v_sal           NUMBER(7,2);
+   v_comm          NUMBER(7,2);
+   v_deptno        NUMBER(2);
+BEGIN
+   v_empno := new_empno;
+   INSERT INTO emp VALUES (v_empno, p_ename, 'CLERK', 7782,
+       TRUNC(SYSDATE), 950.00, NULL, p_deptno);
+   SELECT empno, ename, job, mgr, hiredate, sal, comm, deptno INTO
+       v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
+       FROM emp WHERE empno = v_empno;
+   DBMS_OUTPUT.PUT_LINE('Department : ' || v_deptno);
+   DBMS_OUTPUT.PUT_LINE('Employee No: ' || v_empno);
+   DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+   DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+   DBMS_OUTPUT.PUT_LINE('Manager    : ' || v_mgr);
+   DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || v_hiredate);
+   DBMS_OUTPUT.PUT_LINE('Salary     : ' || v_sal);
+   DBMS_OUTPUT.PUT_LINE('Commission : ' || v_comm);
+   RETURN v_empno;
+EXCEPTION
+   WHEN OTHERS THEN
+       DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+       DBMS_OUTPUT.PUT_LINE(SQLERRM);
+       DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+       DBMS_OUTPUT.PUT_LINE(SQLCODE);
+       RETURN -1;
+END;
+/
+--
+--  PostgreSQL PL/pgSQL function that adds a new salesman
+--  to table 'emp'.
+--
+CREATE OR REPLACE FUNCTION hire_salesman (
+   p_ename         VARCHAR,
+   p_sal           NUMERIC,
+   p_comm          NUMERIC
+) RETURNS NUMERIC
+AS $$
+DECLARE
+   v_empno         NUMERIC(4);
+   v_ename         VARCHAR(10);
+   v_job           VARCHAR(9);
+   v_mgr           NUMERIC(4);
+   v_hiredate      DATE;
+   v_sal           NUMERIC(7,2);
+   v_comm          NUMERIC(7,2);
+   v_deptno        NUMERIC(2);
+BEGIN
+   v_empno := new_empno();
+   INSERT INTO emp VALUES (v_empno, p_ename, 'SALESMAN', 7698,
+       CURRENT_DATE, p_sal, p_comm, 30);
+   SELECT INTO
+       v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
+       empno, ename, job, mgr, hiredate, sal, comm, deptno
+       FROM emp WHERE empno = v_empno;
+   RAISE INFO 'Department : %', v_deptno;
+   RAISE INFO 'Employee No: %', v_empno;
+   RAISE INFO 'Name       : %', v_ename;
+   RAISE INFO 'Job        : %', v_job;
+   RAISE INFO 'Manager    : %', v_mgr;
+   RAISE INFO 'Hire Date  : %', v_hiredate;
+   RAISE INFO 'Salary     : %', v_sal;
+   RAISE INFO 'Commission : %', v_comm;
+   RETURN v_empno;
+EXCEPTION
+   WHEN OTHERS THEN
+       RAISE INFO 'The following is SQLERRM:';
+       RAISE INFO '%', SQLERRM;
+       RAISE INFO 'The following is SQLSTATE:';
+       RAISE INFO '%', SQLSTATE;
+       RETURN -1;
+END;
+$$ LANGUAGE 'plpgsql';
+/
+--
+--  Rule to INSERT into view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_i AS ON INSERT TO salesemp
+DO INSTEAD
+   INSERT INTO emp VALUES (NEW.empno, NEW.ename, 'SALESMAN', 7698,
+       NEW.hiredate, NEW.sal, NEW.comm, 30);
+--
+--  Rule to UPDATE view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_u AS ON UPDATE TO salesemp
+DO INSTEAD
+   UPDATE emp SET empno    = NEW.empno,
+                  ename    = NEW.ename,
+                  hiredate = NEW.hiredate,
+                  sal      = NEW.sal,
+                  comm     = NEW.comm
+       WHERE empno = OLD.empno;
+--
+--  Rule to DELETE from view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_d AS ON DELETE TO salesemp
+DO INSTEAD
+   DELETE FROM emp WHERE empno = OLD.empno;
+--
+--  After statement-level trigger that displays a message after
+--  an insert, update, or deletion to the 'emp' table.  One message
+--  per SQL command is displayed.
+--
+CREATE OR REPLACE TRIGGER user_audit_trig
+   AFTER INSERT OR UPDATE OR DELETE ON emp
+DECLARE
+   v_action        VARCHAR2(24);
+BEGIN
+   IF INSERTING THEN
+       v_action := ' added employee(s) on ';
+   ELSIF UPDATING THEN
+       v_action := ' updated employee(s) on ';
+   ELSIF DELETING THEN
+       v_action := ' deleted employee(s) on ';
+   END IF;
+   DBMS_OUTPUT.PUT_LINE('User ' || USER || v_action ||
+TO_CHAR(SYSDATE,'YYYY-MM-DD'));
+END;
+/
+--
+--  Before row-level trigger that displays employee number and
+--  salary of an employee that is about to be added, updated,
+--  or deleted in the 'emp' table.
+--
+CREATE OR REPLACE TRIGGER emp_sal_trig
+   BEFORE DELETE OR INSERT OR UPDATE ON emp
+   FOR EACH ROW
+DECLARE
+   sal_diff       NUMBER;
+BEGIN
+   IF INSERTING THEN
+       DBMS_OUTPUT.PUT_LINE('Inserting employee ' || :NEW.empno);
+       DBMS_OUTPUT.PUT_LINE('..New salary: ' || :NEW.sal);
+   END IF;
+   IF UPDATING THEN
+       sal_diff := :NEW.sal - :OLD.sal;
+       DBMS_OUTPUT.PUT_LINE('Updating employee ' || :OLD.empno);
+       DBMS_OUTPUT.PUT_LINE('..Old salary: ' || :OLD.sal);
+       DBMS_OUTPUT.PUT_LINE('..New salary: ' || :NEW.sal);
+       DBMS_OUTPUT.PUT_LINE('..Raise     : ' || sal_diff);
+    END IF;
+    IF DELETING THEN
+       DBMS_OUTPUT.PUT_LINE('Deleting employee ' || :OLD.empno);
+       DBMS_OUTPUT.PUT_LINE('..Old salary: ' || :OLD.sal);
+    END IF;
+END;
+/
+--
+--  Package specification for the 'emp_admin' package.
+--
+CREATE OR REPLACE PACKAGE emp_admin
+IS
+   FUNCTION get_dept_name (
+       p_deptno        NUMBER
+   ) RETURN VARCHAR2;
+   FUNCTION update_emp_sal (
+       p_empno         NUMBER,
+       p_raise         NUMBER
+   ) RETURN NUMBER;
+   PROCEDURE hire_emp (
+       p_empno         NUMBER,
+       p_ename         VARCHAR2,
+       p_job           VARCHAR2,
+       p_sal           NUMBER,
+       p_hiredate      DATE,
+       p_comm          NUMBER,
+       p_mgr           NUMBER,
+       p_deptno        NUMBER
+   );
+   PROCEDURE fire_emp (
+       p_empno         NUMBER
+   );
+END emp_admin;
+/
+--
+--  Package body for the 'emp_admin' package.
+--
+CREATE OR REPLACE PACKAGE BODY emp_admin
+IS
+   --
+   --  Function that queries the 'dept' table based on the department
+   --  number and returns the corresponding department name.
+   --
+   FUNCTION get_dept_name (
+       p_deptno        IN NUMBER
+   ) RETURN VARCHAR2
+   IS
+       v_dname         VARCHAR2(14);
+   BEGIN
+       SELECT dname INTO v_dname FROM dept WHERE deptno = p_deptno;
+       RETURN v_dname;
+   EXCEPTION
+       WHEN NO_DATA_FOUND THEN
+           DBMS_OUTPUT.PUT_LINE('Invalid department number ' || p_deptno);
+           RETURN '';
+   END;
+   --
+   --  Function that updates an employee's salary based on the
+   --  employee number and salary increment/decrement passed
+   --  as IN parameters.  Upon successful completion the function
+   --  returns the new updated salary.
+   --
+   FUNCTION update_emp_sal (
+       p_empno         IN NUMBER,
+       p_raise         IN NUMBER
+   ) RETURN NUMBER
+   IS
+       v_sal           NUMBER := 0;
+   BEGIN
+       SELECT sal INTO v_sal FROM emp WHERE empno = p_empno;
+       v_sal := v_sal + p_raise;
+       UPDATE emp SET sal = v_sal WHERE empno = p_empno;
+       RETURN v_sal;
+   EXCEPTION
+       WHEN NO_DATA_FOUND THEN
+           DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno || ' not found');
+           RETURN -1;
+       WHEN OTHERS THEN
+           DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+           DBMS_OUTPUT.PUT_LINE(SQLERRM);
+           DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+           DBMS_OUTPUT.PUT_LINE(SQLCODE);
+           RETURN -1;
+   END;
+   --
+   --  Procedure that inserts a new employee record into the 'emp' table.
+   --
+   PROCEDURE hire_emp (
+       p_empno         NUMBER,
+       p_ename         VARCHAR2,
+       p_job           VARCHAR2,
+       p_sal           NUMBER,
+       p_hiredate      DATE,
+       p_comm          NUMBER,
+       p_mgr           NUMBER,
+       p_deptno        NUMBER
+   )
+   AS
+   BEGIN
+       INSERT INTO emp(empno, ename, job, sal, hiredate, comm, mgr, deptno)
+           VALUES(p_empno, p_ename, p_job, p_sal,
+                  p_hiredate, p_comm, p_mgr, p_deptno);
+   END;
+   --
+   --  Procedure that deletes an employee record from the 'emp' table based
+   --  on the employee number.
+   --
+   PROCEDURE fire_emp (
+       p_empno         NUMBER
+   )
+   AS
+   BEGIN
+       DELETE FROM emp WHERE empno = p_empno;
+   END;
+END;
+/
+COMMIT;
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/index.mdx
new file mode 100644
index 00000000000..5201dfeb10a
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/01_sample_database/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Sample database"
+indexCards: simple
+description: "Provides an introduction to the key elements of the sample database"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.010.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.010.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/01_sample_database/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sample_database" class="registered_link"></div>
+
+Throughout this tutorial, we work with a sample database to help explain database concepts, from basic to advanced. 
+
+<div class="toctree" maxdepth="3">
+
+sample_database_installation sample_database_description
+
+</div>
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/02_creating_a_new_table.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/02_creating_a_new_table.mdx
new file mode 100644
index 00000000000..fafd0bfb54c
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/02_creating_a_new_table.mdx
@@ -0,0 +1,43 @@
+---
+title: "Creating a new table"
+description: "Describes how to create a new table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.011.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.011.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/02_creating_a_new_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="creating_a_new_table" class="registered_link"></div>
+
+Create a new table by specifying the table name, along with all column names and their types. The following is a simplified version of the `emp` sample table with the minimal information needed to define a table.
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4),
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    mgr             NUMBER(4),
+    hiredate        DATE,
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2)
+);
+```
+
+You can enter this code into PSQL with line breaks. PSQL recognizes that the command isn't terminated until the semicolon.
+
+You can use white space (spaces, tabs, and newlines) in SQL commands. You can align the command as you want or even put all the text all on one line. 
+
+Two dashes ("--") introduce comments. Whatever follows them is ignored up to the end of the line. In addition, SQL is not case sensitive about key words and identifiers, except when identifiers are double-quoted to preserve the case.
+
+`VARCHAR2(10)` specifies a data type that can store arbitrary character strings up to 10 characters in length. `NUMBER(7,2)` is a fixed-point number with precision 7 and scale 2. `NUMBER(4)` is an integer number with precision 4 and scale 0.
+
+EDB Postgres Advanced Server supports the usual SQL data types: `INTEGER`, `SMALLINT`, `NUMBER`, `REAL`, `DOUBLE PRECISION`, `CHAR`, `VARCHAR2`, `DATE`, and `TIMESTAMP` as well as various synonyms for these types.
+
+If you don’t need a table or want to recreate it, you can remove it using the following command:
+
+```sql
+DROP TABLE tablename;
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/03_populating_a_table_with_rows.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/03_populating_a_table_with_rows.mdx
new file mode 100644
index 00000000000..7be39cac16d
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/03_populating_a_table_with_rows.mdx
@@ -0,0 +1,36 @@
+---
+title: "Populating a table With rows"
+description: "Provides an example of how to populate table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.012.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.012.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/03_populating_a_table_with_rows/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="populating_a_table_with_rows" class="registered_link"></div>
+
+Use the `INSERT` statement to populate a table with rows:
+
+```sql
+INSERT INTO emp VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
+```
+
+All data types use obvious input formats. Constants that aren't simple numeric values usually are surrounded by single quotes ('), as in the example. The `DATE` type is flexible in what it accepts. However, for this tutorial we use the unambiguous format shown here.
+
+The syntax used so far requires you to remember the order of the columns. An alternative syntax allows you to list the columns explicitly:
+
+```sql
+INSERT INTO emp(empno,ename,job,mgr,hiredate,sal,comm,deptno)
+    VALUES (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
+```
+
+You can list the columns in a different order if you want or even omit some columns, for example, if the commission is unknown:
+
+```sql
+INSERT INTO emp(empno,ename,job,mgr,hiredate,sal,deptno)
+    VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,20);
+```
+
+Many developers consider explicitly listing the columns better style than relying on the order implicitly.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/04_querying_a_table.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/04_querying_a_table.mdx
new file mode 100644
index 00000000000..c4bb74b05ab
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/04_querying_a_table.mdx
@@ -0,0 +1,125 @@
+---
+title: "Querying a table"
+description: "Provides an example of how to query a table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.013.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.013.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/04_querying_a_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="querying_a_table" class="registered_link"></div>
+
+To retrieve data from a table, you execute a *query* using an SQL `SELECT` statement. The statement is divided into: 
+-  A select list (the part that lists the columns to return) 
+-  A table list (the part that lists the tables from which to retrieve the data)
+-  An optional qualification (the part that specifies any restrictions)
+
+The following query lists all columns of all employees in the table in no particular order.
+
+```sql
+SELECT * FROM emp;
+```
+
+Here, “\*” in the select list means all columns. The following is the output from this query.
+
+```sql
+__OUTPUT__
+empno| ename |  job     | mgr  |      hiredate      | sal     | comm  | deptno
+-----+-------+----------+------+--------------------+---------+-------+-------
+7369 | SMITH | CLERK    | 7902 | 17-DEC-80 00:00:00 | 800.00  |       | 20
+7499 | ALLEN | SALESMAN | 7698 | 20-FEB-81 00:00:00 | 1600.00 | 300.00| 30
+7521 | WARD  | SALESMAN | 7698 | 22-FEB-81 00:00:00 | 1250.00 | 500.00| 30
+7566 | JONES | MANAGER  | 7839 | 02-APR-81 00:00:00 | 2975.00 |       | 20
+7654 | MARTIN| SALESMAN | 7698 | 28-SEP-81 00:00:00 | 1250.00 |1400.00| 30
+7698 | BLAKE | MANAGER  | 7839 | 01-MAY-81 00:00:00 | 2850.00 |       | 30
+7782 | CLARK | MANAGER  | 7839 | 09-JUN-81 00:00:00 | 2450.00 |       | 10
+7788 | SCOTT | ANALYST  | 7566 | 19-APR-87 00:00:00 | 3000.00 |       | 20
+7839 | KING  | PRESIDENT|      | 17-NOV-81 00:00:00 | 5000.00 |       | 10
+7844 | TURNER| SALESMAN | 7698 | 08-SEP-81 00:00:00 | 1500.00 | 0.00  | 30
+7876 | ADAMS | CLERK    | 7788 | 23-MAY-87 00:00:00 | 1100.00 |       | 20
+7900 | JAMES | CLERK    | 7698 | 03-DEC-81 00:00:00 |  950.00 |       | 30
+7902 | FORD  | ANALYST  | 7566 | 03-DEC-81 00:00:00 | 3000.00 |       | 20
+7934 | MILLER| CLERK    | 7782 | 23-JAN-82 00:00:00 | 1300.00 |       | 10
+(14 rows)
+```
+
+You can specify any arbitrary expression in the select list. For example, you can do:
+
+```sql
+SELECT ename, sal, sal * 24 AS yearly_salary, deptno FROM emp;
+__OUTPUT__
+ ename   |   sal   | yearly_salary | deptno
+---------+---------+---------------+--------
+ SMITH   |  800.00 |      19200.00 |     20
+ ALLEN   | 1600.00 |      38400.00 |     30
+ WARD    | 1250.00 |      30000.00 |     30
+ JONES   | 2975.00 |      71400.00 |     20
+ MARTIN  | 1250.00 |      30000.00 |     30
+ BLAKE   | 2850.00 |      68400.00 |     30
+ CLARK   | 2450.00 |      58800.00 |     10
+ SCOTT   | 3000.00 |      72000.00 |     20
+ KING    | 5000.00 |     120000.00 |     10
+ TURNER  | 1500.00 |      36000.00 |     30
+ ADAMS   | 1100.00 |      26400.00 |     20
+ JAMES   |  950.00 |      22800.00 |     30
+ FORD    | 3000.00 |      72000.00 |     20
+ MILLER  | 1300.00 |      31200.00 |     10
+(14 rows)
+```
+
+Notice how the `AS` clause is used to relabel the output column. The `AS` clause is optional.
+
+You can qualify a query by adding a `WHERE` clause that specifies the rows you want. The `WHERE` clause contains a Boolean (truth value) expression. Only rows for which the Boolean expression is true are returned. The usual Boolean operators (`AND`, `OR`, and `NOT`) are allowed in the qualification. For example, the following retrieves the employees in department 20 with salaries over $1000.00:
+
+```sql
+SELECT ename, sal, deptno FROM emp WHERE deptno = 20 AND sal > 1000;
+__OUTPUT__
+ ename |   sal   | deptno
+-------+---------+--------
+ JONES | 2975.00 |     20
+ SCOTT | 3000.00 |     20
+ ADAMS | 1100.00 |     20
+ FORD  | 3000.00 |     20
+(4 rows)
+```
+
+You can request to return the results of a query in sorted order:
+
+```sql
+SELECT ename, sal, deptno FROM emp ORDER BY ename;
+__OUTPUT__
+ ename  |   sal   | deptno
+--------+---------+--------
+ ADAMS  | 1100.00 |     20
+ ALLEN  | 1600.00 |     30
+ BLAKE  | 2850.00 |     30
+ CLARK  | 2450.00 |     10
+ FORD   | 3000.00 |     20
+ JAMES  |  950.00 |     30
+ JONES  | 2975.00 |     20
+ KING   | 5000.00 |     10
+ MARTIN | 1250.00 |     30
+ MILLER | 1300.00 |     10
+ SCOTT  | 3000.00 |     20
+ SMITH  |  800.00 |     20
+ TURNER | 1500.00 |     30
+ WARD   | 1250.00 |     30
+(14 rows)
+```
+
+You can request to remove duplicate rows from the result of a query:
+
+```sql
+SELECT DISTINCT job FROM emp;
+__OUTPUT__
+   job
+-----------
+ ANALYST
+ CLERK
+ MANAGER
+ PRESIDENT
+ SALESMAN
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/05_joins_between_tables.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/05_joins_between_tables.mdx
new file mode 100644
index 00000000000..96bdb869de3
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/05_joins_between_tables.mdx
@@ -0,0 +1,171 @@
+---
+title: "Executing joins between tables"
+description: "Describes how to execute a join query"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.014.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.014.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/05_joins_between_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="joins_between_tables" class="registered_link"></div>
+
+Queries can access multiple tables at once or access the same table in such a way that multiple rows of the table are processed at the same time. A query that accesses multiple rows of the same or different tables at one time is called a *join* query. 
+
+## Executing a join query 
+
+For example, suppose you want to list all the employee records together with the name and location of the associated department. To do that, you need to compare the `deptno` column of each row of the `emp` table with the `deptno` column of all rows in the `dept` table. Then select the pairs of rows where these values match. You can accomplish this using the following query:
+
+```sql
+SELECT emp.ename, emp.sal, dept.deptno, dept.dname, dept.loc FROM emp, dept
+WHERE emp.deptno = dept.deptno;
+__OUTPUT__
+ ename  |   sal   | deptno |   dname    |   loc
+--------+---------+--------+------------+----------
+ MILLER | 1300.00 |     10 | ACCOUNTING | NEW YORK
+ CLARK  | 2450.00 |     10 | ACCOUNTING | NEW YORK
+ KING   | 5000.00 |     10 | ACCOUNTING | NEW YORK
+ SCOTT  | 3000.00 |     20 | RESEARCH   | DALLAS
+ JONES  | 2975.00 |     20 | RESEARCH   | DALLAS
+ SMITH  |  800.00 |     20 | RESEARCH   | DALLAS
+ ADAMS  | 1100.00 |     20 | RESEARCH   | DALLAS
+ FORD   | 3000.00 |     20 | RESEARCH   | DALLAS
+ WARD   | 1250.00 |     30 | SALES      | CHICAGO
+ TURNER | 1500.00 |     30 | SALES      | CHICAGO
+ ALLEN  | 1600.00 |     30 | SALES      | CHICAGO
+ BLAKE  | 2850.00 |     30 | SALES      | CHICAGO
+ MARTIN | 1250.00 |     30 | SALES      | CHICAGO
+ JAMES  |  950.00 |     30 | SALES      | CHICAGO
+(14 rows)
+```
+
+Observe two things about the result set:
+
+-   There's no result row for department 40. That's because there's no matching entry in the `emp` table for department 40, so the join ignores the unmatched rows in the `dept` table. The code that follows shows how to fix this.
+-   It's more desirable to list the output columns qualified by table name rather than using \* or leaving out the qualification as follows:
+
+```sql
+SELECT ename, sal, dept.deptno, dname, loc FROM emp, dept WHERE emp.deptno =
+dept.deptno;
+```
+
+Since all the columns had different names (except for `deptno`, which therefore must be qualified), the parser found the table they belong to. However, it's best practice to fully qualify column names in join queries.
+
+You can also write this kind of join queries in this alternative form:
+
+```sql
+SELECT emp.ename, emp.sal, dept.deptno, dept.dname, dept.loc FROM emp INNER
+JOIN dept ON emp.deptno = dept.deptno;
+```
+
+This syntax is not as commonly used, but we show it here to help you understand the following topics.
+
+## Executing an outer join 
+
+In all the above results for joins, no employees were returned that belonged to department 40. As a consequence, the record for department 40 never appears. Next, resolve how to get the department 40 record in the results despite the fact that there are no matching employees. The query must scan the `dept` table and, for each row, find the matching `emp` row. If no matching row is found, we want to substitute some “empty” values for the `emp` table’s columns. This kind of query is called an *outer join*. (The joins you have seen so far are *inner joins*.) The command looks like this:
+
+```sql
+SELECT emp.ename, emp.sal, dept.deptno, dept.dname, dept.loc FROM dept LEFT
+OUTER JOIN emp ON emp.deptno = dept.deptno;
+__OUTPUT__
+ ename  |   sal   | deptno |   dname    |   loc
+--------+---------+--------+------------+----------
+ MILLER | 1300.00 |     10 | ACCOUNTING | NEW YORK
+ CLARK  | 2450.00 |     10 | ACCOUNTING | NEW YORK
+ KING   | 5000.00 |     10 | ACCOUNTING | NEW YORK
+ SCOTT  | 3000.00 |     20 | RESEARCH   | DALLAS
+ JONES  | 2975.00 |     20 | RESEARCH   | DALLAS
+ SMITH  |  800.00 |     20 | RESEARCH   | DALLAS
+ ADAMS  | 1100.00 |     20 | RESEARCH   | DALLAS
+ FORD   | 3000.00 |     20 | RESEARCH   | DALLAS
+ WARD   | 1250.00 |     30 | SALES      | CHICAGO
+ TURNER | 1500.00 |     30 | SALES      | CHICAGO
+ ALLEN  | 1600.00 |     30 | SALES      | CHICAGO
+ BLAKE  | 2850.00 |     30 | SALES      | CHICAGO
+ MARTIN | 1250.00 |     30 | SALES      | CHICAGO
+ JAMES  |  950.00 |     30 | SALES      | CHICAGO
+        |         |     40 | OPERATIONS | BOSTON
+(15 rows)
+```
+
+This query is called a *left outer join*. The table mentioned on the left of the join operator has each of its rows in the output at least once. The table on the right has only those rows output that match some row of the left table. When a left-table row is selected for which there is no right-table match, empty (`NULL`) values are substituted for the right-table columns.
+
+An alternative syntax for an outer join is to use the outer join operator, “(+)”, in the join condition in the `WHERE` clause. The outer join operator is placed after the column name of the table for which you substitute null values for unmatched rows. So for all the rows in the `dept` table that have no matching rows in the `emp` table, EDB Postgres Advanced Server returns null for any select list expressions containing columns of `emp`. Hence you can rewrite the earlier example as:
+
+```sql
+SELECT emp.ename, emp.sal, dept.deptno, dept.dname, dept.loc FROM dept, emp
+WHERE emp.deptno(+) = dept.deptno;
+__OUTPUT__
+ ename  |   sal   | deptno |   dname    |   loc
+--------+---------+--------+------------+----------
+ MILLER | 1300.00 |     10 | ACCOUNTING | NEW YORK
+ CLARK  | 2450.00 |     10 | ACCOUNTING | NEW YORK
+ KING   | 5000.00 |     10 | ACCOUNTING | NEW YORK
+ SCOTT  | 3000.00 |     20 | RESEARCH   | DALLAS
+ JONES  | 2975.00 |     20 | RESEARCH   | DALLAS
+ SMITH  |  800.00 |     20 | RESEARCH   | DALLAS
+ ADAMS  | 1100.00 |     20 | RESEARCH   | DALLAS
+ FORD   | 3000.00 |     20 | RESEARCH   | DALLAS
+ WARD   | 1250.00 |     30 | SALES      | CHICAGO
+ TURNER | 1500.00 |     30 | SALES      | CHICAGO
+ ALLEN  | 1600.00 |     30 | SALES      | CHICAGO
+ BLAKE  | 2850.00 |     30 | SALES      | CHICAGO
+ MARTIN | 1250.00 |     30 | SALES      | CHICAGO
+ JAMES  |  950.00 |     30 | SALES      | CHICAGO
+        |         |     40 | OPERATIONS | BOSTON
+(15 rows)
+```
+
+## Executing a self join 
+
+You can also join a table against itself, which is called a *self join*. As an example, suppose you want to find the name of each employee and the name of that employee’s manager. You need to compare the `mgr` column of each `emp` row to the `empno` column of all other `emp` rows.
+
+```sql
+SELECT e1.ename || ' works for ' || e2.ename AS "Employees and their
+Managers" FROM emp e1, emp e2 WHERE e1.mgr = e2.empno;
+__OUTPUT__
+ Employees and their Managers
+------------------------------
+ FORD works for JONES
+ SCOTT works for JONES
+ WARD works for BLAKE
+ TURNER works for BLAKE
+ MARTIN works for BLAKE
+ JAMES works for BLAKE
+ ALLEN works for BLAKE
+ MILLER works for CLARK
+ ADAMS works for SCOTT
+ CLARK works for KING
+ BLAKE works for KING
+ JONES works for KING
+ SMITH works for FORD
+(13 rows)
+```
+
+Here, the `emp` table was relabeled as `e1` to represent the employee row in the select list and in the join condition. It was also relabeled as `e2` to represent the matching employee row acting as manager in the select list and in the join condition. You can use these kinds of aliases in other queries to save some typing. For example:
+
+```sql
+SELECT e.ename, e.mgr, d.deptno, d.dname, d.loc FROM emp e, dept d WHERE
+e.deptno = d.deptno;
+__OUTPUT__
+ ename  | mgr  | deptno |   dname    |   loc
+--------+------+--------+------------+----------
+ MILLER | 7782 |     10 | ACCOUNTING | NEW YORK
+ CLARK  | 7839 |     10 | ACCOUNTING | NEW YORK
+ KING   |      |     10 | ACCOUNTING | NEW YORK
+ SCOTT  | 7566 |     20 | RESEARCH   | DALLAS
+ JONES  | 7839 |     20 | RESEARCH   | DALLAS
+ SMITH  | 7902 |     20 | RESEARCH   | DALLAS
+ ADAMS  | 7788 |     20 | RESEARCH   | DALLAS
+ FORD   | 7566 |     20 | RESEARCH   | DALLAS
+ WARD   | 7698 |     30 | SALES      | CHICAGO
+ TURNER | 7698 |     30 | SALES      | CHICAGO
+ ALLEN  | 7698 |     30 | SALES      | CHICAGO
+ BLAKE  | 7839 |     30 | SALES      | CHICAGO
+ MARTIN | 7698 |     30 | SALES      | CHICAGO
+ JAMES  | 7698 |     30 | SALES      | CHICAGO
+(14 rows)
+```
+
+This style of abbreviating is used often.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/06_aggregate_functions.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/06_aggregate_functions.mdx
new file mode 100644
index 00000000000..099e52f9c39
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/06_aggregate_functions.mdx
@@ -0,0 +1,88 @@
+---
+title: "Aggregating data"
+description: "Provides an example of how to aggregate data"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.015.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.138.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.015.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.047.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/06_aggregate_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="aggregate_functions" class="registered_link"></div>
+
+Like most other relational database products, EDB Postgres Advanced Server supports aggregate functions. An aggregate function computes a single result from multiple input rows. For example, some aggregates compute the `COUNT`, `SUM`, `AVG` (average), `MAX` (maximum), and `MIN` (minimum) over a set of rows.
+
+As an example, you can find the highest and lowest salaries with the following query:
+
+```sql
+SELECT MAX(sal) highest_salary, MIN(sal) lowest_salary FROM emp;
+__OUTPUT__
+ highest_salary | lowest_salary
+----------------+---------------
+       5000.00  |        800.00
+(1 row)
+```
+
+If you want to find the employee with the largest salary, you might be tempted to try:
+
+```sql
+SELECT ename FROM emp WHERE sal = MAX(sal);
+__OUTPUT__
+ERROR:  aggregates not allowed in WHERE clause
+```
+
+This approach doesn't work because you can't use the aggregate function `MAX` in the `WHERE` clause. This restriction exists because the `WHERE` clause determines the rows that go into the aggregation stage. Hence, it has to be evaluated before aggregate functions are computed. However, you can restart the query to accomplish the intended result by using a *subquery*. The subquery is an independent computation that obtains its own result separately from the outer query.
+
+```sql
+SELECT ename FROM emp WHERE sal = (SELECT MAX(sal) FROM emp);
+__OUTPUT__
+ ename
+-------
+ KING
+(1 row)
+```
+
+Aggregates are also useful in combination with the `GROUP BY` clause. For example, the following query gets the highest salary in each department.
+
+```sql
+SELECT deptno, MAX(sal) FROM emp GROUP BY deptno;
+__OUTPUT__
+ deptno |   max
+--------+---------
+     10 | 5000.00
+     20 | 3000.00
+     30 | 2850.00
+(3 rows)
+```
+
+This query produces one output row per department. Each aggregate result is computed over the rows matching that department. These grouped rows can be filtered using the `HAVING` clause.
+
+```sql
+SELECT deptno, MAX(sal) FROM emp GROUP BY deptno HAVING AVG(sal) > 2000;
+__OUTPUT__
+ deptno |   max
+--------+---------
+     10 | 5000.00
+     20 | 3000.00
+(2 rows)
+```
+
+This query gives the same results for only those departments that have an average salary greater than 2000.
+
+Finally, the following query takes into account only the highest paid employees who are analysts in each department.
+
+```sql
+SELECT deptno, MAX(sal) FROM emp WHERE job = 'ANALYST' GROUP BY deptno HAVING AVG(sal) > 2000;
+__OUTPUT__
+ deptno |   max
+--------+---------
+     20 | 3000.00
+(1 row)
+```
+
+There's a subtle distinction between the `WHERE` and `HAVING` clauses. The `WHERE` clause filters out rows before grouping occurs and aggregate functions are applied. The `HAVING` clause applies filters on the results after rows are grouped and aggregate functions are computed for each group.
+
+So, in the previous example, only employees who are analysts are considered. From this subset, the employees are grouped by department. Only those groups where the average salary of analysts in the group is greater than 2000 are in the final result. This is true only of the group for department 20, and the maximum analyst salary in department 20 is 3000.00.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/07_updates.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/07_updates.mdx
new file mode 100644
index 00000000000..9e16486dbf8
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/07_updates.mdx
@@ -0,0 +1,37 @@
+---
+title: "Updating a table"
+description: "Provides an example of updating a table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.016.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.016.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/07_updates/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="updates" class="registered_link"></div>
+
+You can change the column values of existing rows using the `UPDATE` command. For example, the following sequence of commands shows the before and after results of giving everyone who is a manager a 10% raise:
+
+```sql
+SELECT ename, sal FROM emp WHERE job = 'MANAGER';
+__OUTPUT__
+ ename |   sal
+-------+---------
+ JONES | 2975.00
+ BLAKE | 2850.00
+ CLARK | 2450.00
+(3 rows)
+```
+```sql
+UPDATE emp SET sal = sal * 1.1 WHERE job = 'MANAGER';
+
+SELECT ename, sal FROM emp WHERE job = 'MANAGER';
+__OUTPUT__
+ ename |   sal
+-------+---------
+ JONES | 3272.50
+ BLAKE | 3135.00
+ CLARK | 2695.00
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/08_deletions.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/08_deletions.mdx
new file mode 100644
index 00000000000..51bb75ca035
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/08_deletions.mdx
@@ -0,0 +1,64 @@
+---
+title: "Deleting a table"
+description: "Provides an example of how to delete a table"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.017.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.017.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/08_deletions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="deletions" class="registered_link"></div>
+
+You can remove rows from a table using the `DELETE` command. For example, the following sequence of commands shows the before and after results of deleting all employees in department `20`.
+
+```sql
+SELECT ename, deptno FROM emp;
+__OUTPUT__
+ ename  | deptno
+--------+--------
+ SMITH  |     20
+ ALLEN  |     30
+ WARD   |     30
+ JONES  |     20
+ MARTIN |     30
+ BLAKE  |     30
+ CLARK  |     10
+ SCOTT  |     20
+ KING   |     10
+ TURNER |     30
+ ADAMS  |     20
+ JAMES  |     30
+ FORD   |     20
+ MILLER |     10
+(14 rows)
+```
+```sql
+DELETE FROM emp WHERE deptno = 20;
+
+SELECT ename, deptno FROM emp;
+__OUTPUT__
+ ename  | deptno
+--------+--------
+ ALLEN  |     30
+ WARD   |     30
+ MARTIN |     30
+ BLAKE  |     30
+ CLARK  |     10
+ KING   |     10
+ TURNER |     30
+ JAMES  |     30
+ MILLER |     10
+(9 rows)
+```
+
+!!! Warning
+Be careful when giving a `DELETE` command without a `WHERE` clause such as the following:
+
+```sql
+DELETE FROM tablename;
+```
+
+This statement removes all rows from the given table, leaving it completely empty. The system doesn't request confirmation before doing this.
+!!!
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx
new file mode 100644
index 00000000000..24566cae9c4
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/09_the_sql_language.mdx
@@ -0,0 +1,20 @@
+---
+title: "The SQL language"
+description: "Provides an introduction to the subset of the EDB Postgres Advanced Server SQL language that is compatible with Oracle databases"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.037.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/09_the_sql_language/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="the_sql_language" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports SQL language that's compatible with Oracle syntax as well as syntax and commands for extended functionality. Extended functionality doesn't provide database compatibility for Oracle or support Oracle-styled applications.
+
+[SQL reference](../../../reference/sql_reference/) provides detailed information about:
+
+-   [Compatible SQL syntax and language elements](../../../reference/sql_reference/01_sql_syntax/)
+-   [Data types](../../../reference/sql_reference/02_data_types/)
+-   [Functions and operators for the built-in data types](../../../reference/sql_reference/03_functions_and_operators/)
+
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/index.mdx
new file mode 100644
index 00000000000..75ecdddd3f1
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/02_sql_tutorial/index.mdx
@@ -0,0 +1,25 @@
+---
+title: "SQL tutorial"
+indexCards: simple
+description: "Helps you get started with SQL quickly and effectively through practical examples"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.008.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.008.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/02_sql_tutorial/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sql_tutorial" class="registered_link"></div>
+
+EDB Postgres Advanced Server is a *relational database management system* (RDBMS), which means it's a system for managing data stored in *relations*. A relation is essentially a mathematical term for a *table*. Each table is a named collection of *rows*. Each row of a given table has the same set of named *columns*, and each column is of a specific *data type*. Whereas columns have a fixed order in each row, it's important to remember that SQL doesn't guarantee the order of the rows in the table in any way (although you can explicitly sort them for display).
+
+Tables are grouped into *databases*, and a collection of databases managed by a single EDB Postgres Advanced Server instance constitutes a database *cluster*.
+
+This tutorial walks you through the main features of an RDBMS using a sample database.
+
+<div class="toctree" maxdepth="3">
+
+sample_database creating_a_new_table populating_a_table_with_rows querying_a_table joins_between_tables aggregate_functions updates deletions the_sql_language
+
+</div>
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/01_views.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/01_views.mdx
new file mode 100644
index 00000000000..7fda427e5a4
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/01_views.mdx
@@ -0,0 +1,66 @@
+---
+title: "Views"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/01_views/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="views" class="registered_link"></div>
+
+A *view* provides a consistent interface that encapsulates details of the structure of your tables that might change as your application evolves. Making liberal use of views is a key aspect of good SQL database design.
+
+Consider the following `SELECT` command:
+
+```sql
+SELECT ename, sal, sal * 24 AS yearly_salary, deptno FROM emp;
+__OUTPUT__
+ ename  |   sal   | yearly_salary | deptno
+--------+---------+---------------+--------
+ SMITH  |  800.00 |      19200.00 |     20
+ ALLEN  | 1600.00 |      38400.00 |     30
+ WARD   | 1250.00 |      30000.00 |     30
+ JONES  | 2975.00 |      71400.00 |     20
+ MARTIN | 1250.00 |      30000.00 |     30
+ BLAKE  | 2850.00 |      68400.00 |     30
+ CLARK  | 2450.00 |      58800.00 |     10
+ SCOTT  | 3000.00 |      72000.00 |     20
+ KING   | 5000.00 |     120000.00 |     10
+ TURNER | 1500.00 |      36000.00 |     30
+ ADAMS  | 1100.00 |      26400.00 |     20
+ JAMES  |  950.00 |      22800.00 |     30
+ FORD   | 3000.00 |      72000.00 |     20
+ MILLER | 1300.00 |      31200.00 |     10
+(14 rows)
+```
+
+If this is a query that you use repeatedly, a shorthand method of reusing this query without retyping the entire `SELECT` command each time is to create a *view*:
+
+```sql
+CREATE VIEW employee_pay AS SELECT ename, sal, sal * 24 AS yearly_salary,
+deptno FROM emp;
+```
+
+The view name, `employee_pay`, can now be used like an ordinary table name to perform the query:
+
+```sql
+SELECT * FROM employee_pay;
+__OUTPUT__
+ ename  |   sal   | yearly_salary | deptno
+--------+---------+---------------+--------
+ SMITH  |  800.00 |      19200.00 |     20
+ ALLEN  | 1600.00 |      38400.00 |     30
+ WARD   | 1250.00 |      30000.00 |     30
+ JONES  | 2975.00 |      71400.00 |     20
+ MARTIN | 1250.00 |      30000.00 |     30
+ BLAKE  | 2850.00 |      68400.00 |     30
+ CLARK  | 2450.00 |      58800.00 |     10
+ SCOTT  | 3000.00 |      72000.00 |     20
+ KING   | 5000.00 |     120000.00 |     10
+ TURNER | 1500.00 |      36000.00 |     30
+ ADAMS  | 1100.00 |      26400.00 |     20
+ JAMES  |  950.00 |      22800.00 |     30
+ FORD   | 3000.00 |      72000.00 |     20
+ MILLER | 1300.00 |      31200.00 |     10
+(14 rows)
+```
+
+You can use views in almost any place that you use a real table. Building views on other views is also common.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/02_foreign_keys.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/02_foreign_keys.mdx
new file mode 100644
index 00000000000..b0964db35f6
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/02_foreign_keys.mdx
@@ -0,0 +1,45 @@
+---
+title: "Foreign keys"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.019.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.019.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/02_foreign_keys/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="foreign_keys" class="registered_link"></div>
+
+A *foreign key* represents one or more than one column used to establish and enforce a link between data in two database tables for controlling data stored in the foreign key table.
+
+Suppose you want to make sure all employees belong to a valid department, that is, you want to maintain the *referential integrity* of your data. In simplistic database systems, you can ensure referential integrity by first looking at the `dept` table to check if a matching record exists and then inserting or rejecting the new employee record. 
+
+This approach has a number of problems and is inconvenient. EDB Postgres Advanced Server can make it easier for you.
+
+A modified version of the `emp` table presented in [Creating a new table](../02_sql_tutorial/02_creating_a_new_table/#creating_a_new_table) is shown here with the addition of a foreign key constraint. The modified `emp` table looks like the following:
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    mgr             NUMBER(4),
+    hiredate        DATE,
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                        REFERENCES dept(deptno)
+);
+```
+
+If you try to issue the following `INSERT` command in the sample `emp` table, the foreign key constraint `emp_ref_dept_fk` is meant to ensure that department `50` exists in the `dept` table. Since it doesn't, the command is rejected.
+
+```sql
+INSERT INTO emp VALUES (8000,'JONES','CLERK',7902,'17-AUG-07',1200,NULL,50);
+
+ERROR:  insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+DETAIL:  Key (deptno)=(50) is not present in table "dept".
+```
+
+You can finely tune the behavior of foreign keys to your application. Making correct use of foreign keys improves the quality of your database applications. We strongly encourage you to learn more about them.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/03_the_rownum_pseudo_column.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/03_the_rownum_pseudo_column.mdx
new file mode 100644
index 00000000000..da9b251a296
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/03_the_rownum_pseudo_column.mdx
@@ -0,0 +1,79 @@
+---
+title: "The ROWNUM pseudo-column"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.020.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.020.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/03_the_rownum_pseudo_column/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="the_rownum_pseudo_column" class="registered_link"></div>
+
+`ROWNUM` is a pseudo-column that's assigned an incremental, unique integer value for each row based on the order the rows were retrieved from a query. Therefore, the first row retrieved has `ROWNUM` of `1`, the second row has `ROWNUM` of `2`, and so on.
+
+## Limiting the number or rows returned
+
+You can use this feature to limit the number of rows retrieved by a query:
+
+```sql
+SELECT empno, ename, job FROM emp WHERE ROWNUM < 5;
+__OUTPUT__
+ empno | ename |   job
+-------+-------+----------
+ 7369  | SMITH | CLERK
+ 7499  | ALLEN | SALESMAN
+ 7521  | WARD  | SALESMAN
+ 7566  | JONES | MANAGER
+(4 rows)
+```
+
+The `ROWNUM` value is assigned to each row before any sorting of the result set takes place. Thus, the result set is returned in the order given by the `ORDER BY` clause. However, the `ROWNUM` values might not be in ascending order:
+
+```sql
+SELECT ROWNUM, empno, ename, job FROM emp WHERE ROWNUM < 5 ORDER BY ename;
+__OUTPUT__
+ rownum | empno | ename |   job
+--------+-------+-------+----------
+      2 |  7499 | ALLEN | SALESMAN
+      4 |  7566 | JONES | MANAGER
+      1 |  7369 | SMITH | CLERK
+      3 |  7521 | WARD  | SALESMAN
+(4 rows)
+```
+## Adding a sequence number to rows in a table
+
+The following example shows how you can add a sequence number to every row in the `jobhist` table. First add a column named `seqno` to the table. Then set `seqno` to `ROWNUM` in the `UPDATE` command.
+
+```sql
+ALTER TABLE jobhist ADD seqno NUMBER(3);
+UPDATE jobhist SET seqno = ROWNUM;
+```
+
+The following `SELECT` command shows the new `seqno` values:
+
+```sql
+SELECT seqno, empno, TO_CHAR(startdate,'DD-MON-YY') AS start, job FROM
+jobhist;
+__OUTPUT__
+seqno  | empno |   start   |    job
+-------+-------+-----------+-----------
+     1 |  7369 | 17-DEC-80 | CLERK
+     2 |  7499 | 20-FEB-81 | SALESMAN
+     3 |  7521 | 22-FEB-81 | SALESMAN
+     4 |  7566 | 02-APR-81 | MANAGER
+     5 |  7654 | 28-SEP-81 | SALESMAN
+     6 |  7698 | 01-MAY-81 | MANAGER
+     7 |  7782 | 09-JUN-81 | MANAGER
+     8 |  7788 | 19-APR-87 | CLERK
+     9 |  7788 | 13-APR-88 | CLERK
+    10 |  7788 | 05-MAY-90 | ANALYST
+    11 |  7839 | 17-NOV-81 | PRESIDENT
+    12 |  7844 | 08-SEP-81 | SALESMAN
+    13 |  7876 | 23-MAY-87 | CLERK
+    14 |  7900 | 03-DEC-81 | CLERK
+    15 |  7900 | 15-JAN-83 | CLERK
+    16 |  7902 | 03-DEC-81 | ANALYST
+    17 |  7934 | 23-JAN-82 | CLERK
+(17 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/04_synonyms.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/04_synonyms.mdx
new file mode 100644
index 00000000000..85d2e4ffaae
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/04_synonyms.mdx
@@ -0,0 +1,160 @@
+---
+title: "Synonyms"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.021.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.021.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.035.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/04_synonyms/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="synonyms" class="registered_link"></div>
+
+A *synonym* is an identifier that you can use to reference another database object in a SQL statement. A synonym is useful in cases where a database object normally requires full qualification by schema name to be properly referenced in a SQL statement. A synonym defined for that object simplifies the reference to a single, unqualified name.
+
+EDB Postgres Advanced Server supports synonyms for:
+
+-   Tables
+-   Views
+-   Materialized views
+-   Sequences
+-   Packages
+-   Procedures
+-   Functions
+-   Types
+-   Objects that you can access through a database link
+-   Other synonyms
+
+Neither the referenced schema or referenced object must exist when you create the synonym. A synonym can refer to a nonexistent object or schema. A synonym becomes invalid if you drop the referenced object or schema. You must explicitly drop a synonym to remove it.
+
+As with any other schema object, EDB Postgres Advanced Server uses the search path to resolve unqualified synonym names. If you have two synonyms with the same name, an unqualified reference to a synonym resolves to the first synonym with the given name in the search path. If `public` is in your search path, you can refer to a synonym in that schema without qualifying that name.
+
+When EDB Postgres Advanced Server executes an SQL command, the privileges of the current user are checked against the synonym’s underlying database object. If the user doesn't have the proper permissions for that object, the SQL command fails.
+
+## Creating a synonym
+
+Use the `CREATE SYNONYM` command to create a synonym. The syntax is:
+
+```sql
+CREATE [OR REPLACE] [PUBLIC] SYNONYM [<schema>.]<syn_name>
+       FOR <object_schema>.<object_name>[<@dblink_name>];
+```
+
+### Parameters
+
+`syn_name`
+
+`syn_name` is the name of the synonym. A synonym name must be unique in a schema.
+
+`schema`
+
+`schema` specifies the name of the schema that the synonym resides in. If you don't specify a schema name, the synonym is created in the first existing schema in your search path.
+
+`object_name`
+
+`object_name` specifies the name of the object.
+
+`object_schema`
+
+`object_schema` specifies the name of the schema that the object resides in.
+
+`dblink_name`
+
+`dblink_name` specifies the name of the database link through which you can access a target object.
+
+Include the `REPLACE` clause to replace an existing synonym definition with a new synonym definition.
+
+Include the `PUBLIC` clause to create the synonym in the `public` schema. Compatible with Oracle databases, the `CREATE PUBLIC SYNONYM` command creates a synonym that resides in the `public` schema:
+
+```sql
+CREATE [OR REPLACE] PUBLIC SYNONYM <syn_name> FOR
+<object_schema>.<object_name>;
+```
+
+This is a shorthand way to write:
+
+```sql
+CREATE [OR REPLACE] SYNONYM public.<syn_name> FOR
+<object_schema>.<object_name>;
+```
+
+This example creates a synonym named `personnel` that refers to the `enterprisedb.emp` table:
+
+```sql
+CREATE SYNONYM personnel FOR enterprisedb.emp;
+```
+
+Unless the synonym is schema qualified in the `CREATE SYNONYM` command, it's created in the first existing schema in your search path. You can view your search path by executing the following command:
+
+```sql
+SHOW SEARCH_PATH;
+__OUTPUT__
+   search_path
+-----------------------
+ development,accounting
+(1 row)
+```
+### Example
+
+In the example, if a schema named `development` doesn't exist, the synonym are created in the schema named `accounting`.
+
+Now you can reference the `emp` table in the `enterprisedb` schema in any SQL statement (DDL or DML) by using the synonym `personnel`:
+
+```sql
+INSERT INTO personnel VALUES (8142,'ANDERSON','CLERK',7902,'17-DEC-06',1300,NULL,20);
+
+SELECT * FROM personnel;
+__OUTPUT__
+ empno | ename   |  job     | mgr |    hiredate      | sal    | comm  |deptno
+-------+---------+----------+-----+------------------+--------+-------+------
+ 7369  | SMITH   | CLERK    |7902 |17-DEC-80 00:00:00| 800.00 |       |  20
+ 7499  | ALLEN   | SALESMAN |7698 |20-FEB-81 00:00:00| 1600.00|300.00 |  30
+ 7521  | WARD    | SALESMAN |7698 |22-FEB-81 00:00:00| 1250.00|500.00 |  30
+ 7566  | JONES   | MANAGER  |7839 |02-APR-81 00:00:00| 2975.00|       |  20
+ 7654  | MARTIN  | SALESMAN |7698 |28-SEP-81 00:00:00| 1250.00|1400.00|  30
+ 7698  | BLAKE   | MANAGER  |7839 |01-MAY-81 00:00:00| 2850.00|       |  30
+ 7782  | CLARK   | MANAGER  |7839 |09-JUN-81 00:00:00| 2450.00|       |  10
+ 7788  | SCOTT   | ANALYST  |7566 |19-APR-87 00:00:00| 3000.00|       |  20
+ 7839  | KING    | PRESIDENT|     |17-NOV-81 00:00:00| 5000.00|       |  10
+ 7844  | TURNER  | SALESMAN |7698 |08-SEP-81 00:00:00| 1500.00| 0.00  |  30
+ 7876  | ADAMS   | CLERK    |7788 |23-MAY-87 00:00:00| 1100.00|       |  20
+ 7900  | JAMES   | CLERK    |7698 |03-DEC-81 00:00:00| 950.00 |       |  30
+ 7902  | FORD    | ANALYST  |7566 |03-DEC-81 00:00:00| 3000.00|       |  20
+ 7934  | MILLER  | CLERK    |7782 |23-JAN-82 00:00:00| 1300.00|       |  10
+ 8142  | ANDERSON| CLERK    |7902 |17-DEC-06 00:00:00| 1300.00|       |  20
+(15 rows)
+```
+
+## Deleting a synonym
+
+To delete a synonym, use the command `DROP SYNONYM`. The syntax is:
+
+```sql
+DROP [PUBLIC] SYNONYM [<schema>.] <syn_name>
+```
+
+### Parameters
+
+`syn_name`
+
+`syn_name` is the name of the synonym. A synonym name must be unique in a schema.
+
+`schema`
+
+`schema` specifies the name of the schema in which the synonym resides.
+
+Like any other object that can be schema qualified, you can have two synonyms with the same name in your search path. To disambiguate the name of the synonym that you're dropping, include a schema name. Unless a synonym is schema qualified in the `DROP SYNONYM` command, EDB Postgres Advanced Server deletes the first instance of the synonym it finds in your search path.
+
+You can optionally include the `PUBLIC` clause to drop a synonym that resides in the `public` schema. Compatible with Oracle databases, the `DROP PUBLIC SYNONYM` command drops a synonym that resides in the `public` schema:
+
+```sql
+DROP PUBLIC SYNONYM <syn_name>;
+```
+### Example
+
+The following example drops the synonym `personnel`:
+
+```sql
+DROP SYNONYM personnel;
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/01_defining_the_parent_child_relationship.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/01_defining_the_parent_child_relationship.mdx
new file mode 100644
index 00000000000..711b17d94fb
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/01_defining_the_parent_child_relationship.mdx
@@ -0,0 +1,24 @@
+---
+title: "Defining the parent/child relationship"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/01_defining_the_parent_child_relationship/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="defining_the_parent_child_relationship" class="registered_link"></div>
+
+To determine the children for any given row:
+
+1.  Evaluate `parent_expr` on the given row.
+
+2.  Evaluate `child_expr` on any other row resulting from the evaluation of `table_expression`.
+
+3.  If `parent_expr = child_expr`, then this row is a child node of the given parent row.
+
+4.  Repeat the process for all remaining rows in `table_expression`. All rows that satisfy the equation in step 3 are the children nodes of the given parent row.
+
+!!! Note
+    The evaluation process to determine if a row is a child node occurs on every row returned by `table_expression` before the `WHERE` clause is applied to `table_expression`.
+
+Iteratively repeating this process, treating each child node found in the prior steps as a parent, constructs an inverted tree of nodes. The process is complete when the final set of child nodes has no children of its own. These are the leaf nodes.
+
+A `SELECT` command that includes a `CONNECT BY` clause typically includes the `START WITH` clause. The `START WITH` clause determines the rows that are to be the root nodes, that is, the rows that are the initial parent nodes upon which to apply the algorithm. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/02_selecting_the_root_nodes.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/02_selecting_the_root_nodes.mdx
new file mode 100644
index 00000000000..89e21c03a5d
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/02_selecting_the_root_nodes.mdx
@@ -0,0 +1,9 @@
+---
+title: "Selecting the root nodes"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/02_selecting_the_root_nodes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="selecting_the_root_nodes" class="registered_link"></div>
+
+The `START WITH` clause determines the rows selected by `table_expression` to use as the root nodes. All rows selected by `table_expression` where `start_expression` evaluates to `true` become a root node of a tree. Thus, the number of potential trees in the result set is equal to the number of root nodes. As a consequence, if the `START WITH` clause is omitted, then every row returned by `table_expression` is a root of its own tree.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/03_organization_tree_in_the_sample_application.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/03_organization_tree_in_the_sample_application.mdx
new file mode 100644
index 00000000000..8c01a6aba63
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/03_organization_tree_in_the_sample_application.mdx
@@ -0,0 +1,47 @@
+---
+title: "Organization tree in the sample application"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/03_organization_tree_in_the_sample_application/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="organization_tree_in_the_sample_application" class="registered_link"></div>
+
+To see an example of an organizational tree, consider the `emp` table of the sample application. The rows of the `emp` table form a hierarchy based on the `mgr` column, which contains the employee number of the employee’s manager. Each employee has at most one manager. `KING` is the president of the company. He has no manager, therefore KING’s `mgr` column is null. Also, it's possible for an employee to act as a manager for more than one employee. This relationship forms a typical tree-structured hierarchical organization chart:
+
+![Employee Organization Hierarchy](../../../../images/employee_organization_hierarchy.png)
+
+To form a hierarchical query based on this relationship, the `SELECT` command includes the clause `CONNECT BY PRIOR empno = mgr`. For example, given the company president, `KING`, with employee number `7839`, any employee whose `mgr` column is `7839` reports directly to `KING`. This relationship is true for `JONES`, `BLAKE`, and `CLARK`, the child nodes of `KING`. Similarly, for employee `JONES`, any other employee with `mgr` column equal to `7566` is a child node of `JONES`. These nodes are `SCOTT` and `FORD` in the example.
+
+The top of the organization chart is `KING`, so there is one root node in this tree. The `START WITH mgr IS NULL` clause selects only `KING` as the initial root node.
+
+The complete `SELECT` command is:
+
+```sql
+SELECT ename, empno, mgr
+FROM emp
+START WITH mgr IS NULL
+CONNECT BY PRIOR empno = mgr;
+```
+
+The rows in the query output traverse each branch from the root to leaf moving in a top-to-bottom, left-to-right order: 
+
+```sql
+__OUTPUT__
+ename  | empno | mgr
+-------+-------+------
+KING   |  7839 |
+JONES  |  7566 | 7839
+SCOTT  |  7788 | 7566
+ADAMS  |  7876 | 7788
+FORD   |  7902 | 7566
+SMITH  |  7369 | 7902
+BLAKE  |  7698 | 7839
+ALLEN  |  7499 | 7698
+WARD   |  7521 | 7698
+MARTIN |  7654 | 7698
+TURNER |  7844 | 7698
+JAMES  |  7900 | 7698
+CLARK  |  7782 | 7839
+MILLER |  7934 | 7782
+(14 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/04_node_level.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/04_node_level.mdx
new file mode 100644
index 00000000000..bf2daa8d57a
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/04_node_level.mdx
@@ -0,0 +1,44 @@
+---
+title: "Designating the node level"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/04_node_level/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="node_level" class="registered_link"></div>
+
+`LEVEL` is a pseudo-column that you can use wherever a column can appear in the `SELECT` command. For each row in the result set, `LEVEL` returns a non-zero integer value designating the depth in the hierarchy of the node represented by this row. The `LEVEL` for root nodes is 1. The `LEVEL` for direct children of root nodes is 2, and so on.
+
+## Example 
+
+The following query is a modification of the previous query with the addition of the `LEVEL` pseudo-column. In addition, using the `LEVEL` value, the employee names are indented to further emphasize the depth in the hierarchy of each row.
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr
+FROM emp START WITH mgr IS NULL
+CONNECT BY PRIOR empno = mgr;
+```
+
+The output from this query is:
+
+```sql
+__OUTPUT__
+level |  employee   | empno | mgr
+------+-------------+-------+------
+   1  | KING        |  7839 |
+   2  |   JONES     |  7566 | 7839
+   3  |     SCOTT   |  7788 | 7566
+   4  |       ADAMS |  7876 | 7788
+   3  |     FORD    |  7902 | 7566
+   4  |       SMITH |  7369 | 7902
+   2  |   BLAKE     |  7698 | 7839
+   3  |     ALLEN   |  7499 | 7698
+   3  |     WARD    |  7521 | 7698
+   3  |     MARTIN  |  7654 | 7698
+   3  |     TURNER  |  7844 | 7698
+   3  |     JAMES   |  7900 | 7698
+   2  |   CLARK     |  7782 | 7839
+   3  |     MILLER  |  7934 | 7782
+(14 rows)
+```
+
+Nodes that share a common parent and are at the same level are called *siblings*. For example, in the above output, employees `ALLEN`, `WARD`, `MARTIN`, `TURNER`, and `JAMES` are siblings since they are all at level three with parent `BLAKE`. `JONES`, `BLAKE`, and `CLARK` are siblings since they are at level two and `KING` is their common parent.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/05_ordering_the_siblings.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/05_ordering_the_siblings.mdx
new file mode 100644
index 00000000000..35f599a88d2
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/05_ordering_the_siblings.mdx
@@ -0,0 +1,66 @@
+---
+title: "Ordering the siblings"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/05_ordering_the_siblings/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ordering_the_siblings" class="registered_link"></div>
+
+You can order the result set so the siblings appear in ascending or descending order by selected column values using the `ORDER SIBLINGS BY` clause. This is a special case of the `ORDER BY` clause that you can use only with hierarchical queries.
+
+You can further modify the previous query by adding `ORDER SIBLINGS BY` ename `ASC`.
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr
+FROM emp START WITH mgr IS NULL
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+The output from the prior query is now modified so the siblings appear in ascending order by name. Siblings `BLAKE`, `CLARK`, and `JONES` are now alphabetically arranged under `KING`. Siblings `ALLEN`, `JAMES`, `MARTIN`, `TURNER`, and `WARD` are alphabetically arranged under `BLAKE`, and so on.
+
+```sql
+__OUTPUT__
+level |  employee   | empno | mgr
+------+-------------+-------+------
+  1   | KING        |  7839 |
+  2   |   BLAKE     |  7698 | 7839
+  3   |     ALLEN   |  7499 | 7698
+  3   |     JAMES   |  7900 | 7698
+  3   |     MARTIN  |  7654 | 7698
+  3   |     TURNER  |  7844 | 7698
+  3   |     WARD    |  7521 | 7698
+  2   |   CLARK     |  7782 | 7839
+  3   |     MILLER  |  7934 | 7782
+  2   |   JONES     |  7566 | 7839
+  3   |     FORD    |  7902 | 7566
+  4   |       SMITH |  7369 | 7902
+  3   |     SCOTT   |  7788 | 7566
+  4   |       ADAMS |  7876 | 7788
+(14 rows)
+```
+
+This final example adds the `WHERE` clause and starts with three root nodes. After the node tree is constructed, the `WHERE` clause filters out rows in the tree to form the result set.
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr
+FROM emp WHERE mgr IN (7839, 7782, 7902, 7788)
+START WITH ename IN ('BLAKE','CLARK','JONES')
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+The output from the query shows three root nodes (level one): `BLAKE`, `CLARK`, and `JONES`. In addition, rows that don't satisfy the `WHERE` clause were eliminated from the output.
+
+```sql
+__OUTPUT__
+level | employee  | empno | mgr
+------+-----------+-------+------
+  1   | BLAKE     |  7698 | 7839
+  1   | CLARK     |  7782 | 7839
+  2   |   MILLER  |  7934 | 7782
+  1   | JONES     |  7566 | 7839
+  3   |     SMITH |  7369 | 7902
+  3   |     ADAMS |  7876 | 7788
+(6 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root.mdx
new file mode 100644
index 00000000000..0c1bbcbab9b
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root.mdx
@@ -0,0 +1,223 @@
+---
+title: "Retrieving the root node with CONNECT_BY_ROOT"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="retrieving_the_root_node_with_connect_by_root" class="registered_link"></div>
+
+`CONNECT_BY_ROOT` is a unary operator that you can use to qualify a column to return the column’s value of the row considered to be the root node in relation to the current row.
+
+!!! Note
+    A *unary operator* operates on a single operand. In the case of `CONNECT_BY_ROOT`, it's the column name following the `CONNECT_BY_ROOT` keyword.
+
+## Syntax 
+
+In the consql of the `SELECT` list, the `CONNECT_BY_ROOT` operator is shown by the following.
+
+```sql
+SELECT [... ,] CONNECT_BY_ROOT <column> [, ...]
+  FROM <table_expression> ...
+```
+
+Some points to note about the `CONNECT_BY_ROOT` operator:
+
+-   You can use the `CONNECT_BY_ROOT` operator in the `SELECT` list, `WHERE` clause, `GROUP BY` clause, `HAVING` clause, `ORDER BY` clause, and `ORDER SIBLINGS BY` clause as long as the `SELECT` command is for a hierarchical query.
+-   You can't use the `CONNECT_BY_ROOT` operator in the `CONNECT BY` clause or the `START WITH` clause of the hierarchical query.
+-   You can apply `CONNECT_BY_ROOT` to an expression involving a column. To do so, you must enclose the expression in parentheses.
+
+## Examples 
+
+The following query shows the use of the `CONNECT_BY_ROOT` operator to return the employee number and employee name of the root node for each employee listed in the result set based on trees starting with employees `BLAKE`, `CLARK`, and `JONES`.
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr,
+CONNECT_BY_ROOT empno "mgr empno",
+CONNECT_BY_ROOT ename "mgr ename"
+FROM emp
+START WITH ename IN ('BLAKE','CLARK','JONES')
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+The output from the query shows that all of the root nodes in columns `mgr empno` and `mgr ename` are one of the employees&mdash;`BLAKE`, `CLARK`, or `JONES`&mdash;listed in the `START WITH` clause.
+
+```sql
+__OUTPUT__
+level | employee  | empno | mgr  | mgr empno | mgr ename
+------+-----------+-------+------+-----------+-----------
+  1   | BLAKE     |  7698 | 7839 |      7698 | BLAKE
+  2   |   ALLEN   |  7499 | 7698 |      7698 | BLAKE
+  2   |   JAMES   |  7900 | 7698 |      7698 | BLAKE
+  2   |   MARTIN  |  7654 | 7698 |      7698 | BLAKE
+  2   |   TURNER  |  7844 | 7698 |      7698 | BLAKE
+  2   |   WARD    |  7521 | 7698 |      7698 | BLAKE
+  1   | CLARK     |  7782 | 7839 |      7782 | CLARK
+  2   |   MILLER  |  7934 | 7782 |      7782 | CLARK
+  1   | JONES     |  7566 | 7839 |      7566 | JONES
+  2   |   FORD    |  7902 | 7566 |      7566 | JONES
+  3   |     SMITH |  7369 | 7902 |      7566 | JONES
+  2   |   SCOTT   |  7788 | 7566 |      7566 | JONES
+  3   |     ADAMS |  7876 | 7788 |      7566 | JONES
+(13 rows)
+```
+
+A similar query but producing only one tree starting with the single, top-level employee where the `mgr` column is null:
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr,
+CONNECT_BY_ROOT empno "mgr empno",
+CONNECT_BY_ROOT ename "mgr ename"
+FROM emp START WITH mgr IS NULL
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+In the following output, all of the root nodes in columns `mgr empno` and `mgr ename` indicate `KING` as the root for this query:
+
+```sql
+__OUTPUT__
+level |  employee   | empno | mgr  | mgr empno | mgr ename
+------+-------------+-------+------+-----------+-----------
+    1 | KING        |  7839 |      |      7839 | KING
+    2 |   BLAKE     |  7698 | 7839 |      7839 | KING
+    3 |     ALLEN   |  7499 | 7698 |      7839 | KING
+    3 |     JAMES   |  7900 | 7698 |      7839 | KING
+    3 |     MARTIN  |  7654 | 7698 |      7839 | KING
+    3 |     TURNER  |  7844 | 7698 |      7839 | KING
+    3 |     WARD    |  7521 | 7698 |      7839 | KING
+    2 |   CLARK     |  7782 | 7839 |      7839 | KING
+    3 |     MILLER  |  7934 | 7782 |      7839 | KING
+    2 |   JONES     |  7566 | 7839 |      7839 | KING
+    3 |     FORD    |  7902 | 7566 |      7839 | KING
+    4 |       SMITH |  7369 | 7902 |      7839 | KING
+    3 |     SCOTT   |  7788 | 7566 |      7839 | KING
+    4 |       ADAMS |  7876 | 7788 |      7839 | KING
+(14 rows)
+```
+
+By contrast, this example omits the `START WITH` clause, thereby resulting in 14 trees:
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr,
+CONNECT_BY_ROOT empno "mgr empno",
+CONNECT_BY_ROOT ename "mgr ename"
+FROM emp
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+In the output from the query, each node appears at least once as a root node under the `mgr empno` and `mgr ename` columns, since even the leaf nodes form the top of their own trees.
+
+```sql
+__OUTPUT__
+level |  employee   | empno | mgr  | mgr empno | mgr ename
+------+-------------+-------+------+-----------+-----------
+    1 | ADAMS       |  7876 | 7788 |      7876 | ADAMS
+    1 | ALLEN       |  7499 | 7698 |      7499 | ALLEN
+    1 | BLAKE       |  7698 | 7839 |      7698 | BLAKE
+    2 |   ALLEN     |  7499 | 7698 |      7698 | BLAKE
+    2 |   JAMES     |  7900 | 7698 |      7698 | BLAKE
+    2 |   MARTIN    |  7654 | 7698 |      7698 | BLAKE
+    2 |   TURNER    |  7844 | 7698 |      7698 | BLAKE
+    2 |   WARD      |  7521 | 7698 |      7698 | BLAKE
+    1 | CLARK       |  7782 | 7839 |      7782 | CLARK
+    2 |   MILLER    |  7934 | 7782 |      7782 | CLARK
+    1 | FORD        |  7902 | 7566 |      7902 | FORD
+    2 |   SMITH     |  7369 | 7902 |      7902 | FORD
+    1 | JAMES       |  7900 | 7698 |      7900 | JAMES
+    1 | JONES       |  7566 | 7839 |      7566 | JONES
+    2 |   FORD      |  7902 | 7566 |      7566 | JONES
+    3 |     SMITH   |  7369 | 7902 |      7566 | JONES
+    2 |   SCOTT     |  7788 | 7566 |      7566 | JONES
+    3 |     ADAMS   |  7876 | 7788 |      7566 | JONES
+    1 | KING        |  7839 |      |      7839 | KING
+    2 |   BLAKE     |  7698 | 7839 |      7839 | KING
+    3 |     ALLEN   |  7499 | 7698 |      7839 | KING
+    3 |     JAMES   |  7900 | 7698 |      7839 | KING
+    3 |     MARTIN  |  7654 | 7698 |      7839 | KING
+    3 |     TURNER  |  7844 | 7698 |      7839 | KING
+    3 |     WARD    |  7521 | 7698 |      7839 | KING
+    2 |   CLARK     |  7782 | 7839 |      7839 | KING
+    3 |     MILLER  |  7934 | 7782 |      7839 | KING
+    2 |   JONES     |  7566 | 7839 |      7839 | KING
+    3 |     FORD    |  7902 | 7566 |      7839 | KING
+    4 |       SMITH |  7369 | 7902 |      7839 | KING
+    3 |     SCOTT   |  7788 | 7566 |      7839 | KING
+    4 |       ADAMS |  7876 | 7788 |      7839 | KING
+    1 | MARTIN      |  7654 | 7698 |      7654 | MARTIN
+    1 | MILLER      |  7934 | 7782 |      7934 | MILLER
+    1 | SCOTT       |  7788 | 7566 |      7788 | SCOTT
+    2 |   ADAMS     |  7876 | 7788 |      7788 | SCOTT
+    1 | SMITH       |  7369 | 7902 |      7369 | SMITH
+    1 | TURNER      |  7844 | 7698 |      7844 | TURNER
+    1 | WARD        |  7521 | 7698 |      7521 | WARD
+(39 rows)
+```
+
+When applied to an expression that isn't enclosed in parentheses, the `CONNECT_BY_ROOT` operator affects only the term `ename` immediately following it. The subsequent concatenation of `|| ' manages ' || ename` isn't part of the `CONNECT_BY_ROOT` operation. Hence the second occurrence of `ename` results in the value of the currently processed row, while the first occurrence of `ename` results in the value from the root node.
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr,
+CONNECT_BY_ROOT ename || ' manages ' || ename "top mgr/employee"
+FROM emp
+START WITH ename IN ('BLAKE','CLARK','JONES')
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+Note the values produced under the `top mgr/employee` column in the output from the query:
+
+```sql
+__OUTPUT__
+level | employee  | empno | mgr  |   top mgr/employee
+------+-----------+-------+------+----------------------
+    1 | BLAKE     |  7698 | 7839 | BLAKE manages BLAKE
+    2 |   ALLEN   |  7499 | 7698 | BLAKE manages ALLEN
+    2 |   JAMES   |  7900 | 7698 | BLAKE manages JAMES
+    2 |   MARTIN  |  7654 | 7698 | BLAKE manages MARTIN
+    2 |   TURNER  |  7844 | 7698 | BLAKE manages TURNER
+    2 |   WARD    |  7521 | 7698 | BLAKE manages WARD
+    1 | CLARK     |  7782 | 7839 | CLARK manages CLARK
+    2 |   MILLER  |  7934 | 7782 | CLARK manages MILLER
+    1 | JONES     |  7566 | 7839 | JONES manages JONES
+    2 |   FORD    |  7902 | 7566 | JONES manages FORD
+    3 |     SMITH |  7369 | 7902 | JONES manages SMITH
+    2 |   SCOTT   |  7788 | 7566 | JONES manages SCOTT
+    3 |     ADAMS |  7876 | 7788 | JONES manages ADAMS
+(13 rows)
+```
+
+This example uses the `CONNECT_BY_ROOT` operator on an expression enclosed in parentheses:
+
+```sql
+SELECT LEVEL, LPAD (' ', 2 * (LEVEL - 1)) || ename "employee", empno, mgr,
+CONNECT_BY_ROOT ('Manager ' || ename || ' is emp # ' || empno)
+"top mgr/empno"
+FROM emp
+START WITH ename IN ('BLAKE','CLARK','JONES')
+CONNECT BY PRIOR empno = mgr
+ORDER SIBLINGS BY ename ASC;
+```
+
+The values of both `ename` and `empno` are affected by the `CONNECT_BY_ROOT` operator. As a result, they return the values from the root node under the `top mgr/empno` column:
+
+```sql
+__OUTPUT__
+level | employee  | empno | mgr  |        top mgr/empno
+------+-----------+-------+------+-----------------------------
+    1 | BLAKE     |  7698 | 7839 | Manager BLAKE is emp # 7698
+    2 |   ALLEN   |  7499 | 7698 | Manager BLAKE is emp # 7698
+    2 |   JAMES   |  7900 | 7698 | Manager BLAKE is emp # 7698
+    2 |   MARTIN  |  7654 | 7698 | Manager BLAKE is emp # 7698
+    2 |   TURNER  |  7844 | 7698 | Manager BLAKE is emp # 7698
+    2 |   WARD    |  7521 | 7698 | Manager BLAKE is emp # 7698
+    1 | CLARK     |  7782 | 7839 | Manager CLARK is emp # 7782
+    2 |   MILLER  |  7934 | 7782 | Manager CLARK is emp # 7782
+    1 | JONES     |  7566 | 7839 | Manager JONES is emp # 7566
+    2 |   FORD    |  7902 | 7566 | Manager JONES is emp # 7566
+    3 |     SMITH |  7369 | 7902 | Manager JONES is emp # 7566
+    2 |   SCOTT   |  7788 | 7566 | Manager JONES is emp # 7566
+    3 |     ADAMS |  7876 | 7788 | Manager JONES is emp # 7566
+(13 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/07_retrieving_a_path_with_sys_connect_by_path.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/07_retrieving_a_path_with_sys_connect_by_path.mdx
new file mode 100644
index 00000000000..ef90f228ea9
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/07_retrieving_a_path_with_sys_connect_by_path.mdx
@@ -0,0 +1,63 @@
+---
+title: "Retrieving a path with SYS_CONNECT_BY_PATH"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/07_retrieving_a_path_with_sys_connect_by_path/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="retrieving_a_path_with_sys_connect_by_path" class="registered_link"></div>
+
+`SYS_CONNECT_BY_PATH` is a function that works in a hierarchical query to retrieve the column values of a specified column that occur between the current node and the root node. 
+
+## Syntax 
+
+The signature of the function is:
+
+```sql
+SYS_CONNECT_BY_PATH (<column>, <delimiter>)
+```
+
+The function takes two arguments:
+
+-  `column` is the name of a column that resides in a table specified in the hierarchical query that's calling the function.
+-  `delimiter` is the `varchar` value that separates each entry in the specified column.
+
+## Examples 
+
+This example returns a list of employee names and their managers. If the manager has a manager, that name is appended to the result.
+
+```sql
+edb=# SELECT level, ename , SYS_CONNECT_BY_PATH(ename, '/') managers
+      FROM emp
+      CONNECT BY PRIOR empno = mgr
+      START WITH mgr IS NULL
+      ORDER BY level, ename, managers;
+__OUTPUT__
+ level | ename  |        managers
+-------+--------+-------------------------
+     1 | KING   | /KING
+     2 | BLAKE  | /KING/BLAKE
+     2 | CLARK  | /KING/CLARK
+     2 | JONES  | /KING/JONES
+     3 | ALLEN  | /KING/BLAKE/ALLEN
+     3 | FORD   | /KING/JONES/FORD
+     3 | JAMES  | /KING/BLAKE/JAMES
+     3 | MARTIN | /KING/BLAKE/MARTIN
+     3 | MILLER | /KING/CLARK/MILLER
+     3 | SCOTT  | /KING/JONES/SCOTT
+     3 | TURNER | /KING/BLAKE/TURNER
+     3 | WARD   | /KING/BLAKE/WARD
+     4 | ADAMS  | /KING/JONES/SCOTT/ADAMS
+     4 | SMITH  | /KING/JONES/FORD/SMITH
+(14 rows)
+```
+
+In the result set:
+
+-   The `level` column displays the number of levels that the query returned.
+-   The `ename` column displays the employee name.
+-   The `managers` column contains the hierarchical list of managers.
+
+The EDB Postgres Advanced Server implementation of `SYS_CONNECT_BY_PATH` doesn't support use of:
+
+-   `SYS_CONNECT_BY_PATH` inside `CONNECT_BY_PATH`
+-   `SYS_CONNECT_BY_PATH` inside `SYS_CONNECT_BY_PATH`
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/index.mdx
new file mode 100644
index 00000000000..af6471ee026
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/05_hierarchical_queries/index.mdx
@@ -0,0 +1,219 @@
+---
+title: "Hierarchical queries"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.022.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.022.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.036.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/05_hierarchical_queries/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="hierarchical_queries" class="registered_link"></div>
+
+A *hierarchical query* is a type of query that returns the rows of the result set in a hierarchical order based on data forming a parent-child relationship. A hierarchy is typically represented by an inverted tree structure. The tree is made up of interconnected *nodes*. Each node can be connected to none, one, or multiple *child* nodes. Each node is connected to one *parent* node except for the top node, which has no parent. This node is the *root* node. Each tree has exactly one root node. 
+
+Nodes that don’t have any children are called *leaf* nodes. A tree always has at least one leaf node, for example, the trivial case where the tree is made up of a single node. In this case, the node is both the root and the leaf.
+
+In a hierarchical query, the rows of the result set represent the nodes of one or more trees.
+
+!!! Note
+    A single given row can appear in more than one tree and thus appear more than once in the result set.
+
+## Syntax 
+
+The hierarchical relationship in a query is described by the `CONNECT BY` clause, which forms the basis of the order in which rows are returned in the result set. This example shows the context of where the `CONNECT BY` clause and its associated optional clauses appear in the `SELECT` command:
+
+```sql
+SELECT <select_list> FROM <table_expression> [ WHERE ...]
+  [ START WITH <start_expression> ]
+    { CONNECT BY <condition> }
+  [ ORDER SIBLINGS BY <column1> [ ASC | DESC ]
+      [, <column2> [ ASC | DESC ] ] ...
+  [ GROUP BY ...]
+  [ HAVING ...]
+  [ <other> ...]
+```
+
+`select_list` is one or more expressions that make up the fields of the result set. `table_expression` is one or more tables or views from which the rows of the result set originate. `other` is any additional legal `SELECT` command clauses. 
+
+`CONNECT BY` specifies the relationship between a parent record and its child records of the hierarchy. 
+
+-  You can specify the `PRIOR` keyword with only one expression in a condition in the `CONNECT BY` clause. You must specify it with either right or left expression to refer to a parent row in a hierarchical query. For example:
+
+   ```sql
+   PRIOR expr = expr
+   or
+   expr = PRIOR expr
+   ```
+
+-  If the `CONNECT BY condition` is compound, only one condition requires the `PRIOR` keyword, although there can be multiple `PRIOR` conditions.
+
+-  You can use the `PRIOR` keyword to evaluate the parent row in a parent-child relationship in a hierarchical query. 
+
+-  You can't use `PRIOR` keyword with unary expressions.
+
+-  You can use the `PRIOR` keyword to add a pseudo-column for each record corresponding to an expression in a target list. The pseudo-column represents a parent record's actual value when referenced in a child query using a `PRIOR` expression.
+
+Use the `CONNECT_BY_ROOT` operator to further enhance the functionality of the `CONNECT BY [PRIOR]` condition. This operator returns not only immediate parent rows but also all ancestors rows in the hierarchy. For more information, see [Retrieving the root node with CONNECT_BY_ROOT](../05_hierarchical_queries/06_retrieving_the_root_node_with_connect_by_root/#retrieving_the_root_node_with_connect_by_root).
+
+## Examples
+
+This example uses the `CONNECT BY` clause with `PRIOR` to define a relationship between employees and managers. Using the `LEVEL` value, the employee names are indented to further emphasize the depth in the hierarchy of each row.
+
+```sql
+SELECT LPAD(ename,length(ename)+2 *(LEVEL - 1),' ') AS employee, empno, mgr, LEVEL 
+FROM emp 
+CONNECT BY PRIOR empno = mgr AND PRIOR emp.deptno = emp.deptno;
+```
+
+The output from this query is:
+
+```sql
+__OUTPUT__
+employee    | empno | mgr  | level 
+------------+-------+------+-------
+ SMITH      |  7369 | 7902 |     1
+ ALLEN      |  7499 | 7698 |     1
+ WARD       |  7521 | 7698 |     1
+ JONES      |  7566 | 7839 |     1
+   FORD     |  7902 | 7566 |     2
+     SMITH  |  7369 | 7902 |     3
+   SCOTT    |  7788 | 7566 |     2
+     ADAMS  |  7876 | 7788 |     3
+ MARTIN     |  7654 | 7698 |     1
+ BLAKE      |  7698 | 7839 |     1
+   WARD     |  7521 | 7698 |     2
+   TURNER   |  7844 | 7698 |     2
+   MARTIN   |  7654 | 7698 |     2
+   JAMES    |  7900 | 7698 |     2
+   ALLEN    |  7499 | 7698 |     2
+ CLARK      |  7782 | 7839 |     1
+   MILLER   |  7934 | 7782 |     2
+ SCOTT      |  7788 | 7566 |     1
+   ADAMS    |  7876 | 7788 |     2
+ KING       |  7839 |      |     1
+   CLARK    |  7782 | 7839 |     2
+     MILLER |  7934 | 7782 |     3
+ TURNER     |  7844 | 7698 |     1
+ ADAMS      |  7876 | 7788 |     1
+ JAMES      |  7900 | 7698 |     1
+ FORD       |  7902 | 7566 |     1
+   SMITH    |  7369 | 7902 |     2
+ MILLER     |  7934 | 7782 |     1
+(28 rows)
+```
+
+This example adds the `ORDER BY` clause and a compound condition with `AND` operator in a `CONNECT BY` clause to show employee and manager hierarchy:
+
+```sql
+SELECT LPAD(ename,length(ename)+2 *(LEVEL - 1),' ') AS employee, empno, mgr, LEVEL
+FROM emp
+CONNECT BY PRIOR empno = mgr AND LEVEL <= 3
+ORDER BY LEVEL, ename;
+```
+
+The output from this query is:
+
+```sql
+__OUTPUT__
+employee    | empno | mgr  | level 
+------------+-------+------+-------
+ ADAMS      |  7876 | 7788 |     1
+ ALLEN      |  7499 | 7698 |     1
+ BLAKE      |  7698 | 7839 |     1
+ CLARK      |  7782 | 7839 |     1
+ FORD       |  7902 | 7566 |     1
+ JAMES      |  7900 | 7698 |     1
+ JONES      |  7566 | 7839 |     1
+ KING       |  7839 |      |     1
+ MARTIN     |  7654 | 7698 |     1
+ MILLER     |  7934 | 7782 |     1
+ SCOTT      |  7788 | 7566 |     1
+ SMITH      |  7369 | 7902 |     1
+ TURNER     |  7844 | 7698 |     1
+ WARD       |  7521 | 7698 |     1
+   ADAMS    |  7876 | 7788 |     2
+   ALLEN    |  7499 | 7698 |     2
+   BLAKE    |  7698 | 7839 |     2
+   CLARK    |  7782 | 7839 |     2
+   FORD     |  7902 | 7566 |     2
+   JAMES    |  7900 | 7698 |     2
+   JONES    |  7566 | 7839 |     2
+   MARTIN   |  7654 | 7698 |     2
+   MILLER   |  7934 | 7782 |     2
+   SCOTT    |  7788 | 7566 |     2
+   SMITH    |  7369 | 7902 |     2
+   TURNER   |  7844 | 7698 |     2
+   WARD     |  7521 | 7698 |     2
+     ADAMS  |  7876 | 7788 |     3
+     ALLEN  |  7499 | 7698 |     3
+     FORD   |  7902 | 7566 |     3
+     JAMES  |  7900 | 7698 |     3
+     MARTIN |  7654 | 7698 |     3
+     MILLER |  7934 | 7782 |     3
+     SCOTT  |  7788 | 7566 |     3
+     SMITH  |  7369 | 7902 |     3
+     TURNER |  7844 | 7698 |     3
+     WARD   |  7521 | 7698 |     3
+(37 rows)
+```
+
+This example uses the `PRIOR` keyword to return the employee name and manager name for each employee:
+
+```sql
+SELECT ename, PRIOR ename AS mgr FROM emp START WITH mgr 
+IS NULL CONNECT BY PRIOR empno = mgr ORDER BY ename;
+```
+
+The output from this query is:
+
+```sql
+__OUTPUT__
+ename   |  mgr  
+--------+-------
+ ADAMS  | SCOTT
+ ALLEN  | BLAKE
+ BLAKE  | KING
+ CLARK  | KING
+ FORD   | JONES
+ JAMES  | BLAKE
+ JONES  | KING
+ KING   | 
+ MARTIN | BLAKE
+ MILLER | CLARK
+ SCOTT  | JONES
+ SMITH  | FORD
+ TURNER | BLAKE
+ WARD   | BLAKE
+(14 rows)
+```
+
+This example uses a `CONNECT BY` clause with an optional `PRIOR` statement to show the level value:
+
+```sql
+SELECT LEVEL
+FROM DUAL
+CONNECT BY LEVEL <= 5;
+```
+
+The output from this query is:
+
+```sql
+__OUTPUT__
+level 
+--------
+     1
+     2
+     3
+     4
+     5
+(5 rows)
+```
+
+
+<div class="toctree" maxdepth="3">
+
+defining_the_parent_child_relationship selecting_the_root_nodes organization_tree_in_the_sample_application node_level ordering_the_siblings retrieving_the_root_node_with_connect_by_root retrieving_a_path_with_sys_connect_by_path
+
+</div>
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/01_rollup_extension.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/01_rollup_extension.mdx
new file mode 100644
index 00000000000..172126bafff
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/01_rollup_extension.mdx
@@ -0,0 +1,158 @@
+---
+title: "ROLLUP extension"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.024.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.024.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/01_rollup_extension/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="rollup_extension" class="registered_link"></div>
+
+The `ROLLUP` extension produces a hierarchical set of groups with subtotals for each hierarchical group as well as a grand total. The order of the hierarchy is determined by the order of the expressions given in the `ROLLUP` expression list. The top of the hierarchy is the left-most item in the list. Each successive item proceeding to the right moves down the hierarchy. The right-most item is at the lowest level.
+
+## Syntax 
+
+The syntax for a single `ROLLUP` is:
+
+```sql
+ROLLUP ( { <expr_1> | ( <expr_1a> [, <expr_1b> ] ...) }
+  [, <expr_2> | ( <expr_2a> [, <expr_2b> ] ...) ] ...)
+```
+
+Each `expr` is an expression that determines the grouping of the result set. If enclosed in parenthesis as `( expr_1a, expr_1b, ...)`, then the combination of values returned by `expr_1a` and `expr_1b` defines a single grouping level of the hierarchy.
+
+The base level of aggregates returned in the result set is for each unique combination of values returned by the expression list.
+
+In addition, a subtotal is returned for the first item in the list (`expr_1` or the combination of `( expr_1a, expr_1b, ...)`, whichever is specified) for each unique value. A subtotal is returned for the second item in the list (`expr_2` or the combination of `( expr_2a, expr_2b, ...)`, whichever is specified) for each unique value in each grouping of the first item and so on. Finally, a grand total is returned for the entire result set.
+
+For the subtotal rows, null is returned for the items across which the subtotal is taken.
+
+The `ROLLUP` extension specified in the context of the `GROUP BY` clause is shown by the following:
+
+```sql
+SELECT <select_list> FROM ...
+GROUP BY [... ,] ROLLUP ( <expression_list> ) [, ...]
+```
+
+The items specified in `select_list` must either:
+
+-  Also appear in the `ROLLUP expression_list` 
+-  Be aggregate functions such as `COUNT`, `SUM`, `AVG`, `MIN,` or `MAX`
+-  Be constants or functions whose return values are independent of the individual rows in the group (for example, the `SYSDATE` function)
+
+Use the `GROUP BY` clause to specify multiple `ROLLUP` extensions as well as multiple occurrences of other `GROUP BY` extensions and individual expressions.
+
+Use the `ORDER BY` clause to display the output in a hierarchical or other meaningful structure. Using this clause guarantees the order of the result set.
+
+The number of grouping levels or totals is *n* + *1* where *n* represents the number of items in the `ROLLUP` expression list. A parenthesized list counts as one item.
+
+## Examples 
+
+The following query produces a rollup based on a hierarchy of columns `loc`, `dname`, and then `job`.
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (loc, dname, job)
+ORDER BY 1, 2, 3;
+```
+
+The result of the query displays a count of the number of employees for each unique combination of `loc`, `dname`, and `job`, as well as subtotals for each unique combination of `loc` and `dname` for each unique value of `loc`. A grand total appears on the last line:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | OPERATIONS |           |         3
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   | RESEARCH   |           |         5
+BOSTON   |            |           |         8
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  | SALES      |           |         6
+CHICAGO  |            |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK | ACCOUNTING |           |         3
+NEW YORK |            |           |         3
+         |            |           |        17
+(20 rows)
+```
+
+The following query shows the effect of combining items in the `ROLLUP` list in parentheses:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (loc, (dname, job))
+ORDER BY 1, 2, 3;
+```
+
+The output doesn't include subtotals for `loc` and `dname` combinations as in the prior example:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   |            |           |         8
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  |            |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK |            |           |         3
+         |            |           |        17
+(16 rows)
+```
+
+If the first two columns in the `ROLLUP` list are enclosed in parentheses, the subtotal levels differ as well:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP ((loc, dname), job)
+ORDER BY 1, 2, 3;
+```
+
+Now there's a subtotal for each unique `loc` and `dname` combination but none for unique values of `loc`:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | OPERATIONS |           |         3
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   | RESEARCH   |           |         5
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  | SALES      |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK | ACCOUNTING |           |         3
+         |            |           |        17
+(17 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/02_cube_extension.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/02_cube_extension.mdx
new file mode 100644
index 00000000000..e74134f2a7b
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/02_cube_extension.mdx
@@ -0,0 +1,227 @@
+---
+title: "CUBE extension"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.025.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.025.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/02_cube_extension/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="cube_extension" class="registered_link"></div>
+
+The `CUBE` extension is similar to the `ROLLUP` extension. However, `ROLLUP` produces groupings and results in a hierarchy based on a left-to-right listing of items in the `ROLLUP` expression list. A `CUBE` produces groupings and subtotals based on every permutation of all items in the `CUBE` expression list. Thus, the result set contains more rows than a `ROLLUP` performed on the same expression list.
+
+## Syntax 
+
+The syntax for a single `CUBE` is:
+
+```sql
+CUBE ( { <expr_1> | ( <expr_1a> [, <expr_1b> ] ...) }
+  [, <expr_2> | ( <expr_2a> [, <expr_2b> ] ...) ] ...)
+```
+
+Each `expr` is an expression that determines the grouping of the result set. If enclosed in parenthesis as `( expr_1a, expr_1b, ...)`, then the combination of values returned by `expr_1a` and `expr_1b` defines a single group.
+
+The base level of aggregates returned in the result set is for each unique combination of values returned by the expression list.
+
+In addition, a subtotal is returned for the first item in the list (`expr_1` or the combination of `( expr_1a, expr_1b, ...)`, whichever is specified) for each unique value. A subtotal is returned for the second item in the list (`expr_2` or the combination of `( expr_2a, expr_2b, ...)`, whichever is specified) for each unique value. A subtotal is also returned for each unique combination of the first item and the second item. Similarly, if there's a third item, a subtotal is returned for:
+
+-  Each unique value of the third item
+-  Each unique value of the third item and first item combination 
+-  Each unique value of the third item and second item combination
+-  Each unique value of the third item, second item, and first item combination
+
+Finally, a grand total is returned for the entire result set.
+
+For the subtotal rows, null is returned for the items across which the subtotal is taken.
+
+The `CUBE` extension specified in the context of the `GROUP BY` clause is shown by the following:
+
+```sql
+SELECT <select_list> FROM ...
+GROUP BY [... ,] CUBE ( <expression_list> ) [, ...]
+```
+
+The items specified in `select_list` must either: 
+
+-  Also appear in the `CUBE expression_list`
+-  Be aggregate functions such as `COUNT`, `SUM`, `AVG`, `MIN`, or `MAX`
+-  Be constants or functions whose return values are independent of the individual rows in the group (for example, the `SYSDATE` function)
+
+Use the `GROUP BY` clause to specify multiple `CUBE` extensions as well as multiple occurrences of other `GROUP BY` extensions and individual expressions.
+
+Use the `ORDER BY` clause to display the output in a meaningful structure and to guarantee the order of the result set.
+
+The number of grouping levels or totals is `2` raised to the power of *n*, where *n* represents the number of items in the `CUBE` expression list. A parenthesized list counts as one item.
+
+## Examples 
+
+The following query produces a cube based on permutations of columns `loc`, `dname`, and `job`.
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (loc, dname, job)
+ORDER BY 1, 2, 3;
+```
+
+The following is the result of the query. It displays a count of the number of employees for each combination of `loc`, `dname`, and `job`, as well as subtotals for:
+
+-  Each combination of `loc` and `dname`
+-  Each combination of `loc` and `job`
+-  Each combination of `dname` and `job`
+-  Each unique value of `loc`
+-  Each unique value of `dname`
+-  Each unique value of `job`
+
+A grand total appears on the last line.
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | OPERATIONS |           |         3
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   | RESEARCH   |           |         5
+BOSTON   |            | ANALYST   |         3
+BOSTON   |            | CLERK     |         3
+BOSTON   |            | MANAGER   |         2
+BOSTON   |            |           |         8
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  | SALES      |           |         6
+CHICAGO  |            | CLERK     |         1
+CHICAGO  |            | MANAGER   |         1
+CHICAGO  |            | SALESMAN  |         4
+CHICAGO  |            |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK | ACCOUNTING |           |         3
+NEW YORK |            | CLERK     |         1
+NEW YORK |            | MANAGER   |         1
+NEW YORK |            | PRESIDENT |         1
+NEW YORK |            |           |         3
+         | ACCOUNTING | CLERK     |         1
+         | ACCOUNTING | MANAGER   |         1
+         | ACCOUNTING | PRESIDENT |         1
+         | ACCOUNTING |           |         3
+         | OPERATIONS | ANALYST   |         1
+         | OPERATIONS | CLERK     |         1
+         | OPERATIONS | MANAGER   |         1
+         | OPERATIONS |           |         3
+         | RESEARCH   | ANALYST   |         2
+         | RESEARCH   | CLERK     |         2
+         | RESEARCH   | MANAGER   |         1
+         | RESEARCH   |           |         5
+         | SALES      | CLERK     |         1
+         | SALES      | MANAGER   |         1
+         | SALES      | SALESMAN  |         4
+         | SALES      |           |         6
+         |            | ANALYST   |         3
+         |            | CLERK     |         5
+         |            | MANAGER   |         4
+         |            | PRESIDENT |         1
+         |            | SALESMAN  |         4
+         |            |           |        17
+(50 rows)
+```
+
+The following query shows the effect of combining items in the `CUBE` list in parentheses:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (loc, (dname, job))
+ORDER BY 1, 2, 3;
+```
+
+The output has no subtotals for permutations involving `loc` and `dname` combinations, `loc` and `job` combinations, for `dname` by itself, or for `job` by itself.
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   |            |           |         8
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  |            |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK |            |           |         3
+         | ACCOUNTING | CLERK     |         1
+         | ACCOUNTING | MANAGER   |         1
+         | ACCOUNTING | PRESIDENT |         1
+         | OPERATIONS | ANALYST   |         1
+         | OPERATIONS | CLERK     |         1
+         | OPERATIONS | MANAGER   |         1
+         | RESEARCH   | ANALYST   |         2
+         | RESEARCH   | CLERK     |         2
+         | RESEARCH   | MANAGER   |         1
+         | SALES      | CLERK     |         1
+         | SALES      | MANAGER   |         1
+         | SALES      | SALESMAN  |         4
+         |            |           |        17
+(28 rows)
+```
+
+The following query shows another variation whereby the first expression is specified outside of the `CUBE` extension:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY loc, CUBE (dname, job)
+ORDER BY 1, 2, 3;
+```
+
+In this output, the permutations are performed for `dname` and `job` in each grouping of `loc`:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | OPERATIONS |           |         3
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+BOSTON   | RESEARCH   |           |         5
+BOSTON   |            | ANALYST   |         3
+BOSTON   |            | CLERK     |         3
+BOSTON   |            | MANAGER   |         2
+BOSTON   |            |           |         8
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+CHICAGO  | SALES      |           |         6
+CHICAGO  |            | CLERK     |         1
+CHICAGO  |            | MANAGER   |         1
+CHICAGO  |            | SALESMAN  |         4
+CHICAGO  |            |           |         6
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+NEW YORK | ACCOUNTING |           |         3
+NEW YORK |            | CLERK     |         1
+NEW YORK |            | MANAGER   |         1
+NEW YORK |            | PRESIDENT |         1
+NEW YORK |            |           |         3
+(28 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/03_grouping_sets_extension.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/03_grouping_sets_extension.mdx
new file mode 100644
index 00000000000..e3a166ab7fe
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/03_grouping_sets_extension.mdx
@@ -0,0 +1,330 @@
+---
+title: "GROUPING SETS extension"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.026.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/03_grouping_sets_extension/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="grouping_sets_extension" class="registered_link"></div>
+
+The use of the `GROUPING SETS` extension in the `GROUP BY` clause provides a means to produce one result set that's the concatenation of multiple results sets based on different groupings. In other words, a `UNION ALL` operation is performed combining the result sets of multiple groupings into one result set.
+
+A `UNION ALL` operation, and therefore the `GROUPING SETS` extension, doesn't eliminate duplicate rows from the result sets that are being combined.
+
+## Syntax 
+
+The syntax for a single `GROUPING SETS` extension is:
+
+```sql
+GROUPING SETS (
+   { <expr_1> | ( <expr_1a> [, <expr_1b> ] ...) |
+     ROLLUP ( <expr_list> ) | CUBE ( <expr_list> )
+   } [, ...] )
+```
+
+A `GROUPING SETS` extension can contain any combination of one or more comma-separated expressions, lists of expressions enclosed in parentheses, `ROLLUP` extensions, and `CUBE` extensions.
+
+The `GROUPING SETS` extension is specified in the context of the `GROUP BY` clause:
+
+```sql
+SELECT <select_list> FROM ...
+GROUP BY [... ,] GROUPING SETS ( <expression_list> ) [, ...]
+```
+
+The items specified in `select_list` must also either: 
+
+-  Appear in the `GROUPING SETS expression_list`
+-  Be aggregate functions such as `COUNT, SUM, AVG, MIN`, or `MAX`
+-  Be constants or functions whose return values are independent of the individual rows in the group (for example, the `SYSDATE` function)
+
+Use the `GROUP BY` clause to specify multiple `GROUPING SETS` extensions as well as multiple occurrences of other `GROUP BY` extensions and individual expressions.
+
+Use the `ORDER BY` clause to display the output in a meaningful structure and to guarantee the order of the result set.
+
+## Examples 
+
+The following query produces a union of groups given by columns `loc`, `dname`, and `job`:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY GROUPING SETS (loc, dname, job)
+ORDER BY 1, 2, 3;
+```
+
+The result is as follows:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   |            |           |         8
+CHICAGO  |            |           |         6
+NEW YORK |            |           |         3
+         | ACCOUNTING |           |         3
+         | OPERATIONS |           |         3
+         | RESEARCH   |           |         5
+         | SALES      |           |         6
+         |            | ANALYST   |         3
+         |            | CLERK     |         5
+         |            | MANAGER   |         4
+         |            | PRESIDENT |         1
+         |            | SALESMAN  |         4
+(12 rows)
+```
+
+This is equivalent to the following query, which uses the `UNION ALL` operator:
+
+```sql
+SELECT loc AS "loc", NULL AS "dname", NULL AS "job", COUNT(*) AS "employees"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY loc
+  UNION ALL
+SELECT NULL, dname, NULL, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY dname
+  UNION ALL
+SELECT NULL, NULL, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY job
+ORDER BY 1, 2, 3;
+```
+
+The output from the `UNION ALL` query is the same as the `GROUPING SETS` output:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   |            |           |         8
+CHICAGO  |            |           |         6
+NEW YORK |            |           |         3
+         | ACCOUNTING |           |         3
+         | OPERATIONS |           |         3
+         | RESEARCH   |           |         5
+         | SALES      |           |         6
+         |            | ANALYST   |         3
+         |            | CLERK     |         5
+         |            | MANAGER   |         4
+         |            | PRESIDENT |         1
+         |            | SALESMAN  |         4
+(12 rows)
+```
+
+This example shows how you can use various types of `GROUP BY` extensions together in a `GROUPING SETS` expression list:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY GROUPING SETS (loc, ROLLUP (dname, job), CUBE (job, loc))
+ORDER BY 1, 2, 3;
+```
+
+The following is the output from this query:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   |            | ANALYST   |         3
+BOSTON   |            | CLERK     |         3
+BOSTON   |            | MANAGER   |         2
+BOSTON   |            |           |         8
+BOSTON   |            |           |         8
+CHICAGO  |            | CLERK     |         1
+CHICAGO  |            | MANAGER   |         1
+CHICAGO  |            | SALESMAN  |         4
+CHICAGO  |            |           |         6
+CHICAGO  |            |           |         6
+NEW YORK |            | CLERK     |         1
+NEW YORK |            | MANAGER   |         1
+NEW YORK |            | PRESIDENT |         1
+NEW YORK |            |           |         3
+NEW YORK |            |           |         3
+         | ACCOUNTING | CLERK     |         1
+         | ACCOUNTING | MANAGER   |         1
+         | ACCOUNTING | PRESIDENT |         1
+         | ACCOUNTING |           |         3
+         | OPERATIONS | ANALYST   |         1
+         | OPERATIONS | CLERK     |         1
+         | OPERATIONS | MANAGER   |         1
+         | OPERATIONS |           |         3
+         | RESEARCH   | ANALYST   |         2
+         | RESEARCH   | CLERK     |         2
+         | RESEARCH   | MANAGER   |         1
+         | RESEARCH   |           |         5
+         | SALES      | CLERK     |         1
+         | SALES      | MANAGER   |         1
+         | SALES      | SALESMAN  |         4
+         | SALES      |           |         6
+         |            | ANALYST   |         3
+         |            | CLERK     |         5
+         |            | MANAGER   |         4
+         |            | PRESIDENT |         1
+         |            | SALESMAN  |         4
+         |            |           |        17
+         |            |           |        17
+(38 rows)
+```
+
+The output is basically a concatenation of the result sets from `GROUP BY loc`, `GROUP BY ROLLUP (dname, job)`, and `GROUP BY CUBE (job, loc)`. These individual queries are:
+
+```sql
+SELECT loc, NULL AS "dname", NULL AS "job", COUNT(*) AS "employees"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY loc
+ORDER BY 1;
+```
+
+The result set from the `GROUP BY loc` clause is:
+
+```sql
+__OUTPUT__
+loc      | dname | job | employees
+----------+-------+-----+-----------
+BOSTON   |       |     |         8
+CHICAGO  |       |     |         6
+NEW YORK |       |     |         3
+(3 rows)
+```
+
+The following query uses the `GROUP BY ROLLUP (dname, job)` clause:
+
+```sql
+SELECT NULL AS "loc", dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (dname, job)
+ORDER BY 2, 3;
+```
+
+The result set from the `GROUP BY ROLLUP (dname, job)` clause is:
+
+```sql
+__OUTPUT__
+loc |   dname    |    job    | employees
+----+------------+-----------+-----------
+    | ACCOUNTING | CLERK     |         1
+    | ACCOUNTING | MANAGER   |         1
+    | ACCOUNTING | PRESIDENT |         1
+    | ACCOUNTING |           |         3
+    | OPERATIONS | ANALYST   |         1
+    | OPERATIONS | CLERK     |         1
+    | OPERATIONS | MANAGER   |         1
+    | OPERATIONS |           |         3
+    | RESEARCH   | ANALYST   |         2
+    | RESEARCH   | CLERK     |         2
+    | RESEARCH   | MANAGER   |         1
+    | RESEARCH   |           |         5
+    | SALES      | CLERK     |         1
+    | SALES      | MANAGER   |         1
+    | SALES      | SALESMAN  |         4
+    | SALES      |           |         6
+    |            |           |        17
+(17 rows)
+```
+
+The following query uses the `GROUP BY CUBE (job, loc)` clause:
+
+```sql
+SELECT loc, NULL AS "dname", job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (job, loc)
+ORDER BY 1, 3;
+```
+
+The result set from the `GROUP BY CUBE (job, loc)` clause is:
+
+```sql
+__OUTPUT__
+loc      | dname |    job    | employees
+---------+-------+-----------+-----------
+BOSTON   |       | ANALYST   |         3
+BOSTON   |       | CLERK     |         3
+BOSTON   |       | MANAGER   |         2
+BOSTON   |       |           |         8
+CHICAGO  |       | CLERK     |         1
+CHICAGO  |       | MANAGER   |         1
+CHICAGO  |       | SALESMAN  |         4
+CHICAGO  |       |           |         6
+NEW YORK |       | CLERK     |         1
+NEW YORK |       | MANAGER   |         1
+NEW YORK |       | PRESIDENT |         1
+NEW YORK |       |           |         3
+         |       | ANALYST   |         3
+         |       | CLERK     |         5
+         |       | MANAGER   |         4
+         |       | PRESIDENT |         1
+         |       | SALESMAN  |         4
+         |       |           |        17
+(18 rows)
+```
+
+If the previous three queries are combined with the `UNION ALL` operator, a concatenation of the three results sets is produced:
+
+```sql
+SELECT loc AS "loc", NULL AS "dname", NULL AS "job", COUNT(*) AS "employees"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY loc
+  UNION ALL
+SELECT NULL, dname, job, count(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (dname, job)
+  UNION ALL
+SELECT loc, NULL, job, count(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (job, loc)
+ORDER BY 1, 2, 3;
+```
+
+The output is the same as when the `GROUP BY GROUPING SETS (loc, ROLLUP (dname, job), CUBE (job, loc))` clause is used.
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   |            | ANALYST   |         3
+BOSTON   |            | CLERK     |         3
+BOSTON   |            | MANAGER   |         2
+BOSTON   |            |           |         8
+BOSTON   |            |           |         8
+CHICAGO  |            | CLERK     |         1
+CHICAGO  |            | MANAGER   |         1
+CHICAGO  |            | SALESMAN  |         4
+CHICAGO  |            |           |         6
+CHICAGO  |            |           |         6
+NEW YORK |            | CLERK     |         1
+NEW YORK |            | MANAGER   |         1
+NEW YORK |            | PRESIDENT |         1
+NEW YORK |            |           |         3
+NEW YORK |            |           |         3
+         | ACCOUNTING | CLERK     |         1
+         | ACCOUNTING | MANAGER   |         1
+         | ACCOUNTING | PRESIDENT |         1
+         | ACCOUNTING |           |         3
+         | OPERATIONS | ANALYST   |         1
+         | OPERATIONS | CLERK     |         1
+         | OPERATIONS | MANAGER   |         1
+         | OPERATIONS |           |         3
+         | RESEARCH   | ANALYST   |         2
+         | RESEARCH   | CLERK     |         2
+         | RESEARCH   | MANAGER   |         1
+         | RESEARCH   |           |         5
+         | SALES      | CLERK     |         1
+         | SALES      | MANAGER   |         1
+         | SALES      | SALESMAN  |         4
+         | SALES      |           |         6
+         |            | ANALYST   |         3
+         |            | CLERK     |         5
+         |            | MANAGER   |         4
+         |            | PRESIDENT |         1
+         |            | SALESMAN  |         4
+         |            |           |        17
+         |            |           |        17
+(38 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/04_grouping_function.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/04_grouping_function.mdx
new file mode 100644
index 00000000000..536d1248fba
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/04_grouping_function.mdx
@@ -0,0 +1,152 @@
+---
+title: "GROUPING function"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.027.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.027.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/04_grouping_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="grouping_function" class="registered_link"></div>
+
+When using the `ROLLUP`, `CUBE`, or `GROUPING SETS` extensions to the `GROUP BY` clause, it can sometimes be difficult to differentiate between the various levels of subtotals generated by the extensions as well as the base aggregate rows in the result set. The `GROUPING` function provides a means of making this distinction.
+
+## Syntax 
+
+The general syntax for use of the `GROUPING` function is:
+
+```sql
+SELECT [ <expr> ...,] GROUPING( <col_expr> ) [, <expr> ] ...
+FROM ...
+GROUP BY [...,]
+  { ROLLUP | CUBE | GROUPING SETS }( [...,] <col_expr>
+  [, ...] ) [, ...]
+```
+
+The `GROUPING` function takes a single parameter that must be an expression of a dimension column specified in the expression list of a `ROLLUP`, `CUBE`, or `GROUPING SETS` extension of the `GROUP BY` clause.
+
+The return value of the `GROUPING` function is either a 0 or 1. In the result set of a query:  
+
+- If the column expression specified in the `GROUPING` function is null because the row represents a subtotal over multiple values of that column, then the `GROUPING` function returns a value of 1. 
+- If the row returns results based on a particular value of the column specified in the `GROUPING` function, then the `GROUPING` function returns a value of 0. 
+
+In the latter case, the column can be null as well as non-null. In any case, it's for a particular value of that column, not a subtotal across multiple values.
+
+## Examples 
+
+The following query shows how the return values of the `GROUPING` function correspond to the subtotal lines:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees",
+  GROUPING(loc) AS "gf_loc",
+  GROUPING(dname) AS "gf_dname",
+  GROUPING(job) AS "gf_job"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (loc, dname, job)
+ORDER BY 1, 2, 3;
+```
+
+In the three right-most columns displaying the output of the `GROUPING` functions, a value of 1 appears on a subtotal line wherever a subtotal is taken across values of the corresponding columns:
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees | gf_loc | gf_dname | gf_job
+---------+------------+-----------+-----------+--------+----------+--------
+BOSTON   | OPERATIONS | ANALYST   |         1 |      0 |        0 |      0
+BOSTON   | OPERATIONS | CLERK     |         1 |      0 |        0 |      0
+BOSTON   | OPERATIONS | MANAGER   |         1 |      0 |        0 |      0
+BOSTON   | OPERATIONS |           |         3 |      0 |        0 |      1
+BOSTON   | RESEARCH   | ANALYST   |         2 |      0 |        0 |      0
+BOSTON   | RESEARCH   | CLERK     |         2 |      0 |        0 |      0
+BOSTON   | RESEARCH   | MANAGER   |         1 |      0 |        0 |      0
+BOSTON   | RESEARCH   |           |         5 |      0 |        0 |      1
+BOSTON   |            |           |         8 |      0 |        1 |      1
+CHICAGO  | SALES      | CLERK     |         1 |      0 |        0 |      0
+CHICAGO  | SALES      | MANAGER   |         1 |      0 |        0 |      0
+CHICAGO  | SALES      | SALESMAN  |         4 |      0 |        0 |      0
+CHICAGO  | SALES      |           |         6 |      0 |        0 |      1
+CHICAGO  |            |           |         6 |      0 |        1 |      1
+NEW YORK | ACCOUNTING | CLERK     |         1 |      0 |        0 |      0
+NEW YORK | ACCOUNTING | MANAGER   |         1 |      0 |        0 |      0
+NEW YORK | ACCOUNTING | PRESIDENT |         1 |      0 |        0 |      0
+NEW YORK | ACCOUNTING |           |         3 |      0 |        0 |      1
+NEW YORK |            |           |         3 |      0 |        1 |      1
+         |            |           |        17 |      1 |        1 |      1
+(20 rows)
+```
+
+You can use these indicators as screening criteria for particular subtotals. For example, using the previous query, you can display only those subtotals for `loc` and `dname` combinations by using the `GROUPING` function in a `HAVING` clause:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees",
+  GROUPING(loc) AS "gf_loc",
+  GROUPING(dname) AS "gf_dname",
+  GROUPING(job) AS "gf_job"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY ROLLUP (loc, dname, job)
+HAVING GROUPING(loc) = 0
+  AND  GROUPING(dname) = 0
+  AND  GROUPING(job) = 1
+ORDER BY 1, 2;
+```
+
+This query produces the following result:
+
+```sql
+__OUTPUT__
+loc      |   dname    | job | employees | gf_loc | gf_dname | gf_job
+---------+------------+-----+-----------+--------+----------+--------
+BOSTON   | OPERATIONS |     |         3 |      0 |        0 |      1
+BOSTON   | RESEARCH   |     |         5 |      0 |        0 |      1
+CHICAGO  | SALES      |     |         6 |      0 |        0 |      1
+NEW YORK | ACCOUNTING |     |         3 |      0 |        0 |      1
+(4 rows)
+```
+
+You can use the `GROUPING` function to distinguish a subtotal row from a base aggregate row or from certain subtotal rows. These subtotal rows have one item in the expression list that returns null as a result of the column on which the expression is based being null for one or more rows in the table. This is opposed to representing a subtotal over the column.
+
+To illustrate this point, the following row is added to the `emp` table, which provides a row with a null value for the `job` column:
+
+```sql
+INSERT INTO emp (empno,ename,deptno) VALUES (9004,'PETERS',40);
+```
+
+The following query is issued using a reduced number of rows for clarity:
+
+```sql
+SELECT loc, job, COUNT(*) AS "employees",
+  GROUPING(loc) AS "gf_loc",
+  GROUPING(job) AS "gf_job"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno AND loc = 'BOSTON'
+GROUP BY CUBE (loc, job)
+ORDER BY 1, 2;
+```
+
+The output contains two rows containing `BOSTON` in the `loc` column and spaces in the `job` column (fourth and fifth entries in the table):
+
+```sql
+__OUTPUT__
+loc    |   job   | employees | gf_loc | gf_job
+-------+---------+-----------+--------+--------
+BOSTON | ANALYST |         3 |      0 |      0
+BOSTON | CLERK   |         3 |      0 |      0
+BOSTON | MANAGER |         2 |      0 |      0
+BOSTON |         |         1 |      0 |      0
+BOSTON |         |         9 |      0 |      1
+       | ANALYST |         3 |      1 |      0
+       | CLERK   |         3 |      1 |      0
+       | MANAGER |         2 |      1 |      0
+       |         |         1 |      1 |      0
+       |         |         9 |      1 |      1
+(10 rows)
+```
+
+The fifth row, where the `GROUPING` function on the `job` column `(gf_job)` returns 1, indicates this is a subtotal over all jobs. The row contains a subtotal value of 9 in the `employees` column.
+
+In the fourth row, the `GROUPING` function on the `job` column as well as on the `loc` column returns 0. This indicates that this is a base aggregate of all rows, where `loc` is `BOSTON` and `job` is null, which is the row inserted for this example. The `employees` column contains 1, which is the count of the single such row inserted.
+
+In the ninth row (next to last) the `GROUPING` function on the `job` column returns 0, while the `GROUPING` function on the `loc` column returns 1. This indicates that this is a subtotal over all locations where the `job` column is null which, again, is a count of the single row inserted for this example.
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/05_grouping_id_function.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/05_grouping_id_function.mdx
new file mode 100644
index 00000000000..32136f1629e
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/05_grouping_id_function.mdx
@@ -0,0 +1,114 @@
+---
+title: "GROUPING_ID function"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.028.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.028.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/05_grouping_id_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="grouping_id_function" class="registered_link"></div>
+
+The `GROUPING_ID` function provides a simplification of the `GROUPING` function to determine the subtotal level of a row in the result set from a `ROLLBACK`, `CUBE`, or `GROUPING SETS` extension.
+
+The `GROUPING` function takes only one column expression and returns an indication of whether a row is a subtotal over all values of the given column. Thus, you might need multiple `GROUPING` functions to interpret the level of subtotals for queries with multiple grouping columns.
+
+The `GROUPING_ID` function accepts one or more column expressions that were used in the `ROLLBACK`, `CUBE`, or `GROUPING SETS` extensions. It returns a single integer that you can use to determine over which of these columns a subtotal was aggregated.
+
+## Syntax
+
+The general syntax for the `GROUPING_ID` function is:
+
+```sql
+SELECT [ <expr> ...,]
+  GROUPING_ID( <col_expr_1> [, <col_expr_2> ] ... )
+  [, <expr> ] ...
+FROM ...
+GROUP BY [...,]
+  { ROLLUP | CUBE | GROUPING SETS }( [...,] <col_expr_1>
+  [, <col_expr_2> ] [, ...] ) [, ...]
+```
+
+The `GROUPING_ID` function takes one or more parameters that must be expressions of dimension columns specified in the expression list of a `ROLLUP`, `CUBE`, or `GROUPING SETS` extension of the `GROUP BY` clause.
+
+The `GROUPING_ID` function returns an integer value. This value corresponds to the base-10 interpretation of a bit vector consisting of the concatenated 1s and 0s returned by a series of `GROUPING` functions specified in the same left-to-right order as the ordering of the parameters specified in the `GROUPING_ID` function.
+
+## Examples
+
+The following query shows how the returned values of the `GROUPING_ID` function represented in column `gid` correspond to the values returned by two `GROUPING` functions on columns `loc` and `dname`:
+
+```sql
+SELECT loc, dname, COUNT(*) AS "employees",
+  GROUPING(loc) AS "gf_loc", GROUPING(dname) AS "gf_dname",
+  GROUPING_ID(loc, dname) AS "gid"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (loc, dname)
+ORDER BY 6, 1, 2;
+```
+
+In the following output, note the relationship between a bit vector consisting of the `gf_loc` value and `gf_dname` value compared to the integer given in `gid`:
+
+```sql
+__OUTPUT__
+loc      |   dname    | employees | gf_loc | gf_dname | gid
+---------+------------+-----------+--------+----------+-----
+BOSTON   | OPERATIONS |         3 |      0 |        0 |   0
+BOSTON   | RESEARCH   |         5 |      0 |        0 |   0
+CHICAGO  | SALES      |         6 |      0 |        0 |   0
+NEW YORK | ACCOUNTING |         3 |      0 |        0 |   0
+BOSTON   |            |         8 |      0 |        1 |   1
+CHICAGO  |            |         6 |      0 |        1 |   1
+NEW YORK |            |         3 |      0 |        1 |   1
+         | ACCOUNTING |         3 |      1 |        0 |   2
+         | OPERATIONS |         3 |      1 |        0 |   2
+         | RESEARCH   |         5 |      1 |        0 |   2
+         | SALES      |         6 |      1 |        0 |   2
+         |            |        17 |      1 |        1 |   3
+(12 rows)
+```
+
+The following table provides specific examples of the `GROUPING_ID` function calculations based on the `GROUPING` function return values for four rows of the output.
+
+| loc      | dname        | Bit Vector<br /><br />gf_loc gf_dname | GROUPING_ID<br /><br /> gid |
+| -------- | ------------ | ------------------------------------- | --------------------------- |
+| `BOSTON` | `OPERATIONS` | 0 \* 2¹ + 0 \* 2⁰                     | `0`                         |
+| `BOSTON` | `null`       | 0 \* 2¹ + 1 \* 2⁰                     | `1`                         |
+| `null`   | `ACCOUNTING` | 1 \* 2¹ + 0 \* 2⁰                     | `2`                         |
+| `null`   | `null`       | 1 \* 2¹ + 1 \* 2⁰                     | `3`                         |
+
+The following table summarizes how the `GROUPING_ID` function return values correspond to the grouping columns over which aggregation occurs.
+
+| Aggregation by Column | Bit Vector<br /><br />gf_loc gf_dname | GROUPING_ID<br /><br /> gid |
+| --------------------- | ------------------------------------- | --------------------------- |
+| `loc, dname`          | `0`   `0`                             | `0`                         |
+| `loc`                 | `0`   `1`                             | `1`                         |
+| `dname`               | `1`   `0`                             | `2`                         |
+| `Grand Total`         | `1`   `1`                             | `3`                         |
+
+To display only those subtotals by `dname`, use the following simplified query with a `HAVING` clause based on the `GROUPING_ID` function:
+
+```sql
+SELECT loc, dname, COUNT(*) AS "employees",
+  GROUPING(loc) AS "gf_loc", GROUPING(dname) AS "gf_dname",
+  GROUPING_ID(loc, dname) AS "gid"
+FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY CUBE (loc, dname)
+HAVING GROUPING_ID(loc, dname) = 2
+ORDER BY 6, 1, 2;
+```
+
+The result of the query is:
+
+```sql
+__OUTPUT__
+loc |   dname    | employees | gf_loc | gf_dname | gid
+----+------------+-----------+--------+----------+-----
+    | ACCOUNTING |         3 |      1 |        0 |   2
+    | OPERATIONS |         3 |      1 |        0 |   2
+    | RESEARCH   |         5 |      1 |        0 |   2
+    | SALES      |         6 |      1 |        0 |   2
+(4 rows)
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/index.mdx
new file mode 100644
index 00000000000..2e5afe2209b
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/06_multidimensional_analysis/index.mdx
@@ -0,0 +1,111 @@
+---
+title: "Multidimensional analysis"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.023.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.023.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/06_multidimensional_analysis/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="multidimensional_analysis" class="registered_link"></div>
+
+*Multidimensional analysis* refers to the process of examining data using various combinations of dimensions. *Dimensions* are categories used to classify data such as time, geography, a company’s departments, product lines, and so forth. This process is commonly used in data warehousing applications. The results associated with a particular set of dimensions are called *facts*. Facts are typically figures associated with product sales, profits, volumes, counts, and so on.
+
+To obtain these facts according to a set of dimensions in a relational database system, you typically use *SQL aggregation*. SQL aggregation basically means data is grouped according to certain criteria (dimensions), and the result set consists of aggregates of facts, such as counts, sums, and averages of the data in each group.
+
+## Aggregating results
+
+The `GROUP BY` clause of the SQL `SELECT` command supports the following extensions that simplify the process of producing aggregate results:
+
+-   `ROLLUP` extension
+-   `CUBE` extension
+-   `GROUPING SETS` extension
+
+In addition, you can use the `GROUPING` function and the `GROUPING_ID` function in the `SELECT` list or the `HAVING` clause to aid with the interpretation of the results when you use these extensions.
+
+!!! Note
+    The sample `dept` and `emp` tables are used extensively in this discussion to provide usage examples. The following changes were applied to these tables to provide more informative results:
+
+```sql
+UPDATE dept SET loc = 'BOSTON' WHERE deptno = 20;
+INSERT INTO emp (empno,ename,job,deptno) VALUES (9001,'SMITH','CLERK',40);
+INSERT INTO emp (empno,ename,job,deptno) VALUES (9002,'JONES','ANALYST',40);
+INSERT INTO emp (empno,ename,job,deptno) VALUES (9003,'ROGERS','MANAGER',40);
+```
+
+The following rows from a join of the `emp` and `dept` tables are used:
+
+```sql
+SELECT loc, dname, job, empno FROM emp e, dept d
+WHERE e.deptno = d.deptno
+ORDER BY 1, 2, 3, 4;
+__OUTPUT__
+   loc    |   dname    |    job    | empno
+----------+------------+-----------+-------
+ BOSTON   | OPERATIONS | ANALYST   |  9002
+ BOSTON   | OPERATIONS | CLERK     |  9001
+ BOSTON   | OPERATIONS | MANAGER   |  9003
+ BOSTON   | RESEARCH   | ANALYST   |  7788
+ BOSTON   | RESEARCH   | ANALYST   |  7902
+ BOSTON   | RESEARCH   | CLERK     |  7369
+ BOSTON   | RESEARCH   | CLERK     |  7876
+ BOSTON   | RESEARCH   | MANAGER   |  7566
+ CHICAGO  | SALES      | CLERK     |  7900
+ CHICAGO  | SALES      | MANAGER   |  7698
+ CHICAGO  | SALES      | SALESMAN  |  7499
+ CHICAGO  | SALES      | SALESMAN  |  7521
+ CHICAGO  | SALES      | SALESMAN  |  7654
+ CHICAGO  | SALES      | SALESMAN  |  7844
+ NEW YORK | ACCOUNTING | CLERK     |  7934
+ NEW YORK | ACCOUNTING | MANAGER   |  7782
+ NEW YORK | ACCOUNTING | PRESIDENT |  7839
+(17 rows)
+```
+
+The `loc`, `dname`, and `job` columns are used for the dimensions of the SQL aggregations used in the examples. The resulting facts of the aggregations are the number of employees obtained by using the `COUNT(*)` function.
+
+## Aggregation example
+
+A basic query grouping the `loc`, `dname`, and `job` columns is given by the following:
+
+```sql
+SELECT loc, dname, job, COUNT(*) AS "employees" FROM emp e, dept d
+WHERE e.deptno = d.deptno
+GROUP BY loc, dname, job
+ORDER BY 1, 2, 3;
+```
+
+The rows of this result set using the basic `GROUP BY` clause without extensions are referred to as the *base aggregate* rows.
+
+```sql
+__OUTPUT__
+loc      |   dname    |    job    | employees
+---------+------------+-----------+-----------
+BOSTON   | OPERATIONS | ANALYST   |         1
+BOSTON   | OPERATIONS | CLERK     |         1
+BOSTON   | OPERATIONS | MANAGER   |         1
+BOSTON   | RESEARCH   | ANALYST   |         2
+BOSTON   | RESEARCH   | CLERK     |         2
+BOSTON   | RESEARCH   | MANAGER   |         1
+CHICAGO  | SALES      | CLERK     |         1
+CHICAGO  | SALES      | MANAGER   |         1
+CHICAGO  | SALES      | SALESMAN  |         4
+NEW YORK | ACCOUNTING | CLERK     |         1
+NEW YORK | ACCOUNTING | MANAGER   |         1
+NEW YORK | ACCOUNTING | PRESIDENT |         1
+(12 rows)
+```
+## Useful extensions
+
+The `ROLLUP` and `CUBE` extensions add to the base aggregate rows by providing additional levels of subtotals to the result set.
+
+The `GROUPING SETS` extension lets you combine different types of groupings into a single result set.
+
+The `GROUPING` and `GROUPING_ID` functions help you to interpret the result set.
+
+<div class="toctree" maxdepth="3">
+
+rollup_extension cube_extension grouping_sets_extension grouping_function grouping_id_function
+
+</div>
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/index.mdx
new file mode 100644
index 00000000000..680ead0e172
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_advanced_concepts/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Advanced concepts"
+indexCards: simple
+description: "Introduces the SQL concepts applied in the tutorial"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.018.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.018.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/03_advanced_concepts/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="advanced_concepts" class="registered_link"></div>
+
+Advanced SQL features can simplify management and prevent loss or corruption of your data. 
+
+<div class="toctree" maxdepth="3">
+
+views foreign_keys the_rownum_pseudo_column synonyms hierarchical_queries multidimensional_analysis
+
+</div>
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_examples_used.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_examples_used.mdx
new file mode 100644
index 00000000000..46b8ef794fc
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/03_examples_used.mdx
@@ -0,0 +1,503 @@
+---
+title: "Sample database description"
+description: "Provides background information about the sample database examples"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.06.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.006.html"
+redirects:
+  - /epas/latest/epas_guide/01_introduction/03_examples_used/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="examples_used" class="registered_link"></div>
+
+The examples in the documentation use the sample tables `dept`, `emp`, and `jobhist`, which are created and loaded when EDB Postgres Advanced Server is installed.
+
+## Available scripts
+
+You can re-create the tables and programs in the sample database at any time by executing the following script:
+
+```sql
+/usr/edb/as<xx>/share/pg-sample.sql
+```
+
+Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+In addition, a script in the same directory contains the database objects created using syntax compatible with Oracle databases. This script file is `edb-sample.sql`. The script:
+
+-   Creates the sample tables and programs in the currently connected database.
+-   Grants all permissions on the tables to the `PUBLIC` group.
+
+The tables and programs are created in the first schema of the search path in which the current user has permission to create tables and procedures. You can display the search path using the command:
+
+```sql
+SHOW SEARCH_PATH;
+```
+
+You can use PSQL (a terminal-based interface for PostgreSQL) commands to modify the search path.
+
+## About the sample database
+
+The sample database represents employees in an organization. It contains three types of records: employees, departments, and historical records of employees.
+
+Each employee has an identification number, name, hire date, salary, and manager. Some employees earn a commission in addition to their salary. All employee-related information is stored in the `emp` table.
+
+The sample company is regionally diverse, so it tracks the locations of its departments. Each company employee is assigned to a department. Each department is identified by a unique department number and a short name. Each department is associated with one location. All department-related information is stored in the `dept` table.
+
+The company also tracks information about jobs held by the employees. Some employees have been with the company for a long time and have held different positions, received raises, switched departments, and so on. When a change in employee status occurs, the company records the end date of the former position. A new job record is added with the start date and the new job title, department, salary, and the reason for the status change. All employee history is maintained in the `jobhist` table.
+
+The following is the `pg-sample.sql` script:
+
+```sql
+SET datestyle TO 'iso, dmy';
+
+--
+--  Script that creates the 'sample' tables, views
+--  functions, triggers, etc.
+--
+--  Start new transaction - commit all or nothing
+--
+BEGIN;
+--
+--  Create and load tables used in the documentation examples.
+--
+--  Create the 'dept' table
+--
+CREATE TABLE dept (
+    deptno           NUMERIC(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+    dname            VARCHAR(14) CONSTRAINT dept_dname_uq UNIQUE,
+    loc              VARCHAR(13)
+);
+--
+--  Create the 'emp' table
+--
+CREATE TABLE emp (
+    empno            NUMERIC(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename            VARCHAR(10),
+    job              VARCHAR(9),
+    mgr              NUMERIC(4),
+    hiredate         DATE,
+    sal              NUMERIC(7,2) CONSTRAINT emp_sal_ck CHECK (sal > 0),
+    comm             NUMERIC(7,2),
+    deptno           NUMERIC(2) CONSTRAINT emp_ref_dept_fk
+                         REFERENCES dept(deptno)
+);
+--
+--  Create the 'jobhist' table
+--
+CREATE TABLE jobhist (
+    empno            NUMERIC(4) NOT NULL,
+    startdate        TIMESTAMP(0) NOT NULL,
+    enddate          TIMESTAMP(0),
+    job              VARCHAR(9),
+    sal              NUMERIC(7,2),
+    comm             NUMERIC(7,2),
+    deptno           NUMERIC(2),
+    chgdesc          VARCHAR(80),
+    CONSTRAINT jobhist_pk PRIMARY KEY (empno, startdate),
+    CONSTRAINT jobhist_ref_emp_fk FOREIGN KEY (empno)
+        REFERENCES emp(empno) ON DELETE CASCADE,
+    CONSTRAINT jobhist_ref_dept_fk FOREIGN KEY (deptno)
+        REFERENCES dept (deptno) ON DELETE SET NULL,
+    CONSTRAINT jobhist_date_chk CHECK (startdate <= enddate)
+);
+--
+--  Create the 'salesemp' view
+--
+CREATE OR REPLACE VIEW salesemp AS
+    SELECT empno, ename, hiredate, sal, comm FROM emp WHERE job = 'SALESMAN';
+--
+--  Sequence to generate values for function 'new_empno'.
+--
+CREATE SEQUENCE next_empno START WITH 8000 INCREMENT BY 1;
+--
+--  Issue PUBLIC grants
+--
+--GRANT ALL ON emp TO PUBLIC;
+--GRANT ALL ON dept TO PUBLIC;
+--GRANT ALL ON jobhist TO PUBLIC;
+--GRANT ALL ON salesemp TO PUBLIC;
+--GRANT ALL ON next_empno TO PUBLIC;
+--
+--  Load the 'dept' table
+--
+INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+INSERT INTO dept VALUES (20,'RESEARCH','DALLAS');
+INSERT INTO dept VALUES (30,'SALES','CHICAGO');
+INSERT INTO dept VALUES (40,'OPERATIONS','BOSTON');
+--
+--  Load the 'emp' table
+--
+INSERT INTO emp VALUES (7369,'SMITH','CLERK',7902,'17-DEC-80',800,NULL,20);
+INSERT INTO emp VALUES (7499,'ALLEN','SALESMAN',7698,'20-FEB-81',1600,300,30);
+INSERT INTO emp VALUES (7521,'WARD','SALESMAN',7698,'22-FEB-81',1250,500,30);
+INSERT INTO emp VALUES (7566,'JONES','MANAGER',7839,'02-APR-81',2975,NULL,20);
+INSERT INTO emp VALUES (7654,'MARTIN','SALESMAN',7698,'28-SEP-81',1250,1400,30);
+INSERT INTO emp VALUES (7698,'BLAKE','MANAGER',7839,'01-MAY-81',2850,NULL,30);
+INSERT INTO emp VALUES (7782,'CLARK','MANAGER',7839,'09-JUN-81',2450,NULL,10);
+INSERT INTO emp VALUES (7788,'SCOTT','ANALYST',7566,'19-APR-87',3000,NULL,20);
+INSERT INTO emp VALUES (7839,'KING','PRESIDENT',NULL,'17-NOV-81',5000,NULL,10);
+INSERT INTO emp VALUES (7844,'TURNER','SALESMAN',7698,'08-SEP-81',1500,0,30);
+INSERT INTO emp VALUES (7876,'ADAMS','CLERK',7788,'23-MAY-87',1100,NULL,20);
+INSERT INTO emp VALUES (7900,'JAMES','CLERK',7698,'03-DEC-81',950,NULL,30);
+INSERT INTO emp VALUES (7902,'FORD','ANALYST',7566,'03-DEC-81',3000,NULL,20);
+INSERT INTO emp VALUES (7934,'MILLER','CLERK',7782,'23-JAN-82',1300,NULL,10);
+--
+--  Load the 'jobhist' table
+--
+INSERT INTO jobhist VALUES (7369,'17-DEC-80',NULL,'CLERK',800,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7499,'20-FEB-81',NULL,'SALESMAN',1600,300,30,'New Hire');
+INSERT INTO jobhist VALUES (7521,'22-FEB-81',NULL,'SALESMAN',1250,500,30,'New Hire');
+INSERT INTO jobhist VALUES (7566,'02-APR-81',NULL,'MANAGER',2975,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7654,'28-SEP-81',NULL,'SALESMAN',1250,1400,30,'New Hire');
+INSERT INTO jobhist VALUES (7698,'01-MAY-81',NULL,'MANAGER',2850,NULL,30,'New Hire');
+INSERT INTO jobhist VALUES (7782,'09-JUN-81',NULL,'MANAGER',2450,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7788,'19-APR-87','12-APR-88','CLERK',1000,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7788,'13-APR-88','04-MAY-89','CLERK',1040,NULL,20,'Raise');
+INSERT INTO jobhist VALUES (7788,'05-MAY-90',NULL,'ANALYST',3000,NULL,20,'Promoted to Analyst');
+INSERT INTO jobhist VALUES (7839,'17-NOV-81',NULL,'PRESIDENT',5000,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7844,'08-SEP-81',NULL,'SALESMAN',1500,0,30,'New Hire');
+INSERT INTO jobhist VALUES (7876,'23-MAY-87',NULL,'CLERK',1100,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7900,'03-DEC-81','14-JAN-83','CLERK',950,NULL,10,'New Hire');
+INSERT INTO jobhist VALUES (7900,'15-JAN-83',NULL,'CLERK',950,NULL,30,'Changed to Dept 30');
+INSERT INTO jobhist VALUES (7902,'03-DEC-81',NULL,'ANALYST',3000,NULL,20,'New Hire');
+INSERT INTO jobhist VALUES (7934,'23-JAN-82',NULL,'CLERK',1300,NULL,10,'New Hire');
+--
+--  Populate statistics table and view (pg_statistic/pg_stats)
+--
+ANALYZE dept;
+ANALYZE emp;
+ANALYZE jobhist;
+--
+--  Function that lists all employees' numbers and names
+--  from the 'emp' table using a cursor.
+--
+CREATE OR REPLACE FUNCTION list_emp() RETURNS VOID
+AS $$
+DECLARE
+    v_empno        NUMERIC(4);
+    v_ename        VARCHAR(10);
+    emp_cur CURSOR FOR
+        SELECT empno, ename FROM emp ORDER BY empno;
+BEGIN
+    OPEN emp_cur;
+    RAISE INFO 'EMPNO ENAME';
+    RAISE INFO '----- -------';
+    LOOP
+        FETCH emp_cur INTO v_empno, v_ename;
+        EXIT WHEN NOT FOUND;
+        RAISE INFO '% %', v_empno, v_ename;
+    END LOOP;
+    CLOSE emp_cur;
+    RETURN;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function that selects an employee row given the employee
+--  number and displays certain columns.
+--
+CREATE OR REPLACE FUNCTION select_emp (
+    p_empno         NUMERIC
+) RETURNS VOID
+AS $$
+DECLARE
+    v_ename         emp.ename%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_comm          emp.comm%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_disp_date     VARCHAR(10);
+BEGIN
+    SELECT INTO
+        v_ename, v_hiredate, v_sal, v_comm, v_dname
+        ename, hiredate, sal, COALESCE(comm, 0), dname
+        FROM emp e, dept d
+        WHERE empno = p_empno
+          AND e.deptno = d.deptno;
+    IF NOT FOUND THEN
+        RAISE INFO 'Employee % not found', p_empno;
+        RETURN;
+    END IF;
+    v_disp_date := TO_CHAR(v_hiredate, 'MM/DD/YYYY');
+    RAISE INFO 'Number    : %', p_empno;
+    RAISE INFO 'Name      : %', v_ename;
+    RAISE INFO 'Hire Date : %', v_disp_date;
+    RAISE INFO 'Salary    : %', v_sal;
+    RAISE INFO 'Commission: %', v_comm;
+    RAISE INFO 'Department: %', v_dname;
+    RETURN;
+EXCEPTION
+    WHEN OTHERS THEN
+        RAISE INFO 'The following is SQLERRM : %', SQLERRM;
+        RAISE INFO 'The following is SQLSTATE: %', SQLSTATE;
+        RETURN;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  A RECORD type used to format the return value of
+--  function, 'emp_query'.
+--
+CREATE TYPE emp_query_type AS (
+    empno        NUMERIC,
+    ename        VARCHAR(10),
+    job          VARCHAR(9),
+    hiredate     DATE,
+    sal          NUMERIC
+);
+--
+--  Function that queries the 'emp' table based on
+--  department number and employee number or name. Returns
+--  employee number and name as INOUT parameters and job,
+--  hire date, and salary as OUT parameters. These are
+--  returned in the form of a record defined by
+--  RECORD type, 'emp_query_type'.
+--
+CREATE OR REPLACE FUNCTION emp_query (
+    IN p_deptno           NUMERIC,
+    INOUT p_empno         NUMERIC,
+    INOUT p_ename         VARCHAR,
+    OUT p_job             VARCHAR,
+    OUT p_hiredate        DATE,
+    OUT p_sal             NUMERIC
+)
+AS $$
+BEGIN
+    SELECT INTO
+        p_empno, p_ename, p_job, p_hiredate, p_sal
+        empno, ename, job, hiredate, sal
+        FROM emp
+        WHERE deptno = p_deptno
+          AND (empno = p_empno
+           OR ename = UPPER(p_ename));
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function to call 'emp_query_caller' with IN and INOUT
+--  parameters. Displays the results received from INOUT and
+--  OUT parameters.
+--
+CREATE OR REPLACE FUNCTION emp_query_caller() RETURNS VOID
+AS $$
+DECLARE
+    v_deptno          NUMERIC;
+    v_empno           NUMERIC;
+    v_ename           VARCHAR;
+    v_rows            INTEGER;
+    r_emp_query       EMP_QUERY_TYPE;
+BEGIN
+    v_deptno := 30;
+    v_empno := 0;
+    v_ename := 'Martin';
+    r_emp_query := emp_query(v_deptno, v_empno, v_ename);
+    RAISE INFO 'Department : %', v_deptno;
+    RAISE INFO 'Employee No: %', (r_emp_query).empno;
+    RAISE INFO 'Name       : %', (r_emp_query).ename;
+    RAISE INFO 'Job        : %', (r_emp_query).job;
+    RAISE INFO 'Hire Date  : %', (r_emp_query).hiredate;
+    RAISE INFO 'Salary     : %', (r_emp_query).sal;
+    RETURN;
+EXCEPTION
+    WHEN OTHERS THEN
+        RAISE INFO 'The following is SQLERRM : %', SQLERRM;
+        RAISE INFO 'The following is SQLSTATE: %', SQLSTATE;
+        RETURN;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function to compute yearly compensation based on semimonthly
+--  salary.
+--
+CREATE OR REPLACE FUNCTION emp_comp (
+    p_sal          NUMERIC,
+    p_comm         NUMERIC
+) RETURNS NUMERIC
+AS $$
+BEGIN
+    RETURN (p_sal + COALESCE(p_comm, 0)) * 24;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function that gets the next number from sequence, 'next_empno',
+--  and ensures it is not already in use as an employee number.
+--
+CREATE OR REPLACE FUNCTION new_empno() RETURNS INTEGER
+AS $$
+DECLARE
+    v_cnt            INTEGER := 1;
+    v_new_empno      INTEGER;
+BEGIN
+    WHILE v_cnt > 0 LOOP
+        SELECT INTO v_new_empno nextval('next_empno');
+        SELECT INTO v_cnt COUNT(*) FROM emp WHERE empno = v_new_empno;
+    END LOOP;
+    RETURN v_new_empno;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function that adds a new clerk to table 'emp'.
+--
+CREATE OR REPLACE FUNCTION hire_clerk (
+    p_ename         VARCHAR,
+    p_deptno        NUMERIC
+) RETURNS NUMERIC
+AS $$
+DECLARE
+    v_empno         NUMERIC(4);
+    v_ename         VARCHAR(10);
+    v_job           VARCHAR(9);
+    v_mgr           NUMERIC(4);
+    v_hiredate      DATE;
+    v_sal           NUMERIC(7,2);
+    v_comm          NUMERIC(7,2);
+    v_deptno        NUMERIC(2);
+BEGIN
+    v_empno := new_empno();
+    INSERT INTO emp VALUES (v_empno, p_ename, 'CLERK', 7782,
+        CURRENT_DATE, 950.00, NULL, p_deptno);
+    SELECT INTO
+        v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
+        empno, ename, job, mgr, hiredate, sal, comm, deptno
+        FROM emp WHERE empno = v_empno;
+    RAISE INFO 'Department : %', v_deptno;
+    RAISE INFO 'Employee No: %', v_empno;
+    RAISE INFO 'Name       : %', v_ename;
+    RAISE INFO 'Job        : %', v_job;
+    RAISE INFO 'Manager    : %', v_mgr;
+    RAISE INFO 'Hire Date  : %', v_hiredate;
+    RAISE INFO 'Salary     : %', v_sal;
+    RAISE INFO 'Commission : %', v_comm;
+    RETURN v_empno;
+EXCEPTION
+    WHEN OTHERS THEN
+        RAISE INFO 'The following is SQLERRM : %', SQLERRM;
+        RAISE INFO 'The following is SQLSTATE: %', SQLSTATE;
+        RETURN -1;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Function that adds a new salesman to table 'emp'.
+--
+CREATE OR REPLACE FUNCTION hire_salesman (
+    p_ename           VARCHAR,
+    p_sal             NUMERIC,
+    p_comm            NUMERIC
+) RETURNS NUMERIC
+AS $$
+DECLARE
+    v_empno           NUMERIC(4);
+    v_ename           VARCHAR(10);
+    v_job             VARCHAR(9);
+    v_mgr             NUMERIC(4);
+    v_hiredate        DATE;
+    v_sal             NUMERIC(7,2);
+    v_comm            NUMERIC(7,2);
+    v_deptno          NUMERIC(2);
+BEGIN
+    v_empno := new_empno();
+    INSERT INTO emp VALUES (v_empno, p_ename, 'SALESMAN', 7698,
+        CURRENT_DATE, p_sal, p_comm, 30);
+    SELECT INTO
+        v_empno, v_ename, v_job, v_mgr, v_hiredate, v_sal, v_comm, v_deptno
+        empno, ename, job, mgr, hiredate, sal, comm, deptno
+        FROM emp WHERE empno = v_empno;
+    RAISE INFO 'Department : %', v_deptno;
+    RAISE INFO 'Employee No: %', v_empno;
+    RAISE INFO 'Name       : %', v_ename;
+    RAISE INFO 'Job        : %', v_job;
+    RAISE INFO 'Manager    : %', v_mgr;
+    RAISE INFO 'Hire Date  : %', v_hiredate;
+    RAISE INFO 'Salary     : %', v_sal;
+    RAISE INFO 'Commission : %', v_comm;
+    RETURN v_empno;
+EXCEPTION
+    WHEN OTHERS THEN
+        RAISE INFO 'The following is SQLERRM : %', SQLERRM;
+        RAISE INFO 'The following is SQLSTATE: %', SQLSTATE;
+        RETURN -1;
+END;
+$$ LANGUAGE 'plpgsql';
+--
+--  Rule to INSERT into view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_i AS ON INSERT TO salesemp
+DO INSTEAD
+    INSERT INTO emp VALUES (NEW.empno, NEW.ename, 'SALESMAN', 7698,
+        NEW.hiredate, NEW.sal, NEW.comm, 30);
+--
+--  Rule to UPDATE view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_u AS ON UPDATE TO salesemp
+DO INSTEAD
+    UPDATE emp SET empno    = NEW.empno,
+                   ename    = NEW.ename,
+                   hiredate = NEW.hiredate,
+                   sal      = NEW.sal,
+                   comm     = NEW.comm
+        WHERE empno = OLD.empno;
+--
+--  Rule to DELETE from view 'salesemp'
+--
+CREATE OR REPLACE RULE salesemp_d AS ON DELETE TO salesemp
+DO INSTEAD
+    DELETE FROM emp WHERE empno = OLD.empno;
+--
+--  After statement-level trigger that displays a message after
+--  an insert, update, or deletion to the 'emp' table. One message
+--  per SQL command is displayed.
+--
+CREATE OR REPLACE FUNCTION user_audit_trig() RETURNS TRIGGER
+AS $$
+DECLARE
+    v_action          VARCHAR(24);
+    v_text            TEXT;
+BEGIN
+    IF TG_OP = 'INSERT' THEN
+        v_action := ' added employee(s) on ';
+    ELSIF TG_OP = 'UPDATE' THEN
+        v_action := ' updated employee(s) on ';
+    ELSIF TG_OP = 'DELETE' THEN
+        v_action := ' deleted employee(s) on ';
+    END IF;
+    v_text := 'User ' || USER || v_action || CURRENT_DATE;
+    RAISE INFO ' %', v_text;
+    RETURN NULL;
+END;
+$$ LANGUAGE 'plpgsql';
+CREATE TRIGGER user_audit_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+    FOR EACH STATEMENT EXECUTE PROCEDURE user_audit_trig();
+--
+--  Before row-level trigger that displays employee number and
+--  salary of an employee that is about to be added, updated,
+--  or deleted in the 'emp' table.
+--
+CREATE OR REPLACE FUNCTION emp_sal_trig() RETURNS TRIGGER
+AS $$
+DECLARE
+    sal_diff        NUMERIC(7,2);
+BEGIN
+    IF TG_OP = 'INSERT' THEN
+        RAISE INFO 'Inserting employee %', NEW.empno;
+        RAISE INFO '..New salary: %', NEW.sal;
+        RETURN NEW;
+    END IF;
+    IF TG_OP = 'UPDATE' THEN
+        sal_diff := NEW.sal - OLD.sal;
+        RAISE INFO 'Updating employee %', OLD.empno;
+        RAISE INFO '..Old salary: %', OLD.sal;
+        RAISE INFO '..New salary: %', NEW.sal;
+        RAISE INFO '..Raise : %', sal_diff;
+        RETURN NEW;
+    END IF;
+    IF TG_OP = 'DELETE' THEN
+        RAISE INFO 'Deleting employee %', OLD.empno;
+        RAISE INFO '..Old salary: %', OLD.sal;
+        RETURN OLD;
+    END IF;
+END;
+$$ LANGUAGE 'plpgsql';
+CREATE TRIGGER emp_sal_trig
+    BEFORE DELETE OR INSERT OR UPDATE ON emp
+    FOR EACH ROW EXECUTE PROCEDURE emp_sal_trig();
+COMMIT;
+```
diff --git a/product_docs/docs/epas/16/fundamentals/sql_fundamentals/index.mdx b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/index.mdx
new file mode 100644
index 00000000000..2bb453f95a5
--- /dev/null
+++ b/product_docs/docs/epas/16/fundamentals/sql_fundamentals/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "SQL fundamentals"
+description: "Walks you through a tutorial using a sample database to help explain database concepts"
+indexCards: simple
+---
+
+Structured Query Language (SQL) is a standard language for accessing and manipulating databases. These fundamentals provide a starting point for the most common actions for working with SQL, with pointers to more in-depth documentation. The tutorial uses a sample database and explains key concepts.
diff --git a/product_docs/docs/epas/16/images/accessing_configuration_files.png b/product_docs/docs/epas/16/images/accessing_configuration_files.png
new file mode 100644
index 00000000000..132e7c299b9
--- /dev/null
+++ b/product_docs/docs/epas/16/images/accessing_configuration_files.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e71983a1e03a73deb5a9a2c625a5344edf318ea69ac7bddd9454808209e84085
+size 24163
diff --git a/product_docs/docs/epas/16/images/acknowledging_components_removed.png b/product_docs/docs/epas/16/images/acknowledging_components_removed.png
new file mode 100755
index 00000000000..53d72cb197c
--- /dev/null
+++ b/product_docs/docs/epas/16/images/acknowledging_components_removed.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:09a4b2b819eb880df79be65701ebfa794ef80296649ff02acf1abd24569c99fb
+size 8523
diff --git a/product_docs/docs/epas/16/images/additional_configuration.png b/product_docs/docs/epas/16/images/additional_configuration.png
new file mode 100644
index 00000000000..880838207b2
--- /dev/null
+++ b/product_docs/docs/epas/16/images/additional_configuration.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0054129de0ab95c26f935a87f2b7613b54aee81f9cd60a51bf54af3a5a837afa
+size 87925
diff --git a/product_docs/docs/epas/16/images/additional_directories.png b/product_docs/docs/epas/16/images/additional_directories.png
new file mode 100644
index 00000000000..102702804ab
--- /dev/null
+++ b/product_docs/docs/epas/16/images/additional_directories.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cf2b62f0b7a0867c228d36456ddf26a67144a5783e0ecfe295cde21d5a635df3
+size 47831
diff --git a/product_docs/docs/epas/16/images/advanced_server_dialect.png b/product_docs/docs/epas/16/images/advanced_server_dialect.png
new file mode 100644
index 00000000000..f851d74c513
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_dialect.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:27ce9560cb3fb34cc2ec8e824b93cdb6fbc86fb19a234b17442f7078f030a06c
+size 151461
diff --git a/product_docs/docs/epas/16/images/advanced_server_installation_completion.png b/product_docs/docs/epas/16/images/advanced_server_installation_completion.png
new file mode 100755
index 00000000000..ab3793d5ff0
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_installation_completion.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c24de01669db8c9d49ea0d9df2212ab8e968764c0413b1ab9a2b11cb0962d676
+size 57855
diff --git a/product_docs/docs/epas/16/images/advanced_server_installer_welcome.png b/product_docs/docs/epas/16/images/advanced_server_installer_welcome.png
new file mode 100644
index 00000000000..8f8759b1906
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_installer_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:42fc7096b4809c470412a52bdd2aa227d52366c84a15e0a0b8b9dd26cae3943a
+size 84422
diff --git a/product_docs/docs/epas/16/images/advanced_server_services.png b/product_docs/docs/epas/16/images/advanced_server_services.png
new file mode 100644
index 00000000000..604ee29ea7e
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_services.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e30d058bdbccd2ac467ab7d16cf2e95c0cf4eeb8ec7342e839fbc12b3c8ea7dd
+size 167234
diff --git a/product_docs/docs/epas/16/images/advanced_server_startup.png b/product_docs/docs/epas/16/images/advanced_server_startup.png
new file mode 100644
index 00000000000..12aec23eec7
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_startup.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41330b9c8db6e9670075d727aea1216d5ac42e7153ca00519c13c7061a6cdc63
+size 49419
diff --git a/product_docs/docs/epas/16/images/advanced_server_uninstaller.png b/product_docs/docs/epas/16/images/advanced_server_uninstaller.png
new file mode 100755
index 00000000000..c6c0d5aede4
--- /dev/null
+++ b/product_docs/docs/epas/16/images/advanced_server_uninstaller.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8309d613b6b64bd06ac7323cdeffcb5fc31cfa60a62e7a080ceee87ccaee7e92
+size 16974
diff --git a/product_docs/docs/epas/16/images/configuring_advanced_server_to_use_trust_authentication.png b/product_docs/docs/epas/16/images/configuring_advanced_server_to_use_trust_authentication.png
new file mode 100644
index 00000000000..c48ff9dfab6
--- /dev/null
+++ b/product_docs/docs/epas/16/images/configuring_advanced_server_to_use_trust_authentication.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:492f7c3e097a3bed25609ba56f33f431f9d4106633bb82ed094553877763f54e
+size 34425
diff --git a/product_docs/docs/epas/16/images/connecting_server.png b/product_docs/docs/epas/16/images/connecting_server.png
new file mode 100644
index 00000000000..baef85e1ec6
--- /dev/null
+++ b/product_docs/docs/epas/16/images/connecting_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:38d2963521056f3860d400661f534a7e646afca9e265f02c0f0f24857f908e92
+size 26611
diff --git a/product_docs/docs/epas/16/images/connecting_to_advanced_server_database.png b/product_docs/docs/epas/16/images/connecting_to_advanced_server_database.png
new file mode 100644
index 00000000000..29cce16192d
--- /dev/null
+++ b/product_docs/docs/epas/16/images/connecting_to_advanced_server_database.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:86e690943f298532d9d53bc9f9a4bafe91f54a7cd853de0926052c30f672f86f
+size 205013
diff --git a/product_docs/docs/epas/16/images/connecting_to_server.png b/product_docs/docs/epas/16/images/connecting_to_server.png
new file mode 100644
index 00000000000..4f5de24f8c4
--- /dev/null
+++ b/product_docs/docs/epas/16/images/connecting_to_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:dc9837d27ee517004be298059e1d0bd9d241f450b445f7b2f15baacdf1d5bb80
+size 108327
diff --git a/product_docs/docs/epas/16/images/definer's_rights_package.png b/product_docs/docs/epas/16/images/definer's_rights_package.png
new file mode 100755
index 00000000000..eff47bf9058
--- /dev/null
+++ b/product_docs/docs/epas/16/images/definer's_rights_package.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:89d79f4e078a0a507127191caae821b82c85590b59f8de7dac54afc184ca0099
+size 19423
diff --git a/product_docs/docs/epas/16/images/download-complete-confirmation.png b/product_docs/docs/epas/16/images/download-complete-confirmation.png
new file mode 100644
index 00000000000..311a2f19d49
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/download_complete.png b/product_docs/docs/epas/16/images/download_complete.png
new file mode 100644
index 00000000000..8d67d478dc3
--- /dev/null
+++ b/product_docs/docs/epas/16/images/download_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9b01b8df3f6b8cf554f1497364448463b93947c41f1ba0c54c841c588cccd427
+size 107845
diff --git a/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_server_utilization.png b/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_server_utilization.png
new file mode 100644
index 00000000000..754c505bee3
--- /dev/null
+++ b/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_server_utilization.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:52e9b9a896437f2449823eb29abf3e1a01e57c97a80b1421d45631a47b3c25da
+size 92286
diff --git a/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_workload_profile.png b/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_workload_profile.png
new file mode 100644
index 00000000000..1473b53a3ee
--- /dev/null
+++ b/product_docs/docs/epas/16/images/dynatune_dynamic_tuning_workload_profile.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7db0e9d569bc038c159a62906d2635cfd0c1a43e24a6604a8217b397582ce4bd
+size 85812
diff --git a/product_docs/docs/epas/16/images/ecpg_path.png b/product_docs/docs/epas/16/images/ecpg_path.png
new file mode 100755
index 00000000000..c08335bc0f8
--- /dev/null
+++ b/product_docs/docs/epas/16/images/ecpg_path.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:848c6389145c5062fe2fac5b6235b381616c6b8a99311de5ee91e09b036ea205
+size 73046
diff --git a/product_docs/docs/epas/16/images/employee_organization_hierarchy.png b/product_docs/docs/epas/16/images/employee_organization_hierarchy.png
new file mode 100755
index 00000000000..50c9d6a31d8
--- /dev/null
+++ b/product_docs/docs/epas/16/images/employee_organization_hierarchy.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f0a57314f901e43cd2a446dd545c35c4fe13c996d2bc5d123b82333ce63ba1a9
+size 46248
diff --git a/product_docs/docs/epas/16/images/enterprisedb_license_agreement.png b/product_docs/docs/epas/16/images/enterprisedb_license_agreement.png
new file mode 100644
index 00000000000..019a07158f6
--- /dev/null
+++ b/product_docs/docs/epas/16/images/enterprisedb_license_agreement.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3cdd3111496406d324ffa4d51426b96fff25810e50d26c78fd2fff3fc66fddac
+size 223329
diff --git a/product_docs/docs/epas/16/images/epas_tools_utility_edb_wrap.png b/product_docs/docs/epas/16/images/epas_tools_utility_edb_wrap.png
new file mode 100755
index 00000000000..20e4753e58f
--- /dev/null
+++ b/product_docs/docs/epas/16/images/epas_tools_utility_edb_wrap.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4f482eeee0b168b2d2304e52f01248babae91b7ca4c23688d8b6e27d7eed6275
+size 29357
diff --git a/product_docs/docs/epas/16/images/installation_directory.png b/product_docs/docs/epas/16/images/installation_directory.png
new file mode 100644
index 00000000000..586ccc57c50
--- /dev/null
+++ b/product_docs/docs/epas/16/images/installation_directory.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:30c9729b3c9dfa1dca6243f5180aad66a0da8a0760551807c25c7d8ecfc79333
+size 36366
diff --git a/product_docs/docs/epas/16/images/installing_advanced_server.png b/product_docs/docs/epas/16/images/installing_advanced_server.png
new file mode 100644
index 00000000000..b4b58238514
--- /dev/null
+++ b/product_docs/docs/epas/16/images/installing_advanced_server.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0159528548cf725a036855319e1d64654cdcbfc03c486b7dbe85f30f0c9a8461
+size 84614
diff --git a/product_docs/docs/epas/16/images/invokers_rights_programs.png b/product_docs/docs/epas/16/images/invokers_rights_programs.png
new file mode 100755
index 00000000000..0447f5d9f7e
--- /dev/null
+++ b/product_docs/docs/epas/16/images/invokers_rights_programs.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bd88c09a0907e24e609303655d3364f4f218982a14dccf3d419a6c9cf74611fc
+size 22493
diff --git a/product_docs/docs/epas/16/images/open_client_library.png b/product_docs/docs/epas/16/images/open_client_library.png
new file mode 100755
index 00000000000..86b512073b7
--- /dev/null
+++ b/product_docs/docs/epas/16/images/open_client_library.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:929a50d978c2a657f27dcd0fd1b9464e043985a8019b5964f4a6c4ae3a7eefe2
+size 114191
diff --git a/product_docs/docs/epas/16/images/parameters_tab.png b/product_docs/docs/epas/16/images/parameters_tab.png
new file mode 100755
index 00000000000..f79c2c5945f
--- /dev/null
+++ b/product_docs/docs/epas/16/images/parameters_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:680cef1ddba3e90b8a5f30f589aae8af6138d92d80c767e19a6d3103f1b257e4
+size 271993
diff --git a/product_docs/docs/epas/16/images/password_window.png b/product_docs/docs/epas/16/images/password_window.png
new file mode 100644
index 00000000000..ba77ea26326
--- /dev/null
+++ b/product_docs/docs/epas/16/images/password_window.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34093c8a5691291ad9d6a9296d30d4e7db548fe7949d8bcaca67a74a2c2a835b
+size 58804
diff --git a/product_docs/docs/epas/16/images/pgadmin4_client_dashboard.png b/product_docs/docs/epas/16/images/pgadmin4_client_dashboard.png
new file mode 100755
index 00000000000..fc816fbf1f1
--- /dev/null
+++ b/product_docs/docs/epas/16/images/pgadmin4_client_dashboard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:663378fa1d875a1f2cb29058ca4a1dc3b955da4fb6e6bbcdfbfe1a29f156cf12
+size 75783
diff --git a/product_docs/docs/epas/16/images/pre_installation_summary.png b/product_docs/docs/epas/16/images/pre_installation_summary.png
new file mode 100644
index 00000000000..4022a35672e
--- /dev/null
+++ b/product_docs/docs/epas/16/images/pre_installation_summary.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6b371d1f158e987464dd961fc651a2c296693b7a3ae22d0ada8ee6a59f701511
+size 54310
diff --git a/product_docs/docs/epas/16/images/program_body.png b/product_docs/docs/epas/16/images/program_body.png
new file mode 100755
index 00000000000..f0383060537
--- /dev/null
+++ b/product_docs/docs/epas/16/images/program_body.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:84230643c11c49aaa90945abed66b600d063f709415277f869edc6a549870289
+size 299900
diff --git a/product_docs/docs/epas/16/images/proxy_servers.png b/product_docs/docs/epas/16/images/proxy_servers.png
new file mode 100755
index 00000000000..c5c235c7aec
--- /dev/null
+++ b/product_docs/docs/epas/16/images/proxy_servers.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1bf7b1cf6e75dad66590e07966e142fe863ccc9c1168e0cf70e27f20d5466742
+size 27052
diff --git a/product_docs/docs/epas/16/images/ready_to_install.png b/product_docs/docs/epas/16/images/ready_to_install.png
new file mode 100644
index 00000000000..d5b3fe06673
--- /dev/null
+++ b/product_docs/docs/epas/16/images/ready_to_install.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3ad3896f2beb991c7780da6f34019263f35197d0a3ada9044c0391ff0c04255f
+size 55901
diff --git a/product_docs/docs/epas/16/images/sample_database_tables.png b/product_docs/docs/epas/16/images/sample_database_tables.png
new file mode 100755
index 00000000000..89d78afb530
--- /dev/null
+++ b/product_docs/docs/epas/16/images/sample_database_tables.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6babf1dbeea767b7b9270d1b85786881ecbf242206ce91f86291316ce487f5b2
+size 9418
diff --git a/product_docs/docs/epas/16/images/select_components.png b/product_docs/docs/epas/16/images/select_components.png
new file mode 100644
index 00000000000..6e3215c7e44
--- /dev/null
+++ b/product_docs/docs/epas/16/images/select_components.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5031d2dbca7fdf66fa68818bdb8b6697c6493392fc1c3555b0d736daa8a34e7a
+size 87827
diff --git a/product_docs/docs/epas/16/images/selected-packages-summary-window.png b/product_docs/docs/epas/16/images/selected-packages-summary-window.png
new file mode 100644
index 00000000000..8325bc25697
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/setting_global_breakpoint_from_left-hand_margin.png b/product_docs/docs/epas/16/images/setting_global_breakpoint_from_left-hand_margin.png
new file mode 100755
index 00000000000..31ac340addf
--- /dev/null
+++ b/product_docs/docs/epas/16/images/setting_global_breakpoint_from_left-hand_margin.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:afc952052cf888ddb7ee6aba5f513294082128428c35e614816251407c8d0c9f
+size 344554
diff --git a/product_docs/docs/epas/16/images/setup_wizard.png b/product_docs/docs/epas/16/images/setup_wizard.png
new file mode 100644
index 00000000000..923efee7e1a
--- /dev/null
+++ b/product_docs/docs/epas/16/images/setup_wizard.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7ac01c0c80e48c7dd75997f34b66acc04ec8590f09150c30248cb5d2c338c72b
+size 160406
diff --git a/product_docs/docs/epas/16/images/stack_tab.png b/product_docs/docs/epas/16/images/stack_tab.png
new file mode 100755
index 00000000000..317aece56f1
--- /dev/null
+++ b/product_docs/docs/epas/16/images/stack_tab.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aee3fc542a22bc181d5918c5de0ad88916ce7ac23e1011827ead09da24c0f4b4
+size 270652
diff --git a/product_docs/docs/epas/16/images/stackbuilder-plus-confirms-the-completed-installation.png b/product_docs/docs/epas/16/images/stackbuilder-plus-confirms-the-completed-installation.png
new file mode 100644
index 00000000000..f7eacf0d2ef
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/stackbuilder_plus_completed_installation.png b/product_docs/docs/epas/16/images/stackbuilder_plus_completed_installation.png
new file mode 100644
index 00000000000..87450cbfa14
--- /dev/null
+++ b/product_docs/docs/epas/16/images/stackbuilder_plus_completed_installation.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9988dbfc0e39b0cdd9bf2523c41b120e676ef30c3dbc92a36739ac2dee88aa7c
+size 121533
diff --git a/product_docs/docs/epas/16/images/stackbuilder_plus_module_selection.png b/product_docs/docs/epas/16/images/stackbuilder_plus_module_selection.png
new file mode 100644
index 00000000000..358d34b3d61
--- /dev/null
+++ b/product_docs/docs/epas/16/images/stackbuilder_plus_module_selection.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1db55b623f2a9a27b40a17ac6843df32974dd222801abdaa7b9d68ecb3c15762
+size 131606
diff --git a/product_docs/docs/epas/16/images/stackbuilder_plus_welcome.png b/product_docs/docs/epas/16/images/stackbuilder_plus_welcome.png
new file mode 100644
index 00000000000..c1e77e75dae
--- /dev/null
+++ b/product_docs/docs/epas/16/images/stackbuilder_plus_welcome.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5d7ce4f0780ff2f0af65b21185a1a239969fdafde6300b23d91444e866022ab0
+size 118938
diff --git a/product_docs/docs/epas/16/images/summary-window-displaying-selected-packages.png b/product_docs/docs/epas/16/images/summary-window-displaying-selected-packages.png
new file mode 100644
index 00000000000..459bd0a99ca
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/the-proxy-servers-dialog.png b/product_docs/docs/epas/16/images/the-proxy-servers-dialog.png
new file mode 100755
index 00000000000..3b5c76bd9c9
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/the-stackbuilder-plus-module-selection-window.png b/product_docs/docs/epas/16/images/the-stackbuilder-plus-module-selection-window.png
new file mode 100644
index 00000000000..b0a60a603bc
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/the-stackbuilder-plus-welcome.png b/product_docs/docs/epas/16/images/the-stackbuilder-plus-welcome.png
new file mode 100644
index 00000000000..15ab6e100bf
--- /dev/null
+++ b/product_docs/docs/epas/16/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/16/images/uninstallation_complete.png b/product_docs/docs/epas/16/images/uninstallation_complete.png
new file mode 100755
index 00000000000..3056b512b76
--- /dev/null
+++ b/product_docs/docs/epas/16/images/uninstallation_complete.png
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfbc9145a5666c67d715d19ef90eb68dc38af58523b94860156c003678089379
+size 5627
diff --git a/product_docs/docs/epas/16/index.mdx b/product_docs/docs/epas/16/index.mdx
new file mode 100644
index 00000000000..a57540a542e
--- /dev/null
+++ b/product_docs/docs/epas/16/index.mdx
@@ -0,0 +1,44 @@
+---
+title: EDB Postgres Advanced Server (EPAS)
+directoryDefaults:
+  description: "EDB Postgres Advanced Server Version 16 documentation and release notes. Oracle database compatibility with higher security and data redaction for enterprises."
+navigation:
+  - epas_rel_notes
+  - epas_platform_support
+  - fundamentals
+  - planning
+  - installing
+  - upgrading
+  - database_administration
+  - epas_security_guide
+  - managing_performance
+  - application_programming
+  - working_with_oracle_data
+  - tools_utilities_and_components
+  - reference
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/p/edb-postgres-advanced-server/9.6"
+  - "/edb-docs/p/edb-postgres-advanced-server/9.5"
+redirects:
+  - epas_guide/
+  - epas_guide/03_database_administration/
+  - epas_guide/01_introduction/
+---
+
+EDB is the only worldwide company to deliver innovative and low-cost, open-source-derived database solutions. These solutions offer commercial quality, ease of use, compatibility, scalability, and performance for small or large-scale enterprises. EDB Postgres Advanced Server (sometimes referred to as EPAS in this documentation) adds extended functionality to open-source PostgreSQL, including:
+- [Database administration](database_administration)
+- [Enhanced SQL capabilities](application_programming/15_enhanced_sql_and_other_misc_features/)
+- [Database and application security](epas_security_guide)
+- [Performance monitoring and analysis](managing_performance)
+- [Application development utilities](application_programming)
+- [Advanced replication (version 14 and higher)](https://www.enterprisedb.com/docs/pgd/latest/). 
+
+All of these features are available in Postgres mode and [Oracle compatibility mode](working_with_oracle_data). When you launch EDB Postgres Advanced Server in Oracle compatibility mode, you get additional features that help with Oracle-to-Postgres migrations.
+- [Oracle-compatible custom data types](reference/sql_reference/02_data_types/)
+- [Oracle keywords](reference/sql_reference/01_sql_syntax/)
+- [Oracle functions](reference/sql_reference/03_functions_and_operators/)
+- [Oracle-style catalog views](reference/oracle_compatibility_reference/epas_compat_cat_views/)
+- [Additional compatibility with Oracle MERGE](reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx). 
+
+EDB also makes available a [full suite of tools and utilities](tools_utilities_and_components) that helps you monitor and manage your EDB Postgres Advanced Server deployment.
diff --git a/product_docs/docs/epas/16/installing/index.mdx b/product_docs/docs/epas/16/installing/index.mdx
new file mode 100644
index 00000000000..254c2681d1d
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/index.mdx
@@ -0,0 +1,66 @@
+---
+navTitle: Installing
+title: Installing EDB Postgres Advanced Server
+
+# 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.
+# 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/
+
+navigation:
+  - linux_x86_64
+  - linux_ppc64le
+  - linux_arm64
+  - windows
+  - linux_install_details
+  - windows_install_details
+---
+
+Select a link to access the applicable installation instructions:
+
+## Linux [x86-64 (amd64)](linux_x86_64)
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](linux_x86_64/epas_rhel_9), [RHEL 8](linux_x86_64/epas_rhel_8)
+
+- [Oracle Linux (OL) 9](linux_x86_64/epas_rhel_9), [Oracle Linux (OL) 8](linux_x86_64/epas_rhel_8)
+
+- [Rocky Linux 9](linux_x86_64/epas_other_linux_9), [Rocky Linux 8](linux_x86_64/epas_other_linux_8)
+
+- [AlmaLinux 9](linux_x86_64/epas_other_linux_9), [AlmaLinux 8](linux_x86_64/epas_other_linux_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](linux_x86_64/epas_sles_15)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](linux_x86_64/epas_ubuntu_22), [Ubuntu 20.04](linux_x86_64/epas_ubuntu_20)
+
+- [Debian 12](linux_x86_64/epas_debian_12), [Debian 11](linux_x86_64/epas_debian_11)
+
+## Linux [IBM Power (ppc64le)](linux_ppc64le)
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](linux_ppc64le/epas_rhel_9), [RHEL 8](linux_ppc64le/epas_rhel_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](linux_ppc64le/epas_sles_15)
+
+## Linux [AArch64 (ARM64)](linux_arm64)
+
+### Debian and derivatives
+
+- [Debian 12](linux_arm64/epas_debian_12)
+
+## Windows
+
+- [Windows Server 2019](windows)
diff --git a/product_docs/docs/epas/16/installing/linux_arm64/epas_debian_12.mdx b/product_docs/docs/epas/16/installing/linux_arm64/epas_debian_12.mdx
new file mode 100644
index 00000000000..981f6583186
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_arm64/epas_debian_12.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: Debian 12
+title: Installing EDB Postgres Advanced Server on Debian 12 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_deb12_arm
+  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/arm/epas_deb12_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:
+
+  `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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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 (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
new file mode 100644
index 00000000000..c1e50ddb610
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_arm64/index.mdx
@@ -0,0 +1,13 @@
+---
+title: "Installing EDB Postgres Advanced Server on Linux AArch64 (ARM64)"
+navTitle: "On Linux ARM64"
+
+navigation:
+  - epas_debian_12
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Debian and derivatives
+
+- [Debian 12](epas_debian_12)
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx b/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
new file mode 100644
index 00000000000..c251989554f
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/component_locations.mdx
@@ -0,0 +1,57 @@
+---
+title: Default component locations
+description: "Provides information about accessing EDB Postgres Advanced Server components after installation"
+redirects:
+- /epas/latest/epas_inst_linux/install_details/component_locations/
+---
+
+The package managers for the various Linux variations install EDB Postgres Advanced Server components in different locations. If you need to access the components after installation, see:
+
+- [RHEL/Rocky Linux/AlmaLinux/SLES locations](#rhelrocky-linuxalmalinuxsles-locations)
+- [Debian/Ubuntu locations](#debianubuntu-locations)
+
+## RHEL/Rocky Linux/AlmaLinux/SLES Locations
+
+The RPM installers place EDB Postgres Advanced Server components in the directories listed in the table.
+
+| Component                         | Location                                   |
+| --------------------------------- | ------------------------------------------ |
+| Executables                       | `/usr/edb/as16/bin`                        |
+| Libraries                         | `/usr/edb/as16/lib`                        |
+| Cluster configuration files       | `/var/lib/edb/as16`                            |
+| Documentation                     | `/usr/edb/as16/share/doc`                  |
+| Contrib                           | `/usr/edb/as16/share/contrib`              |
+| Data                              | `/var/lib/edb/as16/data`                   |
+| Logs                              | `/var/log/edb/as16`                            |
+| Lock files                        | `/var/lock/edb/as16`                           |
+| Backup area                       | `/var/lib/edb/as16/backups`                |
+| Templates                         | `/usr/edb/as16/share`                      |
+| Procedural Languages              | `/usr/edb/as16/lib or /usr/edb/as16/lib64` |
+| Development Headers               | `/usr/edb/as16/include`                    |
+| Shared data                       | `/usr/edb/as16/share`                      |
+| SGML Documentation                | `/usr/edb/as16/share/doc`                  |
+
+## Debian/Ubuntu Locations
+
+The Debian package manager places EDB Postgres Advanced Server and supporting components in the directories listed in the table.
+
+| Component                        | Location                                                                                |
+| -------------------------------- | --------------------------------------------------------------------------------------- |
+| Server                           | `/usr/lib/edb-as/16/`                                                                   |
+| Data and Configuration Directory | `/var/lib/edb-as/16/main`<br /><br />`/etc/edb-as/16/main/`                             |
+| pgAgent                          | `/usr/lib/edb-as/16`                                                                    |
+| Pgpool                           | `/usr/edb/pgpool4.1/`                                                                   |
+| Postgis                          | `/usr/lib/edb-as/16/`                                                                   |
+| PGSNMPD                          | `/usr/lib/edb-as/16`                                                                    |
+| Slony Replication                | `/usr/lib/edb-as/16`                                                                    |
+| pgBouncer                        | `/usr/edb/pgbouncer1.21/`                                                               |
+| pgBouncer Configuration Files    | `/etc/edb/pgbouncer1.21/pgbouncer.ini`<br /><br />`/etc/edb/pgbouncer1.21/userlist.txt` |
+| SQL-Profiler                     | `/usr/lib/edb-as/16/lib`                                                                |
+| SQL-Protect                      | `/usr/lib/edb-as/16/lib`                                                                |
+| SSLUTILS                         | `/usr/lib/edb-as/16/lib`                                                                |
+| PL-PERL                          | `/usr/lib/edb-as/16/lib`                                                                |
+| PL-PYTHON                        | `/usr/lib/edb-as/16/lib`                                                                |
+| PLTCL                            | `/usr/lib/edb-as/16/lib`                                                                |
+| EFM                              | `/usr/edb/efm-4.1/`                                                                     |
+| JDBC                             | `/usr/edb/jdbc`                                                                         |
+| MTK                              | `/usr/edb/migrationtoolkit/`                                                            |
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/index.mdx b/product_docs/docs/epas/16/installing/linux_install_details/index.mdx
new file mode 100644
index 00000000000..ff6ba25f53a
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/index.mdx
@@ -0,0 +1,14 @@
+---
+title: "Linux installation details"
+indexCards: simple
+redirects:
+- /epas/latest/epas_inst_linux/install_details/
+navigation:
+- component_locations
+- rpm_packages
+- updating_an_rpm_installation
+- installing_epas_using_local_repository
+- managing_an_advanced_server_installation
+---
+
+These additional use cases apply to Linux installations.
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx b/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
new file mode 100644
index 00000000000..53d38026d3b
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/installing_epas_using_local_repository.mdx
@@ -0,0 +1,57 @@
+---
+title: "Installing on Linux using a local repository"
+navTitle: "Setting up a local repository"
+description: "How to set up a local repository and install EDB Postgres Advanced Server"
+redirects:
+- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#creating-an-edb-postgres-advanced-server-repository-on-an-isolated-network
+- /epas/latest/epas_inst_linux/installing_epas_using_local_repository/
+---
+
+If the server on which you want to install EDB Postgres Advanced Server or the supporting components can't directly access the EDB repository, you can create a local repository to act as a host for the EDB Postgres Advanced Server native packages. For your network, modify this process from these high-level steps.
+
+To create and use a local repository, you must:
+
+-   Use `dnf` to install the `epel-release`, `yum-utils`, and `createrepo` packages.
+
+    On RHEL or Rocky Linux or AlmaLinux 8.x:
+
+    ```bash
+    dnf install epel-release
+    dnf install yum-utils
+    dnf install createrepo
+    ```
+
+-   Create a directory in which to store the repository:
+
+    ```text
+    mkdir /srv/repos
+    ```
+
+-   Copy the RPM installation packages to your local repository. You can download the individual packages or use a tarball to populate the repository. The packages are available from the [EDB repository](https://repos.enterprisedb.com/).
+
+-   Sync the RPM packages, and create the repository.
+
+    ```text
+    reposync -r edbas16 -p /srv/repos
+    createrepo /srv/repos
+    ```
+
+-   Install your preferred webserver on the host that acts as your local repository, and ensure that the repository directory is accessible to the other servers on your network.
+
+-   On each isolated database server, configure yum or dnf to pull updates from the mirrored repository on your local network. For example, you might create a repository configuration file called `/etc/yum.repos.d/edb-repo` with connection information that specifies:
+
+    ```text
+    [edbas16]
+    name=EnterprisEDB Postgres Advanced Server 16
+    baseurl=https://yum.your_domain.com/edbas16
+    enabled=1
+    gpgcheck=0
+    ```
+
+After specifying the location and connection information for your local repository, you can use the dnf command to install EDB Postgres Advanced Server and its supporting components on the isolated servers. For example, on RHEL or Rocky Linux or AlmaLinux 8:
+
+```text
+dnf -y install edb-as16-server
+```
+
+For more information about creating a local yum repository, see the [Centos wiki](https://wiki.centos.org/HowTos/CreateLocalRepos).
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
new file mode 100644
index 00000000000..4de069cff88
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/configuring_a_package_installation.mdx
@@ -0,0 +1,61 @@
+---
+title: "Configuring a package installation"
+---
+
+The packages that install the database server component create a unit file on version 7.x or 8.x hosts and service startup scripts.
+
+## Creating a database cluster and starting the service
+
+The PostgreSQL `initdb` command creates a database cluster. When installing EDB Postgres Advanced Server with an RPM package, the `initdb` executable is in `/usr/edb/asx.x/bin`. After installing EDB Postgres Advanced Server, you must manually configure the service and invoke `initdb` to create your cluster. When invoking `initdb`, you can:
+
+-   Specify environment options on the command line.
+-   Include the systemd service manager on RHEL/Rocky Linux/AlmaLinux 8.x and use a service configuration file to configure the environment.
+
+For more information, see the [`initdb` documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
+
+After specifying any options in the service configuration file, you can create the database cluster and start the service. The steps are platform specific.
+
+### On RHEL/Rocky Linux/AlmaLinux 8.x
+
+To invoke `initdb` on a RHEL/Rocky Linux/AlmaLinux 8.x system with the options specified in the service configuration file, assume the identity of the operating system superuser:
+
+```text
+su - root
+```
+
+To initialize a cluster with nondefault values, you can use the `PGSETUP_INITDB_OPTIONS` environment variable. You can initialize the cluster using the `edb-as-16-setup` script under `EPAS_Home/bin`.
+
+To invoke `initdb`, export the `PGSETUP_INITDB_OPTIONS` environment variable:
+
+```text
+PGSETUP_INITDB_OPTIONS="-E UTF-8" /usr/edb/as16/bin/edb-as-16-setup initdb
+```
+
+After creating the cluster, use `systemctl` to start, stop, or restart the service:
+
+```text
+systemctl { start | stop | restart } edb-as-16
+```
+
+### On Debian 11.x or Ubuntu 20.04 | 22.04
+
+You can initialize multiple clusters using the bundled scripts. To create a new cluster, assume root privileges, and invoke the bundled script:
+
+```text
+/usr/bin/epas_createcluster 16 main2
+```
+
+To start a new cluster:
+
+```text
+/usr/bin/epas_ctlcluster 16 main2 start  
+```
+
+To list all the available clusters:
+
+```text
+/usr/bin/epas_lsclusters
+```
+
+!!! Note
+    The data directory is created under `/var/lib/edb-as/16/main2`, and the configuration directory is created under `/etc/edb-as/16/main/`.
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/connecting_to_epas.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/connecting_to_epas.mdx
new file mode 100644
index 00000000000..321346f3678
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/connecting_to_epas.mdx
@@ -0,0 +1,28 @@
+---
+title: "Connecting to EDB Postgres Advanced Server with edb-psql"
+navTitle: "Connecting to EDB Postgres Advanced Server"
+---
+
+edb-psql is a command-line client application that allows you to execute SQL commands and view the results. To open the edb-psql client, the client must be in your search path. The executable resides in the `bin` directory under your EDB Postgres Advanced Server installation.
+
+## Starting the client
+
+Use the following command and options to start the edb-psql client:
+
+```text
+edb-psql -d edb -U enterprisedb
+```
+
+Where:
+
+`-d` specifies the database to which edb-psql connects.
+
+`-U` specifies the identity of the database user to use for the session.
+
+The `edb-psql` executable file is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community psql, with added support for EDB Postgres Advanced Server features. For more information about using the command-line client, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-psql.html).
+
+## Managing authentication on a Debian or Ubuntu host
+
+By default, the server is running with the peer or md5 permission on a Debian or Ubuntu host. You can change the authentication method by modifying the `pg_hba.conf` file, located under `/etc/edb-as/16/main/`.
+
+For more information about modifying the `pg_hba.conf` file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html).
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/index.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/index.mdx
new file mode 100644
index 00000000000..0f3cfff1f01
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/index.mdx
@@ -0,0 +1,12 @@
+---
+title: "Managing an EDB Postgres Advanced Server installation"
+navTitle: "Managing an installation"
+description: "Provides information about managing start/stop/restart of services, managing authentication, and initializing new clusters"
+redirects:
+- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#configuring-a-package-installation
+- /epas/latest/epas_inst_linux/07_managing_an_advanced_server_installation/
+- /epas/latest/epas_inst_linux/03_using_a_package_manager_to_install_advanced_server/#starting-multiple-postmasters-with-different-clusters
+- /epas/latest/epas_inst_linux/managing_an_advanced_server_installation/
+---
+
+ Unless otherwise noted, all commands and paths assume that you performed an installation using the native packages.
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
new file mode 100644
index 00000000000..be18b1e31f8
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/modifying_the_data_directory_location.mdx
@@ -0,0 +1,114 @@
+---
+title: "Modifying the data directory location"
+---
+
+## On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+
+On a RHEL/Rocky Linux/AlmaLinux 8.x or 9.x host, the unit file is named `edb-as-<xx>.service`, where `<xx>` is the EDB Postgres Advanced Server version. It resides in `/usr/lib/systemd/system`. The unit file contains references to the location of the EDB Postgres Advanced Server `data` directory. Avoid making any modifications directly to the unit file because they might be overwritten during package upgrades.
+
+By default, data files reside under the `/var/lib/edb/as16/data` directory. To use a data directory that resides in a nondefault location:
+
+-   Create a copy of the unit file under the `/etc` directory:
+
+    ```text
+    cp /usr/lib/systemd/system/edb-as-16.service /etc/systemd/system/
+    ```
+
+-   In the `/etc/systemd/system/edb-as-15.service` file, update the following values with the new location of the data directory:
+
+    ```text
+    Environment=PGDATA=/var/lib/edb/as16/data
+    PIDFile=/var/lib/edb/as16/data/postmaster.pid
+    ```
+
+-   Go to bin directory and initialize the cluster with the new location:
+
+    ```text
+    ./edb-as-16-setup initdb
+    ```
+
+-   Start the EDB Postgres Advanced Server service:
+
+    ```text
+    systemctl start edb-as-16
+    ```
+
+## Configuring SELinux policy to change the data directory location on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+
+By default, the data files reside under the `/var/lib/edb/as16/data` directory. To change the default data directory location depending on individual environment preferences, you must configure the SELinux policy:
+
+-   Stop the server:
+
+    ```text
+    systemctl stop edb-as-16
+    ```
+
+-   Check the status of SELinux using the `getenforce` or `sestatus` command:
+
+    ```text
+    # getenforce
+    Enforcing
+
+    # sestatus
+    SELinux status:                 enabled
+    SELinuxfs mount:                /sys/fs/selinux
+    SELinux root directory:         /etc/selinux
+    Loaded policy name:             targeted
+    Current mode:                   enforcing
+    Mode from config file:          enforcing
+    Policy MLS status:              enabled
+    Policy deny_unknown status:     allowed
+    Max kernel policy version:      31
+    ```
+
+-   View the SELinux context of the default database location:
+
+    ```text
+    ls -lZ /var/lib/edb/as16/data
+    drwx------. enterprisedb enterprisedb unconfined_u:object_r:var_lib_t:s0 log
+    ```
+
+-   Create a directory for a new location of the database:
+
+    ```text
+    mkdir /opt/edb
+    ```
+
+-   Move the data directory to `/opt/edb`:
+
+    ```text
+    mv /var/lib/edb/as16/data /opt/edb/
+    ```
+
+-   Create a file `edb-as-16.service` under `/etc/systemd/system` to include the location of a new data directory:
+
+    ```text
+    .include /lib/systemd/system/edb-as-16.service
+    [Service]
+    Environment=PGDATA=/opt/edb/data
+    PIDFile=/opt/edb/data/postmaster.pid
+    ```
+
+-   Use the semanage utility to set the context mapping for `/opt/edb/`. The mapping is written to the `/etc/selinux/targeted/contexts/files/file.contexts.local` file.
+
+    ```text
+    semanage fcontext --add --equal /var/lib/edb/as16/data /opt/edb
+    ```
+
+-   Apply the context mapping using the restorecon utility:
+
+    ```text
+    restorecon -rv /opt/edb/
+    ```
+
+-   Reload systemd to modify the service script:
+
+    ```text
+    systemctl daemon-reload
+    ```
+
+-   With the `/opt/edb` location labeled correctly with the context, start the service:
+
+    ```text
+    systemctl start edb-as-16
+    ```
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options.mdx
new file mode 100644
index 00000000000..fea4810a438
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/specifying_cluster_options.mdx
@@ -0,0 +1,95 @@
+---
+title: "Specifying cluster options with INITDBOPTS"
+navTitle: "Specifying cluster options"
+---
+
+You can use the `INITDBOPTS` variable to specify your cluster configuration preferences. By default, the `INITDBOPTS` variable is commented out in the service configuration file. Unless you modify it, when you run the service startup script, the new cluster is created in a mode compatible with Oracle databases. Clusters created in this mode contain a database named `edb` and have a database superuser named enterprisedb.
+
+## Initializing the cluster in Oracle mode
+
+If you initialize the database using Oracle-compatibility mode, the installation includes:
+
+-   Data dictionary views compatible with Oracle databases.
+-   Oracle data type conversions.
+-   Date values displayed in a format compatible with Oracle syntax.
+-   Support for Oracle-styled concatenation rules. If you concatenate a string value with a `NULL` value, the returned value is the value of the string.
+-   Support for the following Oracle built-in packages.
+
+| Package          | Functionality compatible with Oracle databases                                                                                                                               |
+| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `dbms_alert`     | Provides the capability to register for, send, and receive alerts.                                                                                                           |
+| `dbms_job`       | Provides the capability to create, schedule, and manage jobs.                                                                                                  |
+| `dbms_lob`       | Provides the capability to manage on large objects.                                                                                                                          |
+| `dbms_output`    | Provides the capability to send messages to a message buffer or get messages from the message buffer.                                                                       |
+| `dbms_pipe`      | Provides the capability to send messages through a pipe within or between sessions connected to the same database cluster.                                                   |
+| `dbms_rls`       | Enables the implementation of Virtual Private Database on certain EDB Postgres Advanced Server database objects.                                                                          |
+| `dbms_sql`       | Provides an application interface to the EDB dynamic SQL functionality.                                                                                                      |
+| `dbms_utility`   | Provides various utility programs.                                                                                                                                           |
+| `dbms_aqadm`     | Provides supporting procedures for Advanced Queueing functionality.                                                                                                          |
+| `dbms_aq`        | Provides message queueing and processing for EDB Postgres Advanced Server.                                                                                                                |
+| `dbms_profiler`  | Collects and stores performance information about the PL/pgSQL and SPL statements that are executed during a performance profiling session.                                  |
+| `dbms_random`    | Provides a number of methods to generate random values.                                                                                                                      |
+| `dbms_redact`    | Enables redacting or masking data that's returned by a query.                                                                                                        |
+| `dbms_lock`      | Provides support for the `DBMS_LOCK.SLEEP` procedure.                                                                                                                        |
+| `dbms_scheduler` | Provides a way to create and manage jobs, programs, and job schedules.                                                                                                       |
+| `dbms_crypto`    | Provides functions and procedures to encrypt or decrypt RAW, BLOB, or CLOB data. You can also use `DBMS_CRYPTO` functions to generate cryptographically strong random values. |
+| `dbms_mview`     | Provides a way to manage and refresh materialized views and their dependencies.                                                                                              |
+| `dbms_session`   | Provides support for the `DBMS_SESSION.SET_ROLE` procedure.                                                                                                                  |
+| `utl_encode`     | Provides a way to encode and decode data.                                                                                                                                    |
+| `utl_http`       | Provides a way to use the HTTP or HTTPS protocol to retrieve information found at a URL.                                                                                    |
+| `utl_file`       | Provides the capability to read from and write to files on the operating system’s file system.                                                                              |
+| `utl_smtp`       | Provides the capability to send emails over the Simple Mail Transfer Protocol (SMTP).                                                                                       |
+| `utl_mail`       | Provides the capability to manage email.                                                                                                                                    |
+| `utl_url`        | Provides a way to escape illegal and reserved characters in a URL.                                                                                                      |
+| `utl_raw`        | Provides a way to manipulate or retrieve the length of raw data types.                                                                                                       |
+
+
+## Initializing the cluster in Postgres mode
+
+Clusters created in PostgreSQL mode don't include compatibility features. To create a new cluster in PostgreSQL mode, remove the pound sign (#) in front of the `INITDBOPTS` variable, which enables the `--no-redwood-compat` option. Clusters created in PostgreSQL mode contain a database named `postgres` and have a database superuser named postgres.
+
+You can also specify multiple `initdb` options. For example, the following statement creates a database cluster without compatibility features for Oracle. The cluster contains a database named `postgres` that's owned by a user named alice. The cluster uses UTF-8 encoding.
+
+```text
+INITDBOPTS="--no-redwood-compat -U alice --locale=en_US.UTF-8"
+```
+
+If you initialize the database using `--no-redwood-compat` mode, the installation includes the following packages.
+
+| Package            | Functionality noncompatible with Oracle databases                                                               |
+| ------------------ | ---------------------------------------------------------------------------------------------------------------- |
+| `dbms_aqadm`       | Provides supporting procedures for Advanced Queueing functionality.                                              |
+| `dbms_aq`          | Provides message queueing and processing for EDB Postgres Advanced Server.                                                    |
+| `edb_bulkload`     | Provides direct/conventional data loading capability when loading huge amount of data into a database.           |
+| `edb_gen`          | Provides miscellaneous packages to run built-in packages.                                                        |
+| `edb_objects`      | Provides Oracle-compatible objects such as packages and procedures.                                             |
+| `waitstates`       | Provides monitor session blocking.                                                                               |
+| `edb_dblink_libpq` | Provides link to foreign databases by way of libpq.                                                                    |
+| `edb_dblink_oci`   | Provides link to foreign databases by way of OCI.                                                                      |
+| `snap_tables`      | Creates tables to hold wait information. Included with DRITA scripts.                                            |
+| `snap_functions`   | Creates functions to return a list of snap ids and the time the snapshot was taken. Included with DRITA scripts. |
+| `sys_stats`        | Provides OS performance statistics.                                                                              |
+
+In addition to the cluster configuration options documented in the PostgreSQL core documentation, EDB Postgres Advanced Server supports the following `initdb` options:
+
+`--no-redwood-compat`
+
+Include the `--no-redwood-compat` keywords to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is postgres, and the name of the default database is `postgres`. The few EDB Postgres Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using the EDB Postgres Advanced Server in redwood compatibility mode to use all its features.
+
+`--redwood-like`
+
+Include the `--redwood-like` keywords to use an escape character. The character is an empty string ('') and it follows the `LIKE` (or PostgreSQL-compatible `ILIKE`) operator in a SQL statement that's compatible with Oracle syntax.
+
+`--icu-short-form`
+
+Include the `--icu-short-form` keywords to create a cluster that uses a default International Components for Unicode (ICU) collation for all databases in the cluster. For more information about Unicode collations, see [Unicode collation algorithm](/epas/latest/tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm/).
+
+For more information about using `initdb` and the available cluster configuration options, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-initdb.html).
+
+You can also view online help for `initdb` by assuming superuser privileges and entering:
+
+```text
+/path_to_initdb_installation_directory/initdb --help
+```
+
+Where `path_to_initdb_installation_directory` specifies the location of the `initdb` binary file.
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
new file mode 100644
index 00000000000..8986d9b6f4d
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_and_stopping_services.mdx
@@ -0,0 +1,117 @@
+---
+title: "Starting and stopping services"
+---
+
+A service is a program that runs in the background and doesn't require user interaction. A service has no user interface. You can configure a service to start at boot time or manually on demand. Services are best controlled using the platform-specific operating system service control utility. Many of the EDB Postgres Advanced Server supporting components are services.
+
+## List of services
+
+The following table lists the names of the services that control EDB Postgres Advanced Server and services that control EDB Postgres Advanced Server supporting components.
+
+| EDB Postgres Advanced Server component name | Linux service name       | Debian service name                     |
+| ------------------------------ | ------------------------ | --------------------------------------- |
+| EDB Postgres Advanced Server   | edb-as-16                | edb-as@16-main                          |
+| pgAgent                        | edb-pgagent-16           | edb-as16-pgagent                        |
+| PgBouncer                      | edb-pgbouncer-1.21       | edb-pgbouncer121                        |
+| pgPool-II                      | edb-pgpool-4.4           | edb-pgpool44                            |
+| Slony                          | edb-slony-replication-15 | edb-as15-slony-replication              |
+| EFM                            | edb-efm-4.0              | edb-efm-4.0                             |
+
+You can use the Linux command line to control the EDB Postgres Advanced Server database server and the services of EDB Postgres Advanced Server's supporting components. The commands that control the EDB Postgres Advanced Server service on a Linux platform are host specific.
+
+## Controlling a service on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+
+If your installation of EDB Postgres Advanced Server resides on version 8.x | 9.x of RHEL, you must use the `systemctl` command to control the EDB Postgres Advanced Server service and supporting components.
+
+The `systemctl` command must be in your search path, and you must invoke it with superuser privileges. To use the command, at the command line, enter:
+
+```text
+systemctl <action> <service_name>
+```
+
+Where:
+
+`service_name` specifies the name of the service.
+
+`action` specifies the action taken by the service command. Specify:
+
+-   `start` to start the service.
+-   `stop` to stop the service.
+-   `restart` to stop and then start the service.
+-   `status` to discover the current status of the service.
+
+## Controlling a service on Debian 11.x or Ubuntu 20.04 | 22.04
+
+If your installation of EDB Postgres Advanced Server resides on version 11.x of Debian or 20.04 | 22.04 of Ubuntu, assume superuser privileges and invoke the following commands using bundled scripts to manage the service. Use the following commands to:
+
+-   Discover the current status of a service:
+
+    ```text
+    /usr/edb/as15/bin/epas_ctlcluster 15 main status
+    ```
+
+-   Stop a service:
+
+    ```text
+    /usr/edb/as15/bin/epas_ctlcluster 15 main stop
+    ```
+
+-   Restart a service:
+
+    ```text
+    /usr/edb/as15/bin/epas_ctlcluster 15 main restart
+    ```
+
+-   Reload a service:
+
+    ```text
+    /usr/edb/as15/bin/epas_ctlcluster 15 main reload
+    ```
+
+-   Control the component services:
+
+    ```text
+    systemctl restart edb-as@15-main
+    ```
+
+## Using pg_ctl to control EDB Postgres Advanced Server
+
+You can use the pg_ctl utility to control an EDB Postgres Advanced Server service from the command line on any platform. pg_ctl allows you to:
+
+-  Start, stop, or restart the EDB Postgres Advanced Server database server
+-  Reload the configuration parameters
+-  Display the status of a running server 
+
+To invoke the utility, assume the identity of the cluster owner. In the home directory of EDB Postgres Advanced Server, enter:
+
+```text
+./bin/pg_ctl -D <data_directory> <action>
+```
+
+`data_directory` is the location of the data controlled by the EDB Postgres Advanced Server cluster.
+
+`action` specifies the action taken by the pg_ctl utility. Specify:
+
+-   `start` to start the service.
+-   `stop` to stop the service.
+-   `restart` to stop and then start the service.
+-   `reload` to send the server a `SIGHUP` signal, reloading configuration parameters.
+-   `status` to discover the current status of the service.
+
+For more information about using the pg_ctl utility or the command-line options available, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-pg-ctl.html).
+
+### Choosing between pg_ctl and the service command
+
+You can use the pg_ctl utility to manage the status of an EDB Postgres Advanced Server cluster. However, it's important to know that pg_ctl doesn't alert the operating system service controller to changes in the status of a server. We recommend using the `service` command when possible.
+
+## Configuring component services to autostart at system reboot
+
+After installing, configuring, and starting the services of EDB Postgres Advanced Server supporting components on a Linux system, you must manually configure your system to autostart the service when your system restarts. To configure a service to autostart on a Linux system, at the command line, assume superuser privileges, and enter the command.
+
+On a Redhat-compatible Linux system, enter:
+
+```text
+/sbin/chkconfig <service_name> on
+```
+
+Where `service_name` specifies the name of the service.
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
new file mode 100644
index 00000000000..eb00c38e798
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/managing_an_advanced_server_installation/starting_multiple_postmasters.mdx
@@ -0,0 +1,41 @@
+---
+title: "Starting multiple postmasters with different clusters"
+---
+
+You can configure EDB Postgres Advanced Server to use multiple postmasters, each with its own database cluster. The steps required are specific to the version of the Linux host.
+
+## On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x
+
+The `edb-as16-server-core` RPM for version 8.x | 9.x contains a unit file that starts the EDB Postgres Advanced Server instance. The file allows you to start multiple services with unique `data` directories and monitor different ports. You need root access to invoke or modify the script.
+
+This example creates an EDB Postgres Advanced Server installation with two instances. The secondary instance is named `secondary`.
+
+-   Make a copy of the default file with the new name. As noted at the top of the file, all modifications must reside under `/etc`. You must pick a name that isn't already used in `/etc/systemd/system`.
+
+    ```text
+    cp /usr/lib/systemd/system/edb-as-16.service /etc/systemd/system/secondary-edb-as-15.service
+    ```
+
+-   Edit the file, changing `PGDATA` to point to the new `data` directory that you're creating the cluster against.
+
+-   Create the target `PGDATA` with the user enterprisedb.
+
+-   Run `initdb`, specifying the setup script:
+
+    ```text
+    /usr/edb/as16/bin/edb-as-16-setup initdb secondary-edb-as-16
+    ```
+
+-   Edit the `postgresql.conf` file for the new instance, specifying the port, the IP address, TCP/IP settings, and so on.
+
+-   Make sure that the new cluster runs after a reboot:
+
+    ```text
+    systemctl enable secondary-edb-as-16
+    ```
+
+-   Start the second cluster:
+
+    ```text
+    systemctl start secondary-edb-as-16
+    ```
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx b/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
new file mode 100644
index 00000000000..213dc7d35e4
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/rpm_packages.mdx
@@ -0,0 +1,152 @@
+---
+title: "Available native packages"
+description: "Provides information about available native packages from the EDB repository"
+redirects:
+- /epas/latest/epas_inst_linux/install_details/rpm_packages/
+---
+
+EDB provides a number of native packages in the EDB repository. The packages vary slightly for the various Linux variations. See:
+
+- [RHEL/Rocky Linux/AlmaLinux/SLES packages](#rhelrocky-linuxalmalinuxsles-packages)
+- [Debian/Ubuntu packages](#debianubuntu-packages)
+
+## RHEL/Rocky Linux/AlmaLinux/SLES packages
+
+### EDB Postgres Advanced Server RPM packages
+
+The tables that follow list the RPM packages that are available from EDB. You can also use the `dnf search` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
+
+On RHEL or Rocky Linux or AlmaLinux 8:
+
+```text
+dnf search <package>
+```
+
+Where `package` is the search term that specifies the name or partial name of a package.
+
+!!! Note
+    The available package list is subject to change.
+
+|           Package name           | Installed by default |                                                                                                                                                                      Package installs                                                                                                                                                                       |
+| -------------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| edb-as16-server                  | Yes                  | Installs core components of the EDB Postgres Advanced Server database server.                                                                                                                                                                                                                                                                               |
+| edb-as16-server-client           | Yes                  | Client programs and utilities that you can use to access and manage EDB Postgres Advanced Server.                                                                                                                                                                                                                                                           |
+| edb-as16-server-contrib          | Yes                  | Installs contributed tools and utilities that are distributed with EDB Postgres Advanced Server. Files for these modules are installed in:<br /><br />Documentation: `/usr/edb/as16/share/doc`<br /><br />Loadable modules: `/usr/edb/as16/lib`<br /><br />Binaries: `/usr/edb/as16/bin`                                                                    |
+| edb-as16-server-core             | Yes                  | Includes the programs needed to create the core functionality behind the EDB Postgres Advanced Server database.                                                                                                                                                                                                                                             |
+| edb-as16-server-devel            | Yes                  | Installs the header files and libraries needed to compile C or C++ applications that directly interact with an EDB Postgres Advanced Server server and the ecpg or ecpgPlus C preprocessor.                                                                                                                                                                 |
+| edb-as16-server-docs             | Yes                  | Installs the readme file.                                                                                                                                                                                                                                                                                                                                   |
+| edb-as16-server-edb-modules      | No                   | Installs supporting modules for EDB Postgres Advanced Server.                                                                                                                                                                                                                                                                                               |
+| edb-as16-server-libs             | Yes                  | Provides the essential shared libraries for any EDB Postgres Advanced Server client program or interface.                                                                                                                                                                                                                                                   |
+| edb-as16-server-llvmjit          | No                   | Contains support for just-in-time (JIT) compiling parts of EDB Postgres Advanced Server's queries. You need to install this package separately.                                                                                                                                                                                                             |
+| edb-as16-server-pldebugger       | No                   | Implements an API for debugging PL/pgSQL functions on EDB Postgres Advanced Server.                                                                                                                                                                                                                                                                         |
+| edb-as16-server-plperl           | Yes                  | Installs the PL/Perl procedural language for EDB Postgres Advanced Server. The `edb-as16-server-plperl` package depends on the platform-supplied version of Perl.                                                                                                                                                                                           |
+| edb-as16-server-plpython3        | Yes                  | Installs the PL/Python procedural language for EDB Postgres Advanced Server. The PL/Python2 support is no longer available in EDB Postgres Advanced Server version 15 and later.                                                                                                                                                                            |
+| edb-as16-server-pltcl            | Yes                  | Installs the PL/Tcl procedural language for EDB Postgres Advanced Server. The `edb-as16-server-pltcl` package depends on the platform-supplied version of TCL.                                                                                                                                                                                                     |
+| edb-as16-server-sqlprofiler      | No                   | Installs EDB Postgres Advanced Server's SQL Profiler feature. SQL Profiler helps identify and optimize SQL code.                                                                                                                                                                                                                                            |
+| edb-as16-server-sqlprotect       | Yes                  | Installs EDB Postgres Advanced Server's SQL Protect feature. SQL Protect provides protection against SQL injection attacks.                                                                                                                                                                                                                                 |
+| edb-as16-server-sslutils         | No                   | Installs functionality that provides SSL support.                                                                                                                                                                                                                                                                                                           |
+| edb-as16-server-cloneschema      | No                   | Installs the EDB Clone Schema extension. For more information about EDB Clone Schema, see [EDB clone schema](../../database_administration/14_edb_clone_schema/).                                                                                                                                                                                           |
+| edb-as16-server-parallel-clone   | No                   | Installs functionality that supports the EDB Clone Schema extension.                                                                                                                                                                                                                                                                                        |
+| edb-as16-pgagent                 | No                   | Installs pgAgent: Installs pgAgent, a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install EPEL repository. For detailed information about installing EPEL, see [Linux installation troubleshooting](../troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/).                             |
+| edb-as16-edbplus                 | No                   | The `edb-edbplus` package contains the files required to install the EDB\*Plus command line client. EDB\*Plus commands are compatible with Oracle's SQL\*Plus.                                                                                                                                                                                              |
+| edb-as16-pgpool44-extensions     | No                   | Creates pgPool extensions required by the server for use with pgpool.                                                                                                                                                                                                                                                                                       |
+| edb-as16-postgis34               | No                   | Installs POSTGIS meta RPMs.                                                                                                                                                                                                                                                                                                                                 |
+| edb-as16-postgis34-core          | No                   | Provides support for geographic objects to the PostgreSQL object-relational database. In effect, PostGIS "spatially enables" the PostgreSQL server, allowing it to be used as a backend spatial database for geographic information systems (GIS), much like ESRI's SDE or Oracle's Spatial extension.                                                      |
+| edb-as16-postgis34-docs          | No                   | Installs PDF documentation of PostGIS.                                                                                                                                                                                                                                                                                                                      |
+| edb-as16-postgis34-utils         | No                   | Installs the utilities for PostGIS.                                                                                                                                                                                                                                                                                                                         |
+| edb-as16-postgis34-gui           | No                   | Provides a GUI for PostGIS.                                                                                                                                                                                                                                                                                                                                 |
+| edb-as16-libicu                  | No                   | Contains the supporting library files. 
+| edb-as16-hdfs-fdw                | No                   | The Hadoop Data Adapter allows you to query and join data from Hadoop environments with your Postgres or EDB Postgres Advanced Server instances. It's YARN Ready certified with HortonWorks and provides optimizations for performance with predicate pushdown support.                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-hdfs-fdw-doc            | No                   | Documentation for the Hadoop Data Adapter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-as16-mongo-fdw               | No                   | EDB Postgres Advanced Server extension that implements a foreign data wrapper for MongoDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-as16-mongo-fdw-doc           | No                   | Documentation for the foreign data wrapper for MongoDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-mysql-fdw               | No                   | EDB Postgres Advanced Server extension that implements a foreign data wrapper for MySQL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+
+The following table lists the packages for EDB Postgres Advanced Server supporting components.
+
+| Package name                | Package installs                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| --------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| edb-pgpool44                | Contains the pgPool-II installer. The pgpool-II utility package acts as a middleman between client applications and server database servers. pgpool-II functionality is transparent to client applications. Client applications connect to pgpool-II instead of directly to EDB Postgres Advanced Server, and pgpool-II manages the connection. EDB supports the following pgpool-II features: <br />-   Load balancing    <br /> -   Connection pooling   <br /> -   High availability   <br /> -   Connection limits   <br /><br /><br />pgpool-II runs as a service on Linux systems, and isn't supported on Windows systems.<br /> |
+| edb-jdbc                    | The `edb-jdbc` package includes the `.jar` files needed for Java programs to access an EDB Postgres Advanced Server database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-migrationtoolkit        | The `edb-migrationtoolkit` package installs Migration Toolkit, facilitating migration to an EDB Postgres Advanced Server database from Oracle, PostgreSQL, MySQL, Sybase, and SQL Server.                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-oci                     | The `edb-oci` package installs the EDB Open Client library, allowing applications that use the Oracle Call Interface API to connect to an EDB Postgres Advanced Server database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| edb-oci-devel               | Installs the OCI include files. Install this package if you're developing C/C++ applications that require these files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| edb-odbc                    | Installs the driver needed for applications to access an EDB Postgres Advanced Server system by way of ODBC.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| edb-odbc-devel              | Installs the ODBC include files. Install this package if you're developing C/C++ applications that require these files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| edb-pgbouncer121            | Contains PgBouncer (a lightweight connection pooler). This package requires the `libevent` package.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ppas-xdb                    | Contains the xDB installer. xDB provides asynchronous cross-database replication.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ppas-xdb-console            | Provides support for xDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ppas-xdb-libs               | Provides support for xDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ppas-xdb-publisher          | Provides support for xDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ppas-xdb-subscriber         | Provides support for xDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| edb-pem                     | The `edb-pem` package installs the management tool that efficiently manages, monitors, and tunes large Postgres deployments from a single remote GUI console.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| edb-pem-agent               | The `edb-pem-agent` is an agent component of Postgres Enterprise Manager.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| edb-pem-docs                | Contains documentation for various languages, which are in HTML format.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| edb-pem-server              | Contains server components of Postgres Enterprise Manager.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| pgadmin4                | Installs all required components to run pgadmin4 in desktop and web modes. Pgadmin4 is a management tool for Postgres capable of hosting the Python application and presenting it to the user as a desktop application.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| pgadmin4-desktop        | Installs pgadmin4 for desktop mode only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| pgadmin4-web            | Installs pgadmin4 for web mode only.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| pgadmin4-server         | Installs pgadmin4's core server package.                                                                                                                                                                                 |
+| edb-efm40                   | Installs EDB Failover Manager that adds fault tolerance to database clusters to minimize downtime when a primary database fails by keeping data online in high availability configurations.                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| edb-rs                      | A Java-based replication framework that provides asynchronous replication across Postgres and EDB Postgres Advanced Server database servers. It supports primary-standby, primary-primary, and hybrid configurations.                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| edb-rs-client               | A Java-based command-line tool that's used to configure and operate a replication network by way of different commands by interacting with the EPRS server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| edb-rs-datavalidator        | A Java-based command-line tool that provides row- and-column level data comparison of a source and target database table. The supported RDBMS servers include PostgreSQL, EDB Postgres Advanced Server, Oracle, and MS SQL Server.                                                                                                                                                                                                                                                                                                                                                                                                               |
+| edb-rs-libs                 | Contains certain libraries that are commonly used by ERPS server, EPRS client, and monitoring modules.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| edb-rs-monitor              | A Java-based application that provides monitoring capabilities to ensure a smooth functioning of the EPRS replication cluster.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-rs-server               | A Java-based replication framework that provides asynchronous replication across Postgres and EDB Postgres Advanced Server database servers. It supports primary-standby, primary-primary, and hybrid configurations.                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| edb-bart                    | Installs the Backup and Recovery Tool (BART) to support online backup and recovery across local and remote PostgreSQL and EDB Postgres Advanced Server servers.                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| libevent-edb                | Contains supporting library files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| libiconv-edb                | Contains supporting library files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| libevent-edb-devel          | Contains supporting library files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+
+## Debian/Ubuntu packages
+
+### EDB Postgres Advanced Server Debian packages
+
+The table lists some of the Debian packages that are available from EDB. You can also use the `apt list` command to access a list of the packages that are currently available from your configured repository. At the command line, assume superuser privileges, and enter:
+
+```text
+apt list edb*
+```
+
+!!! Note
+    The available package list is subject to change.
+
+|           Package name           | Installed by default |                                                                                                                                                                                                                                                                                                            Package installs                                                                                                                                                                                                                                                                                                            |
+| -------------------------------- | -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| edb-as16-server                  | Yes                  | Installs core components of the EDB Postgres Advanced Server database server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-server-client           | Yes                  | Includes client programs and utilities that you can use to access and manage EDB Postgres Advanced Server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-as16-server-core             | Yes                  | Includes the programs needed to create the core functionality behind the EDB Postgres Advanced Server database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| edb-as16-server-dev              | Yes                  | Contains the header files and libraries needed to compile C or C++ applications that directly interact with an EDB Postgres Advanced Server server and the ecpg or ecpgPlus C preprocessor.                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| edb-as16-server-doc              | Yes                  | Installs the readme file.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| edb-as16-server-edb-modules      | No                   | Installs supporting modules for EDB Postgres Advanced Server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-server-pldebugger       | No                   | Implements an API for debugging PL/pgSQL functions on EDB Postgres Advanced Server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| edb-as16-server-plpython3        | Yes                  | Installs the PL/Python procedural language for EDB Postgres Advanced Server. PL/Python2 support is not available for EDB Postgres Advanced Server version 15 and later.                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-server-pltcl            | Yes                  | Installs the PL/Tcl procedural language for EDB Postgres Advanced Server. The `edb-as16-server-pltcl` package depends on the platform-supplied version of TCL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-server-sqlprofiler      | No                   | Installs EDB Postgres Advanced Server's SQL Profiler feature. SQL Profiler helps identify and optimize SQL code.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| edb-as16-server-sqlprotect       | Yes                  | Installs EDB Postgres Advanced Server's SQL Protect feature. SQL Protect provides protection against SQL injection attacks.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| edb-as16-server-sslutils         | No                   | Installs functionality that provides SSL support.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| edb-as16-server-cloneschema      | No                   | Installs the EDB Clone Schema extension. For more information about EDB Clone Schema, see [EDB Clone Schema](../../database_administration/14_edb_clone_schema/).                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| edb-as16-server-parallel-clone   | No                   | Installs functionality that supports the EDB Clone Schema extension.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| edb-as16-edbplus                 | No                   | Contains the files required to install the EDB\*Plus command-line client. EDB\*Plus commands are compatible with Oracle's SQL\*Plus.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| edb-as16-pgadmin4                | No                   | pgAdmin 4 provides a graphical management interface for EDB Postgres Advanced Server and PostgreSQL databases.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| edb-as16-pgadmin-apache          | No                   | Apache support module for pgAdmin 4.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| edb-as16-pgadmin4-common         | No                   | pgAdmin 4 supporting files.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| edb-as16-pgadmin4-doc            | No                   | pgAdmin 4 documentation module.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| edb-as16-pgpool44-extensions     | No                   | Creates pgPool extensions required by the server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| edb-as16-postgis34               | No                   | Installs POSTGIS support for geospatial data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-postgis34-scripts       | No                   | Installs POSTGIS support for geospatial data.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-postgis34-doc           | No                   | Provides support for POSTGIS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-postgis34-gui           | No                   | Provides a GUI for POSTGIS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+| edb-as16-postgis-scripts         | No                   | Provides support for POSTGIS.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| edb-as16-pgagent                 | No                   | Installs pgAgent, a job scheduler for EDB Postgres Advanced Server. Before installing this package, you must install the EPEL repository. For detailed information about installing EPEL, see [Linux installation troubleshooting](../troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/).                                                                                                                                                                                                                                                                                                                      |
+| edb-as16-hdfs-fdw                | No                   | The Hadoop Data Adapter allows you to query and join data from Hadoop environments with your Postgres or EDB Postgres Advanced Server instances. It's YARN Ready certified with HortonWorks and provides optimizations for performance with predicate pushdown support.                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-hdfs-fdw-doc            | No                   | Documentation for the Hadoop Data Adapter.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-as16-mongo-fdw               | No                   | EDB Postgres Advanced Server extension that implements a foreign data wrapper for MongoDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| edb-as16-mongo-fdw-doc           | No                   | Documentation for the foreign data wrapper for MongoDB.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| edb-as16-mysql-fdw               | No                   | EDB Postgres Advanced Server extension that implements a foreign data wrapper for MySQL.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| edb-pgpool44                     | No                   | Contains the pgPool-II installer. The pgpool-II utility package acts as a middleman between client applications and server database servers. pgpool-II functionality is transparent to client applications. Client applications connect to pgpool-II instead of directly to EDB Postgres Advanced Server, and pgpool-II manages the connection. EDB supports the following pgpool-II features: <br />-   Load balancing    <br /> -   Connection pooling   <br /> -   High availability   <br /> -   Connection limits   <br /><br /><br />pgpool-II runs as a service on Linux systems, and isn't supported on Windows systems.<br /> |
+| edb-jdbc                         | No                   | Includes the .jar files needed for Java programs to access an EDB Postgres Advanced Server database.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| edb-migrationtoolkit             | No                   | Installs Migration Toolkit, facilitating migration to an EDB Postgres Advanced Server database from Oracle, PostgreSQL, MySQL, Sybase, and SQL Server.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| edb-pgbouncer121                 | No                   | PgBouncer, a lightweight connection pooler. This package requires the `libevent` package.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| edb-efm40                        | No                   | Installs EDB Failover Manager, which adds fault tolerance to database clusters to minimize downtime when a primary database fails by keeping data online in high availability configurations.                                                                                                                                                                                                                                                                                                                                                                                                                                          |
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx b/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
new file mode 100644
index 00000000000..7bf129adabe
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_install_details/updating_an_rpm_installation.mdx
@@ -0,0 +1,23 @@
+---
+title: "Updating an RPM installation"
+description: "Describes how to upgrade your repository configuration file and update to a more recent product version"
+---
+
+If you have an existing EDB Postgres Advanced Server RPM installation, you can use yum or dnf to upgrade your repository configuration file and update to a more recent product version. 
+
+To update the `edb.repo` file, assume superuser privileges and enter:
+
+```text
+dnf upgrade edb-repo
+```
+
+`dnf` updates the `edb.repo` file to enable access to the current EDB repository, configured to connect with the credentials specified in your `edb.repo` file. Then, you can use `dnf` to upgrade all packages whose names include the expression `edb`:
+
+```text
+dnf upgrade edb*
+```
+
+!!! Note
+    The `dnf upgrade` command performs an update only between minor releases. To update between major releases, use `pg_upgrade`.
+
+For more information about using dnf commands and options, see the [dnf documentation](https://docs.fedoraproject.org/en-US/quick-docs/dnf/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_8.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_8.mdx
new file mode 100644
index 00000000000..a6c43b87cb0
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_8.mdx
@@ -0,0 +1,159 @@
+---
+navTitle: RHEL 8
+title: Installing EDB Postgres Advanced Server on RHEL 8 ppc64le
+# 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/ibm_power_ppc64le/epas_rhel8_ppcle
+  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel8_ppcle
+---
+
+## 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-8.noarch.rpm
+  ```
+- Refresh the cache:
+  ```shell
+  sudo dnf makecache
+  ```
+- If you're also installing PostGIS, enable additional repositories to resolve dependencies:
+
+  ```shell
+  ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms"
+  ```
+
+  !!!note
+
+  If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using.
+
+  !!!
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_ppc64le/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx
new file mode 100644
index 00000000000..a52bf214cda
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_rhel_9.mdx
@@ -0,0 +1,159 @@
+---
+navTitle: RHEL 9
+title: Installing EDB Postgres Advanced Server on RHEL 9 ppc64le
+# 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/ibm_power_ppc64le/epas_rhel9_ppcle
+  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_rhel9_ppcle
+---
+
+## 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
+  ```
+- Refresh the cache:
+  ```shell
+  sudo dnf makecache
+  ```
+- 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_ppc64le/epas_sles_15.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_15.mdx
new file mode 100644
index 00000000000..d486d61de90
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_ppc64le/epas_sles_15.mdx
@@ -0,0 +1,147 @@
+---
+navTitle: SLES 15
+title: Installing EDB Postgres Advanced Server on SLES 15 ppc64le
+# 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/ibm_power_ppc64le/epas_sles15_ppcle
+  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/ppcle/epas_sles15_ppcle
+---
+
+## 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:
+
+  `zypper lr -E | 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.
+
+- Activate the required SUSE module:
+  ```shell
+  sudo SUSEConnect -p PackageHub/15.4/ppc64le
+
+  ```
+- Refresh the metadata:
+  ```shell
+  sudo zypper refresh
+  ```
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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_ppc64le/index.mdx b/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
new file mode 100644
index 00000000000..3cf00fbf03f
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_ppc64le/index.mdx
@@ -0,0 +1,30 @@
+---
+title: "Installing EDB Postgres Advanced Server on Linux IBM Power (ppc64le)"
+navTitle: "On Linux ppc64le"
+
+# 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.
+# 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
+
+navigation:
+  - epas_rhel_9
+  - epas_rhel_8
+  - epas_sles_15
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Red Hat Enterprise Linux (RHEL)
+
+- [RHEL 9](epas_rhel_9)
+
+- [RHEL 8](epas_rhel_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](epas_sles_15)
diff --git a/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_11.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_11.mdx
new file mode 100644
index 00000000000..155cd9dcd78
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_11.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: Debian 11
+title: Installing EDB Postgres Advanced Server on Debian 11 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/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
+---
+
+## 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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 (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_x86_64/epas_debian_12.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_12.mdx
new file mode 100644
index 00000000000..7566c7cf518
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_debian_12.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: Debian 12
+title: Installing EDB Postgres Advanced Server on Debian 12 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/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
+---
+
+## 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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 (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_x86_64/epas_other_linux_8.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_8.mdx
new file mode 100644
index 00000000000..2c8b4b896e6
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_8.mdx
@@ -0,0 +1,150 @@
+---
+navTitle: AlmaLinux 8 or Rocky Linux 8
+title: Installing EDB Postgres Advanced Server on AlmaLinux 8 or Rocky Linux 8 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/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
+---
+
+## 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 epel-release
+  ```
+
+- Enable additional repositories to resolve dependencies:
+  ```shell
+  sudo dnf config-manager --set-enabled powertools
+  ```
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_x86_64/epas_other_linux_9.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_9.mdx
new file mode 100644
index 00000000000..6664b93d760
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_other_linux_9.mdx
@@ -0,0 +1,150 @@
+---
+navTitle: AlmaLinux 9 or Rocky Linux 9
+title: Installing EDB Postgres Advanced Server on AlmaLinux 9 or Rocky Linux 9 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/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
+---
+
+## 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 epel-release
+  ```
+
+- Enable additional repositories to resolve dependencies:
+  ```shell
+  sudo dnf config-manager --set-enabled crb
+  ```
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_x86_64/epas_rhel_8.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_8.mdx
new file mode 100644
index 00000000000..d635274737b
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_8.mdx
@@ -0,0 +1,157 @@
+---
+navTitle: RHEL 8 or OL 8
+title: Installing EDB Postgres Advanced Server on RHEL 8 or OL 8 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/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
+---
+
+## 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-8.noarch.rpm
+  ```
+
+- If you're also installing PostGIS, enable additional repositories to resolve dependencies:
+
+  ```shell
+  ARCH=$( /bin/arch ) subscription-manager repos --enable "codeready-builder-for-rhel-8-${ARCH}-rpms"
+  ```
+
+  !!!note
+
+  If you're using a public cloud RHEL image, `subscription manager` might not be enabled. Enabling it might incur unnecessary charges. Equivalent packages might be available under a different name, such as `codeready-builder-for-rhel-8-rhui-rpms`. To determine how to install `codeready-builder`, consult the documentation for the RHEL image you're using.
+
+  !!!
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_x86_64/epas_rhel_9.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_rhel_9.mdx
new file mode 100644
index 00000000000..d188cc94221
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/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 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/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
+---
+
+## 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+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_x86_64/epas_sles_15.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_15.mdx
new file mode 100644
index 00000000000..d00dc432be4
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_sles_15.mdx
@@ -0,0 +1,147 @@
+---
+navTitle: SLES 15
+title: Installing EDB Postgres Advanced Server on SLES 15 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/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
+---
+
+## 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:
+
+  `zypper lr -E | 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.
+
+- Activate the required SUSE module:
+  ```shell
+  sudo SUSEConnect -p PackageHub/15.4/x86_64
+
+  ```
+- Refresh the metadata:
+  ```shell
+  sudo zypper refresh
+  ```
+
+## Install the package
+
+```shell
+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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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_x86_64/epas_ubuntu_20.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_20.mdx
new file mode 100644
index 00000000000..4ff3a4e421c
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_20.mdx
@@ -0,0 +1,129 @@
+---
+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/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
+---
+
+## 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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 (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_x86_64/epas_ubuntu_22.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_22.mdx
new file mode 100644
index 00000000000..74d784ec8a8
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/epas_ubuntu_22.mdx
@@ -0,0 +1,129 @@
+---
+navTitle: Ubuntu 22.04
+title: Installing EDB Postgres Advanced Server on Ubuntu 22.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/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
+---
+
+## 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<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`.
+
+To install an individual component:
+
+```shell
+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/).
+
+## 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 (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_x86_64/index.mdx b/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
new file mode 100644
index 00000000000..5d06a808c66
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/linux_x86_64/index.mdx
@@ -0,0 +1,58 @@
+---
+title: "Installing EDB Postgres Advanced Server on Linux x86 (amd64)"
+navTitle: "On Linux x86"
+
+# 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.
+# Leaf template: products/edb-postgres-advanced-server/x86_64_index.njk
+
+redirects:
+  - ../03_using_a_package_manager_to_install_advanced_server
+  - /epas/16/epas_inst_linux/installing_epas_using_edb_repository/x86_amd64/
+
+navigation:
+  - epas_rhel_9
+  - epas_rhel_8
+  - epas_other_linux_9
+  - epas_other_linux_8
+  - epas_sles_15
+  - epas_ubuntu_22
+  - epas_ubuntu_20
+  - epas_debian_12
+  - epas_debian_11
+---
+
+Operating system-specific install instructions are described in the corresponding documentation:
+
+### Red Hat Enterprise Linux (RHEL) and derivatives
+
+- [RHEL 9](epas_rhel_9)
+
+- [RHEL 8](epas_rhel_8)
+
+- [Oracle Linux (OL) 9](epas_rhel_9)
+
+- [Oracle Linux (OL) 8](epas_rhel_8)
+
+- [Rocky Linux 9](epas_other_linux_9)
+
+- [Rocky Linux 8](epas_other_linux_8)
+
+- [AlmaLinux 9](epas_other_linux_9)
+
+- [AlmaLinux 8](epas_other_linux_8)
+
+### SUSE Linux Enterprise (SLES)
+
+- [SLES 15](epas_sles_15)
+
+### Debian and derivatives
+
+- [Ubuntu 22.04](epas_ubuntu_22)
+
+- [Ubuntu 20.04](epas_ubuntu_20)
+
+- [Debian 12](epas_debian_12)
+
+- [Debian 11](epas_debian_11)
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/index.mdx b/product_docs/docs/epas/16/installing/troubleshooting/index.mdx
new file mode 100644
index 00000000000..1d7c2f6614f
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/troubleshooting/index.mdx
@@ -0,0 +1,11 @@
+---
+title: "Troubleshooting"
+indexCards: simple
+navigation:
+  - linux_troubleshooting
+  - windows_troubleshooting
+redirects:
+  - /epas/latest/troubleshooting/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+You can troubleshoot your EDB Postgres Advanced Server installation on Linux or Windows.
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
new file mode 100644
index 00000000000..dd0b9a6606e
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/enabling_core_dump.mdx
@@ -0,0 +1,232 @@
+---
+title: "Enabling core dumps"
+redirects:
+  - /epas/latest/epas_inst_linux/04_enabling_core_dump/
+  - /epas/latest/troubleshooting/troubleshooting_linux/enabling_core_dump/
+  - /epas/latest/troubleshooting/linux_troubleshooting/enabling_core_dump/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+You can use core dumps to diagnose or debug errors. A core dump is a file containing a process's address space (memory) when the process terminates unexpectedly. Core dumps can be produced on demand, such as by a debugger, or upon termination.
+
+## Enabling core dumps on a RHEL or Rocky Linux or AlmaLinux host
+
+On RHEL/Rocky Linux/AlmaLinux 8.x | 9.x, core file creation is disabled by default. To enable the core file generation:
+
+-   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
+
+    ```text
+    # ulimit -c
+    0
+
+    # ulimit -a
+    core file size          (blocks, -c) 0
+    data seg size           (kbytes, -d) unlimited
+    scheduling priority             (-e) 0
+    file size               (blocks, -f) unlimited
+    pending signals                 (-i) 3756
+    max locked memory       (kbytes, -l) 64
+    max memory size         (kbytes, -m) unlimited
+    open files                      (-n) 1024
+    pipe size            (512 bytes, -p) 8
+    POSIX message queues     (bytes, -q) 819200
+    real-time priority              (-r) 0
+    stack size              (kbytes, -s) 8192
+    cpu time               (seconds, -t) unlimited
+    max user processes              (-u) 3756
+    virtual memory          (kbytes, -v) unlimited
+    file locks                      (-x) unlimited
+    ```
+
+-   Create a directory to store the core dumps, and modify `kernel.core_pattern` to store the dumps in a specified directory:
+
+    ```text
+    mkdir -p /var/coredumps
+    chmod a+w /var/coredumps
+
+    sysctl kernel.core_pattern=/var/coredumps/core-%e-%p
+    kernel.core_pattern = /var/coredumps/core-%e-%p
+    ```
+
+-   Persist the `kernel.core_pattern` setting across reboots:
+
+    ```text
+    echo 'kernel.core_pattern=/var/coredumps/core-%e-%p' >> /etc/sysctl.conf
+    ```
+
+-   Enable core dumps in `/etc/security/limits.conf` to allow a user to create core files. Each line describes a limit for a user in the following form:
+
+    ```text
+    <domain>  <type>  <item>  <value>
+       *       soft    core    unlimited
+    ```
+
+    Use `*` to enable the core dump size to unlimited.
+
+-   Set the limit of core file size to `UNLIMITED`:
+
+    ```text
+    ulimit -c unlimited
+
+    ulimit -c
+    unlimited
+    ```
+
+-   To set a core limit for the services, add the following setting in `/usr/lib/systemd/system/edb-as-16.service`:
+
+    ```text
+    [Service]
+    LimitCore=Infinity
+    ```
+
+-   Reload the service configuration:
+
+    ```text
+    systemctl daemon-reload
+    ```
+
+-   Modify the global default limit using systemd. Add the following setting in `/etc/systemd/system.conf`:
+
+    ```
+    DefaultLimitCORE=Infinity
+    ```
+
+-   Restart systemd:
+
+    ```text
+    systemctl daemon-reexec
+    ```
+
+-   Stop and then start EDB Postgres Advanced Server:
+
+   ```text
+   systemctl stop edb-as-16
+   systemctl start edb-as-16
+   ```
+
+-   Now, the core dumps are enabled. Install the gdb tool and debug packages:   
+
+    ```text
+    yum install gdb
+    debuginfo-install edb-as16 edb-as16-server-contrib edb-as16-server edb-as16-libs
+    ```
+
+-   Replace the path to a core dump file. Then, get a backtrace using the `bt` command to analyze output:
+
+    ```text
+    gdb /usr/edb/as16/bin /var/coredumps/core-edb-postgres-65499
+    (gdb) bt full
+    ```
+
+## Enabling core dumps on a Debian or Ubuntu host
+
+On Debian 11 or Ubuntu 20 and 22, core file creation is disabled by default. To enable the core file generation:
+
+-   Identify the system's current limit using the `ulimit -c` or `ulimit -a` command. `0` indicates that core file generation is disabled.
+
+    ```text
+    # ulimit -c
+    0
+
+    # ulimit -a
+    core file size          (blocks, -c) 0
+    data seg size           (kbytes, -d) unlimited
+    scheduling priority             (-e) 0
+    file size               (blocks, -f) unlimited
+    pending signals                 (-i) 7617
+    max locked memory       (kbytes, -l) 65536
+    max memory size         (kbytes, -m) unlimited
+    open files                      (-n) 1024
+    pipe size            (512 bytes, -p) 8
+    POSIX message queues     (bytes, -q) 819200
+    real-time priority              (-r) 0
+    stack size              (kbytes, -s) 8192
+    cpu time               (seconds, -t) unlimited
+    max user processes              (-u) 7617
+    virtual memory          (kbytes, -v) unlimited
+    file locks                      (-x) unlimited
+    ```
+
+-   Create a new directory to store the core dumps, and modify `kernel.core_pattern` to store the dumps in a specified directory:
+
+    ```text
+    mkdir -p /var/coredumps
+    chmod a+w /var/coredumps
+
+    sysctl kernel.core_pattern=/var/coredumps/core-%e-%p
+    kernel.core_pattern = /var/coredumps/core-%e-%p
+    ```
+
+-   Persist the `kernel.core_pattern` setting across reboots:
+
+    ```text
+    echo 'kernel.core_pattern=/var/coredumps/core-%e-%p' >> /etc/sysctl.conf
+    ```
+
+-   To allow a user to create core files, enable core dumps in `/etc/security/limits.conf`. Each line describes a limit for a user in the following form.
+
+    ```text
+    <domain>  <type>  <item>  <value>
+       *       soft    core    unlimited
+    ```
+
+    Use `*` to enable the core dump size to unlimited.
+
+-   Set the limit of core file size to `UNLIMITED`:
+
+    ```text
+    ulimit -c unlimited
+
+    ulimit -c
+    unlimited
+    ```
+
+-   To set a core limit for the services, add the following setting in `/lib/systemd/system/edb-as@.service`:
+
+    ```text
+    [Service]
+    LimitCore=Infinity
+    ```
+
+-   Reload the service configuration:
+
+    ```text
+    systemctl daemon-reload
+    ```
+
+-   Modify the global default limit using systemd. Add the following setting in `/etc/systemd/system.conf`:
+
+    ```
+    DefaultLimitCORE=Infinity
+    ```
+
+-   Restart systemd:
+
+    ```text
+    systemctl daemon-reexec
+    ```
+
+-   Stop and then start EDB Postgres Advanced Server:
+
+   ```text
+   systemctl stop edb-as@16-main.service
+   systemctl start edb-as@16-main.service
+   ```
+
+-   Now, the core dumps are enabled. Install the gdb tool and debug symbols:   
+
+    ```text
+    apt-get install gdb
+    apt-get install edb-as16 edb-as-contrib edb-as16-server edb-debugger-dbgsym
+    ```
+    
+-   Replace the path to a core dump file. Then get a backtrace using the `bt` command to analyze output:
+
+    ```text
+    gdb /usr/lib/edb-as/16/bin /var/coredumps/core-edb-postgres-21638
+    (gdb) bt full
+    ```
+
+!!! Note
+    -   The debug info packages name on a Debian or Ubuntu host can vary and include a `-dbgsym` or `-dbg` suffix. For more information about setting `sources.list` and installing the debug info packages, see the [Debian wiki](https://wiki.debian.org/HowToGetABacktrace) or the [Ubuntu wiki](https://wiki.ubuntu.com/Debug%20Symbol%20Packages).
+    -   The core files can be huge, depending on the memory usage. Enabling the core dumps on a system might fill up its mass storage over time.
+    
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/index.mdx b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/index.mdx
new file mode 100644
index 00000000000..34ffbbbcef2
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/index.mdx
@@ -0,0 +1,17 @@
+---
+title: "Linux installation troubleshooting"
+navTitle: "On Linux"
+description: "Provides details about troubleshooting installations and enabling core dumps on the Linux platforms"
+redirects:
+  - /epas/latest/troubleshooting/troubleshooting_linux/
+  - /epas/latest/troubleshooting/linux_troubleshooting/ #generated for docs/epas/reorg-role-use-case-mode
+
+navigation:
+  - installation_troubleshooting_linux
+  - enabling_core_dump
+---
+
+On your Linux platform, you can:
+
+- Troubleshoot installations.
+- Enable core dumps.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
new file mode 100644
index 00000000000..c927aa8a210
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux.mdx
@@ -0,0 +1,44 @@
+---
+title: "Installation troubleshooting"
+redirects:
+  - /epas/latest/epas_inst_linux/05_installing_troubleshooting/
+  - /epas/latest/troubleshooting/troubleshooting_linux/installation_troubleshooting_linux/
+  - /epas/latest/troubleshooting/linux_troubleshooting/installation_troubleshooting_linux/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+### Difficulty displaying Java-based applications
+
+If you have difficulty displaying Java-based server features (controls or text not displaying correctly or blank windows), upgrading to the latest `libxcb-xlib` libraries corrects the problem on most distributions. See the [Java bug database](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373) for other possible workarounds.
+
+### The installation fails to complete due to existing data directory contents
+
+If an installation fails to complete due to existing content in the data directory, the server writes an error message to the server logs:
+
+`A data directory is neither empty, or a recognisable data directory.`
+
+If you encounter a similar message, confirm that the data directory is empty. The presence of files, including the system-generated `lost+found` folder, prevents the installation from completing. Either remove the files from the data directory, or specify a different location for the data directory before invoking the installer again to complete the installation.
+
+### Difficulty installing the EPEL release package
+
+If you have difficulty installing the EPEL release package, you can use one of the following commands to install the `epel-release` package on RHEL/Rocky Linux/AlmaLinux 8.x | 9.x:
+
+```text
+dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
+
+dnf -y install https://dl.fedoraproject.org/pub/epel/epel-release-latest-9.noarch.rpm
+```
+
+You might need to enable the `[extras]` repository definition in the `CentOS-Base.repo` file, located in `/etc/yum.repos.d`. If yum can't access a repository that contains `epel-release`, an error message appears:
+
+```text
+No package epel available.
+Error: Nothing to do
+```
+
+If you receive this error, you can download the EPEL rpm package and install it manually. To manually install EPEL, download the rpm package, assume superuser privileges, navigate into the directory that contains the package, and use this command:
+
+```text
+yum -y install epel-release
+
+dnf -y install epel-release
+```
diff --git a/product_docs/docs/epas/16/installing/troubleshooting/windows_troubleshooting.mdx b/product_docs/docs/epas/16/installing/troubleshooting/windows_troubleshooting.mdx
new file mode 100644
index 00000000000..2eaa81a9ba2
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/troubleshooting/windows_troubleshooting.mdx
@@ -0,0 +1,29 @@
+---
+title: "Windows installation troubleshooting"
+navTitle: "On Windows"
+description: "Provides details about troubleshooting installations on Windows platforms"
+redirects:
+  - /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/04_installation_troubleshooting/
+  - /epas/latest/troubleshooting/troubleshooting_windows/
+  - /epas/latest/troubleshooting/windows_troubleshooting/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+### Difficulty displaying Java-based applications
+
+If you have difficulty displaying Java-based server features (controls or text not displaying correctly or blank windows), upgrading to the latest `libxcb-xlib` libraries corrects the problem on most distributions. See the [Java bug database](http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6532373) for other possible workarounds.
+
+### - -mode unattended authentication errors
+
+Authentication errors from component modules during unattended installations might indicate that the specified values of `--servicepassword` or `--superpassword` are incorrect.
+
+### Errors during an EDB Postgres Advanced Server installation
+
+If you encounter an error during the installation process, exit the installation, and ensure that your version of Windows is up to date. After applying any outstanding operating system updates, invoke the EDB Postgres Advanced Server installer again.
+
+### The installation fails to complete due to existing data directory contents
+
+If an installation fails to complete due to existing content in the data directory, the server writes an error message to the server logs:
+
+`A data directory is neither empty, or a recognisable data directory`.
+
+If you encounter a similar message, confirm that the data directory is empty. The presence of files, including the system-generated `lost+found` folder, prevents the installation from completing. Either remove the files from the data directory, or specify a different location for the data directory before invoking the installer again to complete the installation.
diff --git a/product_docs/docs/epas/16/installing/uninstalling/index.mdx b/product_docs/docs/epas/16/installing/uninstalling/index.mdx
new file mode 100644
index 00000000000..ba7158c572f
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/uninstalling/index.mdx
@@ -0,0 +1,10 @@
+---
+title: "Uninstalling EDB Postgres Advanced Server"
+navTitle: "Uninstalling"
+indexCards: simple
+redirects:
+  - /epas/latest/uninstalling_epas/
+  - /epas/latest/uninstalling/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+You can uninstall the EDB Postgres Advanced Server on the platform where it's installed.
diff --git a/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx b/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
new file mode 100644
index 00000000000..b070008d1bc
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/uninstalling/linux_uninstall.mdx
@@ -0,0 +1,62 @@
+---
+title: "Uninstalling EDB Postgres Advanced Server on Linux"
+navTitle: "On Linux"
+description: "Describes how to uninstall EDB Postgres Advanced Server on Linux"
+redirects:
+  - /epas/latest/epas_inst_linux/08_uninstalling_advanced_server/
+  - /epas/latest/uninstalling_epas/on_linux/
+  - /epas/latest/uninstalling/linux_uninstall/ #generated for docs/epas/reorg-role-use-case-mode
+legacyRedirects:
+  - /edb-docs/d/edb-postgres-advanced-server/installation-getting-started/installation-guide/9.6/EDB_Postgres_Advanced_Server_Installation_Guide.1.77.html
+---
+
+!!! Note
+    After uninstalling EDB Postgres Advanced Server, the cluster data files remain intact, and the service user persists. You can manually remove the cluster `data` and service user from the system.
+
+## Uninstalling on RHEL/AlmaLinux/Rocky Linux
+
+You can use  `dnf` command to remove installed packages. Removing a package doesn't damage the EDB Postgres Advanced Server `data` directory.
+
+Include the `-e` option when invoking the `rpm` command to remove an installed package:
+
+```text
+rpm -e <package_name>
+```
+
+Where `package_name` is the name of the package that you want to remove.
+
+You can use the `dnf remove` command to remove a package installed by dnf. To remove a package, at the command line, assume superuser privileges, and enter:
+
+    ```text
+    dnf remove <package_name>
+    ```
+
+Where `package_name` is the name of the package that you want to remove.
+
+yum and rpm don't remove a package that's required by another package. If you attempt to remove a package that satisfies a package dependency, yum or rpm provides a warning.
+
+!!! Note
+    In RHEL or Rocky Linux or AlmaLinux 8 or 9, removing a package also removes all its dependencies that aren't required by other packages. To override this default behavior of RHEL or Rocky Linux or AlmaLinux 8 or 9, disable the `clean_requirements_on_remove` parameter in the `/etc/yum.conf` file.
+
+To uninstall EDB Postgres Advanced Server and its dependent packages, enter:
+
+```text
+dnf remove edb-as<xx>-server*
+```
+
+Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+
+## Uninstalling on Debian or Ubuntu
+
+-   To uninstall EDB Postgres Advanced Server, invoke the following command. The configuration files and data directory remains intact.
+
+    ```text
+    apt-get remove edb-as<xx>-server*
+    ```
+
+-   To uninstall EDB Postgres Advanced Server, configuration files, and data directory, invoke the following command:
+
+    ```text
+    apt-get purge edb-as<xx>-server*
+    ```
diff --git a/product_docs/docs/epas/16/installing/uninstalling/windows_uninstall.mdx b/product_docs/docs/epas/16/installing/uninstalling/windows_uninstall.mdx
new file mode 100644
index 00000000000..15f862262f6
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/uninstalling/windows_uninstall.mdx
@@ -0,0 +1,41 @@
+---
+title: "Uninstalling EDB Postgres Advanced Server on Windows"
+navTitle: "On Windows"
+description: "Describes how to uninstall EDB Postgres Advanced Server on Windows"
+redirects:
+  - /epas/latest/epas_inst_windows/07_uninstalling_advanced_server/
+  - /epas/latest/uninstalling_epas/on_windows/
+  - /epas/latest/uninstalling/windows_uninstall/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+!!! Note 
+    After uninstalling EDB Postgres Advanced Server, the cluster data files remain intact, and the service user persists. You can manually remove the cluster data and service user from the system.
+
+## Using EDB Postgres Advanced Server uninstallers at the command line
+
+The EDB Postgres Advanced Server interactive installer creates an uninstaller that you can use to remove EDB Postgres Advanced Server or components that reside on a Windows host. The uninstaller is created in `C:\Program Files\edb\as<xx>`. 
+
+1. Assume superuser privileges and, in the directory that contains the uninstaller, enter:
+
+    ```text
+    uninstall-edb-as<xx>-server.exe
+    ```
+    Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+    The uninstaller opens.
+
+    ![The EDB Postgres Advanced Server uninstaller](../../images/advanced_server_uninstaller.png)
+
+1.  By default, the installer removes the entire application. If you instead want to select components to remove, select **Individual components**. A dialog box prompts you to select the components you want to remove. Make your selections.
+
+1. Select **Next**.
+
+    If you selected components to remove that depend on EDB Postgres Advanced Server, those components are removed first. 
+
+    ![Acknowledge that dependent components are removed first](../../images/acknowledging_components_removed.png)
+
+1.  To continue, select **Yes**.
+
+    Progress bars are displayed as the software is removed. A confirmation reports when the uninstall process is complete.
+
+    ![The uninstall is complete](../../images/uninstallation_complete.png)
diff --git a/product_docs/docs/epas/16/installing/windows/index.mdx b/product_docs/docs/epas/16/installing/windows/index.mdx
new file mode 100644
index 00000000000..98e01027f54
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/index.mdx
@@ -0,0 +1,16 @@
+---
+title: "EDB Postgres Advanced Server installation for Windows"
+navTitle: "On Windows"
+redirects:
+- /epas/latest/epas_inst_windows/05_managing_an_advanced_server_installation/
+- /epas/latest/epas_inst_windows/
+navigation:
+- installing_advanced_server_with_the_interactive_installer
+- managing_an_advanced_server_installation
+indexCards: simple
+---
+
+With Windows, you can:
+
+-   Install EDB Postgres Advanced Server using [graphical installation options](installing_advanced_server_with_the_interactive_installer) available with the interactive wizard on Windows.
+-   [Manage an EDB Postgres Advanced Server installation](managing_an_advanced_server_installation).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/index.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/index.mdx
new file mode 100644
index 00000000000..b28d79368ab
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/index.mdx
@@ -0,0 +1,30 @@
+---
+title: "Installing EDB Postgres Advanced Server with the interactive installer"
+navTitle: "Using the installer"
+indexCards: simple
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/
+navigation:
+
+- performing_a_graphical_installation_on_windows
+- invoking_the_graphical_installer_from_the_command_line
+- using_stackbuilder_plus
+---
+
+<div id="installing_advanced_server_with_the_interactive_installer" class="registered_link"></div>
+
+You can use the EDB Postgres Advanced Server interactive installer to install EDB Postgres Advanced Server on Windows. The interactive installer is available from [Downloads page](https://www.enterprisedb.com/advanced-downloads) on the EDB website.
+
+You can invoke the graphical installer in different installation modes to perform an EDB Postgres Advanced Server installation.
+
+During the installation, the graphical installer copies a number of temporary files to the location specified by the `TEMP` environment variable. You can optionally specify an alternative location for the temporary files by modifying the value of the `TEMP` environment variable at the command line:
+
+```text
+SET TEMP=<temp_file_location>
+```
+
+Where `<temp_file_location>` specifies the alternative location for the temporary files and must match the permissions with the `TEMP` environment variable.
+
+!!! Note
+    If you're invoking the installer to perform a system upgrade, the installer preserves the configuration options specified during the previous installation.
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/index.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/index.mdx
new file mode 100644
index 00000000000..a3b99380add
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/index.mdx
@@ -0,0 +1,29 @@
+---
+title: "Invoking the graphical installer from the command line"
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/
+navigation:
+
+- performing_an_unattended_installation
+- performing_an_installation_with_limited_privileges
+- reference_command_line_options
+---
+
+<div id="invoking_the_graphical_installer_from_the_command_line" class="registered_link"></div>
+
+The command line options of the EDB Postgres Advanced Server installer offer functionality for Windows systems that reside in situations where a graphical installation might not work because of limited resources or privileges. You can:
+
+-   Include the `--mode unattended` option when invoking the installer to perform an installation without user input.
+-   Invoke the installer with the `--extract-only` option to perform a minimal installation when you don’t hold the privileges required to perform a complete installation.
+
+Not all command line options are suitable for all situations. For a complete reference guide to the command line options, see [Reference - Command Line Options](reference_command_line_options/#reference_command_line_options).
+
+!!! Note
+    If you're invoking the installer from the command line to perform a system upgrade, the installer ignores command line options and preserves the configuration of the previous installation.
+
+<div class="toctree" maxdepth="3">
+
+performing_an_unattended_installation performing_an_installation_with_limited_privileges reference_command_line_options
+
+</div>
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_installation_with_limited_privileges.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_installation_with_limited_privileges.mdx
new file mode 100644
index 00000000000..c7dd832991d
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_installation_with_limited_privileges.mdx
@@ -0,0 +1,64 @@
+---
+title: "Performing an installation with limited privileges"
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/02_performing_an_installation_with_limited_privileges/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_installation_with_limited_privileges/
+---
+
+<div id="performing_an_installation_with_limited_privileges" class="registered_link"></div>
+
+To perform an abbreviated installation of EDB Postgres Advanced Server without access to administrative privileges, invoke the installer from the command line and include the `--extract-only` option. The `--extract-only` option extracts the binary files in an unaltered form, allowing you to experiment with a minimal installation of EDB Postgres Advanced Server.
+
+If you invoke the installer with the `--extract-only` options, you can either manually create a cluster and start the service, or run the installation script. To manually create the cluster, you must:
+
+-   Use initdb to initialize the cluster
+-   Configure the cluster
+-   Use pg_ctl to start the service
+
+For more information about initdb and pg_ctl, see the PostgreSQL core documentation for [initdb](https://www.postgresql.org/docs/current/static/app-initdb.html) and [pg_ctl](https://www.postgresql.org/docs/current/static/app-pg-ctl.html).
+
+If you include the `--extract-only` option, the installer steps through a shortened form of the setup wizard. During the brief installation process, the installer generates an installation script that can be later used to complete a more complete installation. You must have administrative privileges to invoke the installation script.
+
+The installation script:
+
+-   Initializes the database cluster if the cluster is empty.
+-   Configures the server to start at boot time.
+-   Establishes initial values for Dynatune (dynamic tuning) variables.
+
+The scripted EDB Postgres Advanced Server installation doesn't create menu shortcuts or provide access to EDB Postgres StackBuilder Plus, and it doesn't make changes to registry files.
+
+To perform a limited installation and generate an installation script: 
+
+1. Download and unpack the EDB Postgres Advanced Server installer. 
+
+1. Navigate to the directory that contains the installer, and invoke the installer:
+
+  ```text
+  edb-as<xx>-server-xx.x.x-x-windows.exe --extract-only yes
+  ```
+
+  Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+  A dialog box opens, prompting you to choose an installation language. 
+    
+1. Select a language for the installation, and select **OK**. The setup wizard opens.
+
+    ![The Welcome window](../../../../images/advanced_server_installer_welcome.png)
+
+1. Select **Next**.
+
+    ![Specify an installation directory](../../../../images/installation_directory.png)
+
+    On Windows, the default EDB Postgres Advanced Server installation directory is `C:\Program Files\edb\as15`.
+
+1. Accept the default installation location and select **Next** to continue to the Ready to Install window. Alternatively,you can select the file browser to choose a different installation directory.
+
+    ![The Setup wizard is ready to install EDB Postgres Advanced Server](../../../../images/ready_to_install.png)
+
+1. To proceed with the EDB Postgres Advanced Server installation, select **Next**. 
+
+    During the installation, progress bars and popups mark the installation progress. The installer notifies you when the installation is complete.
+
+    ![The EDB Postgres Advanced Server installation is complete](../../../../images/advanced_server_installation_completion.png)
+
+After completing the minimal installation, you can execute a script to initialize a cluster and start the service. The script is by default located in `C:\Program Files\edb`.
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_unattended_installation.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_unattended_installation.mdx
new file mode 100644
index 00000000000..e428ceca262
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_unattended_installation.mdx
@@ -0,0 +1,31 @@
+---
+title: "Performing an unattended installation"
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/01_performing_an_unattended_installation/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/performing_an_unattended_installation/
+---
+
+<div id="performing_an_unattended_installation" class="registered_link"></div>
+
+To specify that the installer should run without user interaction, include the `--mode unattended` command line option. In unattended mode, the installer uses one of the following sources for configuration parameters:
+
+-   Command line options (specified when invoking the installer)
+-   Parameters specified in an option file
+-   EDB Postgres Advanced Server installation defaults
+
+You can embed the non-interactive EDB Postgres Advanced Server installer within another application installer; during the installation process, a progress bar allows the user to view the progression of the installation.
+
+You must have administrative privileges to install EDB Postgres Advanced Server using the `--mode unattended` option. If you are using the `--mode unattended` option to install EDB Postgres Advanced Server with a client, the calling client must be invoked with superuser or administrative privileges.
+
+To start the installer in unattended mode, navigate to the directory that contains the executable file, and enter:
+
+```text
+edb-as<xx>-server-xx.x.x-x-windows-x64.exe --mode unattended --superpassword
+database_superuser_password --servicepassword system_password
+```
+
+Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+When invoking the installer, include the `--servicepassword` option to specify an operating system password for the user installing EDB Postgres Advanced Server.
+
+Use the `--superpassword` option to specify a password that conforms to the password security policies defined on the host; enforced password policies on your system may not accept the default password `(enterprisedb)`.
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx
new file mode 100644
index 00000000000..0ffd82a3468
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options.mdx
@@ -0,0 +1,172 @@
+---
+title: "Installation command line options"
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/02_invoking_the_graphical_installer_from_the_command_line/03_reference_command_line_options/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/invoking_the_graphical_installer_from_the_command_line/reference_command_line_options/
+---
+
+<div id="reference_command_line_options" class="registered_link"></div>
+
+When invoking the EDB Postgres Advanced Server installer, you can optionally include the following parameters for an EDB Postgres Advanced Server installation on the command line or in a configuration file.
+
+`--create_samples { yes | no }`
+
+Specifies whether to create the sample tables and procedures for the database dialect specified with the `--databasemode` parameter. The default is `yes`.
+
+`--databasemode { oracle | postgresql }`
+
+Specifies a database dialect. The default is `oracle`.
+
+`--datadir data_directory`
+
+Specifies a location for the cluster's data directory. `data_directory` is the name of the directory. Include the complete path to the desired directory.
+
+`--debuglevel { 0 | 1 | 2 | 3 | 4 }`
+
+Sets the level of detail written to the `debug_log` file (see `--debugtrace`). Higher values produce more detail in a longer trace file. The default is `2`.
+
+`--debugtrace debug_log`
+
+Helps with troubleshooting installation problems. `debug_log` is the name of the file that contains troubleshooting details.
+
+`--disable-components component_list`
+
+Specifies a list of EDB Postgres Advanced Server components to exclude from the installation. By default, `component_list` contains '' (the empty string). `component_list` is a comma-separated list containing one or more of the following components:
+
+- `dbserver` &mdash; EDB Postgres Advanced Server.
+
+- `pgadmin4` &mdash; The EDB Postgres pgAdmin 4 provides a powerful graphical interface for database management and monitoring.
+
+`--enable_acledit { 1 | 0 }`
+
+The `--enable_acledit 1` option grants permission to the user specified by the `--serviceaccount` option to access the EDB Postgres Advanced Server binaries and `data` directory. By default, this option is disabled if `--enable_acledit 0` is specified or if the `--enable_acledit` option is completely omitted.
+
+!!! Note
+    Specifying this option is valid only when installing on Windows. Specify the `--enable_acledit 1` option when a discretionary access control list (DACL) needs to be set for allowing access to objects on which to install EDB Postgres Advanced Server. For information on a DACL, see [DACLs and ACEs](https://msdn.microsoft.com/en-us/library/windows/desktop/aa446597(v=vs.85).aspx) in the Microsoft documentation.
+
+To perform future operations, such as upgrading EDB Postgres Advanced Server, the service account user specified by the `--serviceaccount` option must have access to the `data` directory. The `--enable_acledit 1` option provides access to the `data` directory by the service account user.
+
+`--enable-components component_list`
+
+Although this option is listed when you run the installer with the `--help` option, the `--enable-components` parameter has no effect on the components installed. All components are installed regardless of this setting. To install only specific selected components, use the `--disable-components` parameter to list the components you don't want to install.
+
+`--extract-only { yes | no }`
+
+Include the `--extract-only` parameter to extract the EDB Postgres Advanced Server binaries without performing a complete installation. Superuser privileges aren't required for the `--extract-only` option. The default value is `no`.
+
+`--help`
+
+Displays a list of the optional parameters.
+
+`--installer-language { en | ja | zh_CN | zh_TW | ko }`
+
+Specifies an installation language for EDB Postgres Advanced Server.
+
+- `en` specifies English. This is the default.
+
+- `ja` specifies Japanese
+
+- `zh_CN` specifies Chinese Simplified.
+
+- `zh_TW` specifies Traditional Chinese.
+
+- `ko` specifies Korean.
+
+`--install_runtimes { yes | no }`
+
+Specifies whether to install the Microsoft Visual C++ runtime libraries. The default is `yes`.
+
+`--locale locale`
+
+Specifies the locale for the EDB Postgres Advanced Server cluster. By default, the installer uses the locale detected by `initdb`.
+
+`--mode { unattended }`
+
+Specifies to perform an installation that requires no user input during the installation process.
+
+`--optionfile config_file`
+
+Specifies the name of a file that contains the installation configuration parameters. `config_file` must specify the complete path to the configuration parameter file.
+
+`--prefix installation_dir/as16`
+
+Specifies an installation directory for EDB Postgres Advanced Server. The installer appends a version-specific subdirectory (that is, `as16`) to the specified directory. The default installation directory is:
+
+```text
+C:\Program Files\edb\as16
+```
+
+`--serverport port_number`
+
+Specifies a listener port number for EDB Postgres Advanced Server.
+
+If you're installing EDB Postgres Advanced Server in unattended mode and don't specify a value using the `--serverport` parameter, the installer uses port `5444` or the first available port after port `5444` as the default listener port.
+
+`--server_utilization {33 | 66 | 100}`
+
+Specifies a value for the `edb_dynatune` configuration parameter. The `edb_dynatune` configuration parameter determines how EDB Postgres Advanced Server allocates system resources.
+
+-   A value of `33` is appropriate for a system used for development. A low value dedicates the least amount of the host machine’s resources to the database server.
+-   A value of `66` is appropriate for an application server with a fixed number of applications. A midrange value dedicates a moderate amount of system resources to the database server. This is the default value.
+-   A value of `100` is appropriate for a host machine that's dedicated to running EDB Postgres Advanced Server. A high value dedicates most of the system resources to the database server.
+
+When the installation is complete, you can adjust the value of `edb_dynatune` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for the changes to take effect.
+
+`--serviceaccount user_account_name`
+
+Specifies the name of the user account that owns the server process.
+
+-   If `--databasemode` is set to `oracle` (the default), the default value of `--serviceaccount` is `enterprisedb`.
+-   If `--databasemode` is `postgresql`, the default value of `--serviceaccount` is `postgres`.
+
+For security reasons, the `--serviceaccount` parameter must specify the name of an account that doesn't hold administrator privileges.
+
+If you specify both the `--serviceaccount` option and the `--enable_acledit 1` option when invoking the installer, the database service and pgAgent uses the same service account. They therefore have the permissions required to access the EDB Postgres Advanced Server binaries and `data` directory.
+
+!!! Note
+    If you don't include the `--serviceaccount` option when invoking the installer, the NetworkService account owns the database service, and the pgAgent service is owned by either enterprisedb or postgres, depending on the installation mode.
+
+`--servicename service_name`
+
+Specifies the name of the EDB Postgres Advanced Server service. The default is `edb-as-16`.
+
+`--servicepassword user_password`
+
+Specifies the OS system password. If unspecified, the value of `--servicepassword` defaults to the value of `--superpassword`.
+
+`--superaccount super_user_name`
+
+Specifies the user name of the database superuser.
+
+-   If `--databasemode` is set to `oracle` (the default), the default value of `--superaccount` is `enterprisedb`.
+-   If `--databasemode` is set to `postgresql`, the default value of `--superaccount` is `postgres`.
+
+`--superpassword superuser_password`
+
+Specifies the database superuser password. If you're installing in non-interactive mode, `--superpassword` defaults to `enterprisedb`.
+
+`--unattendedmodeui { none | minimal | minimalWithDialogs }`
+
+Specifies installer behavior during an unattended installation.
+
+Include `--unattendedmodeui none` if you don't want to display progress bars during the EDB Postgres Advanced Server installation.
+
+Include `--unattendedmodeui minimal` to display progress bars during the installation process. This is the default behavior.
+
+Include `--unattendedmodeui minimalWithDialogs` to display progress bars and report any errors encountered during the installation process in additional dialog boxes.
+
+`--version`
+
+Retrieves version information about the installer.
+
+`--workload_profile {oltp | mixed | reporting}`
+
+Specifies an initial value for the `edb_dynatune_profile` configuration parameter. `edb_dynatune_profile` controls aspects of performance-tuning based on the type of work that the server performs.
+
+-   Specify `oltp` if the EDB Postgres Advanced Server installation is used to support heavy online transaction processing workloads. This is the default value.
+-   Specify `mixed` if EDB Postgres Advanced Server provides a mix of transaction processing and data reporting.
+-   Specify `reporting` if EDB Postgres Advanced Server is used for heavy data reporting.
+
+After the installation is complete, you can adjust the value of `edb_dynatune_profile` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for the changes to take effect.
+
+For more information about `edb_dynatune` and other performance-related topics, see [Managing performance](../../../../managing_performance/).
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx
new file mode 100644
index 00000000000..f4243844b64
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows.mdx
@@ -0,0 +1,200 @@
+---
+title: "Performing a graphical installation on Windows"
+redirects:
+- /epas/latest/epas_inst_windows/03_installing_advanced_server_with_the_interactive_installer/01_performing_a_graphical_installation_on_windows/
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/performing_a_graphical_installation_on_windows/
+---
+
+<div id="performing_a_graphical_installation_on_windows" class="registered_link"></div>
+
+A graphical installation is a quick and easy way to install EDB Postgres Advanced Server on a Windows system. Use the wizard's screens to specify information about your system and system usage. After you complete the screens, the installer performs an installation based on the selections made during the setup process.
+
+1. Assume administrator privileges, and double-click the `edb-as<xx>-server-xx.x.x-x-windows-x64` executable file, where `<xx>` is the EDB Postgres Advanced Server version number.
+
+    !!! Note
+        To install EDB Postgres Advanced Server on some versions of Windows, you might need to right-click the file and select **Run as Administrator** from the context menu to invoke the installer with administrator privileges.
+
+    ![The EDB Postgres Advanced Server installer Welcome window](../../../images/advanced_server_installer_welcome.png)
+
+1. Select **Next**. The EnterpriseDB license agreement opens.
+
+    ![The EnterpriseDB License Agreement](../../../images/enterprisedb_license_agreement.png)
+
+1. Carefully review the license agreement before selecting the appropriate option. Select **Next**. 
+
+    The Installation Directory window opens.
+
+    ![The Installation Directory window](../../../images/installation_directory.png)
+
+    By default, the EDB Postgres Advanced Server installation directory is:
+
+    ```text
+    C:\Program Files\edb\as<xx>
+    ```
+
+    Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+1.  Accept the default installation location and select **Next**. Alternatively, select the file browser icon to open the Browse For Folder dialog box to choose a different installation directory.
+
+    !!! Note
+        Don't store the `data` directory of a production database on an NFS file system.
+
+    The Select Components window opens, which contains a list of optional components that you can install with the EDB Postgres Advanced Server setup wizard. You can omit a component from the EDB Postgres Advanced Server installation by clearing the check box next to its name.
+    
+    ![The Select Components window](../../../images/select_components.png)
+
+    The setup wizard can install the following components while installing EDB Postgres Advanced Server:
+
+    -  Select **EDB Postgres Advanced Server** to install EDB Postgres Advanced Server.
+
+    -  Select **StackBuilder Plus** to install that utility. The StackBuilder Plus utility is a graphical tool that can update installed products or download and add supporting modules (and the resulting dependencies) after your EDB Postgres Advanced Server setup and installation completes. See [Using StackBuilder Plus](using_stackbuilder_plus/) for more information.
+
+    - The **Command Line Tools** option installs command line tools and supporting client libraries including these and others:
+
+        -   libpq
+        -   psql
+        -   EDB\*Loader
+        -   ecpgPlus
+        -   pg_basebackup, pg_dump, and pg_restore 
+        -   pg_bench
+
+    !!! Note
+        The command line tools are required if you're installing EDB Postgres Advanced Server or pgAdmin 4.
+
+1. After selecting the components you want to install, select **Next**. The Additional Directories window opens.
+
+    ![The Additional Directories window](../../../images/additional_directories.png)
+
+    By default, the EDB Postgres Advanced Server data files are saved to:
+
+  ```text
+  C:\Program Files\edb<xx>\data
+  ```
+  Where `<xx>` is the EDB Postgres Advanced Server version number.
+
+  The default location of the EDB Postgres Advanced Server `Write-Ahead Log (WAL) Directory` is:
+
+  ```text
+  C:\Program Files\edb\as<xx>\data\pg_wal
+  ```
+    
+  EDB Postgres Advanced Server uses write-ahead logs to promote transaction safety and speed transaction processing. When you make a change to a table, the change is stored in shared memory, and a record of the change is written to the write-ahead log. When you perform a COMMIT, EDB Postgres Advanced Server writes contents of the write-ahead log to disk.
+
+1. Accept the default file locations, or use the file browser to select a different location. Select **Next**. 
+
+    The EDB Postgres Advanced Server Dialect window opens. The server dialect specifies the compatibility features supported by EDB Postgres Advanced Server.
+
+    ![The EDB Postgres Advanced Server Dialect window](../../../images/advanced_server_dialect.png)
+
+1. From the list, select a server dialect. 
+
+    By default, EDB Postgres Advanced Server installs in Compatible with Oracle mode. You can choose between Compatible with Oracle and Compatible with PostgreSQL installation modes.
+
+    If you select **Compatible with Oracle**, the installation includes the following features:
+
+    -   Data dictionary views that are compatible with Oracle databases.
+    -   Oracle data type conversions.
+    -   Date values displayed in a format compatible with Oracle syntax.
+    -   Support for Oracle-styled concatenation rules. (If you concatenate a string value with a `NULL` value, the returned value is the value of the string.)
+    -   Schemas (`dbo` and `sys`) compatible with Oracle databases added to the `SEARCH_PATH`.
+    -   Support for the following Oracle built-in packages.
+
+    | Package          | Functionality compatible with Oracle databases                                                                                                                               |
+    | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+    | `dbms_alert`     | Provides the capability to register for, send, and receive alerts.                                                                                                           |
+    | `dbms_job`       | Provides the capability for creating, scheduling, and managing jobs.                                                                                                  |
+    | `dbms_lob`       | Provides the capability to manage on large objects.                                                                                                                          |
+    | `dbms_output`    | Provides the capability to send messages to a message buffer or get messages from the message buffer.                                                                       |
+    | `dbms_pipe`      | Provides the capability to send messages through a pipe within or between sessions connected to the same database cluster.                                                   |
+   | `dbms_rls`       | Enables the implementation of Virtual Private Database on certain EDB Postgres Advanced Server database objects.                                                                          |
+    | `dbms_sql`       | Provides an application interface to the EDB dynamic SQL functionality.                                                                                                      |
+    | `dbms_utility`   | Provides various utility programs.                                                                                                                                           |
+    | `dbms_aqadm`     | Provides supporting procedures for Advanced Queueing functionality.                                                                                                          |
+    | `dbms_aq`        | Provides message queueing and processing for EDB Postgres Advanced Server.                                                                                                                |
+    | `dbms_profiler`  | Collects and stores performance information about the PL/pgSQL and SPL statements that are executed during a performance profiling session.                                  |
+    | `dbms_random`    | Provides a number of methods to generate random values.                                                                                                                      |
+    | `dbms_redact`    | Enables redacting or masking of data that's returned by a query.                                                                                                        |
+    | `dbms_lock`      | Provides support for the `DBMS_LOCK.SLEEP` procedure.                                                                                                                        |
+    | `dbms_scheduler` | Provides a way to create and manage jobs, programs, and job schedules.                                                                                                       |
+    | `dbms_crypto`    | Provides functions and procedures to encrypt or decrypt RAW, BLOB, or CLOB data. You can also use `DBMS_CRYPTO` functions to generate cryptographically strong random values. |
+    | `dbms_mview`     | Provides a way to manage and refresh materialized views and their dependencies.                                                                                              |
+    | `dbms_session`   | Provides support for the `DBMS_SESSION.SET_ROLE` procedure.                                                                                                                  |
+    | `utl_encode`     | Provides a way to encode and decode data.                                                                                                                                    |
+    | `utl_http`       | Provides a way to use the HTTP or HTTPS protocol to retrieve information found at a URL.                                                                                    |
+    | `utl_file`       | Provides the capability to read from and write to files on the operating system’s file system.                                                                              |
+    | `utl_smtp`       | Provides the capability to send emails over the simple mail transfer protocol (SMTP).                                                                                       |
+    | `utl_mail`       | Provides the capability to manage email.                                                                                                                                    |
+    | `utl_url`        | Provides a way to escape illegal and reserved characters in a URL.                                                                                                      |
+    | `utl_raw`        | Provides a way to manipulate or retrieve the length of raw data types.                                                                                                       |
+
+    This isn't a comprehensive list of the compatibility features for Oracle included when EDB Postgres Advanced Server is installed in Compatible with Oracle mode. For more information, see the [Database compatibility for Oracle developers built-in package](../../../reference/oracle_compatibility_reference/epas_compat_bip_guide/).
+
+    If you choose to install in Compatible with Oracle mode, the EDB Postgres Advanced Server superuser name is enterprisedb.
+
+    If you select **Compatible with PostgreSQL**, EDB Postgres Advanced Server exhibits compatibility with PostgreSQL version 15. If you choose to install in Compatible with PostgreSQL mode, the default EDB Postgres Advanced Server superuser name is postgres. For detailed information about PostgreSQL functionality, see the [PostgreSQL website](http://www.postgresql.org).
+
+1. After specifying a configuration mode, select **Next**. The Password window opens.
+
+    ![The Password window](../../../images/password_window.png)
+
+    EDB Postgres Advanced Server uses the password specified on the Password window for the database superuser. The specified password must confirm to any security policies on the EDB Postgres Advanced Server host.
+
+1. After you enter a password in the **Password** field and confirm the password in the **Retype Password** field, select **Next**. The Additional Configuration window opens.
+
+    ![The Additional Configuration window](../../../images/additional_configuration.png)
+
+1. Use the fields on the Additional Configuration window to specify installation details:
+
+    -   Use the **Port** field to specify the port number for EDB Postgres Advanced Server to listen to for connection requests from client applications. The default is `5444`.
+    -   If the **Locale** field is set to **[Default locale]**, EDB Postgres Advanced Server uses the system locale as the working locale. From the list, select an alternative locale for EDB Postgres Advanced Server.
+    -   By default, the setup wizard installs corresponding sample data for the server dialect specified by the compatibility mode (Oracle or PostgreSQL). If you don't want to install sample data, clear the check box next to **Install sample tables and procedures**.
+
+1. After verifying the information on the Additional Configuration window, select **Next**. The Dynatune Dynamic Tuning: Server Utilization window opens.
+
+    ![The Dynatune Dynamic Tuning: Server Utilization window](../../../images/dynatune_dynamic_tuning_server_utilization.png)
+
+    The setup wizard helps with performance tuning by way of the Dynatune Dynamic Tuning feature. Dynatune functionality allows EDB Postgres Advanced Server to make optimal use of the system resources available on the host machine on which it's installed.
+
+1. Use the options on the Server Utilization window to set the initial value of the `edb_dynatune` configuration parameter. The `edb_dynatune` configuration parameter determines how EDB Postgres Advanced Server allocates system resources.
+
+    -   Select **Development** to set the value of `edb_dynatune` to `33`. A low value dedicates the least amount of the host machine’s resources to the database server. This seletion is a good choice for a development machine.
+    -   Select **General Purpose** to set the value of `edb_dynatune` to `66`. A mid-range value dedicates a moderate amount of system resources to the database server. This setting is good for an application server with a fixed number of applications running on the same host as EDB Postgres Advanced Server.
+    -   Select **Dedicated** to set the value of `edb_dynatune` to `100`. A high value dedicates most of the system resources to the database server. This setting is a good choice for a dedicated server host.
+
+    (After the installation is complete, you can adjust the value of `edb_dynatune` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for your changes to take effect.)
+
+    Select the appropriate setting for your system, and select **Next**. The Dynatune Dynamic Tuning: Workload Profile window opens.
+
+    ![The Dynatune Dynamic Tuning: Workload Profile window](../../../images/dynatune_dynamic_tuning_workload_profile.png)
+
+1. Use the options on the Workload Profile window to specify the initial value of the `edb_dynatune_profile` configuration parameter. The `edb_dynatune_profile` parameter controls performance-tuning aspects based on the type of work that the server performs.
+
+    -   Select **Transaction Processing (OLTP systems)** to specify an `edb_dynatune_profile` value of `oltp`. Recommended when EDB Postgres Advanced Server is supporting heavy online transaction processing.
+    -   Select **General Purpose (OLTP and reporting workloads)** to specify an `edb_dynatune_profile` value of `mixed`. Recommended for servers that provide a mix of transaction processing and data reporting.
+    -   Select **Reporting (Complex queries or OLAP workloads)** to specify an `edb_dynatune_profile` value of `reporting`. Recommended for database servers used for heavy data reporting.
+
+    After the installation is complete, you can adjust the value of `edb_dynatune_profile` by editing the `postgresql.conf` file, located in the `data` directory of your EDB Postgres Advanced Server installation. After editing the `postgresql.conf` file, you must restart the server for your changes to take effect.
+
+    For more information about edb_dynatune and other performance-related topics, see the [Dynatune](../../../managing_performance/using_dynatune).
+
+1.  Select **Next**.
+
+    By default, EDB Postgres Advanced Server is configured to start the service when the system boots. The Pre Installation Summary opens.
+
+    ![The Pre Installation Summary](../../../images/pre_installation_summary.png)
+
+    The Pre Installation Summary provides an overview of the options specified during the setup process. 
+    
+1. Review the options before selecting **Next**. (Use **Back** to navigate back through the screens and update any options.)
+
+    The Ready to Install window confirms that the installer has the information it needs about your configuration preferences to install EDB Postgres Advanced Server. 
+
+1. Select **Next**. As each supporting module is unpacked and installed, the module’s installation is confirmed with a progress bar.
+
+    Before the setup wizard completes the EDB Postgres Advanced Server installation, it prompts: `Launch StackBuilder Plus at exit?`
+
+    ![The Setup wizard offers to Launch StackBuilder Plus at exit](../../../images/setup_wizard.png)
+
+    EDB Postgres StackBuilder Plus is included with the installation of EDB Postgres Advanced Server and its core supporting components. StackBuilder Plus is a graphical tool that can update installed products or download and add supporting modules and the resulting dependencies after your EDB Postgres Advanced Server setup and installation completes. See [Using StackBuilder Plus](using_stackbuilder_plus/) for more information.
+
+1. To complete the EDB Postgres Advanced Server installation, clear the **StackBuilder Plus** check box and select **Finish**. Alternatively, accept the default and proceed to StackBuilder Plus.
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/setting_cluster_preferences.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/setting_cluster_preferences.mdx
new file mode 100644
index 00000000000..938e7d52e80
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/setting_cluster_preferences.mdx
@@ -0,0 +1,27 @@
+---
+title: "Setting cluster preferences during a graphical installation"
+navTitle: "Setting cluster preferences"
+---
+
+During an installation, the graphical installer invokes the PostgreSQL `initdb` utility to initialize a cluster. If you are using the graphical installer, you can use the `INITDBOPTS` environment variable to specify your `initdb` preferences. Before invoking the graphical installer, set the value of `INITDBOPTS` at the command line, specifying one or more cluster options. For example:
+
+```text
+SET INITDBOPTS= -k -E=UTF-8
+```
+
+If you specify values in `INITDBOPTS` that are also provided by the installer (such as the `–D` option, which specifies the installation directory), the value specified in the graphical installer supersedes the value if specified in `INITDBOPTS`.
+
+For more information about using `initdb` cluster configuration options, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-initdb.html). In addition to the cluster configuration options documented in the PostgreSQL core documentation, EDB Postgres Advanced Server supports the following `initdb` options:
+
+`--no-redwood-compat`
+
+`--no-redwood-compat` instructs the server to create the cluster in PostgreSQL mode. When the cluster is created in PostgreSQL mode, the name of the database superuser is `postgres` and the name of the default database is `postgres`. A small subset of Advanced Server features compatible with Oracle databases are available with this mode. However, we recommend using Advanced Server in redwood compatibility mode to have access to all its Oracle compatibility features.
+
+`--redwood-like`
+
+`--redwood-like` instructs the server to use an escape character (an empty string ('')) following the `LIKE` (or PostgreSQL compatible `ILIKE`) operator in a SQL statement that is compatible with Oracle syntax.
+
+`--icu-short-form`
+
+`--icu-short-form` creates a cluster that uses a default ICU (International Components for Unicode) collation for all databases in the cluster. For more information about Unicode collations, see [Basic Unicode collation algorithm concepts](../../../tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm).
+
diff --git a/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus.mdx b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus.mdx
new file mode 100644
index 00000000000..d3861759765
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus.mdx
@@ -0,0 +1,52 @@
+---
+title: "Using StackBuilder Plus"
+redirects:
+- 03_using_stackbuilder_plus
+- /epas/latest/epas_inst_windows/installing_advanced_server_with_the_interactive_installer/using_stackbuilder_plus/
+---
+
+<div id="using_stackbuilder_plus" class="registered_link"></div>
+
+The StackBuilder Plus utility provides a graphical interface that simplifies the process of updating, downloading, and installing modules that complement your EDB Postgres Advanced Server installation. When you install a module with StackBuilder Plus, StackBuilder Plus resolves any software dependencies.
+
+You can invoke StackBuilder Plus any time after the installation is complete by selecting **Apps > StackBuilder Plus**. If prompted, enter your system password, and the StackBuilder Plus welcome window opens.
+
+![The StackBuilder Plus welcome window](../../../images/stackbuilder_plus_welcome.png)
+
+From the list, select your EDB Postgres Advanced Server installation.
+
+StackBuilder Plus requires Internet access. If your installation of EDB Postgres Advanced Server is behind a firewall with restricted Internet access, StackBuilder Plus can download program installers through a proxy server. The module provider determines if the module can be accessed through an HTTP proxy or an FTP proxy. Currently, all updates are transferred by way of an HTTP proxy. The FTP proxy information isn't used.
+
+If the selected EDB Postgres Advanced Server installation has restricted Internet access, on the welcome window, select **Proxy Servers** to open the Proxy Servers dialog box.
+
+![The Proxy Servers dialog box](../../../images/proxy_servers.png)
+
+In the Proxy Servers dialog box, in the **HTTP proxy** fieldm enter the IP address and port number of the proxy server. Currently, all StackBuilder Plus modules are distributed by way of HTTP proxy, and FTP proxy information is ignored. Select **OK**.
+
+![The StackBuilder Plus module selection window](../../../images/stackbuilder_plus_module_selection.png)
+
+The tree control on the StackBuilder Plus module selection window displays a node for each module category.
+
+To review a detailed description of the component, expand a module and select a component name in the tree control. To add components to the installation or to upgrade a component, select the check box to the left of a module name and select **Next**.
+
+StackBuilder Plus confirms the packages selected.
+
+![A summary window displays a list of selected packages](../../../images/summary-window-displaying-selected-packages.png)
+
+Use the browse icon (...) to the right of the **Download directory** field to open a file selector and choose an alternativee location to store the downloaded installers. Select **Next** to connect to the server and download the required installation files.
+
+When the download completes, a window opens that confirms the installation files were downloaded and are ready for installation.
+
+![Confirmation that the download process is complete](../../../images/download_complete.png)
+
+To start the installation process, leave the **Skip Installation** box cleared and select **Next**. To exit StackBuilder Plus without installing the downloaded files, select the check box, and select **Next**.
+
+Each downloaded installer has different requirements. As the installers execute, they might prompt you to confirm acceptance of license agreements, enter passwords, and provide configuration information.
+
+During the installation process, you might be prompted by one or more of the installers to restart your system. Select **No** or **Restart Later** until all installations are completed. When the last installation has completed, restart the system to apply all of the updates.
+
+You might occasionally encounter packages that don’t install successfully. If a package fails to install, StackBuilder Plus alerts you to the installation error and writes a message to the log file at `%TEMP%`.
+
+When the installation is complete, StackBuilder Plus alerts you to the success or failure of the installations of the requested packages. If you were prompted by an installer to restart your computer, restart now.
+
+![StackBuilder Plus confirms the completed installation](../../../images/stackbuilder_plus_completed_installation.png)
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx
new file mode 100644
index 00000000000..769155250e0
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/configuring_epas.mdx
@@ -0,0 +1,99 @@
+---
+title: "Configuring EDB Postgres Advanced Server"
+navTitle: "Initial configuration"
+redirects:
+- /epas/latest/epas_inst_windows/06_configuring_advanced_server/
+- /epas/latest/epas_inst_windows/06_configuring_advanced_server/01_setting_advanced_server_environment_variables/
+- /epas/latest/epas_inst_windows/06_configuring_advanced_server/02_connecting_to_advanced_server_with_psql/
+- /epas/latest/epas_inst_windows/04_connecting_to_advanced_server_with_the_pgadmin_4_client/
+- /epas/latest/epas_inst_windows/managing_an_advanced_server_installation/configuring_epas/
+---
+
+You can easily update parameters that determine the behavior of EDB Postgres Advanced Server and supporting components by modifying the following configuration files:
+
+-   The `postgresql.conf` file determines the initial values of EDB Postgres Advanced Server configuration parameters.
+-   The `pg_hba.conf` file specifies your preferences for network authentication and authorization.
+-   The `pg_ident.conf` file maps operating system identities (user names) to EDB Postgres Advanced Server identities (roles) when using `ident`-based authentication.
+
+For more information about modifying the `postgresql.conf` and `pg_hba.conf` files, see [Setting parameters](../../../database_administration/01_configuration_parameters/01_setting_new_parameters/).
+
+You can use your editor of choice to open a configuration file. On Windows, you can navigate through the **EDB Postgres** menu to open a file.
+
+![Accessing the configuration files through the Windows system menu](../../../images/accessing_configuration_files.png)
+
+## Setting EDB Postgres Advanced Server environment variables
+
+The graphical installer provides a script that simplifies the task of setting environment variables for Windows users. The script sets the environment variables for your current shell session. When your shell session ends, the environment variables are destroyed. You might want to invoke `pgplus_env.bat` from your system-wide shell startup script, which definies environment variables for each shell session.
+
+The `pgplus_env` script is created during the EDB Postgres Advanced Server installation process and reflects the choices made during installation. To invoke the script, at the command line, enter:
+
+```text
+C:\Program Files\edb\as16\pgplus_env.bat
+```
+
+As the `pgplus_env.bat` script executes, it sets the following environment variables:
+
+```text
+PATH="C:\Program Files\edb\as16\bin";%PATH%
+EDBHOME=C:\Program Files\edb\as16
+PGDATA=C:\Program Files\edb\as16\data
+PGDATABASE=edb
+REM @SET PGUSER=enterprisedb
+PGPORT=5444
+PGLOCALEDIR=C:\Program Files\edb\as16\share\locale
+```
+
+If you used an installer created by EDB to install PostgreSQL, the `pg_env` script performs the same function:
+
+```text
+C:\Progra~1\PostgreSQL\16\pg_env.bat
+```
+
+As the `pg_env.bat` script executes on PostgreSQL, it sets the following environment variables:
+
+```text
+PATH="C:\Program Files\PostgreSQL\16\bin";%PATH%
+PGDATA=C:\Program Files\PostgreSQL\16\data
+PGDATABASE=postgres
+PGUSER=postgres
+PGPORT=5432
+PGLOCALEDIR=C:\Program Files\PostgreSQL\16\share\locale
+```
+
+## Connecting to EDB Postgres Advanced Server with edb-psql
+
+edb-psql is a command-line client application that allows you to execute SQL commands and view the results. To open the edb-psql client, make sure the client is in your search path. The executable resides in the `bin` directory under your EDB Postgres Advanced Server installation.
+
+Use the following command and options to start the edb-psql client:
+
+```text
+psql -d edb -U enterprisedb
+```
+
+Where:
+
+`-d` specifies the database to which edb-psql connects.
+
+`-U` specifies the identity of the database user to use for the session.
+
+If you performed an installation with the interactive installer, you can access the edb-psql client by selecting **EDB Postgres > EDB-PSQL**. When the client opens, provide connection information for your session.
+
+The `edb-psql` file is a symbolic link to a binary called `psql`, a modified version of the PostgreSQL community psql, with added support for EDB Postgres Advanced Server features. For more information about using the command-line client, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-psql.html).
+
+## Connecting to EDB Postgres Advanced Server with the pgAdmin 4 client
+
+pgAdmin 4 provides a graphical interface that you can use to manage your database and database objects. Dialog boxes and online help simplify tasks such as object creation, role management, and granting or revoking privileges. The tabbed browser panel provides quick access to information about the object currently selected in the pgAdmin tree control.
+
+The client is distributed with the graphical installer. To open pgAdmin, select **EDB Postgres > pgAdmin4**`. The client opens in your default browser.
+
+![The pgAdmin 4 client dashboard](../../../images/pgadmin4_client_dashboard.png)
+
+To connect to the EDB Postgres Advanced Server database server, expand the Servers node of the Browser tree control, and right-click on the EDB Postgres Advanced Server node. From the context menu, select **Connect Server**. The Connect to Server dialog box opens.
+
+![The Connect to Server dialog](../../../images/connecting_server.png)
+
+To connect, in the **Password** field, provide the password associated with the database superuser, and select **OK**.
+
+![Connecting to an EDB Postgres Advanced Server database](../../../images/connecting_to_advanced_server_database.png)
+
+When the client connects, you can use the Browser tree control to retrieve information about existing database objects or to create new objects. For more information about using the pgAdmin client, use the **Help** menu.
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/controlling_server_startup_behavior_on_windows.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/controlling_server_startup_behavior_on_windows.mdx
new file mode 100644
index 00000000000..382e0e2740e
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/controlling_server_startup_behavior_on_windows.mdx
@@ -0,0 +1,17 @@
+---
+title: "Controlling server startup behavior on Windows"
+redirects:
+- /epas/latest/epas_inst_windows/05_managing_an_advanced_server_installation/03_controlling_server_startup_behavior_on_windows/
+- /epas/latest/epas_inst_windows/managing_an_advanced_server_installation/controlling_server_startup_behavior_on_windows/
+---
+
+You can use the Windows Services utility to control the startup behavior of the server. Right-click the name of the service you want to update, and select **Properties** from the context menu. 
+
+In the Properties dialog box, from the **Startup type** list, specify how the EDB Postgres Advanced Server service behaves when the host starts.
+
+![Specifying EDB Postgres Advanced Server's startup behavior](../../../images/advanced_server_startup.png)
+
+-   Select **Automatic (Delayed Start)** to specify to start after boot.
+-   Select **Automatic** to specify to start and stop the server whenever the system starts or stops.
+-   Select **Manual** to specify to start the server manually.
+-   Select **Disabled** to disable the service. After disabling the service, you must stop the service or restart the server to make the change take effect. Once you disable the service, you can't change the server status until you reset **Startup type** to **Automatic (Delayed Start)**, **Automatic**, or **Manual**.
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/index.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/index.mdx
new file mode 100644
index 00000000000..374ba040dad
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "Managing an EDB Postgres Advanced Server installation"
+navTitle: "Managing installations"
+redirects:
+- /epas/latest/epas_inst_windows/managing_an_advanced_server_installation/
+navigation:
+- starting_and_stopping_epas
+- using_the_windows_services_applet
+- using_pg_ctl_to_control_advanced_server
+- controlling_server_startup_behavior_on_windows
+- configuring_epas
+indexCards: simple
+---
+
+<div id="managing_an_advanced_server_installation" class="registered_link"></div>
+
+Unless otherwise noted, the commands and paths for managing an EDB Postgres Advanced Server assume that you performed an installation with the interactive installer.
+
+<div class="toctree" maxdepth="3">
+
+using_the_windows_services_applet using_pg_ctl_to_control_advanced_server controlling_server_startup_behavior_on_windows
+
+</div>
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/starting_and_stopping_epas.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/starting_and_stopping_epas.mdx
new file mode 100644
index 00000000000..fd067f26ccb
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/starting_and_stopping_epas.mdx
@@ -0,0 +1,16 @@
+---
+title: "Starting and stopping EDB Postgres Advanced Server"
+---
+
+A service is a program that runs in the background and requires no user interaction. A service has no user interface. You can configure a service to start at boot time or manually on demand. Services are best controlled using the platform-specific operating system service control utility. Many of the EDB Postgres Advanced Server supporting components are services.
+
+The following table lists the names of the services that control EDB Postgres Advanced Server and services that control EDB Postgres Advanced Server supporting components:
+
+| EDB Postgres Advanced Server component name | Windows service name                |
+| ------------------------------ | ------------------------------------------------ |
+| EDB Postgres Advanced Server   | edb-as-16                                        |
+| pgAgent                        | EDB Postgres Advanced Server Scheduling Agent |
+| PgBouncer                      | edb-pgbouncer-1.21                            |
+| Slony                          | edb-slony-replication-14                         |
+
+You can use the command line or the Windows Services applet to control the EDB Postgres Advanced Server database server and the services of EDB Postgres Advanced Server's supporting components on a Windows host.
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_pg_ctl_to_control_advanced_server.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_pg_ctl_to_control_advanced_server.mdx
new file mode 100644
index 00000000000..76ba9b6835f
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_pg_ctl_to_control_advanced_server.mdx
@@ -0,0 +1,28 @@
+---
+title: "Using pg_ctl to control EDB Postgres Advanced Server"
+redirects:
+- /epas/latest/epas_inst_windows/05_managing_an_advanced_server_installation/02_using_pg_ctl_to_control_advanced_server/
+- /epas/latest/epas_inst_windows/managing_an_advanced_server_installation/using_pg_ctl_to_control_advanced_server/
+---
+
+<div id="using_pg_ctl_to_control_advanced_server" class="registered_link"></div>
+
+You can use the pg_ctl utility to control an EDB Postgres Advanced Server service from the command line on any platform. pg_ctl allows you to start, stop, or restart the EDB Postgres Advanced Server database server, reload the configuration parameters, or display the status of a running server. To invoke the utility, assume the identity of the cluster owner, navigate into the home directory of EDB Postgres Advanced Server, and issue the command:
+
+```text
+./bin/pg_ctl -D <data_directory> <action>
+```
+
+Where:
+
+`data_directory` is the location of the data controlled by the EDB Postgres Advanced Server cluster.
+
+`action` specifies the action taken by the pg_ctl utility. Specify:
+
+-   `start` to start the service.
+-   `stop` to stop the service.
+-   `restart` to stop and then start the service.
+-   `reload` to send the server a `SIGHUP` signal, reloading configuration parameters.
+-   `status` to discover the current status of the service.
+
+For more information about using the pg_ctl utility or the command-line options available, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/app-pg-ctl.html).
diff --git a/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_the_windows_services_applet.mdx b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_the_windows_services_applet.mdx
new file mode 100644
index 00000000000..85ce27bb31b
--- /dev/null
+++ b/product_docs/docs/epas/16/installing/windows/managing_an_advanced_server_installation/using_the_windows_services_applet.mdx
@@ -0,0 +1,19 @@
+---
+title: "Using the Windows services applet"
+redirects:
+- /epas/latest/epas_inst_windows/05_managing_an_advanced_server_installation/01_using_the_windows_services_applet/
+- /epas/latest/epas_inst_windows/managing_an_advanced_server_installation/using_the_windows_services_applet/
+---
+
+<div id="using_the_windows_services_applet" class="registered_link"></div>
+
+The Windows operating system includes a graphical service controller that offers control of EDB Postgres Advanced Server and the services associated with EDB Postgres Advanced Server components. Access the Services utility in the Administrative Tools section of the Windows control panel.
+
+![The EDB Postgres Advanced Server service in the Windows Services window](../../../images/advanced_server_services.png)
+
+The Services window displays an alphabetized list of services. The `edb-as-16` service controls EDB Postgres Advanced Server.
+
+-   Select **Stop** to stop the instance of EDB Postgres Advanced Server. Stopping the service disconnects any user or client application connected to the EDB Postgres Advanced Server instance.
+-   Select **Start** to start the EDB Postgres Advanced Server service.
+-   Select **Pause**  to reload the server configuration parameters without disrupting user sessions for many of the configuration parameters. See [Configuring EDB Postgres Advanced Server](configuring_epas/) for more information about the parameters that can be updated with a server reload.
+-   Select **Restart** to stop and then start the EDB Postgres Advanced Server. Any user sessions are terminated when you stop the service. This option is useful to reset server parameters that take effect only on server start.
diff --git a/product_docs/docs/epas/16/managing_performance/03_sql_profiler.mdx b/product_docs/docs/epas/16/managing_performance/03_sql_profiler.mdx
new file mode 100644
index 00000000000..2cd70320956
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/03_sql_profiler.mdx
@@ -0,0 +1,33 @@
+---
+title: "Using SQL Profiler"
+description: "How to use SQL Profiler to find and optimize inefficient SQL code"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.58.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.128.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/03_sql_profiler/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sql_profiler" class="registered_link"></div>
+
+Inefficient SQL code is a leading cause of database performance problems. The challenge for database administrators and developers is locating and then optimizing this code in large, complex systems. SQL Profiler helps you locate and optimize poorly running SQL code.
+
+Specific features and benefits of SQL Profiler include:
+
+-   **On-demand traces**. You can capture SQL traces at any time by manually setting up your parameters and starting the trace.
+-   **Scheduled traces**. If the current time isn't convenient, you can also specify your trace parameters and schedule them to run later.
+-   **Save traces**. Execute your traces and save them for later review.
+-   **Trace filters**. Selectively filter SQL captures by database and by user, or capture every SQL statement sent by all users against all databases.
+-   **Trace output analyzer**. A graphical table lets you quickly sort and filter queries by duration or statement. A graphical or text-based `EXPLAIN` plan lays out your query paths and joins.
+-   **EDB Query Advisor integration**. After you find your slow queries and optimize them, you can also let Query Advisor recommend the creation of underlying table indices to further improve performance.
+
+!!!SeeAlso "More information"
+
+See these topics in the Postgres Enterprise Manager documentation:
+- [Installing SQL Profiler](/pem/latest/profiling_workloads/installing_sql_profiler/)
+- [Upgrading SQL Profiler](/pem/9/upgrading/upgrading_sql_profiler)
+- [Using SQL Provider](/pem/9/profiling_workloads/using_sql_profiler)
+
+!!!
+
diff --git a/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/index.mdx b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/index.mdx
new file mode 100644
index 00000000000..ce405018d17
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/index.mdx
@@ -0,0 +1,38 @@
+---
+title: "Using the dynamic runtime instrumentation tools architecture (DRITA)"
+description: "How to use Dynamic Runtime Instrumentation Tools Architecture to query catalog views"
+indexCards: simple
+navigation:
+  - taking_a_snapshot
+  - using_drita_functions
+  - performance_tuning_recommendations
+  - simulating_statspack_reports
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.20.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.19.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.21.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.22.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.23.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.24.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.322.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.323.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.321.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.318.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.320.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.319.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.145.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.144.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.143.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.141.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.142.html"
+---
+
+<div id="dynamic_runtime_instrumentation_tools_architecture_DRITA" class="registered_link"></div>
+
+The Dynamic Runtime Instrumentation Tools Architecture (DRITA) enables a DBA to query catalog views to determine the *wait events* that affect the performance of individual sessions or the whole system. DRITA records the number of times each event occurs as well as the time spent waiting. You can use this information to diagnose performance problems. 
+
+DRITA compares *snapshots* to evaluate the performance of a system. A snapshot is a saved set of system performance data at a given point in time. A unique ID number identifies each snapshot. You can use snapshot ID numbers with DRITA reporting functions to return system performance statistics. DRITA consumes minimal system resources.
+
+
+
diff --git a/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/performance_tuning_recommendations.mdx b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/performance_tuning_recommendations.mdx
new file mode 100644
index 00000000000..e02510fdafc
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/performance_tuning_recommendations.mdx
@@ -0,0 +1,105 @@
+---
+title: "Performance tuning recommendations"
+description: "Explains how to review DRITA reports for performance tuning recommendations"
+---
+
+<div id="performance_tuning_recommendations" class="registered_link"></div>
+
+## Reviewing the reports
+
+To use Dynamic Runtime Instrumentation Tools Architecture (DRITA) reports for performance tuning, review the top five events in a report. Look for any event that takes an especially large percentage of resources. In a streamlined system, user I/O generally makes up the largest number of waits. Evaluate waits in the context of CPU usage and total time. An event might not be significant if it takes two minutes out of a total measurement interval of two hours and the rest of the time is consumed by CPU time. Evaluate the component of response time (CPU "work" time or other "wait" time) that consumes the highest percentage of overall time.
+
+When evaluating events, watch for:
+
+| Event type                 | Description                                                                                                                     |
+| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| Checkpoint waits           | Checkpoint waits might indicate that checkpoint parameters need to be adjusted (`checkpoint_segments` and `checkpoint_timeout`). |
+| WAL-related waits          | WAL-related waits might indicate `wal_buffers` are undersized.                                                                   |
+| SQL Parse waits            | If the number of waits is high, try to use prepared statements.                                                                 |
+| db file random reads       | If high, check for appropriate indexes and statistics.                                                                   |
+| db file random writes      | If high, might need to decrease `bgwriter_delay`.                                                                                 |
+| btree random lock acquires | Might indicate indexes are being rebuilt. Schedule index builds during less active time.                                          |
+
+Also look at the hardware, the operating system, the network, and the application SQL statements in performance reviews.
+
+<div id="event_descriptions" class="registered_link"></div>
+
+## Event descriptions
+
+The following table lists the basic wait events that are displayed by DRITA.
+
+| Event name                            | Description                                                                                                                                                                                                        |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `add in shmem lock acquire`           | Obsolete/unused.                                                                                                                                                                                                    |
+| `bgwriter communication lock acquire` | The bgwriter (background writer) process has waited for the short-term lock that synchronizes messages between the bgwriter and a backend process.                                                                 |
+| `btree vacuum lock acquire`           | The server has waited for the short-term lock that synchronizes access to the next available vacuum cycle ID.                                                                                                      |
+| `buffer free list lock acquire`       | The server has waited for the short-term lock that synchronizes access to the list of free buffers (in shared memory).                                                                                             |
+| `checkpoint lock acquire`             | A server process has waited for the short-term lock that prevents simultaneous checkpoints.                                                                                                                        |
+| `checkpoint start lock acquire`       | The server has waited for the short-term lock that synchronizes access to the bgwriter checkpoint schedule.                                                                                                        |
+| `clog control lock acquire`           | The server has waited for the short-term lock that synchronizes access to the commit log.                                                                                                                          |
+| `control file lock acquire`           | The server has waited for the short-term lock that synchronizes write access to the control file. This is usually a low number.                                                                            |
+| `db file extend`                      | A server process has waited for the operating system while adding a new page to the end of a file.                                                                                                                 |e
+| `db file read`                        | A server process has waited for a read from disk to complete.                                                                                                                                              |
+| `db file write`                       | A server process has waited for a write to disk to complete.                                                                                                                                               |
+| `db file sync`                        | A server process has waited for the operating system to flush all changes to disk.                                                                                                                                 |
+| `first buf mapping lock acquire`      | The server has waited for a short-term lock that synchronizes access to the shared-buffer mapping table.                                                                                                           |
+| `freespace lock acquire`              | The server has waited for the short-term lock that synchronizes access to the freespace map.                                                                                                                       |
+| `lwlock acquire`                      | The server has waited for a short-term lock that isn't described elsewhere in this table.                                                                                                                 |
+| `multi xact gen lock acquire`         | The server has waited for the short-term lock that synchronizes access to the next available multi-transaction ID (when a SELECT...FOR SHARE statement executes).                                                  |
+| `multi xact member lock acquire`      | The server has waited for the short-term lock that synchronizes access to the multi-transaction member file (when a SELECT...FOR SHARE statement executes).                                                        |
+| `multi xact offset lock acquire`      | The server has waited for the short-term lock that synchronizes access to the multi-transaction offset file (when a SELECT...FOR SHARE statement executes).                                                        |
+| `oid gen lock acquire`                | The server has waited for the short-term lock that synchronizes access to the next available OID (object ID).                                                                                                      |
+| `query plan`                          | The server has computed the execution plan for a SQL statement.                                                                                                                                                    |
+| `rel cache init lock acquire`         | The server has waited for the short-term lock that prevents simultaneous relation-cache loads/unloads.                                                                                                             |
+| `shmem index lock acquire`            | The server has waited for the short-term lock that synchronizes access to the shared-memory map.                                                                                                                   |
+| `sinval lock acquire`                 | The server has waited for the short-term lock that synchronizes access to the cache invalidation state.                                                                                                            |
+| `sql parse`                           | The server has parsed a SQL statement.                                                                                                                                                                             |
+| `subtrans control lock acquire`       | The server has waited for the short-term lock that synchronizes access to the subtransaction log.                                                                                                                  |
+| `tablespace create lock acquire`      | The server has waited for the short-term lock that prevents simultaneous `CREATE TABLESPACE` or `DROP TABLESPACE` commands.                                                                                        |
+| `two phase state lock acquire`        | The server has waited for the short-term lock that synchronizes access to the list of prepared transactions.                                                                                                       |
+| `wal insert lock acquire`             | The server has waited for the short-term lock that synchronizes write access to the write-ahead log. A high number can indicate that WAL buffers are sized too small.                                              |
+| `wal write lock acquire`              | The server has waited for the short-term lock that synchronizes write-ahead log flushes.                                                                                                                           |
+| `wal file sync`                       | The server has waited for the write-ahead log to sync to disk. This is related to the `wal_sync_method` parameter which, by default, is 'fsync'. You can gain better performance by changing this parameter to `open_sync`. |
+| `wal flush`                           | The server has waited for the write-ahead log to flush to disk.                                                                                                                                                    |
+| `wal write`                           | The server has waited for a write to the write-ahead log buffer. Expect this value to be high.                                                                                                                    |
+| `xid gen lock acquire`                | The server has waited for the short-term lock that synchronizes access to the next available transaction ID.                                                                                                       |
+
+## Wait events related to lightweight locks
+
+When wait events occur for *lightweight locks*, DRITA displays them as well. It uses a lightweight lock to protect a particular data structure in shared memory.
+
+Certain wait events can be due to the server process waiting for one of a group of related lightweight locks, which is referred to as a *lightweight lock tranche*. DRITA doesn't display individual lightweight lock tranches, but it displays their summation with a single event named `other lwlock acquire`.
+
+For a list and description of lightweight locks displayed by DRITA, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-STATS-SETUP). Under [Viewing Statistics](https://www.postgresql.org/docs/current/monitoring-stats.html#MONITORING-STATS-VIEWS), see the Wait Event Type table for more details.
+
+This example displays lightweight locks `ProcArrayLock`, `CLogControlLock`, `WALBufMappingLock`, and `XidGenLock`.
+
+```sql
+postgres=# select * from sys_rpt(40,70,20);
+__OUTPUT__
+                                    sys_rpt
+----------------------------------------------------------------------------
+ WAIT NAME                              COUNT       WAIT TIME        % WAIT
+----------------------------------------------------------------------------
+ wal flush                              56107       44.456494       47.65
+ db file read                           66123       19.543968       20.95
+ wal write                              32886       12.780866       13.70
+ wal file sync                          32933       11.792972       12.64
+ query plan                             223576      4.539186        4.87
+ db file extend                         2339        0.087038        0.09
+ other lwlock acquire                   402         0.066591        0.07
+ ProcArrayLock                          135         0.012942        0.01
+ CLogControlLock                        212         0.010333        0.01
+ WALBufMappingLock                      47          0.006068        0.01
+ XidGenLock                             53          0.005296        0.01
+(13 rows)
+```
+## Wait events related to product features
+
+DRITA also displays wait events that are related to certain EDB Postgres Advanced Server product features. These events and the `other lwlock acquire` event are listed in the following table.
+
+| Event name              | Description                                                       |
+| ----------------------- | ----------------------------------------------------------------- |
+| `BulkLoadLock`          | The server has waited for access related to EDB\*Loader.          |
+| `EDBResoureManagerLock` | The server has waited for access related to EDB Resource Manager. |
+| `other lwlock acquire`  | Summation of waits for lightweight lock tranches.                 |
diff --git a/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/simulating_statspack_reports.mdx b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/simulating_statspack_reports.mdx
new file mode 100644
index 00000000000..e2a75822f16
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/simulating_statspack_reports.mdx
@@ -0,0 +1,941 @@
+---
+title: "Simulating Statspack AWR reports"
+description: "Describes how to use DRITA functions to simulate Oracle Statspack Automatic Workload Repository (AWR) reports"
+redirects:
+  - /epas/latest/epas_compat_tools_guide/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="simulating_statspack_AWR_reports" class="registered_link"></div>
+
+When taking a snapshot, performance data from system catalog tables is saved into history tables. The following functions return information comparable to the information contained in an Oracle Statspack/Automatic Workload Repository (AWR) report. These reporting functions report on the differences between two given snapshots:
+
+-   `stat_db_rpt()`
+-   `stat_tables_rpt()`
+-   `statio_tables_rpt()`
+-   `stat_indexes_rpt()`
+-   `statio_indexes_rpt()`
+
+You can execute the reporting functions individually or you can execute all five functions by calling the `edbreport()` function.
+
+<div id="edbreport" class="registered_link"></div>
+
+## edbreport()
+
+The `edbreport()` function includes data from the other reporting functions, plus system information. The signature is:
+
+```sql
+edbreport(<beginning_id>, <ending_id>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+The call to the `edbreport()` function returns a composite report that contains system information and the reports returned by the other statspack functions:
+
+<!-- Consider replacing -->
+
+```sql
+SELECT * FROM edbreport(9, 10);
+__OUTPUT__
+                                   edbreport
+--------------------------------------------------------------------------------------
+    EnterpriseDB Report for database acctg             25-JUL-18
+ Version: PostgreSQL 14.0 (EnterpriseDB EDB Postgres Advanced Server 14.0.0)on x86_64-pc-linux-gnu,
+compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-18), 64-bit
+
+    Begin snapshot: 9 at 25-JUL-18 09:49:44.788392
+
+    End snapshot: 10 at 25-JUL-18 09:49:49.855821
+
+Size of database acctg is 173 MB
+     Tablespace: pg_default Size: 231 MB Owner: enterprisedb
+     Tablespace: pg_global Size: 719 kB Owner: enterprisedb
+
+Schema: pg_toast_temp_1       Size: 0 bytes     Owner: enterprisedb
+Schema: public                Size: 158 MB      Owner: enterprisedb
+```
+
+### Report introduction
+
+The information displayed in the report introduction includes the database name and version, the current date, the beginning and ending snapshot date and times, database and tablespace details, and schema information.
+
+```sql
+__OUTPUT__
+         Top 10 Relations by pages
+
+TABLE                                        RELPAGES
+-----------------------------------------------------
+pgbench_accounts                             16394
+pgbench_history                              391
+pg_proc                                      145
+pg_attribute                                 92
+pg_depend                                    81
+pg_collation                                 60
+edb$stat_all_indexes                         46
+edb$statio_all_indexes                       46
+pg_description                               44
+edb$stat_all_tables                          29
+```
+### Top 10 Relations by pages
+
+The information displayed in the `Top 10 Relations by pages` section includes:
+
+| Column name | Description                      |
+| ----------- | -------------------------------- |
+| `TABLE`     | The name of the table            |
+| `RELPAGES`  | The number of pages in the table |
+
+```sql
+__OUTPUT__
+       Top 10 Indexes by pages
+
+INDEX                                        RELPAGES
+-----------------------------------------------------
+pgbench_accounts_pkey                        2745
+pg_depend_reference_index                    68
+pg_depend_depender_index                     63
+pg_proc_proname_args_nsp_index               53
+pg_attribute_relid_attnam_index              25
+pg_description_o_c_o_index                   24
+pg_attribute_relid_attnum_index              17
+pg_proc_oid_index                            14
+pg_collation_name_enc_nsp_index              12
+edb$stat_idx_pk                              10
+```
+### Top 10 Indexes by pages
+
+The information displayed in the `Top 10 Indexes by pages` section includes:
+
+| Column name | Description                      |
+| ----------- | -------------------------------- |
+| `INDEX`     | The name of the index            |
+| `RELPAGES`  | The number of pages in the index |
+
+```sql
+__OUTPUT__
+            Top 10 Relations by DML
+
+SCHEMA        RELATION                        UPDATES     DELETES    INSERTS
+----------------------------------------------------------------------------
+public        pgbench_accounts                117209      0          1000000
+public        pgbench_tellers                 117209      0          100
+public        pgbench_branches                117209      0          10
+public        pgbench_history                 0           0          117209
+```
+
+### Top 10 Relations by DML
+
+The information displayed in the `Top 10 Relations by DML` section includes:
+
+| Column name | Description                                       |
+| ----------- | ------------------------------------------------- |
+| `SCHEMA`    | The name of the schema in which the table resides |
+| `RELATION`  | The name of the table                             |
+| `UPDATES`   | The number of UPDATES performed on the table      |
+| `DELETES`   | The number of DELETES performed on the table      |
+| `INSERTS`   | The number of INSERTS performed on the table      |
+
+```sql
+__OUTPUT__
+      DATA from pg_stat_database
+
+DATABASE    NUMBACKENDS  XACT COMMIT   XACT ROLLBACK   BLKS READ  BLKS HIT HIT RATIO
+-------------------------------------------------------------------------------------
+acctg       0            8261          0               117        127985   99.91
+```
+
+### DATA from pg_stat_database
+
+The information displayed in the DATA from `pg_stat_database` section of the report includes:
+
+| Column name     | Description                                                                                                                                                                                                        |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `DATABASE`      | The name of the database.                                                                                                                                                                                          |
+| `NUMBACKENDS`   | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting current state. All other columns return the accumulated values since the last reset. |
+| `XACT COMMIT`   | Number of transactions in this database that were committed.                                                                                                                                                  |
+| `XACT ROLLBACK` | Number of transactions in this database that were rolled back.                                                                                                                                                |
+| `BLKS READ`     | Number of disk blocks read in this database.                                                                                                                                                                       |
+| `BLKS HIT`      | Number of times disk blocks were found already in the buffer cache when a read wasn't necessary.                                                                                                                |
+| `HIT RATIO`     | The percentage of times that a block was found in the shared buffer cache.                                                                                                                                         |
+
+```sql
+__OUTPUT__
+    DATA from pg_buffercache
+
+RELATION                            BUFFERS
+-------------------------------------------
+pgbench_accounts                    16665
+pgbench_accounts_pkey               2745
+pgbench_history                     751
+edb$statio_all_indexes              94
+edb$stat_all_indexes                94
+edb$stat_all_tables                 60
+edb$statio_all_tables               56
+edb$session_wait_history            34
+edb$statio_idx_pk                   17
+pg_depend                           17
+```
+
+### DATA from pg_buffercache
+
+The information displayed in the `DATA from pg_buffercache` section of the report includes:
+
+| Column name | Description                                       |
+| ----------- | ------------------------------------------------- |
+| `RELATION`  | The name of the table                             |
+| `BUFFERS`   | The number of shared buffers used by the relation |
+
+!!! Note
+    To obtain the report for `DATA from pg_buffercache`, the `pg_buffercache` module must be installed in the database. Perform the installation using the `CREATE EXTENSION` command.
+
+For more information on the `CREATE EXTENSION` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
+
+```sql
+__OUTPUT__
+     DATA from pg_stat_all_tables ordered by seq scan
+
+ SCHEMA                RELATION                     SEQ SCAN    REL TUP READ IDX SCAN
+IDX TUP READ INS   UPD     DEL
+-------------------------------------------------------------------------------------
+----------------------------------
+ public                pgbench_branches              8258        82580       0
+0             0     8258    0
+ public                pgbench_tellers               8258        825800      0
+0             0     8258    0
+ pg_catalog            pg_class                      7           3969        92
+80            0     0       0
+ pg_catalog            pg_index                      5           950         31
+38            0     0       0
+ pg_catalog            pg_namespace                  4           144         5
+4             0     0       0
+ pg_catalog            pg_database                   2           12          7
+7             0     0       0
+ pg_catalog            pg_am                         1           1           0
+0             0     0       0
+ pg_catalog            pg_authid                     1           10          2
+2             0     0       0
+ sys                   callback_queue_table          0           0           0
+0             0     0       0
+ sys                   edb$session_wait_history      0           0           0
+0             125   0       0
+```
+
+### DATA from pg_stat_all_tables ordered by seq scan
+
+The information displayed in the `DATA from pg_stat_all_tables ordered by seq scan` section includes:
+
+| Column name    | Description                                            |
+| -------------- | ------------------------------------------------------ |
+| `SCHEMA`       | The name of the schema in which the table resides      |
+| `RELATION`     | The name of the table                                  |
+| `SEQ SCAN`     | The number of sequential scans initiated on this table |
+| `REL TUP READ` | The number of tuples read in the table                 |
+| `IDX SCAN`     | The number of index scans initiated on the table       |
+| `IDX TUP READ` | The number of index tuples read                        |
+| `INS`          | The number of rows inserted                            |
+| `UPD`          | The number of rows updated                             |
+| `DEL`          | The number of rows deleted                             |
+
+```sql
+__OUTPUT__
+    DATA from pg_stat_all_tables ordered by rel tup read
+
+ SCHEMA             RELATION                 SEQ SCAN  REL TUP READ IDX SCAN
+IDX TUP READ INS  UPD    DEL
+---------------------------------------------------------------------------
+--------------------------------------------
+ public             pgbench_tellers          8258      825800       0
+0            0    8258   0
+ public             pgbench_branches         8258      82580        0
+0            0    8258   0
+ pg_catalog         pg_class                 7         3969         92
+80           0    0      0
+ pg_catalog         pg_index                 5         950          31
+38           0    0      0
+ pg_catalog         pg_namespace             4         144          5
+4            0    0      0
+ pg_catalog         pg_database              2         12           7
+7            0    0      0
+ pg_catalog         pg_authid                1         10           2
+2            0    0      0
+ pg_catalog         pg_am                    1         1            0
+0            0    0      0
+ sys                callback_queue_table     0         0            0
+0            0    0      0
+ sys                edb$session_wait_history 0         0            0
+0            125  0      0
+```
+
+### DATA from pg_stat_all_tables ordered by rel tup read
+
+The information displayed in the `DATA from pg_stat_all_tables ordered by rel tup read` section includes:
+
+| Column name    | Description                                           |
+| -------------- | ----------------------------------------------------- |
+| `SCHEMA`       | The name of the schema in which the table resides     |
+| `RELATION`     | The name of the table                                 |
+| `SEQ SCAN`     | The number of sequential scans performed on the table |
+| `REL TUP READ` | The number of tuples read from the table              |
+| `IDX SCAN`     | The number of index scans performed on the table      |
+| `IDX TUP READ` | The number of index tuples read                       |
+| `INS`          | The number of rows inserted                           |
+| `UPD`          | The number of rows updated                            |
+| `DEL`          | The number of rows deleted                            |
+
+```sql
+__OUTPUT__
+    DATA from pg_statio_all_tables
+
+ SCHEMA               RELATION             HEAP     HEAP     IDX      IDX
+TOAST     TOAST     TIDX    TIDX
+                                           READ     HIT      READ     HIT
+READ      HIT       READ    HIT
+-----------------------------------------------------------------------------------
+------------------------------
+ public               pgbench_accounts     32       25016     0       49913
+0         0         0       0
+ public               pgbench_tellers      0        24774     0       0
+0         0         0       0
+ public               pgbench_branches     0        16516     0       0
+0         0         0       0
+ public               pgbench_history      53       8364      0       0
+0         0         0       0
+ pg_catalog           pg_class             0        199       0       187
+0         0         0       0
+ pg_catalog           pg_attribute         0        198       0       395
+0         0         0       0
+ pg_catalog           pg_proc              0        75        0       153
+0         0         0       0
+ pg_catalog           pg_index             0        56        0       33
+0         0         0       0
+ pg_catalog           pg_amop              0        48        0       56
+0         0         0       0
+ pg_catalog           pg_namespace         0        28        0       7
+0         0         0       0
+```
+
+### DATA from pg_statio_all_tables
+
+The information displayed in the `DATA from pg_statio_all_tables` section includes:
+
+| Column name  | Description                                       |
+| ------------ | ------------------------------------------------- |
+| `SCHEMA`     | The name of the schema in which the table resides |
+| `RELATION`   | The name of the table                             |
+| `HEAP READ`  | The number of heap blocks read                    |
+| `HEAP HIT`   | The number of heap blocks hit                     |
+| `IDX READ`   | The number of index blocks read                   |
+| `IDX HIT`    | The number of index blocks hit                    |
+| `TOAST READ` | The number of toast blocks read                   |
+| `TOAST HIT`  | The number of toast blocks hit                    |
+| `TIDX READ`  | The number of toast index blocks read             |
+| `TIDX HIT`   | The number of toast index blocks hit              |
+
+```sql
+__OUTPUT__
+    DATA from pg_stat_all_indexes
+
+ SCHEMA                  RELATION                    INDEX
+IDX SCAN     IDX TUP READ IDX TUP FETCH
+------------------------------------------------------------------------------
+-------------------------------------------
+ public                  pgbench_accounts            pgbench_accounts_pkey
+16516        16679         16516
+ pg_catalog              pg_attribute
+pg_attribute_relid_attnum_index   196               402          402
+ pg_catalog              pg_proc                     pg_proc_oid_index
+70           70            70
+ pg_catalog              pg_class                    pg_class_oid_index
+61           61            61
+ pg_catalog              pg_class                    pg_class_relname_nsp_index
+31           19            19
+ pg_catalog              pg_type                     pg_type_oid_index
+22           22            22
+ pg_catalog             edb_policy                   edb_policy_object_name_index
+21           0             0
+ pg_catalog             pg_amop                      pg_amop_fam_strat_index
+16           16            16
+ pg_catalog             pg_index                     pg_index_indexrelid_index
+16           16            16
+ pg_catalog             pg_index                     pg_index_indrelid_index
+15           22            22
+```
+
+### DATA from pg_stat_all_indexes
+
+The information displayed in the `DATA from pg_stat_all_indexes` section includes:
+
+| Column name     | Description                                                              |
+| --------------- | ------------------------------------------------------------------------ |
+| `SCHEMA`        | The name of the schema in which the index resides                        |
+| `RELATION`      | The name of the table on which the index is defined                      |
+| `INDEX`         | The name of the index                                                    |
+| `IDX SCAN`      | The number of indexes scans initiated on this index                      |
+| `IDX TUP READ`  | Number of index entries returned by scans on this index                  |
+| `IDX TUP FETCH` | Number of live table rows fetched by simple index scans using this index |
+
+```sql
+__OUTPUT__
+   DATA from pg_statio_all_indexes
+
+ SCHEMA            RELATION                  INDEX
+IDX BLKS READ IDX BLKS HIT
+------------------------------------------------------------------------
+------------------------------------------
+ public            pgbench_accounts          pgbench_accounts_pkey
+0             49913
+ pg_catalog        pg_attribute
+pg_attribute_relid_attnum_index    0             395
+ sys               edb$stat_all_indexes      edb$stat_idx_pk
+1            382
+ sys               edb$statio_all_indexes    edb$statio_idx_pk
+1            382
+ sys               edb$statio_all_tables     edb$statio_tab_pk
+2            262
+ sys               edb$stat_all_tables       edb$stat_tab_pk
+0            259
+ sys               edb$session_wait_history  session_waits_hist_pk
+0            251
+ pg_catalog        pg_proc                   pg_proc_oid_index
+0            142
+ pg_catalog        pg_class                  pg_class_oid_index
+0            123
+ pg_catalog        pg_class                  pg_class_relname_nsp_index
+0            63
+```
+
+### DATA from pg_statio_all_indexes
+
+The information displayed in the `DATA from pg_statio_all_indexes` section includes:
+
+| Column name     | Description                                         |
+| --------------- | --------------------------------------------------- |
+| `SCHEMA`        | The name of the schema in which the index resides   |
+| `RELATION`      | The name of the table on which the index is defined |
+| `INDEX`         | The name of the index                               |
+| `IDX BLKS READ` | The number of index blocks read                     |
+| `IDX BLKS HIT`  | The number of index blocks hit                      |
+
+```sql
+__OUTPUT__
+    System Wait Information
+
+WAIT NAME                              COUNT        WAIT TIME        % WAIT
+---------------------------------------------------------------------------
+wal flush                              8359         1.357593          30.62
+wal write                              8358         1.349153          30.43
+wal file sync                          8358         1.286437          29.02
+query plan                             33439        0.439324          9.91
+db file extend                         54           0.000585          0.01
+db file read                           31           0.000307          0.01
+other lwlock acquire                   0            0.000000          0.00
+ProcArrayLock                          0            0.000000          0.00
+CLogControlLock                        0            0.000000          0.00
+```
+
+### System Wait Information
+
+The information displayed in the `System Wait Information` section includes:
+
+| Column name | Description                                                               |
+| ----------- | ------------------------------------------------------------------------- |
+| `WAIT NAME` | The name of the wait                                                     |
+| `COUNT`     | The number of times that the wait event occurred                         |
+| `WAIT TIME` | The length of the wait time in seconds                                   |
+| `% WAIT`    | The percentage of the total wait time used by this wait for this session |
+
+```sql
+__OUTPUT__
+    Database Parameters from postgresql.conf
+
+ PARAMETER                             SETTING
+CONTEXT       MINVAL         MAXVAL
+----------------------------------------------------------------------
+---------------------------------------------------
+ allow_system_table_mods               off
+postmaster
+ application_name                      psql.bin
+user
+ archive_command                       (disabled)
+sighup
+ archive_mode                          off
+postmaster
+ archive_timeout                       0
+sighup      0               1073741823
+ array_nulls                           on
+user
+ authentication_timeout                60
+sighup       1              600
+ autovacuum                            on
+sighup
+ autovacuum_analyze_scale_factor       0.1
+sighup       0              100
+ autovacuum_analyze_threshold          50
+sighup       0              2147483647
+ autovacuum_freeze_max_age             200000000
+postmaster   100000         2000000000
+ autovacuum_max_workers                3
+postmaster   1              262143
+ autovacuum_multixact_freeze_max_age   400000000
+postmaster   10000          2000000000
+ autovacuum_naptime                    60
+sighup       1            2147483
+ autovacuum_vacuum_cost_delay           20
+sighup      -1              100
+                        .
+                        .
+                        .
+```
+
+### Database Parameters from postgresql.conf
+
+The information displayed in the `Database Parameters from postgresql.conf` section includes:
+
+| Column name | Description                                      |
+| ----------- | ------------------------------------------------ |
+| `PARAMETER` | The name of the parameter                       |
+| `SETTING`   | The current value assigned to the parameter     |
+| `CONTEXT`   | The context required to set the parameter value |
+| `MINVAL`    | The minimum value allowed for the parameter     |
+| `MAXVAL`    | The maximum value allowed for the parameter     |
+
+<div id="stat_db_rpt" class="registered_link"></div>
+
+## stat_db_rpt()
+
+The signature is:
+
+```sql
+stat_db_rpt(<beginning_id>, <ending_id>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+This example shows the `stat_db_rpt()` function:
+
+```sql
+SELECT * FROM stat_db_rpt(9, 10);
+__OUTPUT__
+                                    stat_db_rpt
+-------------------------------------------------------------------------------------
+   DATA from pg_stat_database
+
+DATABASE  NUMBACKENDS   XACT COMMIT  XACT ROLLBACK  BLKS READ  BLKS HIT HIT RATIO
+-------------------------------------------------------------------------------------
+acctg     0             8261         0              117        127985   99.91
+(5 rows)
+```
+
+### DATA from pg_stat_database
+
+The information displayed in the DATA from `pg_stat_database` section of the report includes:
+
+| Column name     | Description                                                                                                                                                                                                        |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `DATABASE`      | The name of the database.                                                                                                                                                                                          |
+| `NUMBACKENDS`   | Number of backends currently connected to this database. This is the only column in this view that returns a value reflecting current state. All other columns return the accumulated values since the last reset. |
+| `XACT COMMIT`   | The number of transactions in this database that were committed.                                                                                                                                              |
+| `XACT ROLLBACK` | The number of transactions in this database that were rolled back.                                                                                                                                            |
+| `BLKS READ`     | The number of blocks read.                                                                                                                                                                                         |
+| `BLKS HIT`      | The number of blocks hit.                                                                                                                                                                                          |
+| `HIT RATIO`     | The percentage of times that a block was found in the shared buffer cache.                                                                                                                                         |
+
+<div id="stat_tables_rpt" class="registered_link"></div>
+
+## stat_tables_rpt()
+
+The signature is:
+
+```sql
+function_name(<beginning_id>, <ending_id>, <top_n>, <scope>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+`scope`
+
+ Determines the tables the function returns statistics about. Specify `SYS`, `USER`, or `ALL`:
+
+-   Use `SYS` to return information about system-defined tables. A table is considered a system table if it's stored in the `pg_catalog`, `information_schema`, or `sys` schema.
+-   Use `USER` to return information about user-defined tables.
+-   Use `ALL` to return information about all tables.
+
+The `stat_tables_rpt()` function returns a two-part report. The first portion of the report contains:
+
+```sql
+SELECT * FROM stat_tables_rpt(8, 9, 10, 'ALL');
+__OUTPUT__
+                         stat_tables_rpt
+----------------------------------------------------------------------------
+   DATA from pg_stat_all_tables ordered by seq scan
+
+ SCHEMA               RELATION                      SEQ SCAN   REL TUP READ IDX SCAN
+IDX TUP READ INS   UPD    DEL
+-------------------------------------------------------------------------------------
+----------------------------------
+ public               pgbench_branches               8249       82490       0
+0            0    8249    0
+ public               pgbench_tellers                8249       824900      0
+0            0    8249    0
+ pg_catalog           pg_class                       7          3969        92
+80           0    0       0
+ pg_catalog           pg_index                       5          950         31
+38           0    0       0
+ pg_catalog           pg_namespace                   4          144         5
+4            0    0       0
+ pg_catalog           pg_am                          1          1           0
+0            0    0       0
+ pg_catalog           pg_authid                      1          10          2
+2            0    0       0
+ pg_catalog           pg_database                    1          6           3
+3            0    0       0
+ sys                  callback_queue_table           0          0           0
+0            0    0       0
+ sys                 edb$session_wait_history        0          0           0
+0            125 0        0
+```
+
+### DATA from pg_stat_all_tables ordered by seq scan
+
+The information displayed in the `DATA from pg_stat_all_tables ordered by seq scan` section includes:
+
+| Column name    | Description                                        |
+| -------------- | -------------------------------------------------- |
+| `SCHEMA`       | The name of the schema in which the table resides |
+| `RELATION`     | The name of the table                             |
+| `SEQ SCAN`     | The number of sequential scans on the table       |
+| `REL TUP READ` | The number of tuples read from the table          |
+| `IDX SCAN`     | The number of index scans performed on the table  |
+| `IDX TUP READ` | The number of index tuples read from the table    |
+| `INS`          | The number of rows inserted                       |
+| `UPD`          | The number of rows updated                        |
+| `DEL`          | The number of rows deleted                        |
+
+The second portion of the report contains:
+
+```sql
+__OUTPUT__
+   DATA from pg_stat_all_tables ordered by rel tup read
+
+ SCHEMA               RELATION                 SEQ SCAN REL   TUP READ   IDX SCAN
+IDX TUP READ INS    UPD     DEL
+-----------------------------------------------------------------------------
+--------------------------------------
+ public               pgbench_tellers          8249          824900      0
+0            0     8249     0
+ public               pgbench_branches         8249          82490       0
+0            0     8249     0
+ pg_catalog           pg_class                 7             3969        92
+80           0     0        0
+ pg_catalog           pg_index                 5             950         31
+38           0     0        0
+ pg_catalog           pg_namespace             4             144         5
+4            0     0        0
+ pg_catalog           pg_authid                1             10          2
+2            0     0        0
+ pg_catalog           pg_database              1             6           3
+3            0     0        0
+ pg_catalog           pg_am                    1             1           0
+0            0     0        0
+ sys                  callback_queue_table     0             0           0
+0            0     0        0
+ sys                  edb$session_wait_history 0             0           0
+0            125   0        0
+(29 rows)
+```
+
+### DATA from pg_stat_all_tables ordered by rel tup read
+
+The information displayed in the `DATA from pg_stat_all_tables ordered by rel tup read` section includes:
+
+| Column name    | Description                                            |
+| -------------- | ------------------------------------------------------ |
+| `SCHEMA`       | The name of the schema in which the table resides     |
+| `RELATION`     | The name of the table                                 |
+| `SEQ SCAN`     | The number of sequential scans performed on the table |
+| `REL TUP READ` | The number of tuples read from the table              |
+| `IDX SCAN`     | The number of index scans performed on the table      |
+| `IDX TUP READ` | The number of live rows fetched by index scans        |
+| `INS`          | The number of rows inserted                           |
+| `UPD`          | The number of rows updated                            |
+| `DEL`          | The number of rows deleted                            |
+
+<div id="statio_tables_rpt" class="registered_link"></div>
+
+## statio_tables_rpt()
+
+The signature is:
+
+```sql
+statio_tables_rpt(<beginning_id>, <ending_id>, <top_n>, <scope>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+`scope`
+
+ Determines the tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`:
+
+-   Use `SYS` to return information about system-defined tables. A table is considered a system table if it's stored the `pg_catalog`, `information_schema`, or `sys` schema.
+-   Use `USER` to return information about user-defined tables.
+-   Use `ALL` to return information about all tables.
+
+The `statio_tables_rpt()` function returns a report that contains:
+
+```sql
+SELECT * FROM statio_tables_rpt(9, 10, 10, 'SYS');
+__OUTPUT__
+                                               statio_tables_rpt
+------------------------------------------------------------------------------------
+-------------------------------
+    DATA from pg_statio_all_tables
+
+ SCHEMA                  RELATION             HEAP     HEAP    IDX    IDX   TOAST
+TOAST      TIDX      TIDX
+                                              READ     HIT     READ   HIT   READ
+                                                
+HIT        READ      HIT
+-------------------------------------------------------------------------------------
+----------------------------
+ sys                     edb$stat_all_indexes 8        18      1       382   0
+0          0         0
+ sys                     edb$statio_all_index 8        18      1       382   0
+0          0         0
+ sys                     edb$statio_all_table 5        12      2       262   0
+0          0         0
+ sys                     edb$stat_all_tables  4        10      0       259   0
+0          0         0
+ sys                     edb$session_wait_his 2        6       0       251   0
+0          0         0
+ sys                     edb$session_waits    1        4       0       12    0
+0          0         0
+ sys                     callback_queue_table 0        0       0       0     0
+0          0         0
+ sys                     dual                 0        0       0       0     0
+0          0         0
+ sys                    edb$snap              0        1       0       2     0
+0          0         0
+ sys                    edb$stat_database     0        2       0       7     0
+0          0         0
+(15 rows)
+```
+
+### DATA from pg_statio_all_tables
+
+The information displayed in the `DATA from pg_statio_all_tables` section includes:
+
+| Column name  | Description                                          |
+| ------------ | ---------------------------------------------------- |
+| `SCHEMA`     | The name of the schema in which the relation resides |
+| `RELATION`   | The name of the relation                             |
+| `HEAP READ`  | The number of heap blocks read                       |
+| `HEAP HIT`   | The number of heap blocks hit                        |
+| `IDX READ`   | The number of index blocks read                      |
+| `IDX HIT`    | The number of index blocks hit                       |
+| `TOAST READ` | The number of toast blocks read                      |
+| `TOAST HIT`  | The number of toast blocks hit                       |
+| `TIDX READ`  | The number of toast index blocks read                |
+| `TIDX HIT`   | The number of toast index blocks hit                 |
+
+<div id="stat_indexes_rpt" class="registered_link"></div>
+
+## stat_indexes_rpt()
+
+The signature is:
+
+```sql
+stat_indexes_rpt(<beginning_id>, <ending_id>, <top_n>, <scope>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+`scope`
+
+ Determines the tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`:
+
+-   Use `SYS` to return information about system-defined tables. A table is considered a system table if it's stored in the `pg_catalog`, `information_schema`, or `sys` schema.
+-   Use `USER` to return information about user-defined tables.
+-   Use `ALL` to return information about all tables.
+
+The `stat_indexes_rpt()` function returns a report that contains:
+
+```sql
+edb=# SELECT * FROM stat_indexes_rpt(9, 10, 10, 'ALL');
+__OUTPUT__
+                               stat_indexes_rpt
+-------------------------------------------------------------------------------
+---------------------------------------------
+     DATA from pg_stat_all_indexes
+
+ SCHEMA                   RELATION                  INDEX
+IDX SCAN       IDX TUP READ IDX TUP FETCH
+-------------------------------------------------------------------------------
+------------------------------------------
+ public                   pgbench_accounts          pgbench_accounts_pkey
+16516          16679        16516
+ pg_catalog               pg_attribute
+pg_attribute_relid_attnum_index      196           402      402
+ pg_catalog               pg_proc                   pg_proc_oid_index
+70             70           70
+ pg_catalog               pg_class                  pg_class_oid_index
+61             61           61
+ pg_catalog               pg_class                  pg_class_relname_nsp_index
+31             19           19
+ pg_catalog               pg_type                   pg_type_oid_index
+22             22           22
+ pg_catalog               edb_policy                edb_policy_object_name_index
+21             0            0
+ pg_catalog               pg_amop                   pg_amop_fam_strat_index
+16             16           16
+ pg_catalog               pg_index                  pg_index_indexrelid_index
+16             16           16
+ pg_catalog               pg_index                  pg_index_indrelid_index
+15             22           22
+(14 rows)
+```
+
+### DATA from pg_stat_all_indexes
+
+The information displayed in the `DATA from pg_stat_all_indexes` section includes:
+
+| Column name     | Description                                          |
+| --------------- | ---------------------------------------------------- |
+| `SCHEMA`        | The name of the schema in which the relation resides |
+| `RELATION`      | The name of the relation                             |
+| `INDEX`         | The name of the index                                |
+| `IDX SCAN`      | The number of indexes scanned                        |
+| `IDX TUP READ`  | The number of index tuples read                      |
+| `IDX TUP FETCH` | The number of index tuples fetched                   |
+
+<div id="statio_indexes_rpt" class="registered_link"></div>
+
+## statio_indexes_rpt()
+
+The signature is:
+
+```sql
+statio_indexes_rpt(<beginning_id>, <ending_id>, <top_n>, <scope>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+`scope`
+
+ Determines the tables the function returns statistics about. Specify `SYS`, `USER` or `ALL`:
+
+-   Use `SYS` to return information about system-defined tables. A table is considered a system table if it's stored in the `pg_catalog`, `information_schema`, or `sys` schema.
+-   Use `USER` to return information about user-defined tables.
+-   Use `ALL` to return information about all tables.
+
+The `statio_indexes_rpt()` function returns a report that contains:
+
+```sql
+edb=# SELECT * FROM statio_indexes_rpt(9, 10, 10, 'SYS');
+__OUTPUT__
+                           statio_indexes_rpt
+----------------------------------------------------------------------------
+------------------------------------
+  DATA from pg_statio_all_indexes
+
+ SCHEMA                      RELATION                       INDEX
+IDX BLKS READ         IDX BLKS HIT
+----------------------------------------------------------------------------
+---------------------------------
+ pg_catalog                 pg_attribute
+pg_attribute_relid_attnum_index          0                      395
+ sys                        edb$stat_all_indexes           edb$stat_idx_pk
+1                    382
+ sys                        edb$statio_all_indexes         edb$statio_idx_pk
+1                    382
+ sys                        edb$statio_all_tables          edb$statio_tab_pk
+2                    262
+ sys                        edb$stat_all_tables            edb$stat_tab_pk
+0                    259
+ sys                        edb$session_wait_history       session_waits_hist_pk
+0                    251
+ pg_catalog                 pg_proc                        pg_proc_oid_index
+0                    142
+ pg_catalog                 pg_class                       pg_class_oid_index
+0                    123
+ pg_catalog                 pg_class                       pg_class_relname_nsp_index
+0                    63
+ pg_catalog                 pg_type                        pg_type_oid_index
+0                    45
+(14 rows)
+```
+
+### DATA from pg_statio_all_indexes
+
+The information displayed in the `DATA from pg_statio_all_indexes` report includes:
+
+| Column name     | Description                                          |
+| --------------- | ---------------------------------------------------- |
+| `SCHEMA`        | The name of the schema in which the relation resides |
+| `RELATION`      | The name of the table on which the index is defined  |
+| `INDEX`         | The name of the index                                |
+| `IDX BLKS READ` | The number of index blocks read                      |
+| `IDX BLKS HIT`  | The number of index blocks hit                       |
+
diff --git a/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/taking_a_snapshot.mdx b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/taking_a_snapshot.mdx
new file mode 100644
index 00000000000..239812cfd24
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/taking_a_snapshot.mdx
@@ -0,0 +1,44 @@
+---
+title: "Taking a snapshot"
+description: "Describes how to take a snapshot of system performance data"
+---
+
+<div id="configuring_and_using_DRITA" class="registered_link"></div>
+
+EDB Postgres Advanced Server's `postgresql.conf` file includes a configuration parameter named `timed_statistics` that controls collecting timing data. The valid parameter values are `TRUE` or `FALSE`. The default value is `FALSE`.
+
+`timed_statistics` is a dynamic parameter that you can modify in the `postgresql.conf` file or while a session is in progress. To enable DRITA, you must either:
+
+1.  Modify the `postgresql.conf` file, setting the `timed_statistics` parameter to `TRUE`.
+
+2.  Connect to the server with the EDB-PSQL client and invoke the command:
+
+   ```sql
+   SET timed_statistics = TRUE
+   ```
+
+3. After modifying the `timed_statistics` parameter, take a starting snapshot. A snapshot captures the current state of each timer and event counter. The server compares the starting snapshot to a later snapshot to gauge system performance. Use the `edbsnap()` function to take the beginning snapshot:
+
+   ```sql
+   edb=# SELECT * FROM edbsnap();
+   __OUTPUT__
+       edbsnap
+   ----------------------
+    Statement processed.
+   (1 row)
+   ```
+
+4. Run the workload that you want to evaluate. When the workload is complete or at a strategic point during the workload, take another snapshot:
+
+   ```sql
+   edb=# SELECT * FROM edbsnap();
+   __OUTPUT__
+       edbsnap
+   ----------------------
+    Statement processed.
+   (1 row)
+   ```
+
+You can capture multiple snapshots during a session. Finally, you can use the DRITA functions and reports to manage and compare the snapshots to evaluate performance information.
+
+<div id="DRITA_functions" class="registered_link"></div>
diff --git a/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/using_drita_functions.mdx b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/using_drita_functions.mdx
new file mode 100644
index 00000000000..e123e2c9be9
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/using_drita_functions.mdx
@@ -0,0 +1,479 @@
+---
+title: "Using DRITA functions"
+description: "Describes how to use DRITA functions to gather wait information and manage snapshots"
+---
+
+You can use DRITA functions to gather wait information and manage snapshots. DRITA functions are fully supported by EDB Postgres Advanced Server  whether your installation is made compatible with Oracle databases or is in PostgreSQL-compatible mode.
+
+<div id="get_snaps" class="registered_link"></div>
+
+## Retrieving a list of current snapshots (get_snaps)
+
+The `get_snaps()` function returns a list of the current snapshots. The signature is:
+
+```sql
+get_snaps()
+```
+
+This example uses the `get_snaps()` function to display a list of snapshots:
+
+```sql
+SELECT * FROM get_snaps();
+__OUTPUT__
+       get_snaps
+------------------------------
+ 1 25-JUL-18 09:49:04.224597
+ 2 25-JUL-18 09:49:09.310395
+ 3 25-JUL-18 09:49:14.378728
+ 4 25-JUL-18 09:49:19.448875
+ 5 25-JUL-18 09:49:24.52103
+ 6 25-JUL-18 09:49:29.586889
+ 7 25-JUL-18 09:49:34.65529
+ 8 25-JUL-18 09:49:39.723095
+ 9 25-JUL-18 09:49:44.788392
+ 10 25-JUL-18 09:49:49.855821
+ 11 25-JUL-18 09:49:54.919954
+ 12 25-JUL-18 09:49:59.987707
+(12 rows)
+```
+
+The first column in the result list displays the snapshot identifier. The second column displays the date and time that the snapshot was captured.
+
+<div id="sys_rpt" class="registered_link"></div>
+
+## Retrieving system wait information (sys_rpt)
+
+The `sys_rpt()` function returns system wait information. The signature is:
+
+```sql
+sys_rpt(<beginning_id>, <ending_id>, <top_n>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+This example shows a call to the `sys_rpt()` function:
+
+```sql
+SELECT * FROM sys_rpt(9, 10, 10);
+__OUTPUT__
+                                  sys_rpt
+-----------------------------------------------------------------------------
+WAIT NAME                    COUNT     WAIT TIME                     % WAIT
+---------------------------------------------------------------------------
+wal flush                    8359      1.357593                      30.62
+wal write                    8358      1.349153                      30.43
+wal file sync                8358      1.286437                      29.02
+query plan                   33439     0.439324                       9.91
+db file extend               54        0.000585                       0.01
+db file read                 31        0.000307                       0.01
+other lwlock acquire         0         0.000000                       0.00
+ProcArrayLock                0         0.000000                       0.00
+CLogControlLock              0         0.000000                       0.00
+(11 rows)
+```
+
+### Results
+
+The information displayed in the result set includes:
+
+| Column name | Description                                                              |
+| ----------- | -------------------------------------------------------------------------|
+| `WAIT NAME` | The name of the wait                                                     |
+| `COUNT`     | The number of times that the wait event occurred                         |
+| `WAIT TIME` | The time of the wait event in seconds                                    |
+| `% WAIT`    | The percentage of the total wait time used by this wait for this session |
+
+<div id="sess_rpt" class="registered_link"></div>
+
+## Retrieving session wait information (sess_rpt)
+
+The `sess_rpt()` function returns session wait information. The signature is:
+
+```sql
+sess_rpt(<beginning_id>, <ending_id>, <top_n>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`top_n`
+
+ The number of rows to return.
+
+This example shows a call to the `sess_rpt()` function:
+
+```sql
+SELECT * FROM sess_rpt(8, 9, 10);
+__OUTPUT__
+                                     sess_rpt
+-------------------------------------------------------------------------------------
+ID    USER       WAIT NAME                 COUNT TIME           % WAIT SES % WAIT ALL
+-------------------------------------------------------------------------------------
+3501 enterprise  wal flush                 8354  1.354958      30.61       30.61
+3501 enterprise  wal write                 8354  1.348192      30.46       30.46
+3501 enterprise  wal file sync             8354  1.285607      29.04       29.04
+3501 enterprise  query plan                33413 0.436901      9.87        9.87
+3501 enterprise  db file extend            54    0.000578      0.01        0.01
+3501 enterprise  db file read              56    0.000541      0.01        0.01
+3501 enterprise  ProcArrayLock             0     0.000000      0.00        0.00
+3501 enterprise  CLogControlLock           0     0.000000      0.00        0.00
+(10 rows)
+```
+
+### Results
+
+The information displayed in the result set includes:
+
+| Column name  | Description                                                                |
+| ------------ | -------------------------------------------------------------------------- |
+| `ID`         | The processID of the session                                               |
+| `USER`       | The name of the user incurring the wait                                    |
+| `WAIT NAME`  | The name of the wait event                                                 |
+| `COUNT`      | The number of times that the wait event occurred                           |
+| `TIME`       | The length of the wait event in seconds                                    |
+| `% WAIT SES` | The percentage of the total wait time used by this wait for this session   |
+| `% WAIT ALL` | The percentage of the total wait time used by this wait for all sessions   |
+
+<div id="sessid_rpt" class="registered_link"></div>
+
+## Retrieving ession ID information for a specified backend (sessid_rpt)
+
+The `sessid_rpt()` function returns session ID information for a specified backend. The signature is:
+
+```sql
+sessid_rpt(<beginning_id>, <ending_id>, <backend_id>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`backend_id`
+
+ An integer value that represents the backend identifier.
+
+This example shows a call to `sessid_rpt()`:
+
+```sql
+SELECT * FROM sessid_rpt(8, 9, 3501);
+__OUTPUT__
+                                     sessid_rpt
+-------------------------------------------------------------------------------------
+ID    USER       WAIT NAME                 COUNT  TIME          % WAIT SES % WAIT ALL
+-------------------------------------------------------------------------------------
+3501 enterprise CLogControlLock           0      0.000000      0.00       0.00
+3501 enterprise ProcArrayLock             0      0.000000      0.00       0.00
+3501 enterprise db file read              56     0.000541      0.01       0.01
+3501 enterprise db file extend            54     0.000578      0.01       0.01
+3501 enterprise query plan                33413  0.436901      9.87       9.87
+3501 enterprise wal file sync             8354   1.285607      29.04      29.04
+3501 enterprise wal write                 8354   1.348192      30.46      30.46
+3501 enterprise wal flush                 8354   1.354958      30.61      30.61
+(10 rows)
+```
+
+### Results
+
+The information displayed in the result set includes:
+
+| Column name  | Description                                                                |
+| ------------ | -------------------------------------------------------------------------- |
+| `ID`         | The process ID of the wait                                                 |
+| `USER`       | The name of the user that owns the session                                 |
+| `WAIT NAME`  | The name of the wait event                                                 |
+| `COUNT`      | The number of times that the wait event occurred                           |
+| `TIME`       | The length of the wait in seconds                                          |
+| `% WAIT SES` | The percentage of the total wait time used by this wait for this session   |
+| `% WAIT ALL` | The percentage of the total wait time used by this wait for all sessions   |
+
+<div id="sesshist_rpt" class="registered_link"></div>
+
+## Retrieving session wait information for a specified backend (sesshist_rpt)
+
+The `sesshist_rpt()` function returns session wait information for a specified backend. The signature is:
+
+```sql
+sesshist_rpt(<snapshot_id>, <session_id>)
+```
+
+### Parameters
+
+`snapshot_id`
+
+ An integer value that identifies the snapshot.
+
+`session_id`
+
+ An integer value that represents the session.
+
+This example shows a call to the `sesshist_rpt()` function:
+
+!!! Note
+    The example was shortened. Over 1300 rows are actually generated.
+
+```sql
+SELECT * FROM sesshist_rpt (9, 3501);
+__OUTPUT__
+                                    sesshist_rpt
+-----------------------------------------------------------------------------
+----------
+ ID    USER      SEQ   WAIT NAME      ELAPSED   File   Name                 #
+ of Blk   Sum of Blks
+-----------------------------------------------------------------------------
+---------
+ 3501 enterprise 1     query plan     13        0      N/A
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_password_history
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_password_history
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_password_history
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_profile
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_profile_name_ind
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_profile_oid_inde
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_profile_password
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_resource_group
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_resource_group_n
+0          0
+ 3501 enterprise 1     query plan     13        0      edb_resource_group_o
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_attribute
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_auth_members
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_auth_members_memb
+0          0
+ 3501 enterprise 1     query plan     13        0      pg_auth_members_role
+0          0
+                                       .
+                                       .
+                                       .
+ 3501 enterprise 2     wal flush      149       0      N/A
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_password_history
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_password_history
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_password_history
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_profile
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_profile_name_ind
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_profile_oid_inde
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_profile_password
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_resource_group
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_resource_group_n
+0          0
+ 3501 enterprise 2     wal flush      149       0      edb_resource_group_o
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_attribute
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_auth_members
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_auth_members_memb
+0          0
+ 3501 enterprise 2     wal flush      149       0      pg_auth_members_role
+0          0
+                                       .
+                                       .
+                                       .
+ 3501 enterprise 3     wal write      148       0      N/A
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_password_history
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_password_history
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_password_history
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_profile
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_profile_name_ind
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_profile_oid_inde
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_profile_password
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_resource_group
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_resource_group_n
+0          0
+ 3501 enterprise 3     wal write      148       0      edb_resource_group_o
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_attribute
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_attribute_relid_a
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_auth_members
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_auth_members_memb
+0          0
+ 3501 enterprise 3     wal write      148       0      pg_auth_members_role
+0          0
+                                       .
+                                       .
+                                       .
+ 3501 enterprise 24    wal write      130       0      pg_toast_1255
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_1255_index
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_2396
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_2396_index
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_2964
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_2964_index
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_3592
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_toast_3592_index
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_type
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_type_oid_index
+0          0
+ 3501 enterprise 24    wal write      130       0      pg_type_typname_nsp_
+0          0
+(1304 rows)
+```
+
+### Results
+
+The information displayed in the result set includes:
+
+| Column name   | Description                                                            |
+| ------------- | ---------------------------------------------------------------------- |
+| `ID`          | The system-assigned identifier of the wait                             |
+| `USER`        | The name of the user that incurred the wait                            |
+| `SEQ`         | The sequence number of the wait event                                  |
+| `WAIT NAME`   | The name of the wait event                                             |
+| `ELAPSED`     | The length of the wait event in microseconds                           |
+| `File`        | The relfilenode number of the file                                     |
+| `Name`        | If available, the name of the file name related to the wait event      |
+| `# of Blk`    | The block number read or written for a specific instance of the event  |
+| `Sum of Blks` | The number of blocks read                                              |
+
+<div id="purgesnap" class="registered_link"></div>
+
+## Purging a range of snapshots from the snapshot tables (purgesnap)
+
+The `purgesnap()` function purges a range of snapshots from the snapshot tables. The signature is:
+
+```sql
+purgesnap(<beginning_id>, <ending_id>)
+```
+
+### Parameters
+
+`beginning_id`
+
+ An integer value that represents the beginning session identifier.
+
+`ending_id`
+
+ An integer value that represents the ending session identifier.
+
+`purgesnap()` removes all snapshots between `beginning_id` and `ending_id`, inclusive:
+
+```sql
+SELECT * FROM purgesnap(6, 9);
+__OUTPUT__
+            purgesnap
+------------------------------------
+ Snapshots in range 6 to 9 deleted.
+(1 row)
+```
+
+A call to the `get_snaps()` function after executing the example shows that snapshots `6` through `9` were purged from the snapshot tables:
+
+```sql
+SELECT * FROM get_snaps();
+__OUTPUT__
+        get_snaps
+------------------------------
+ 1 25-JUL-18 09:49:04.224597
+ 2 25-JUL-18 09:49:09.310395
+ 3 25-JUL-18 09:49:14.378728
+ 4 25-JUL-18 09:49:19.448875
+ 5 25-JUL-18 09:49:24.52103
+ 10 25-JUL-18 09:49:49.855821
+ 11 25-JUL-18 09:49:54.919954
+ 12 25-JUL-18 09:49:59.987707
+(8 rows)
+```
+
+<div id="truncsnap" class="registered_link"></div>
+
+## Deleting records from the snapshot table (truncsnap)
+
+Use the truncsnap() function to delete all records from the snapshot table. The signature is:
+
+```sql
+truncsnap()
+```
+
+For example:
+
+```sql
+SELECT * FROM truncsnap();
+__OUTPUT__
+     truncsnap
+----------------------
+ Snapshots truncated.
+(1 row)
+```
+
+A call to the `get_snaps()` function after calling the `truncsnap()` function shows that all records were removed from the snapshot tables:
+
+```sql
+SELECT * FROM get_snaps();
+__OUTPUT__
+ get_snaps
+-----------
+(0 rows)
+```
diff --git a/product_docs/docs/epas/16/managing_performance/evaluating_wait_states.mdx b/product_docs/docs/epas/16/managing_performance/evaluating_wait_states.mdx
new file mode 100644
index 00000000000..6f6edcec858
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/evaluating_wait_states.mdx
@@ -0,0 +1,12 @@
+---
+title: "Evaluating wait states"
+description: "EDB wait states provides a way to capture wait events and other data for performance diagnosis"
+redirects:
+  - /epas/latest/epas_guide/13_performance_analysis_and_tuning/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Wait States is a tool for analyzing performance and tuning by allowing the collection and querying of wait event data. Wait events are recorded alongside other session activity and provide a snapshot of whether a session is waiting for I/O, CPU, IPC, locks, or timeouts. Snapshots of this information are gathered by the EDB Wait States background worker (BGW) at regular intervals. 
+
+The EDB Wait States interface allows you to control when and for how long the wait events are sampled and to extract the gathered samples in `edb_wait_states_data` for further analysis. By gathering this data over time, you can discover optimization opportunities and gain insight into what resources sessions are waiting on when performance is lower than expected.
+
+See [EDB Wait States](/pg_extensions/wait_states) for more information.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/managing_performance/index.mdx b/product_docs/docs/epas/16/managing_performance/index.mdx
new file mode 100644
index 00000000000..d11a1fa5c60
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/index.mdx
@@ -0,0 +1,12 @@
+---
+title: "Managing performance"
+indexCards: simple
+navigation:
+- 04_dynamic_runtime_instrumentation_tools_architecture_DRITA
+- query_advisor
+- using_dynatune
+- evaluating_wait_states
+- 03_sql_profiler
+---
+
+EDB Postgres Advanced Server extends Postgres with features designed to help database administrators manage performance. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/managing_performance/query_advisor.mdx b/product_docs/docs/epas/16/managing_performance/query_advisor.mdx
new file mode 100644
index 00000000000..3d63b6b6686
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/query_advisor.mdx
@@ -0,0 +1,6 @@
+---
+title: "EDB Query Advisor"
+description: "How to use the EDB Query Advisor utility to help determine the columns to index to improve performance in a given workload"
+---
+
+EDB Query Advisor is a Postgres extension that provides index recommendations by keeping statistics on predicates found in WHERE statements, JOIN clauses, and workload queries. It analyzes the cost-benefit to actual workload queries by replanning them with the hypothetical index. Hypothetical indexes are created based on the predicates collected from the workload queries. For more information, see [EDB Query Advisor](/pg_extensions/query_advisor/)
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/managing_performance/using_dynatune.mdx b/product_docs/docs/epas/16/managing_performance/using_dynatune.mdx
new file mode 100644
index 00000000000..af07517e15e
--- /dev/null
+++ b/product_docs/docs/epas/16/managing_performance/using_dynatune.mdx
@@ -0,0 +1,53 @@
+---
+title: "Using dynamic resource tuning"
+description: "Describes how to use the Dynatune feature to support dynamic tuning of the database server to make the optimal use of available system resources"
+---
+
+EDB Postgres Advanced Server supports dynamic tuning of the database server to make the optimal use of the system resources available on the host machine where it's installed. The two parameters that control this functionality are located in the `postgresql.conf` file. These parameters are:
+
+-   `edb_dynatune`
+-   `edb_dynatune_profile`
+
+<div id="edb_dynatune-1" class="registered_link"></div>
+
+## Implementing dynamic tuning
+
+`edb_dynatune` determines how much of the host system's resources for the database server to use. It bases the determination on the host machine's total available resources and the intended use of the host machine.
+
+When EDB Postgres Advanced Server is first installed, you set the `edb_dynatune` parameter according to the host machine's use as a development machine, mixed-use machine, or dedicated server. For most purposes, the database administrator doesn't need to adjust the configuration parameters in the `postgresql.conf` file to improve performance.
+
+Here are some things to keep in mind when setting up dynamic tuning:
+
+- You can change the value of the `edb_dynatune` parameter after the initial installation of EDB Postgres Advanced Server by editing the `postgresql.conf` file. You must restart the postmaster for the new configuration to take effect.
+
+- You can set the `edb_dynatune` parameter to any integer value from 0 to 100. A value of 0 turns off the dynamic tuning feature, leaving the database server resource use under the control of the other configuration parameters in the `postgresql.conf` file.
+
+- A low, non-zero value, that is, 1&ndash;33, dedicates the least amount of the host machine's resources to the database server. Use this setting for a development machine where many other applications are being used.
+
+- A value in the range of 34&ndash;66 dedicates a moderate amount of resources to the database server. You might use this setting for a dedicated application server that has a fixed number of other applications running on the same machine as EDB Postgres Advanced Server.
+
+- The highest values, that is, 67&ndash;100, dedicate most of the server's resources to the database server. Use this setting for a host machine that's totally dedicated to running EDB Postgres Advanced Server.
+
+## Changing parameter values
+
+After you select a value for `edb_dynatune`, you can further fine-tune database server performance by adjusting the other configuration parameters in the `postgresql.conf` file. Any adjusted setting overrides the corresponding value chosen by `edb_dynatune`. 
+
+To change the value of a parameter: 
+
+1.  Uncomment the configuration parameter. 
+1.  Specify the desired value.
+1.  Restart the database server.
+
+<div id="edb_dynatune_profile-1" class="registered_link"></div>
+
+## Controlling tuning behavior
+
+Use the `edb_dynatune_profile` parameter to control tuning aspects based on the expected workload profile on the database server. This parameter takes effect when you start the database server.
+
+The table shows the possible values for `edb_dynatune_profile`.
+
+| Value       | Usage                                                                                             |
+| ----------- | ------------------------------------------------------------------------------------------------- |
+| `oltp`      | Recommended when the database server is processing heavy online transaction processing workloads. |
+| `reporting` | Recommended for database servers used for heavy data reporting.                                   |
+| `mixed`     | Recommended for servers that provide a mix of transaction processing and data reporting.          |
diff --git a/product_docs/docs/epas/16/planning/configuration_mode.mdx b/product_docs/docs/epas/16/planning/configuration_mode.mdx
new file mode 100644
index 00000000000..d2543241515
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/configuration_mode.mdx
@@ -0,0 +1,18 @@
+---
+title: "Choosing the configuration mode"
+description: "Describes how to choose the configuration mode in which you want EDB Postgres Advanced Server to run"
+---
+
+Moving to the cloud can be a challenge, especially if you’re migrating Oracle applications to Postgres in the cloud.
+
+Whether your goal is to reduce database management costs, increase business agility, jumpstart cloud innovation or modernize your data infrastructure, EDB Postgres Advanced Server is the solution specifically designed to assist your migration. EDB Postgres Advanced Server includes feature-rich tools and enhancements that help you maintain, secure, and operate your database environment.
+
+EDB Postgres Advanced Server also has a significant amount of Oracle compatibility features which facilitate Oracle to Postgres migrations. When configured to run in Oracle mode, EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications, as well as compatible procedural logic, data types, system catalog views and other features that enable EDB’s Oracle compatible connectors, EDB\*Plus, EDB\*Loader as well as other functionality. 
+
+When you initialize your EDB Postgres Advanced Server cluster [using the `initdb` command](../installing/linux_install_details/managing_an_advanced_server_installation.mdx), you can choose whether or not to include these compatibility features by specifying a configuration mode. 
+
+There are two options for the configuration mode:
+
+-   Specify the `no-redwood-compat` option to create the cluster in *Postgres mode*. When the cluster is created in PostgreSQL mode, it includes all of the advanced features that help you [maintain](../database_administration/), [secure](../epas_security_guide), and [operate](../managing_performance/) your database environment. While some EDB Postgres Advanced Server features compatible with Oracle databases are available with this mode, such as Oracle style packages and collections, we recommend using the EDB Postgres Advanced Server in redwood compatibility mode if you are implementing an Oracle to Postgres migration.
+
+-   Specify the `redwood-like` option to create the cluster in *Oracle compatibility mode*. This mode enables all of the rich Oracle compatibility features to help you facilitate your Oracle to Postgres migration. These features include Oracle compatible custom data types, keywords, functions, and catalog views. You can find details about these features in [Working with Oracle data](../working_with_oracle_data/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/planning/deployment_options/index.mdx b/product_docs/docs/epas/16/planning/deployment_options/index.mdx
new file mode 100644
index 00000000000..bd844170ab0
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/deployment_options/index.mdx
@@ -0,0 +1,14 @@
+---
+title: "Deployment options"
+description: "How to plan the installation and deployment of EDB Postgres Advanced Server"
+redirects:
+  - /epas/latest/deployment_options/
+---
+
+You can deploy and install EDB products using the following methods:
+
+-   [EDB Postgres AI Cloud Service](/edb-postgres-ai/cloud-service/) is a fully managed database-as-a-service with built-in Oracle compatibility, running in your cloud account and operated by the Postgres experts. Cloud Service makes it easy to set up, manage, and scale your databases. Provision PostgreSQL or EDB Postgres Advanced Server with Oracle compatibility.
+
+-   [EDB PostgreSQL for Kubernetes](/postgres_for_kubernetes/latest/) is an operator designed by EnterpriseDB to manage PostgreSQL workloads on any supported Kubernetes cluster running in private, public, hybrid, or multi-cloud environments. EDB PostgreSQL for Kubernetes adheres to DevOps principles and concepts such as declarative configuration and immutable infrastructure.
+
+-   [Installation using native packages or installers](../../installing)
diff --git a/product_docs/docs/epas/16/planning/index.mdx b/product_docs/docs/epas/16/planning/index.mdx
new file mode 100644
index 00000000000..7a426872ecb
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/index.mdx
@@ -0,0 +1,6 @@
+---
+title: "Planning"
+indexCards: simple
+---
+
+The process for planning the implementation or deployment of EDB Postgres Advanced Server includes several activities:
diff --git a/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
new file mode 100644
index 00000000000..6af15f2f842
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_limitations/index.mdx
@@ -0,0 +1,11 @@
+---
+title: "Limitations"
+description: "Identifies the limitations to consider when implementing EDB Postgres Advanced Server"
+redirects:
+  - /epas/latest/epas_limitations/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The following limitations apply when implementing EDB Postgres Advanced Server:
+
+-   EDB recommends you don't store the `data` directory of a production database on an NFS file system. If you plan to go against this recommendation, see the [19.2.2.1. NFS](https://www.postgresql.org/docs/14/creating-cluster.html#CREATING-CLUSTER-FILESYSTEM) section in the PostgreSQL documentation for guidance about configuration.
+-   The LLVM JIT package is supported only on RHEL x86. 
diff --git a/product_docs/docs/epas/16/planning/planning_prerequisites/epas_requirements/index.mdx b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_requirements/index.mdx
new file mode 100644
index 00000000000..86645c4c395
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/planning_prerequisites/epas_requirements/index.mdx
@@ -0,0 +1,56 @@
+---
+title: Requirements
+description: "Identifies the hardware and software requirements for EDB Postgres Advanced Server installations"
+redirects:
+  - /epas/latest/epas_requirements/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server has certain hardware and software requirements. PostgreSQL has some hard limits that are important to know about during your planning.
+
+## Hardware requirements
+
+The following installation requirements assume that you selected the default options during the installation process. The minimum hardware requirements to install and run EDB Postgres Advanced Server are:
+
+-   1 GHz processor
+-   2 GB of RAM
+-   512 MB of HDD
+
+Additional disk space is required for data or supporting components.
+
+## Software requirements
+
+### User privileges
+
+To perform an EDB Postgres Advanced Server installation on a Linux system you need superuser, administrator, or sudo privileges.
+
+To perform an EDB Postgres Advanced Server installation on a Windows system, you need administrator privileges. If you're installing EDB Postgres Advanced Server on a Windows system that's configured with **User Account Control** enabled, you can assume the privileges required to invoke the graphical installer. Right-click the name of the installer, and select **Run as administrator** from the context menu.
+
+### Windows-specific software requirements
+
+Apply the Windows operating system updates before invoking the installer. If the installer encounters errors during the installation process, exit the installation, and ensure that your Windows version is up to date. Then restart the installer.
+
+See the [release notes](../../../epas_rel_notes) for the features added in EDB Postgres Advanced Server 16.
+
+
+## Hard limits
+
+The following table describes various hard limits of PostgreSQL. However, practical limits such as performance limitations or available disk space might apply before absolute hard limits are reached.
+
+| Item                     | Upper limit                                                           | Comment                                                                |
+| ------------------------ | --------------------------------------------------------------------- | ---------------------------------------------------------------------- |
+| `database size`          | unlimited                                                             |                                                                        |
+| `number of databases`    | 4,294,950,911                                                         |                                                                        |
+| `relations per database` | 1,431,650,303                                                         |                                                                        |
+| `relation size`          | 32 TB                                                                 | with the default BLCKSZ of 8192 bytes                                  |
+| `rows per table`         | limited by the number of tuples that can fit onto 4,294,967,295 pages |                                                                        |
+| `columns per table`      | 1600                                                                  | further limited by tuple size fitting on a single page; see note below |
+| `field size`             | 1 GB                                                                  |                                                                        |
+| `identifier length`      | 63 bytes                                                              | can be increased by recompiling PostgreSQL                             |
+| `indexes per table`      | unlimited                                                             | constrained by maximum relations per database                          |
+| `columns per index`      | 32                                                                    | can be increased by recompiling PostgreSQL                             |
+| `partition keys`         | 32                                                                    | can be increased by recompiling PostgreSQL                             |
+
+!!! Note
+    -   The maximum number of columns for a table is further reduced as the tuple being stored must fit in a single 8192-byte heap page. For example, excluding the tuple header, a tuple made up of 1600 `int` columns consumes 6400 bytes and can be stored in a heap page. But a tuple of 1600 `bigint` columns consumes 12800 bytes and therefore doesn't fit inside a heap page. Variable-length fields of types such as `text`, `varchar`, and `char` can have their values stored out of line in the table's `TOAST` table when the values are large enough to require it. Only an 18-byte pointer must remain inside the tuple in the table's heap. For shorter length variable-length fields, either a 4-byte or 1-byte field header is used, and the value is stored inside the heap tuple.
+
+    -   Columns that were dropped from the table also contribute to the maximum column limit. Moreover, although the dropped column values for newly created tuples are internally marked as null in the tuple's null bitmap, the null bitmap also occupies space.
diff --git a/product_docs/docs/epas/16/planning/planning_prerequisites/index.mdx b/product_docs/docs/epas/16/planning/planning_prerequisites/index.mdx
new file mode 100644
index 00000000000..2cdff85d061
--- /dev/null
+++ b/product_docs/docs/epas/16/planning/planning_prerequisites/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "Planning prerequisites"
+indexCards: simple
+description: "An overview of the requirements for a EDB Postgres Advanced Server installation"
+---
+
+Follow these requirements and considerations before deploying EDB Postgres Advanced Server.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/01_all_part_tables.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/01_all_part_tables.mdx
new file mode 100644
index 00000000000..4cf35b8aee7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/01_all_part_tables.mdx
@@ -0,0 +1,39 @@
+---
+title: "ALL_PART_TABLES"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/01_all_part_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_part_tables" class="registered_link"></div>
+
+The following table lists the information available in the `ALL_PART_TABLES` view.
+
+| Column                      | Type                      | Description                                              |
+| --------------------------- | ------------------------- | -------------------------------------------------------- |
+| `owner`                     | `name`                    | The owner of the table.                                  |
+| `schema_name`               | `name`                    | The schema in which the table resides.                   |
+| `table_name`                | `name`                    | The name of the table.                                   |
+| `partitioning_type`         | `text`                    | RANGE, LIST, or HASH.                                    |
+| `subpartitioning_type`      | `text`                    | RANGE, LIST, HASH, or NONE.                              |
+| `partition_count`           | `bigint`                  | The number of partitions.                                |
+| `def_subpartition_count`    | `integer`                 | The default subpartition count. This value is always 0.  |
+| `partitioning_key_count`    | `integer`                 | The number of columns listed in the partition by clause. |
+| `subpartitioning_key_count` | `integer`                 | The number of columns in the subpartition by clause.     |
+| `status`                    | `character varying(8)`    | This column is always VALID.                        |
+| `def_tablespace_name`       | `character varying(30)`   | This column is always NULL.                         |
+| `def_pct_free`              | `numeric`                 | This column is always NULL.                         |
+| `def_pct_used`              | `numeric`                 | This column is always NULL.                         |
+| `def_ini_trans`             | `numeric`                 | This column is always NULL.                         |
+| `def_max_trans`             | `numeric`                 | This column is always NULL.                         |
+| `def_initial_extent`        | `character varying(40)`   | This column is always NULL.                         |
+| `def_next_extent`           | `character varying(40)`   | This column is always NULL.                         |
+| `def_min_extents`           | `character varying(40)`   | This column is always NULL.                         |
+| `def_max_extents`           | `character varying(40)`   | This column is always NULL.                         |
+| `def_pct_increase`          | `character varying(40)`   | This column is always NULL.                         |
+| `def_freelists`             | `numeric`                 | This column is always NULL.                         |
+| `def_freelist_groups`       | `numeric`                 | This column is always NULL.                         |
+| `def_logging`               | `character varying(7)`    | This column is always YES.                          |
+| `def_compression`           | `character varying(8)`    | This column is always NONE.                         |
+| `def_buffer_pool`           | `character varying(7)`    | This column is always DEFAULT.                      |
+| `ref_ptn_constraint_name`   | `character varying(30)`   | This column is always NULL.                         |
+| `interval`                  | `character varying(1000)` | This column is always NULL.                         |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/02_all_tab_partitions.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/02_all_tab_partitions.mdx
new file mode 100644
index 00000000000..883f68272d8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/02_all_tab_partitions.mdx
@@ -0,0 +1,47 @@
+---
+title: "ALL_TAB_PARTITIONS"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/02_all_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_tab_partitions" class="registered_link"></div>
+
+The following table lists the information available in the `ALL_TAB_PARTITIONS` view.
+
+| Column               | Type                          | Description                                                            |
+| -------------------- | ----------------------------- | ---------------------------------------------------------------------- |
+| `table_owner`        | `name`                        | The owner of the table.                                                |
+| `schema_name`        | `name`                        | The schema in which the table resides.                                 |
+| `table_name`         | `name`                        | The name of the table.                                                 |
+| `composite`          | `text`                        | YES if the table is subpartitioned; NO if it is not subpartitioned.    |
+| `partition_name`     | `name`                        | The name of the partition.                                             |
+| `subpartition_count` | `bigint`                      | The number of subpartitions for this partition.                        |
+| `high_value`         | `text`                        | The high partitioning value specified in the `CREATE TABLE` statement. |
+| `high_value_length`  | `integer`                     | The length of high partitioning value.                                 |
+| `partition_position` | `integer`                     | The ordinal position of this partition.                                |
+| `tablespace_name`    | `name`                        | The tablespace in which this partition resides.                        |
+| `pct_free`           | `numeric`                     | This column is always 0.                                          |
+| `pct_used`           | `numeric`                     | This column is always 0.                                          |
+| `ini_trans`          | `numeric`                     | This column is always 0.                                          |
+| `max_trans`          | `numeric`                     | This column is always 0.                                          |
+| `initial_extent`     | `numeric`                     | This column is always NULL.                                       |
+| `next_extent`        | `numeric`                     | This column is always NULL.                                       |
+| `min_extent`         | `numeric`                     | This column is always 0.                                          |
+| `max_extent`         | `numeric`                     | This column is always 0.                                          |
+| `pct_increase`       | `numeric`                     | This column is always 0.                                          |
+| `freelists`          | `numeric`                     | This column is always NULL.                                       |
+| `freelist_groups`    | `numeric`                     | This column is always NULL.                                       |
+| `logging`            | `character varying(7)`        | This column is always YES.                                        |
+| `compression`        | `character varying(8)`        | This column is always NONE.                                       |
+| `num_rows`           | `numeric`                     | The approx. number of rows in this partition.                          |
+| `blocks`             | `integer`                     | The approx. number of blocks in this partition.                        |
+| `empty_blocks`       | `numeric`                     | This column is always NULL.                                       |
+| `avg_space`          | `numeric`                     | This column is always NULL.                                       |
+| `chain_cnt`          | `numeric`                     | This column is always NULL.                                       |
+| `avg_row_len`        | `numeric`                     | This column is always NULL.                                       |
+| `sample_size`        | `numeric`                     | This column is always NULL.                                       |
+| `last_analyzed`      | `timestamp without time zone` | This column is always NULL.                                       |
+| `buffer_pool`        | `character varying(7)`        | This column is always NULL.                                       |
+| `global_stats`       | `character varying(3)`        | This column is always YES.                                        |
+| `user_stats`         | `character varying(3)`        | This column is always NO.                                         |
+| `backing_table`      | `regclass`                    | OID of the backing table for this partition.                           |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/03_all_tab_subpartitions.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/03_all_tab_subpartitions.mdx
new file mode 100644
index 00000000000..222716ede92
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/03_all_tab_subpartitions.mdx
@@ -0,0 +1,46 @@
+---
+title: "ALL_TAB_SUBPARTITIONS"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/03_all_tab_subpartitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_tab_subpartitions" class="registered_link"></div>
+
+The following table lists the information available in the `ALL_TAB_SUBPARTITIONS` view.
+
+| Column                  | Type                          | Description                                                            |
+| ----------------------- | ----------------------------- | ---------------------------------------------------------------------- |
+| `table_owner`           | `name`                        | The name of the owner of the table.                                    |
+| `schema_name`           | `name`                        | The name of the schema in which the table resides.                     |
+| `table_name`            | `name`                        | The name of the table.                                                 |
+| `partition_name`        | `name`                        | The name of the partition.                                             |
+| `subpartition_name`     | `name`                        | The name of the subpartition.                                          |
+| `high_value`            | `text`                        | The high partitioning value specified in the `CREATE TABLE` statement. |
+| `high_value_length`     | `integer`                     | The length of high partitioning value.                                 |
+| `subpartition_position` | `integer`                     | The ordinal position of this subpartition.                             |
+| `tablespace_name`       | `name`                        | The tablespace in which this subpartition resides.                     |
+| `pct_free`              | `numeric`                     | This column is always 0.                                          |
+| `pct_used`              | `numeric`                     | This column is always 0.                                          |
+| `ini_trans`             | `numeric`                     | This column is always 0.                                          |
+| `max_trans`             | `numeric`                     | This column is always 0.                                          |
+| `initial_extent`        | `numeric`                     | This column is always NULL.                                       |
+| `next_extent`           | `numeric`                     | This column is always NULL.                                       |
+| `min_extent`            | `numeric`                     | This column is always 0.                                          |
+| `max_extent`            | `numeric`                     | This column is always 0.                                          |
+| `pct_increase`          | `numeric`                     | This column is always 0.                                          |
+| `freelists`             | `numeric`                     | This column is always NULL.                                       |
+| `freelist_groups`       | `numeric`                     | This column is always NULL.                                       |
+| `logging`               | `character varying(7)`        | This column is always YES.                                        |
+| `compression`           | `character varying(8)`        | This column is always NONE.                                       |
+| `num_rows`              | `numeric`                     | The approx. number of rows in this subpartition.                       |
+| `blocks`                | `integer`                     | The approx. number of blocks in this subpartition.                     |
+| `empty_blocks`          | `numeric`                     | This column is always NULL.                                       |
+| `avg_space`             | `numeric`                     | This column is always NULL.                                       |
+| `chain_cnt`             | `numeric`                     | This column is always NULL.                                       |
+| `avg_row_len`           | `numeric`                     | This column is always NULL.                                       |
+| `sample_size`           | `numeric`                     | This column is always NULL.                                       |
+| `last_analyzed`         | `timestamp without time zone` | This column is always NULL.                                       |
+| `buffer_pool`           | `character varying(7)`        | This column is always NULL.                                       |
+| `global_stats`          | `character varying(3)`        | This column is always YES.                                        |
+| `user_stats`            | `character varying(3)`        | This column is always NO.                                         |
+| `backing_table`         | `regclass`                    | OID of the backing table for this subpartition.                        |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/04_all_part_key_columns.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/04_all_part_key_columns.mdx
new file mode 100644
index 00000000000..c64461ddb4a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/04_all_part_key_columns.mdx
@@ -0,0 +1,18 @@
+---
+title: "ALL_PART_KEY_COLUMNS"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/04_all_part_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_part_key_columns" class="registered_link"></div>
+
+The following table lists the information available in the `ALL_PART_KEY_COLUMNS` view.
+
+| Column            | Type           | Description                                                                                                                                            |
+| ----------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `owner`           | `name`         | The name of the table owner.                                                                                                                           |
+| `schema_name`     | `name`         | The name of the schema on which the table resides.                                                                                                     |
+| `name`            | `name`         | The name of the table.                                                                                                                                 |
+| `object_type`     | `character(5)` | This column is always `TABLE`.                                                                                                                    |
+| `column_name`     | `name`         | The name of the partitioning key column.                                                                                                               |
+| `column_position` | `integer`      | The position of this column in the partitioning key. The first column has a column position of 1, the second column has a column position of 2, and so on. |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/05_all_subpart_key_columns.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/05_all_subpart_key_columns.mdx
new file mode 100644
index 00000000000..62f7faaad0b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/05_all_subpart_key_columns.mdx
@@ -0,0 +1,18 @@
+---
+title: "ALL_SUBPART_KEY_COLUMNS"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/05_all_subpart_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_subpart_key_columns" class="registered_link"></div>
+
+The following table lists the information available in the `ALL_SUBPART_KEY_COLUMNS` view.
+
+| Column            | Type           | Description                                                                                                                                               |
+| ----------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`           | `name`         | The name of the table owner.                                                                                                                              |
+| `schema_name`     | `name`         | The name of the schema on which the table resides.                                                                                                        |
+| `name`            | `name`         | The name of the table.                                                                                                                                    |
+| `object_type`     | `character(5)` | This column is always `TABLE`.                                                                                                                       |
+| `column_name`     | `name`         | The name of the partitioning key column.                                                                                                                  |
+| `column_position` | `integer`      | The position of this column within the subpartitioning key (the first column has a column position of 1, the second column has a column position of 2...) |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/index.mdx
new file mode 100644
index 00000000000..47350f6656d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/01_table_partitioning_views_reference/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Table partitioning views reference"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.121.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.346.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.070.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/07_retrieving_information_about_a_partitioned_table/01_table_partitioning_views_reference/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="table_partitioning_views_reference" class="registered_link"></div>
+
+Query the catalog views that are compatible with Oracle databases to review detailed information about your partitioned tables.
+
+<div class="toctree" maxdepth="3">
+
+all_part_tables all_tab_partitions all_tab_subpartitions all_part_key_columns all_subpart_key_columns
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/03_system_catalog_tables.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/03_system_catalog_tables.mdx
new file mode 100644
index 00000000000..9a898ca6f26
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/03_system_catalog_tables.mdx
@@ -0,0 +1,135 @@
+---
+title: "System catalog tables"
+description: "Provides descriptions of the supported system catalog tables"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.73.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.202.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.195.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.192.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.194.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.203.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.193.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.198.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.200.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.201.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.199.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.302.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.255.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.250.html"
+redirects:
+  - /epas/latest/epas_compat_reference/03_system_catalog_tables/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../epas_guide/16_system_catalog_tables/
+---
+
+<div id="system_catalog_tables" class="registered_link"></div>
+
+The following system catalog tables contain definitions of database objects. The layout of the system tables is subject to change. If you're writing an application that depends on information stored in the system tables, use an existing catalog view or create a catalog view to isolate the application from changes to the system table.
+
+## dual
+
+`dual` is a single-row, single-column table that's provided only for compatibility with Oracle databases.
+
+| Column  | Type          | Modifiers | Description                      |
+| ------- | ------------- | --------- | -------------------------------- |
+| `dummy` | `VARCHAR2(1)` |           | Provided for compatibility only. |
+
+## edb_dir
+
+The `edb_dir` table contains one row for each alias that points to a directory created with the `CREATE DIRECTORY` command. A directory is an alias for a pathname that allows a user limited access to the host file system.
+
+You can use a directory to fence a user into a specific directory tree in the file system. For example, the `UTL_FILE` package offers functions that allow a user to read and write files and directories in the host file system. However, it allows access only to paths that the database administrator has granted access to by way of a `CREATE DIRECTORY` command.
+
+| Column     | Type        | Modifiers  | Description                                                               |
+| ---------- | ----------- | ---------- | ------------------------------------------------------------------------- |
+| `dirname`  | `"name"`    | `not null` | The name of the alias.                                                    |
+| `dirowner` | `oid`       | `not null` | The `OID` of the user that owns the alias.                                |
+| `dirpath`  | `text`      |            | The directory name to which access is granted.                            |
+| `diracl`   | `aclitem[]` |            | The access control list that determines the users who can access the alias. |
+
+## edb_password_history
+
+The `edb_password_history` table contains one row for each password change. The table is shared across all databases in a cluster.
+
+| Column                  | Type          | References      | Description                          |
+| ----------------------- | ------------- | --------------- | ------------------------------------ |
+| `passhistroleid`        | `oid`         | `pg_authid.oid` | The `ID` of a role.                  |
+| `passhistpassword`      | `text`        |                 | Role password in md5 encrypted form. |
+| `passhistpasswordsetat` | `timestamptz` |                 | The time the password was set.       |
+
+## edb_policy
+
+The `edb_policy` table contains one row for each policy.
+
+| Column              | Type         | Modifiers  | Description                                                                                                        |
+| ------------------- | ------------ | ---------- | ------------------------------------------------------------------------------------------------------------------ |
+| `policyname`        | `name`       | `not null` | The policy name.                                                                                                   |
+| `policygroup`       | `oid`        | `not null` | Currently unused.                                                                                                  |
+| `policyobject`      | `oid`        | `not null` | The `OID` of the table secured by this policy (the `object_schema` plus the `object_name`).                        |
+| `policykind`        | `char`       | `not null` | The kind of object secured by this policy: 'r' for a table, 'v' for a view, = for a synonym. Currently always 'r'. |
+| `policyproc`        | `oid`        | `not null` | The `OID` of the policy function (`function_schema` plus `policy_function`).                                       |
+| `policyinsert`      | `boolean`    | `not null` | True if the policy is enforced by `INSERT` statements.                                                             |
+| `policyselect`      | `boolean`    | `not null` | True if the policy is enforced by `SELECT` statements.                                                             |
+| `policydelete`      | `boolean`    | `not null` | True if the policy is enforced by `DELETE` statements.                                                             |
+| `policyupdate`      | `boolean`    | `not null` | True if the policy is enforced by `UPDATE` statements.                                                             |
+| `policyindex`       | `boolean`    | `not null` | Currently unused.                                                                                                  |
+| `policyenabled`     | `boolean`    | `not null` | True if the policy is enabled.                                                                                     |
+| `policyupdatecheck` | `boolean`    | `not null` | True if rows updated by an `UPDATE` statement must satisfy the policy.                                             |
+| `policystatic`      | `boolean`    | `not null` | Currently unused.                                                                                                  |
+| `policytype`        | `integer`    | `not null` | Currently unused.                                                                                                  |
+| `policyopts`        | `integer`    | `not null` | Currently unused.                                                                                                  |
+| `policyseccols`     | `int2vector` | `not null` | The column numbers for columns listed in `sec_relevant_cols`.                                                      |
+
+## edb_profile
+
+The `edb_profile` table stores information about the available profiles. `edb_profiles` is shared across all databases in a cluster.
+
+| Column                    | Type      | References        | Description                                                                                                                                                                                                      |
+| ------------------------- | --------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `oid`                     | `oid`     |                   | Row identifier (hidden attribute. Must be explicitly selected).                                                                                                                                                  |
+| `prfname`                 | `name`    |                   | The name of the profile.                                                                                                                                                                                         |
+| `prffailedloginattempts`  | `integer` |                   | The number of failed login attempts allowed by the profile. -1 indicates to use the value from the default profile. -2 indicates no limit on failed login attempts.                                 |
+| `prfpasswordlocktime`     | `integer` |                   | The password lock time associated with the profile, in seconds. -1 indicates to use the value from the default profile. -2 indicates to lock the account permanently.                |
+| `prfpasswordlifetime`     | `integer` |                   | The password lifetime associated with the profile, in seconds. -1 indicates to use the value from the default profile. -2 indicates that the password never expires.                              |
+| `prfpasswordgracetime`    | `integer` |                   | The password grace time associated with the profile, in seconds. -1 indicates to use the value from the default profile. -2 indicates that the password never expires.                             |
+| `prfpasswordreusetime`    | `integer` |                   | The number of seconds that a user must wait before reusing a password. -1 indicates to use the value from the default profile. -2 indicates that the old passwords can never be reused.             |
+| `prfpasswordreusemax`     | `integer` |                   | The number of password changes that have to occur before a password can be reused. -1 indicates to use the value from the default profile. -2 indicates that the old passwords can never be reused. |
+| `prfpasswordallowhashed`  | `integer` |                   | Specifies whether an encrypted password is allowed for use. The possible values are `true/on/yes/1`, `false/off/no/0`, and `DEFAULT`.                           |
+| `prfpasswordverifyfuncdb` | `oid`     | `pg_database.oid` | The `OID` of the database in which the password verify function exists.                                                                                                                                          |
+| `prfpasswordverifyfunc`   | `oid`     | `pg_proc.oid`     | The `OID` of the password verify function associated with the profile.                                                                                                                                           |
+
+## edb_variable
+
+The `edb_variable` table contains one row for each package level variable (each variable declared in a package).
+
+| Column       | Type       | Modifiers  | Description                                                                                                                                                                                                                           |
+| ------------ | ---------- | ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `varname`    | `"name"`   | `not null` | The name of the variable.                                                                                                                                                                                                             |
+| `varpackage` | `oid`      | `not null` | The `OID` of the `pg_namespace` row that stores the package.                                                                                                                                                                          |
+| `vartype`    | `oid`      | `not null` | The `OID` of the `pg_type` row that defines the type of the variable.                                                                                                                                                                 |
+| `varaccess`  | `"char"`   | `not null` | `+` if the variable is visible outside of the package. `-` if the variable is visible only in the package. Note: Public variables are declared in the package header. Private variables are declared in the package body. |
+| `varsrc`     | `text`     |            | Contains the source of the variable declaration, including any default value expressions for the variable.                                                                                                                            |
+| `varseq`     | `smallint` | `not null` | The order in which the variable was declared in the package.                                                                                                                                                                          |
+
+## pg_synonym
+
+The `pg_synonym` table contains one row for each synonym created with the `CREATE SYNONYM` command or `CREATE PUBLIC SYNONYM` command.
+
+| Column         | Type     | Modifiers  | Description                                                                                    |
+| -------------- | -------- | ---------- | ---------------------------------------------------------------------------------------------- |
+| `synname`      | `"name"` | `not null` | The name of the synonym.                                                                       |
+| `synnamespace` | `oid`    | `not null` | Replaces `synowner`. Contains the `OID` of the `pg_namespace` row where the synonym is stored. |
+| `synowner`     | `oid`    | `not null` | The `OID` of the user that owns the synonym.                                                   |
+| `synobjschema` | `"name"` | `not null` | The schema in which the referenced object is defined.                                          |
+| `synobjname`   | `"name"` | `not null` | The name of the referenced object.                                                             |
+| `synlink`      | `text`   |            | The optional name of the database link in which the referenced object is defined.            |
+
+## product_component_version
+
+The `product_component_version` table contains information about feature compatibility. An application can query this table during installation or at runtime to verify that features used by the application are available with this deployment.
+
+| Column    | Type                     | Description                        |
+| --------- | ------------------------ | ---------------------------------- |
+| `product` | `character varying (74)` | The name of the product.           |
+| `version` | `character varying (74)` | The version number of the product. |
+| `status`  | `character varying (74)` | The status of the release.         |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/c_preprocessor_directives.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/c_preprocessor_directives.mdx
new file mode 100644
index 00000000000..d84929cc9c8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/c_preprocessor_directives.mdx
@@ -0,0 +1,129 @@
+---
+title: "C-preprocessor directives"
+---
+
+The ECPGPlus C-preprocessor enforces two behaviors that depend on the mode in which you invoke ECPGPlus:
+
+-   `PROC` mode
+-   Non-`PROC` mode
+
+## Compiling in PROC mode
+
+In `PROC` mode, ECPGPlus allows you to:
+
+-   Declare host variables outside of an `EXEC SQL BEGIN/END DECLARE SECTION`.
+-   Use any C variable as a host variable as long as its data type is compatible with ECPG.
+
+When you invoke ECPGPlus in `PROC` mode (by including the `-C PROC` keywords), the ECPG compiler honors the following C-preprocessor directives:
+
+```c
+#include
+#if expression
+#ifdef symbolName
+#ifndef symbolName
+#else
+#elif expression
+#endif
+#define symbolName expansion
+#define symbolName([macro arguments]) expansion
+#undef symbolName
+#defined(symbolName)
+```
+
+Preprocessor directives are used to affect or direct the code that's received by the compiler. For example, consider the following code sample:
+
+```c
+#if HAVE_LONG_LONG == 1
+#define BALANCE_TYPE long long
+#else
+#define BALANCE_TYPE double
+#endif
+...
+BALANCE_TYPE customerBalance;
+```
+
+Suppose you invoke ECPGPlus with the following command-line arguments:
+
+```shell
+ecpg –C PROC –DHAVE_LONG_LONG=1
+```
+
+ECPGPlus copies the entire fragment, without change, to the output file. It sends only the following tokens to the ECPG parser:
+
+```shell
+long long customerBalance;
+```
+
+On the other hand, suppose you invoke ECPGPlus with the following command-line arguments:
+
+```shell
+ecpg –C PROC –DHAVE_LONG_LONG=0
+```
+
+The ECPG parser receives the following tokens:
+
+```shell
+double customerBalance;
+```
+
+If your code uses preprocessor directives to filter the code that's sent to the compiler, the complete code is retained in the original code, while the ECPG parser sees only the processed token stream.
+
+You can also use compatible syntax when executing the following preprocessor directives with an `EXEC` directive:
+
+```sql
+EXEC ORACLE DEFINE
+EXEC ORACLE UNDEF
+EXEC ORACLE INCLUDE
+EXEC ORACLE IFDEF
+EXEC ORACLE IFNDEF
+EXEC ORACLE ELIF
+EXEC ORACLE ELSE
+EXEC ORACLE ENDIF
+EXEC ORACLE OPTION
+```
+
+For example, suppose your code includes the following:
+
+```sql
+EXEC ORACLE IFDEF HAVE_LONG_LONG;
+#define BALANCE_TYPE long long
+EXEC ORACLE ENDIF;
+BALANCE_TYPE customerBalance;
+```
+
+You invoke ECPGPlus with the following command-line arguments:
+
+```shell
+ecpg –C PROC DEFINE=HAVE_LONG_LONG=1
+```
+
+ECPGPlus sends the following tokens to the output file and the ECPG parser:
+
+```c
+long long customerBalance;
+```
+
+!!! Note
+    The `EXEC ORACLE` preprocessor directives work only if you specify `-C PROC` on the ECPG command line.
+
+## Using the SELECT_ERROR precompiler option
+
+When using ECPGPlus in compatible mode, you can use the `SELECT_ERROR` precompiler option to tell your program how to handle result sets that contain more rows than the host variable can accommodate. The syntax is:
+
+```ini
+SELECT_ERROR={YES|NO}
+```
+
+The default value is `YES`. A `SELECT` statement returns an error message if the result set exceeds the capacity of the host variable. Specify `NO` to suppress error messages when a `SELECT` statement returns more rows than a host variable can accommodate.
+
+Use `SELECT_ERROR` with the `EXEC ORACLE OPTION` directive.
+
+## Compiling in non-PROC mode
+
+If you don't include the `-C PROC` command-line option:
+
+-   C preprocessor directives are copied to the output file without change.
+-   You must declare the type and name of each C variable that you intend to use as a host variable in an `EXEC SQL BEGIN/END DECLARE` section.
+
+When invoked in non-`PROC` mode, ECPG implements the behavior described in the PostgreSQL core documentation.
+
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx
new file mode 100644
index 00000000000..52183d3e342
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/ecpgplus_statements.mdx
@@ -0,0 +1,1257 @@
+---
+title: "Language element reference"
+description: "Description of the ECPGPlus language elements"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.55.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.56.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.57.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.23.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.49.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.51.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.28.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.24.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.27.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.48.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.29.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.25.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.30.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.47.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.31.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.46.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.32.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.45.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.33.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.44.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.34.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.26.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.43.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.35.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.52.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.50.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.42.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.53.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.54.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.36.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.59.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.58.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.41.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.37.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.40.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.38.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.39.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.093.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.058.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.031.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.033.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.085.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.087.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.082.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.088.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.349.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.351.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.352.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.350.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.348.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.114.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.119.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.113.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.111.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.108.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.086.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.063.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.061.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.103.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.104.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.100.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.102.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html"
+redirects:
+  - /epas/latest/ecpgplus_guide/07_reference/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/ecpgplus_guide/07_reference/
+---
+
+<div id="sqlda_structure" class="registered_link"></div>
+
+An embedded SQL statement allows your client application to interact with the server. An embedded directive is an instruction to the ECPGPlus compiler.
+
+You can embed any EDB Postgres Advanced Server SQL statement in a C program. Each statement must begin with the keywords `EXEC SQL` and must be terminated with a semi-colon (;). In the C program, a SQL statement takes the form:
+
+```sql
+EXEC SQL <sql_command_body>;
+```
+
+Where `sql_command_body` represents a standard SQL statement. You can use a host variable anywhere that the SQL statement expects a value expression. For more information about substituting host variables for value expressions, see [Declaring host variables](/epas/latest/application_programming/ecpgplus_guide/03_using_embedded_sql/#declaring-host-variables).
+
+ECPGPlus extends the PostgreSQL server-side syntax for some statements. Syntax differences are noted in the reference information that follows. For a complete reference to the supported syntax of other SQL commands, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+## ALLOCATE DESCRIPTOR
+
+Use the `ALLOCATE DESCRIPTOR` statement to allocate an SQL descriptor area:
+
+```sql
+EXEC SQL [FOR <array_size>] ALLOCATE DESCRIPTOR <descriptor_name>
+    [WITH MAX <variable_count>];
+```
+
+Where:
+
+-  `array_size` is a variable that specifies the number of array elements to allocate for the descriptor. `array_size` can be an `INTEGER` value or a host variable.
+-  `descriptor_name` is the host variable that contains the name of the descriptor or the name of the descriptor. This value can take the form of an identifier, a quoted string literal, or of a host variable.
+-  `variable_count` specifies the maximum number of host variables in the descriptor. The default value of `variable_count` is `100`.
+
+The following code fragment allocates a descriptor named `emp_query` that can be processed as an array `(emp_array)`:
+
+```sql
+EXEC SQL FOR :emp_array ALLOCATE DESCRIPTOR emp_query;
+```
+
+## CALL
+
+Use the `CALL` statement to invoke a procedure or function on the server. The `CALL` statement works only on EDB Postgres Advanced Server. The `CALL` statement comes in two forms. The first form is used to call a function:
+
+```sql
+EXEC SQL CALL <program_name> '('[<actual_arguments>]')'
+  INTO [[:<ret_variable>][: <ret_indicator>]];
+```
+
+The second form is used to call a procedure:
+
+```sql
+EXEC SQL CALL <program_name> '('[<actual_arguments>]')';
+```
+
+Where:
+
+-  `program_name` is the name of the stored procedure or function that the `CALL` statement invokes. The program name can be schema qualified, package qualified, or both. If you don't specify the schema or package in which the program resides, ECPGPlus uses the value of `search_path` to locate the program.
+-  `actual_arguments` specifies a comma-separated list of arguments required by the program. Each `actual_argument` corresponds to a formal argument expected by the program. Each formal argument can be an `IN` parameter, an `OUT` parameter, or an `INOUT` parameter.
+-  `:ret_variable` specifies a host variable that receives the value returned if the program is a function.
+-  `:ret_indicator` specifies a host variable that receives the indicator value returned if the program is a function.
+
+For example, the following statement invokes the `get_job_desc` function with the value contained in the `:ename` host variable and captures the value returned by that function in the `:job` host variable:
+
+```sql
+EXEC SQL CALL get_job_desc(:ename)
+  INTO :job;
+```
+
+## CLOSE
+
+Use the `CLOSE` statement to close a cursor and free any resources currently in use by the cursor. A client application can't fetch rows from a closed cursor. The syntax of the `CLOSE` statement is:
+
+```sql
+EXEC SQL CLOSE [<cursor_name>];
+```
+
+Where `cursor_name` is the name of the cursor closed by the statement. The cursor name can take the form of an identifier or of a host variable.
+
+The `OPEN` statement initializes a cursor. Once initialized, a cursor result set remains unchanged unless the cursor is reopened. You don't need to `CLOSE` a cursor before reopening it.
+
+To manually close a cursor named `emp_cursor`, use the command:
+
+```sql
+EXEC SQL CLOSE emp_cursor;
+```
+
+A cursor is automatically closed when an application terminates.
+
+## COMMIT
+
+Use the `COMMIT` statement to complete the current transaction, making all changes permanent and visible to other users. The syntax is:
+
+```sql
+EXEC SQL [AT <database_name>] COMMIT [WORK]
+         [COMMENT <'text'>] [COMMENT <'text'> RELEASE];
+```
+
+Where `database_name` is the name of the database or host variable that contains the name of the database in which the work resides. This value can take the form of an unquoted string literal or of a host variable.
+
+For compatibility, ECPGPlus accepts the `COMMENT` clause without error but doesn't store any text included with the `COMMENT` clause.
+
+Include the `RELEASE` clause to close the current connection after performing the commit.
+
+For example, the following command commits all work performed on the `dept` database and closes the current connection:
+
+```sql
+EXEC SQL AT dept COMMIT RELEASE;
+```
+
+By default, statements are committed only when a client application performs a `COMMIT` statement. Include the `-t` option when invoking ECPGPlus to specify for a client application to invoke `AUTOCOMMIT` functionality. You can also control `AUTOCOMMIT` functionality in a client application with the following statements:
+
+```sql
+EXEC SQL SET AUTOCOMMIT TO ON
+```
+
+and
+
+```sql
+EXEC SQL SET AUTOCOMMIT TO OFF
+```
+
+## CONNECT
+
+Use the `CONNECT` statement to establish a connection to a database. The `CONNECT` statement is available in two forms. One form is compatible with Oracle databases, and the other is not.
+
+The first form is compatible with Oracle databases:
+
+```sql
+EXEC SQL CONNECT
+  {{:<user_name> IDENTIFIED BY :<password>}  | :<connection_id>}
+  [AT <database_name>]
+  [USING :database_string]
+  [ALTER AUTHORIZATION :new_password];
+```
+
+Where:
+
+-  `user_name` is a host variable that contains the role that the client application uses to connect to the server.
+-  `password` is a host variable that contains the password associated with that role.
+-  `connection_id` is a host variable that contains a slash-delimited user name and password used to connect to the database.
+
+Include the `AT` clause to specify the database to which the connection is established. `database_name` is the name of the database to which the client is connecting. Specify the value in the form of a variable or as a string literal.
+
+Include the `USING` clause to specify a host variable that contains a null-terminated string identifying the database to which to establish the connection.
+
+The `ALTER AUTHORIZATION` clause is supported for syntax compatibility only. ECPGPlus parses the `ALTER AUTHORIZATION` clause and reports a warning.
+
+Using the first form of the `CONNECT` statement, a client application might establish a connection with a host variable named `user` that contains the identity of the connecting role and a host variable named `password` that contains the associated password using the following command:
+
+```text
+EXEC SQL CONNECT :user IDENTIFIED BY :password;
+```
+
+A client application can also use the first form of the `CONNECT` statement to establish a connection using a single host variable named `:connection_id`. In the following example, `connection_id` contains the slash-delimited role name and associated password for the user:
+
+```sql
+EXEC SQL CONNECT :connection_id;
+```
+
+The syntax of the second form of the `CONNECT` statement is:
+
+```sql
+EXEC SQL CONNECT TO <database_name>
+[AS <connection_name>] [<credentials>];
+```
+
+Where `credentials` is one of the following:
+
+```sql
+USER user_name password
+USER user_name IDENTIFIED BY password
+USER user_name USING password
+```
+
+In the second form:
+
+`database_name` is the name or identity of the database to which the client is connecting. Specify `database_name` as a variable or as a string literal in one of the following forms:
+
+```text
+<database_name>[@<hostname>][:<port>]
+
+tcp:postgresql://<hostname>[:<port>][/<database_name>][options]
+
+unix:postgresql://<hostname>[:<port>][/<database_name>][options]
+```
+
+Where:
+
+-  `hostname` is the name or IP address of the server on which the database resides.
+-  `port` is the port on which the server listens.
+
+  You can also specify a value of `DEFAULT` to establish a connection with the default database, using the default role name. If you specify `DEFAULT` as the target database, don't include a `connection_name` or `credentials`.
+
+-  `connection_name` is the name of the connection to the database. `connection_name` takes the form of an identifier (that is, not a string literal or a variable). You can open multiple connections by providing a unique `connection_name` for each connection.
+
+  If you don't specify a name for a connection, `ecpglib` assigns a name of `DEFAULT` to the connection. You can refer to the connection by name (`DEFAULT`) in any `EXEC SQL` statement.
+
+-  `CURRENT` is the most recently opened or the connection mentioned in the most-recent `SET CONNECTION TO` statement. If you don't refer to a connection by name in an `EXEC SQL` statement, ECPG assumes the name of the connection to be `CURRENT`.
+
+-  `user_name` is the role used to establish the connection with the EDB Postgres Advanced Server database. The privileges of the specified role are applied to all commands performed through the connection.
+
+-  `password` is the password associated with the specified `user_name`.
+
+The following code fragment uses the second form of the `CONNECT` statement to establish a connection to a database named `edb` using the role `alice` and the password associated with that role, `1safepwd`:
+
+```sql
+EXEC SQL CONNECT TO edb AS acctg_conn
+  USER 'alice' IDENTIFIED BY '1safepwd';
+```
+
+The name of the connection is `acctg_conn`. You can use the connection name when changing the connection name using the `SET CONNECTION` statement.
+
+## DEALLOCATE DESCRIPTOR
+
+Use the `DEALLOCATE DESCRIPTOR` statement to free memory in use by an allocated descriptor. The syntax of the statement is:
+
+```sql
+EXEC SQL DEALLOCATE DESCRIPTOR <descriptor_name>
+```
+
+Where `descriptor_name` is the name of the descriptor. This value can take the form of a quoted string literal or of a host variable.
+
+The following example deallocates a descriptor named `emp_query`:
+
+```sql
+EXEC SQL DEALLOCATE DESCRIPTOR emp_query;
+```
+
+## DECLARE CURSOR
+
+Use the `DECLARE CURSOR` statement to define a cursor. The syntax of the statement is:
+
+```sql
+EXEC SQL [AT <database_name>] DECLARE <cursor_name> CURSOR FOR
+(<select_statement> | <statement_name>);
+```
+
+Where:
+
+-  `database_name` is the name of the database on which the cursor operates. This value can take the form of an identifier or of a host variable. If you don't specify a database name, the default value of `database_name` is the default database.
+-  `cursor_name` is the name of the cursor.
+-  `select_statement` is the text of the `SELECT` statement that defines the cursor result set. The `SELECT` statement can't contain an `INTO` clause.
+-  `statement_name` is the name of a SQL statement or block that defines the cursor result set.
+
+The following example declares a cursor named `employees`:
+
+```sql
+EXEC SQL DECLARE employees CURSOR FOR
+  SELECT
+    empno, ename, sal, comm
+  FROM
+    emp;
+```
+
+The cursor generates a result set that contains the employee number, employee name, salary, and commission for each employee record that's stored in the `emp` table.
+
+## DECLARE DATABASE
+
+Use the `DECLARE DATABASE` statement to declare a database identifier for use in subsequent SQL statements (for example, in a `CONNECT` statement). The syntax is:
+
+```sql
+EXEC SQL DECLARE <database_name> DATABASE;
+```
+
+Where `database_name` specifies the name of the database.
+
+The following example shows declaring an identifier for the `acctg` database:
+
+```sql
+EXEC SQL DECLARE acctg DATABASE;
+```
+
+After invoking the command declaring `acctg` as a database identifier, you can reference the `acctg` database by name when establishing a connection or in `AT` clauses.
+
+This statement has no effect and is provided for Pro\*C compatibility only.
+
+## DECLARE STATEMENT
+
+Use the `DECLARE STATEMENT` directive to declare an identifier for an SQL statement. EDB Postgres Advanced Server supports two versions of the `DECLARE STATEMENT` directive:
+
+```sql
+EXEC SQL [<database_name>] DECLARE <statement_name> STATEMENT;
+```
+
+and
+
+```sql
+EXEC SQL DECLARE STATEMENT <statement_name>;
+```
+
+Where:
+
+-  `statement_name` specifies the identifier associated with the statement.
+-  `database_name` specifies the name of the database. This value may take the form of an identifier or of a host variable that contains the identifier.
+
+A typical usage sequence that includes the `DECLARE STATEMENT` directive is:
+
+```sql
+EXEC SQL DECLARE give_raise STATEMENT;      // give_raise is now a statement
+handle (not prepared)
+EXEC SQL PREPARE give_raise FROM :stmtText; // give_raise is now associated
+with a statement
+EXEC SQL EXECUTE give_raise;
+```
+
+This statement has no effect and is provided for Pro\*C compatibility only.
+
+## DELETE
+
+Use the `DELETE` statement to delete one or more rows from a table. The syntax for the ECPGPlus `DELETE` statement is the same as the syntax for the SQL statement, but you can use parameter markers and host variables any place that an expression is allowed. The syntax is:
+
+```sql
+[FOR <exec_count>] DELETE FROM [ONLY] <table> [[AS] <alias>]
+  [USING <using_list>]
+  [WHERE <condition> | WHERE CURRENT OF <cursor_name>]
+  [{RETURNING|RETURN} * | <output_expression> [[AS] <output_name>]
+[, ...] INTO <host_variable_list> ]
+```
+
+-  Include the `FOR exec_count` clause to specify the number of times the statement executes. This clause is valid only if the `VALUES` clause references an array or a pointer to an array.
+-  `table` is the name (optionally schema qualified) of an existing table. Include the `ONLY` clause to limit processing to the specified table. If you don't include the `ONLY` clause, any tables inheriting from the named table are also processed.
+-  `alias` is a substitute name for the target table.
+-  `using_list` is a list of table expressions, allowing columns from other tables to appear in the `WHERE` condition.
+-  Include the `WHERE` clause to specify the rows to delete. If you don't include a `WHERE` clause in the statement, `DELETE` deletes all rows from the table, leaving the table definition intact.
+-  `condition` is an expression, host variable, or parameter marker that returns a value of type `BOOLEAN`. Those rows for which `condition` returns true are deleted.
+-  `cursor_name` is the name of the cursor to use in the `WHERE CURRENT OF` clause. The row to be deleted is the one most recently fetched from this cursor. The cursor must be a nongrouping query on the `DELETE` statements target table. You can't specify `WHERE CURRENT OF` in a `DELETE` statement that includes a Boolean condition.
+
+The `RETURN/RETURNING` clause specifies an `output_expression` or `host_variable_list` that's returned by the `DELETE` command after each row is deleted:
+
+  -   `output_expression` is an expression to be computed and returned by the `DELETE` command after each row is deleted. `output_name` is the name of the returned column. Include \* to return all columns.
+  -   `host_variable_list` is a comma-separated list of host variables and optional indicator variables. Each host variable receives a corresponding value from the `RETURNING` clause.
+
+For example, the following statement deletes all rows from the `emp` table, where the `sal` column contains a value greater than the value specified in the host variable, `:max_sal:`
+
+```sql
+DELETE FROM emp WHERE sal > :max_sal;
+```
+
+For more information about using the `DELETE` statement, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-delete.html).
+
+## DESCRIBE
+
+Use the `DESCRIBE` statement to find the number of input values required by a prepared statement or the number of output values returned by a prepared statement. The `DESCRIBE` statement is used to analyze a SQL statement whose shape is unknown at the time you write your application.
+
+The `DESCRIBE` statement populates an `SQLDA` descriptor. To populate a SQL descriptor, use the `ALLOCATE DESCRIPTOR` and `DESCRIBE...DESCRIPTOR` statements.
+
+```sql
+EXEC SQL DESCRIBE BIND VARIABLES FOR <statement_name> INTO <descriptor>;
+```
+
+
+```sql
+EXEC SQL DESCRIBE SELECT LIST FOR <statement_name> INTO <descriptor>;
+```
+
+Where:
+
+-  `statement_name` is the identifier associated with a prepared SQL statement or PL/SQL block.
+-  `descriptor` is the name of C variable of type `SQLDA*`. You must allocate the space for the descriptor by calling `sqlald()` and initialize the descriptor before executing the `DESCRIBE` statement.
+
+When you execute the first form of the `DESCRIBE` statement, ECPG populates the given descriptor with a description of each input variable *required* by the statement. For example, given two descriptors:
+
+```sql
+SQLDA *query_values_in;
+SQLDA *query_values_out;
+```
+
+You might prepare a query that returns information from the `emp` table:
+
+```sql
+EXEC SQL PREPARE get_emp FROM
+  "SELECT ename, empno, sal FROM emp WHERE empno = ?";
+```
+
+The command requires one input variable for the parameter marker (?).
+
+```sql
+EXEC SQL DESCRIBE BIND VARIABLES
+  FOR get_emp INTO query_values_in;
+```
+
+After describing the bind variables for this statement, you can examine the descriptor to find the number of variables required and the type of each variable.
+
+When you execute the second form, ECPG populates the given descriptor with a description of each value returned by the statement. For example, the following statement returns three values:
+
+```sql
+EXEC SQL DESCRIBE SELECT LIST
+  FOR get_emp INTO query_values_out;
+```
+
+After describing the select list for this statement, you can examine the descriptor to find the number of returned values and the name and type of each value.
+
+Before executing the statement, you must bind a variable for each input value and a variable for each output value. The variables that you bind for the input values specify the actual values used by the statement. The variables that you bind for the output values tell ECPGPlus where to put the values when you execute the statement.
+
+This is alternative Pro\*C-compatible syntax for the `DESCRIBE DESCRIPTOR` statement.
+
+## DESCRIBE DESCRIPTOR
+
+Use the `DESCRIBE DESCRIPTOR` statement to retrieve information about a SQL statement and store that information in a SQL descriptor. Before using `DESCRIBE DESCRIPTOR`, you must allocate the descriptor with the `ALLOCATE DESCRIPTOR` statement. The syntax is:
+
+```sql
+EXEC SQL DESCRIBE [INPUT | OUTPUT] <statement_identifier>
+  USING [SQL] DESCRIPTOR <descriptor_name>;
+```
+
+Where:
+
+-  `statement_name` is the name of a prepared SQL statement.
+-  `descriptor_name` is the name of the descriptor. `descriptor_name` can be a quoted string value or a host variable that contains the name of the descriptor.
+
+If you include the `INPUT` clause, ECPGPlus populates the given descriptor with a description of each input variable required by the statement.
+
+For example, given two descriptors:
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR query_values_in;
+EXEC SQL ALLOCATE DESCRIPTOR query_values_out;
+```
+
+You might prepare a query that returns information from the `emp` table:
+
+```sql
+EXEC SQL PREPARE get_emp FROM
+  "SELECT ename, empno, sal FROM emp WHERE empno = ?";
+```
+
+The command requires one input variable for the parameter marker (?).
+
+```sql
+EXEC SQL DESCRIBE INPUT get_emp USING 'query_values_in';
+```
+
+After describing the bind variables for this statement, you can examine the descriptor to find the number of variables required and the type of each variable.
+
+If you don't specify the `INPUT` clause, `DESCRIBE DESCRIPTOR` populates the specified descriptor with the values returned by the statement.
+
+If you include the `OUTPUT` clause, ECPGPlus populates the given descriptor with a description of each value returned by the statement.
+
+For example, the following statement returns three values:
+
+```sql
+EXEC SQL DESCRIBE OUTPUT FOR get_emp USING 'query_values_out';
+```
+
+After describing the select list for this statement, you can examine the descriptor to find the number of returned values and the name and type of each value.
+
+## DISCONNECT
+
+Use the `DISCONNECT` statement to close the connection to the server. The syntax is:
+
+```sql
+EXEC SQL DISCONNECT [<connection_name>][CURRENT][DEFAULT][ALL];
+```
+
+Where `connection_name` is the connection name specified in the `CONNECT` statement used to establish the connection. If you don't specify a connection name, the current connection is closed.
+
+Include the `CURRENT` keyword to specify for ECPGPlus to close the connection used most recently.
+
+Include the `DEFAULT` keyword to specify for ECPGPlus to close the connection named `DEFAULT`. If you don't specify a name when opening a connection, ECPGPlus assigns the name `DEFAULT` to the connection.
+
+Include the `ALL` keyword to close all active connections.
+
+The following example creates a connection named `hr_connection` that connects to the `hr` database and then disconnects from the connection:
+
+```c
+/* client.pgc*/
+int main()
+{
+    EXEC SQL CONNECT TO hr AS connection_name;
+    EXEC SQL DISCONNECT connection_name;
+    return(0);
+}
+```
+
+## EXECUTE
+
+Use the `EXECUTE` statement to execute a statement previously prepared using an `EXEC SQL PREPARE` statement. The syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] EXECUTE <statement_name>
+  [USING {DESCRIPTOR <SQLDA_descriptor>
+  |: <host_variable> [[INDICATOR] :<indicator_variable>]}];
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value that specifies the number of rows to process. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `statement_name` specifies the name assigned to the statement when the statement was created using the `EXEC SQL PREPARE` statement.
+
+Include the `USING` clause to supply values for parameters in the prepared statement:
+
+-   Include the `DESCRIPTOR` `SQLDA_descriptor` clause to provide an SQLDA descriptor value for a parameter.
+-   Use a `host_variable` (and an optional `indicator_variable`) to provide a user-specified value for a parameter.
+
+The following example creates a prepared statement that inserts a record into the `emp` table:
+
+```sql
+EXEC SQL PREPARE add_emp (numeric, text, text, numeric) AS
+    INSERT INTO emp VALUES($1, $2, $3, $4);
+```
+
+Each time you invoke the prepared statement, provide fresh parameter values for the statement:
+
+```sql
+EXEC SQL EXECUTE add_emp USING 8000, 'DAWSON', 'CLERK', 7788;
+EXEC SQL EXECUTE add_emp USING 8001, 'EDWARDS', 'ANALYST', 7698;
+```
+
+## EXECUTE DESCRIPTOR
+
+Use the `EXECUTE` statement to execute a statement previously prepared by an `EXEC SQL PREPARE` statement, using an SQL descriptor. The syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] EXECUTE <statement_identifier>
+  [USING [SQL] DESCRIPTOR <descriptor_name>]
+  [INTO [SQL] DESCRIPTOR <descriptor_name>];
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value that specifies the number of rows to process. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `statement_identifier` specifies the identifier assigned to the statement with the `EXEC SQL PREPARE` statement.
+-  `descriptor_name` specifies the name of a descriptor (as a single-quoted string literal), or a host variable that contains the name of a descriptor.
+
+Include the `USING` clause to specify values for any input parameters required by the prepared statement.
+
+Include the `INTO` clause to specify a descriptor into which the `EXECUTE` statement writes the results returned by the prepared statement.
+
+The following example executes the prepared statement, `give_raise`, using the values contained in the descriptor `stmtText:`
+
+```sql
+EXEC SQL PREPARE give_raise FROM :stmtText;
+EXEC SQL EXECUTE give_raise USING DESCRIPTOR :stmtText;
+```
+
+## EXECUTE...END EXEC
+
+Use the `EXECUTE…END-EXEC` statement to embed an anonymous block into a client application. The syntax is:
+
+```sql
+EXEC SQL [AT <database_name>] EXECUTE <anonymous_block> END-EXEC;
+```
+
+Where:
+
+-  `database_name` is the database identifier or a host variable that contains the database identifier. If you omit the `AT` clause, the statement executes on the current default database.
+-  `anonymous_block` is an inline sequence of PL/pgSQL or SPL statements and declarations. You can include host variables and optional indicator variables in the block. Each such variable is treated as an `IN/OUT` value.
+
+The following example executes an anonymous block:
+
+```sql
+EXEC SQL EXECUTE
+  BEGIN
+    IF (current_user = :admin_user_name) THEN
+      DBMS_OUTPUT.PUT_LINE('You are an administrator');
+    END IF;
+END-EXEC;
+```
+
+!!! Note
+    The `EXECUTE…END EXEC` statement is supported only by EDB Postgres Advanced Server.
+
+## EXECUTE IMMEDIATE
+
+Use the `EXECUTE IMMEDIATE` statement to execute a string that contains a SQL command. The syntax is:
+
+```sql
+EXEC SQL [AT <database_name>] EXECUTE IMMEDIATE <command_text>;
+```
+
+Where:
+
+-  `database_name` is the database identifier or a host variable that contains the database identifier. If you omit the `AT` clause, the statement executes on the current default database.
+-  `command_text` is the command executed by the `EXECUTE IMMEDIATE` statement.
+
+This dynamic SQL statement is useful when you don't know the text of an SQL statement when writing a client application. For example, a client application might prompt a trusted user for a statement to execute. After the user provides the text of the statement as a string value, the statement is then executed with an `EXECUTE IMMEDIATE` command.
+
+The statement text can't contain references to host variables. If the statement might contain parameter markers or returns one or more values, use the `PREPARE` and `DESCRIBE` statements.
+
+The following example executes the command contained in the `:command_text` host variable:
+
+```sql
+EXEC SQL EXECUTE IMMEDIATE :command_text;
+```
+
+## FETCH
+
+Use the `FETCH` statement to return rows from a cursor into an SQLDA descriptor or a target list of host variables. Before using a `FETCH` statement to retrieve information from a cursor, you must prepare the cursor using `DECLARE` and `OPEN` statements. The statement syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] FETCH <cursor>
+  { USING DESCRIPTOR <SQLDA_descriptor> }|{ INTO <target_list> };
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value specifying the number of rows to fetch. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `cursor` is the name of the cursor from which rows are being fetched or a host variable that contains the name of the cursor.
+
+If you include a `USING` clause, the `FETCH` statement populates the specified SQLDA descriptor with the values returned by the server.
+
+If you include an `INTO` clause, the `FETCH` statement populates the host variables (and optional indicator variables) specified in the `target_list`.
+
+The following code fragment declares a cursor named `employees` that retrieves the `employee number`, `name`, and `salary` from the `emp` table:
+
+```sql
+EXEC SQL DECLARE employees CURSOR FOR
+    SELECT empno, ename, esal FROM emp;
+EXEC SQL OPEN emp_cursor;
+EXEC SQL FETCH emp_cursor INTO :emp_no, :emp_name, :emp_sal;
+```
+
+## FETCH DESCRIPTOR
+
+Use the `FETCH DESCRIPTOR` statement to retrieve rows from a cursor into an SQL descriptor. The syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] FETCH <cursor>
+  INTO [SQL] DESCRIPTOR <descriptor_name>;
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value specifying the number of rows to fetch. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `cursor` is the name of the cursor from which rows are fetched or a host variable that contains the name of the cursor. The client must `DECLARE` and `OPEN` the cursor before calling the `FETCH DESCRIPTOR` statement.
+-  `descriptor_name` specifies the name of a descriptor (as a single-quoted string literal) or a host variable that contains the name of a descriptor. Prior to use, the descriptor must be allocated using an `ALLOCATE DESCRIPTOR` statement.
+
+Include the `INTO` clause to specify a SQL descriptor into which the `EXECUTE` statement writes the results returned by the prepared statement. 
+
+The following example allocates a descriptor named `row_desc` that holds the description and the values of a specific row in the result set. It then declares and opens a cursor for a prepared statement (`my_cursor`), before looping through the rows in result set, using a `FETCH` to retrieve the next row from the cursor into the descriptor:
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR 'row_desc';
+EXEC SQL DECLARE my_cursor CURSOR FOR query;
+EXEC SQL OPEN my_cursor;
+
+for( row = 0; ; row++ )
+{
+  EXEC SQL BEGIN DECLARE SECTION;
+    int col;
+EXEC SQL END DECLARE SECTION;
+EXEC SQL FETCH my_cursor INTO SQL DESCRIPTOR 'row_desc';
+```
+
+## GET DESCRIPTOR
+
+Use the `GET DESCRIPTOR` statement to retrieve information from a descriptor. The `GET DESCRIPTOR` statement comes in two forms. The first form returns the number of values (or columns) in the descriptor.
+
+```sql
+EXEC SQL GET DESCRIPTOR <descriptor_name>
+  :<host_variable> = COUNT;
+```
+
+The second form returns information about a specific value (specified by the `VALUE column_number` clause):
+
+```sql
+EXEC SQL [FOR <array_size>] GET DESCRIPTOR <descriptor_name>
+  VALUE <column_number> {:<host_variable> = <descriptor_item> {,…}};
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value that specifies the number of rows to process. If you specify an `array_size`, the `host_variable` must be an array of that size. For example, if `array_size` is `10`, `:host_variable` must be a 10-member array of `host_variables`. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `descriptor_name` specifies the name of a descriptor as a single-quoted string literal or a host variable that contains the name of a descriptor.
+
+Include the `VALUE` clause to specify the information retrieved from the descriptor.
+
+-   `column_number` identifies the position of the variable in the descriptor.
+-   `host_variable` specifies the name of the host variable that receives the value of the item.
+-   `descriptor_item` specifies the type of the retrieved descriptor item.
+
+ECPGPlus implements the following `descriptor_item` types:
+
+-   `TYPE`
+-   `LENGTH`
+-   `OCTET_LENGTH`
+-   `RETURNED_LENGTH`
+-   `RETURNED_OCTET_LENGTH`
+-   `PRECISION`
+-   `SCALE`
+-   `NULLABLE`
+-   `INDICATOR`
+-   `DATA`
+-   `NAME`
+
+The following code fragment shows using a `GET DESCRIPTOR` statement to obtain the number of columns entered in a user-provided string:
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR parse_desc;
+EXEC SQL PREPARE query FROM :stmt;
+EXEC SQL DESCRIBE query INTO SQL DESCRIPTOR parse_desc;
+EXEC SQL GET DESCRIPTOR parse_desc :col_count = COUNT;
+```
+
+The example allocates an SQL descriptor named `parse_desc` before using a `PREPARE` statement to check the syntax of the string provided by the user `:stmt`. A `DESCRIBE` statement moves the user-provided string into the descriptor, `parse_desc`. The call to `EXEC SQL GET DESCRIPTOR` interrogates the descriptor to discover the number of columns `(:col_count)` in the result set.
+
+## INSERT
+
+Use the `INSERT` statement to add one or more rows to a table. The syntax for the ECPGPlus `INSERT` statement is the same as the syntax for the SQL statement, but you can use parameter markers and host variables any place that a value is allowed. The syntax is:
+
+```sql
+[FOR <exec_count>] INSERT INTO <table> [(<column> [, ...])]
+  {DEFAULT VALUES |
+   VALUES ({<expression> | DEFAULT} [, ...])[, ...] | <query>}
+  [RETURNING * | <output_expression> [[ AS ] <output_name>] [, ...]]
+```
+
+Include the `FOR exec_count` clause to specify the number of times the statement executes. This clause is valid only if the `VALUES` clause references an array or a pointer to an array.
+
+-  `table` specifies the (optionally schema-qualified) name of an existing table.
+-  `column` is the name of a column in the table. The column name can be qualified with a subfield name or array subscript. Specify the `DEFAULT VALUES` clause to use default values for all columns.
+-  `expression` is the expression, value, host variable, or parameter marker that's assigned to the corresponding column. Specify `DEFAULT` to fill the corresponding column with its default value.
+-  `query` specifies a `SELECT` statement that supplies the rows to insert.
+-  `output_expression` is an expression that's computed and returned by the `INSERT` command after each row is inserted. The expression can refer to any column in the table. Specify \* to return all columns of the inserted rows.
+-  `output_name` specifies a name to use for a returned column.
+
+The following example adds a row to the `employees` table:
+
+```sql
+INSERT INTO emp (empno, ename, job, hiredate)
+    VALUES ('8400', :ename, 'CLERK', '2011-10-31');
+```
+
+!!! Note
+    The `INSERT` statement uses a host variable `:ename` to specify the value of the `ename` column.
+
+For more information about using the `INSERT` statement, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-insert.html).
+
+## OPEN
+
+Use the `OPEN` statement to open a cursor. The syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] OPEN <cursor> [USING <parameters>];
+```
+
+`parameters` is one of the following:
+
+```sql
+DESCRIPTOR <SQLDA_descriptor>
+```
+
+or
+
+```sql
+<host_variable> [ [ INDICATOR ] <indicator_variable>, … ]
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value specifying the number of rows to fetch. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `cursor` is the name of the cursor being opened.
+-  `parameters` is either `DESCRIPTOR SQLDA_descriptor` or a comma-separated list of `host variables` and optional `indicator variables` that initialize the cursor. If specifying an `SQLDA_descriptor`, the descriptor must be initialized with a `DESCRIBE` statement.
+
+The `OPEN` statement initializes a cursor using the values provided in `parameters`. Once initialized, the cursor result set remains unchanged unless the cursor is closed and reopened. A cursor is automatically closed when an application terminates.
+
+The following example declares a cursor named `employees` that queries the `emp` table. It returns the `employee number`, `name`, `salary`, and `commission` of an employee whose name matches a user-supplied value stored in the host variable `:emp_name`.
+
+```sql
+EXEC SQL DECLARE employees CURSOR FOR
+  SELECT
+    empno, ename, sal, comm 
+  FROM 
+    emp
+  WHERE ename = :emp_name;
+EXEC SQL OPEN employees;
+...
+```
+
+After declaring the cursor, the example uses an `OPEN` statement to make the contents of the cursor available to a client application.
+
+## OPEN DESCRIPTOR
+
+Use the `OPEN DESCRIPTOR` statement to open a cursor with a SQL descriptor. The syntax is:
+
+```sql
+EXEC SQL [FOR <array_size>] OPEN <cursor>
+  [USING [SQL] DESCRIPTOR <descriptor_name>]
+  [INTO [SQL] DESCRIPTOR <descriptor_name>];
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value specifying the number of rows to fetch. If you omit the `FOR` clause, the statement is executed once for each member of the array.
+-  `cursor` is the name of the cursor being opened.
+-  `descriptor_name` specifies the name of an SQL descriptor in the form of a single-quoted string literal or a host variable that contains the name of an SQL descriptor that contains the query that initializes the cursor.
+
+For example, the following statement opens a cursor named `emp_cursor` using the host variable `:employees`:
+
+```sql
+EXEC SQL OPEN emp_cursor USING DESCRIPTOR :employees;
+```
+
+## PREPARE
+
+Prepared statements are useful when a client application must perform a task multiple times. The statement is parsed, written, and planned only once rather than each time the statement is executed. This approach saves repetitive processing time.
+
+Use the `PREPARE` statement to prepare a SQL statement or PL/pgSQL block for execution. The statement is available in two forms. The first form is:
+
+```sql
+EXEC SQL [AT <database_name>] PREPARE <statement_name>
+  FROM <sql_statement>;
+```
+
+The second form is:
+
+```sql
+EXEC SQL [AT <database_name>] PREPARE <statement_name>
+  AS <sql_statement>;
+```
+
+Where:
+
+-  `database_name` is the database identifier or a host variable that contains the database identifier against which the statement executes. If you omit the `AT` clause, the statement executes against the current default database.
+-  `statement_name` is the identifier associated with a prepared SQL statement or PL/SQL block.
+-  `sql_statement` can take the form of a `SELECT` statement, a single-quoted string literal, or a host variable that contains the text of an SQL statement.
+
+To include variables in a prepared statement, substitute placeholders (`$1, $2, $3`, and so on) for statement values that might change when you `PREPARE` the statement. When you `EXECUTE` the statement, provide a value for each parameter. Provide the values in the order in which they replace placeholders.
+
+The following example creates a prepared statement named `add_emp` that inserts a record into the `emp` table:
+
+```sql
+EXEC SQL PREPARE add_emp (int, text, text, numeric) AS
+    INSERT INTO emp VALUES($1, $2, $3, $4);
+```
+
+Each time you invoke the statement, provide fresh parameter values for the statement:
+
+```sql
+EXEC SQL EXECUTE add_emp(8003, 'Davis', 'CLERK', 2000.00);
+EXEC SQL EXECUTE add_emp(8004, 'Myer', 'CLERK', 2000.00);
+```
+
+!!! Note
+    A client application must issue a `PREPARE` statement in each session in which a statement executes. Prepared statements persist only for the duration of the current session.
+
+## ROLLBACK
+
+Use the `ROLLBACK` statement to abort the current transaction and discard any updates made by the transaction. The syntax is:
+
+```sql
+EXEC SQL [AT <database_name>] ROLLBACK [WORK]
+  [ { TO [SAVEPOINT] <savepoint> } | RELEASE ]
+```
+
+Where `database_name` is the database identifier or a host variable that contains the database identifier against which the statement executes. If you omit the `AT` clause, the statement executes against the current default database.
+
+Include the `TO` clause to abort any commands that executed after the specified `savepoint`. Use the `SAVEPOINT` statement to define the `savepoint`. If you omit the `TO` clause, the `ROLLBACK` statement aborts the transaction, discarding all updates.
+
+Include the `RELEASE` clause to cause the application to execute an `EXEC SQL COMMIT RELEASE` and close the connection.
+
+Use the following statement to roll back a complete transaction:
+
+```sql
+EXEC SQL ROLLBACK;
+```
+
+Invoking this statement aborts the transaction, undoing all changes, erasing any savepoints, and releasing all transaction locks. Suppose you include a savepoint (`my_savepoint` in the following example):
+
+```sql
+EXEC SQL ROLLBACK TO SAVEPOINT my_savepoint;
+```
+
+Only the portion of the transaction that occurred after the `my_savepoint` is rolled back. `my_savepoint` is retained, but any savepoints created after `my_savepoint` are erased.
+
+Rolling back to a specified savepoint releases all locks acquired after the savepoint.
+
+## SAVEPOINT
+
+Use the `SAVEPOINT` statement to define a *savepoint*. A savepoint is a marker in a transaction. You can use a `ROLLBACK` statement to abort the current transaction, returning the state of the server to its condition prior to the specified savepoint. The syntax of a `SAVEPOINT` statement is:
+
+```sql
+EXEC SQL [AT <database_name>] SAVEPOINT <savepoint_name>
+```
+
+Where:
+
+-  `database_name` is the database identifier or a host variable that contains the database identifier against which the savepoint resides. If you omit the `AT` clause, the statement executes against the current default database.
+-  `savepoint_name` is the name of the savepoint. If you reuse a `savepoint_name`, the original savepoint is discarded.
+
+You can establish savepoints only in a transaction block. A transaction block can contain multiple savepoints.
+
+To create a savepoint named `my_savepoint`, include the statement:
+
+```sql
+EXEC SQL SAVEPOINT my_savepoint;
+```
+
+## SELECT
+
+ECPGPlus extends support of the `SQL SELECT` statement by providing the `INTO host_variables` clause. The clause allows you to select specified information from an EDB Postgres Advanced Server database into a host variable. The syntax for the `SELECT` statement is:
+
+```sql
+EXEC SQL [AT <database_name>]
+SELECT
+  [ <hint> ]
+  [ ALL | DISTINCT [ ON( <expression>, ...) ]]
+  select_list INTO <host_variables>
+  
+  [ FROM from_item [, from_item ]...]
+  [ WHERE condition ]
+  [ hierarchical_query_clause ]
+  [ GROUP BY expression [, ...]]
+  [ HAVING condition ]
+  [ { UNION [ ALL ] | INTERSECT | MINUS } (subquery) ]
+  [ ORDER BY expression [order_by_options]]
+  [ LIMIT { count | ALL }]
+  [ OFFSET start [ ROW | ROWS ] ]
+  [ FETCH { FIRST | NEXT } [ count ] { ROW | ROWS } ONLY ]
+  [ FOR { UPDATE | SHARE } [OF table_name [, ...]][NOWAIT ][...]]
+```
+
+Where:
+
+-  `database_name` is the name of the database or host variable that contains the name of the database in which the table resides. This value can take the form of an unquoted string literal or of a host variable.
+-  `host_variables` is a list of host variables populated by the `SELECT` statement. If the `SELECT` statement returns more than a single row, `host_variables` must be an array.
+
+ECPGPlus provides support for the additional clauses of the SQL `SELECT` statement as documented in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-select.html).
+
+To use the `INTO host_variables` clause, include the names of defined host variables when specifying the `SELECT` statement. For example, the following `SELECT` statement populates the `:emp_name` and `:emp_sal` host variables with a list of employee names and salaries:
+
+```sql
+EXEC SQL SELECT ename, sal
+  INTO :emp_name, :emp_sal
+  FROM emp
+  WHERE empno = 7988;
+```
+
+The enhanced `SELECT` statement also allows you to include parameter markers (question marks) in any clause where a value is allowed. For example, the following query contains a parameter marker in the `WHERE` clause:
+
+```sql
+SELECT * FROM emp WHERE dept_no = ?;
+```
+
+This `SELECT` statement allows you to provide a value at runtime for the `dept_no` parameter marker.
+
+## SET CONNECTION
+
+There are at least three reasons you might need more than one connection in a given client application:
+
+-   You might want different privileges for different statements.
+-   You might need to interact with multiple databases in the same client.
+-   Multiple threads of execution in a client application can't share a connection concurrently.
+
+The syntax for the `SET CONNECTION` statement is:
+
+```sql
+EXEC SQL SET CONNECTION <connection_name>;
+```
+
+Where `connection_name` is the name of the connection to the database.
+
+To use the `SET CONNECTION` statement, open the connection to the database using the second form of the `CONNECT` statement. Include the `AS` clause to specify a `connection_name`.
+
+By default, the current thread uses the current connection. Use the `SET CONNECTION` statement to specify a default connection for the current thread to use. The default connection is used only when you execute an `EXEC SQL` statement that doesn't explicitly specify a connection name. For example, the following statement uses the default connection because it doesn't include an `AT connection_name` clause:
+
+```sql
+EXEC SQL DELETE FROM emp;
+```
+
+This statement doesn't use the default connection because it specifies a connection name using the `AT connection_name` clause:
+
+```sql
+EXEC SQL AT acctg_conn DELETE FROM emp;
+```
+
+For example, suppose a client application creates and maintains multiple connections using either of the following approaches:
+
+```sql
+EXEC SQL CONNECT TO edb AS acctg_conn
+  USER 'alice' IDENTIFIED BY 'acctpwd';
+```
+
+
+```sql
+EXEC SQL CONNECT TO edb AS hr_conn
+  USER 'bob' IDENTIFIED BY 'hrpwd';
+```
+
+It can change between the connections with the `SET CONNECTION` statement:
+
+```sql
+SET CONNECTION acctg_conn;
+```
+
+or
+
+```sql
+SET CONNECTION hr_conn;
+```
+
+The server uses the privileges associated with the connection when determining the privileges available to the connecting client. When using the `acctg_conn` connection, the client has the privileges associated with the role `alice`. When connected using `hr_conn`, the client has the privileges associated with `bob`.
+
+## SET DESCRIPTOR
+
+Use the `SET DESCRIPTOR` statement to assign a value to a descriptor area using information provided by the client application in the form of a host variable or an integer value. The statement comes in two forms. The first form is:
+
+```sql
+EXEC SQL [FOR <array_size>] SET DESCRIPTOR <descriptor_name>
+  VALUE <column_number> <descriptor_item> = <host_variable>;
+```
+
+The second form is:
+
+```sql
+EXEC SQL [FOR <array_size>] SET DESCRIPTOR <descriptor_name>
+  COUNT = integer;
+```
+
+Where:
+
+-  `array_size` is an integer value or a host variable that contains an integer value specifying the number of rows to fetch. If you omit the `FOR` clause, the statement executes once for each member of the array.
+-  `descriptor_name` specifies the name of a descriptor as a single-quoted string literal or a host variable that contains the name of a descriptor.
+
+Include the `VALUE` clause to describe the information stored in the descriptor.
+
+-   `column_number` identifies the position of the variable within the descriptor.
+-   `descriptor_item` specifies the type of the descriptor item.
+-   `host_variable` specifies the name of the host variable that contains the value of the item.
+
+ECPGPlus implements the following `descriptor_item` types:
+
+-   `TYPE`
+-   `LENGTH`
+-   `[REF] INDICATOR`
+-   `[REF] DATA`
+-   `[REF] RETURNED LENGTH`
+
+For example, a client application might prompt a user for a dynamically created query:
+
+```c
+query_text = promptUser("Enter a query");
+```
+
+To execute a dynamically created query, you must first prepare the query (parsing and validating the syntax of the query) and then describe the input parameters found in the query using the `EXEC SQL DESCRIBE INPUT` statement.
+
+```sql
+EXEC SQL ALLOCATE DESCRIPTOR query_params;
+EXEC SQL PREPARE emp_query FROM :query_text;
+
+EXEC SQL DESCRIBE INPUT emp_query
+  USING SQL DESCRIPTOR 'query_params';
+```
+
+After describing the query, the `query_params` descriptor contains information about each parameter required by the query.
+
+For this example, assume that the user entered:
+
+```sql
+SELECT ename FROM emp WHERE sal > ? AND job = ?;,
+```
+
+In this case, the descriptor describes two parameters, one for `sal > ?` and one for `job = ?`.
+
+To discover the number of parameter markers (question marks) in the query and therefore the number of values you must provide before executing the query, use:
+
+```sql
+EXEC SQL GET DESCRIPTOR … :host_variable = COUNT;
+```
+
+Then, you can use `EXEC SQL GET DESCRIPTOR` to retrieve the name of each parameter. You can also use `EXEC SQL GET DESCRIPTOR` to retrieve the type of each parameter from the descriptor, along with the number of parameters. Or you can supply each `value` in the form of a character string and ECPG converts that string into the required data type.
+
+The data type of the first parameter is `numeric`. The type of the second parameter is `varchar`. The name of the first parameter is `sal`. The name of the second parameter is `job`.
+
+Next, loop through each parameter, prompting the user for a value, and store those values in host variables. You can use `GET DESCRIPTOR … COUNT` to find the number of parameters in the query.
+
+```sql
+EXEC SQL GET DESCRIPTOR 'query_params'
+  :param_count = COUNT;
+
+for(param_number = 1;
+    param_number <= param_count;
+    param_number++)
+{
+```
+
+Use `GET DESCRIPTOR` to copy the name of the parameter into the `param_name` host variable:
+
+```sql
+EXEC SQL GET DESCRIPTOR 'query_params'
+  VALUE :param_number :param_name = NAME;
+
+reply = promptUser(param_name);
+if (reply == NULL)
+ reply_ind = 1; /* NULL */
+else
+ reply_ind = 0; /* NOT NULL */
+```
+
+To associate a `value` with each parameter, you use the `EXEC SQL SET DESCRIPTOR` statement. For example:
+
+```sql
+EXEC SQL SET DESCRIPTOR 'query_params'
+  VALUE :param_number DATA = :reply;
+EXEC SQL SET DESCRIPTOR 'query_params'
+  VALUE :param_number INDICATOR = :reply_ind;
+}
+```
+
+Now, you can use the `EXEC SQL EXECUTE DESCRIPTOR` statement to execute the prepared statement on the server.
+
+## UPDATE
+
+Use an `UPDATE` statement to modify the data stored in a table. The syntax is:
+
+```sql
+EXEC SQL [AT <database_name>][FOR <exec_count>]
+    UPDATE [ ONLY ] table [ [ AS ] alias ]
+    SET {column = { expression | DEFAULT } |
+        (column [, ...]) = ({ expression|DEFAULT } [, ...])} [, ...]
+    [ FROM from_list ]
+    [ WHERE condition | WHERE CURRENT OF cursor_name ]
+    [ RETURNING * | output_expression [[ AS ] output_name] [, ...] ]
+```
+
+Where `database_name` is the name of the database or host variable that contains the name of the database in which the table resides. This value can take the form of an unquoted string literal or of a host variable.
+
+Include the `FOR exec_count` clause to specify the number of times the statement executes. This clause is valid only if the `SET` or `WHERE` clause contains an array.
+
+ECPGPlus provides support for the additional clauses of the SQL `UPDATE` statement as documented in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-update.html).
+
+You can use a host variable in any clause that specifies a value. To use a host variable, substitute a defined variable for any value associated with any of the documented `UPDATE` clauses.
+
+The following `UPDATE` statement changes the job description of an employee (identified by the `:ename` host variable) to the value contained in the `:new_job` host variable. It increases the employees salary by multiplying the current salary by the value in the `:increase` host variable:
+
+```sql
+EXEC SQL UPDATE emp
+  SET job = :new_job, sal = sal * :increase
+  WHERE ename = :ename;
+```
+
+The enhanced `UPDATE` statement also allows you to include parameter markers (question marks) in any clause where an input value is permitted. For example, we can write the same update statement with a parameter marker in the `WHERE` clause:
+
+```sql
+EXEC SQL UPDATE emp
+  SET job = ?, sal = sal * ?
+  WHERE ename = :ename;
+```
+
+This `UPDATE` statement allows you to prompt the user for a new value for the `job` column and provide the amount by which the `sal` column is incremented for the employee specified by `:ename`.
+
+## WHENEVER
+
+Use the `WHENEVER` statement to specify the action taken by a client application when it encounters an SQL error or warning. The syntax is:
+
+```sql
+EXEC SQL WHENEVER <condition> <action>;
+```
+
+The following table describes the different conditions that might trigger an `action`.
+
+| Condition     | Description                                                                                                                                   |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `NOT FOUND`   | The server returns a `NOT FOUND` condition when it encounters a `SELECT` that returns no rows or when a `FETCH` reaches the end of a result set. |
+| `SQLERROR`    | The server returns an `SQLERROR` condition when it encounters a serious error returned by an SQL statement.                                       |
+| `SQLWARNING`  | The server returns an `SQLWARNING` condition when it encounters a nonfatal warning returned by an SQL statement.                                 |
+
+The following table describes the actions that result from a client encountering a `condition`.
+
+| Action                        | Description                                                                                                                                                                                             |
+| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CALL function [([args])]`    | Call the named `function`.                                                                                                                                              |
+| `CONTINUE`                    | Proceed to the next statement.                                                                                                                                          |
+| `DO BREAK`                    | Emit a C break statement. A break statement can appear in a `loop` or a `switch` statement. If executed, the break statement terminates the `loop` or the `switch` statement. |
+| `DO CONTINUE`                 | Emit a C `continue` statement. A `continue` statement can exist only in a loop. If executed, it causes the flow of control to return to the top of the loop.   |
+| `DO function ([args])`        | Call the named `function`.                                                                                                                                              |
+| `GOTO label` or `GO TO label` | Proceed to the statement that contains the label.                                                                                                                     |
+| `SQLPRINT`                    | Print a message to standard error.                                                                                                                                      |
+| `STOP`                        | Stop executing.                                                                                                                                                         |
+
+The following code fragment prints a message if the client application encounters a warning and aborts the application if it encounters an error:
+
+```sql
+EXEC SQL WHENEVER SQLWARNING SQLPRINT;
+EXEC SQL WHENEVER SQLERROR STOP;
+```
+
+Include the following code to specify for a client to continue processing after warning a user of a problem:
+
+```sql
+EXEC SQL WHENEVER SQLWARNING SQLPRINT;
+```
+
+Include the following code to call a function if a query returns no rows or when a cursor reaches the end of a result set:
+
+```sql
+EXEC SQL WHENEVER NOT FOUND CALL error_handler(__LINE__);
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx
new file mode 100644
index 00000000000..c855e0c154e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/index.mdx
@@ -0,0 +1,75 @@
+---
+title: "Language element reference"
+description: "Description of the ECPGPlus language elements"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.55.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.56.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.57.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.23.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.49.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.51.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.28.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.24.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.27.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.48.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.29.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.25.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.30.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.47.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.31.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.46.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.32.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.45.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.33.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.44.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.34.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.26.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.43.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.35.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.52.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.50.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.42.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.53.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.54.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.36.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.59.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.58.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.41.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.37.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.40.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.38.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/ecpgplus-guide/9.6/EDB_Postgres_Advanced_Server_ecpgPlus_Guide.1.39.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.093.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.058.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.031.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.033.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.085.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.087.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.082.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.088.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.349.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.351.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.352.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.350.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.348.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.114.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.119.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.113.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.111.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.108.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.086.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.063.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.061.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.103.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.104.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.100.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.102.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.101.html"
+---
+
+<div id="reference" class="registered_link"></div>
+
+ECPGPlus has these language elements.
+
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/sqlda_structure.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/sqlda_structure.mdx
new file mode 100644
index 00000000000..9e4a92a10a9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/sqlda_structure.mdx
@@ -0,0 +1,120 @@
+---
+title: "The SQLDA structure"
+---
+
+Oracle Dynamic SQL method 4 uses the SQLDA data structure to hold the data and metadata for a dynamic SQL statement. A SQLDA structure can describe a set of input parameters corresponding to the parameter markers found in the text of a dynamic statement or the result set of a dynamic statement. 
+
+## Layout
+
+The layout of the SQLDA structure is:
+
+```c
+struct SQLDA
+{
+  int     N; /* Number of entries             */
+  char  **V; /* Variables                 */
+  int    *L; /* Variable lengths          */
+  short  *T; /* Variable types            */
+  short **I; /* Indicators                */
+  int     F; /* Count of variables discovered by DESCRIBE */
+  char  **S; /* Variable names            */
+  short  *M; /* Variable name maximum lengths     */
+  short  *C; /* Variable name actual lengths  */
+  char  **X; /* Indicator names           */
+  short  *Y; /* Indicator name maximum lengths */
+  short  *Z; /* Indicator name actual lengths     */
+};
+```
+
+## Parameters
+
+`N - maximum number of entries`
+
+ The `N` structure member contains the maximum number of entries that the SQLDA can describe. This member is populated by the `sqlald()` function when you allocate the SQLDA structure. Before using a descriptor in an `OPEN` or `FETCH` statement, you must set `N` to the actual number of values described.
+
+`V - data values`
+
+ The `V` structure member is a pointer to an array of data values.
+
+-   For a `SELECT`-list descriptor, `V` points to an array of values returned by a `FETCH` statement. Each member in the array corresponds to a column in the result set.
+-   For a bind descriptor, `V` points to an array of parameter values. You must populate the values in this array before opening a cursor that uses the descriptor.
+
+Your application must allocate the space required to hold each value. See [displayResultSet](/epas/latest/application_programming/ecpgplus_guide/05_building_executing_dynamic_sql_statements/#executing_query_with_unknown_number_of_variables) for an example of how to allocate space for `SELECT`-list values.
+
+`L - length of each data value`
+
+ The `L` structure member is a pointer to an array of lengths. Each member of this array must indicate the amount of memory available in the corresponding member of the `V` array. For example, if `V[5]` points to a buffer large enough to hold a 20-byte NULL-terminated string, `L[5]` must contain the value 21 (20 bytes for the characters in the string plus 1 byte for the NULL-terminator). Your application must set each member of the `L` array.
+
+`T - data types`
+
+ The `T` structure member points to an array of data types, one for each column (or parameter) described by the descriptor.
+
+-   For a bind descriptor, you must set each member of the `T` array to tell ECPGPlus the data type of each parameter.
+-   For a `SELECT`-list descriptor, the `DESCRIBE SELECT LIST` statement sets each member of the `T` array to reflect the type of data found in the corresponding column.
+
+You can change any member of the `T` array before executing a `FETCH` statement to force ECPGPlus to convert the corresponding value to a specific data type. For example, if the `DESCRIBE SELECT LIST` statement indicates that a given column is of type `DATE`, you can change the corresponding `T` member to request that the next `FETCH` statement return that value in the form of a NULL-terminated string. Each member of the `T` array is a numeric type code (see [Type Codes](type_codes.mdx) for a list of type codes). The type codes returned by a `DESCRIBE SELECT LIST` statement differ from those expected by a `FETCH` statement. After executing a `DESCRIBE SELECT LIST` statement, each member of `T` encodes a data type and a flag indicating whether the corresponding column is nullable. You can use the `sqlnul()` function to extract the type code and nullable flag from a member of the T array. The signature of the `sqlnul()` function is as follows:
+
+```c
+void sqlnul(unsigned short *valType,
+            unsigned short *typeCode,
+            int            *isNull)
+```
+
+For example, to find the type code and nullable flag for the third column of a descriptor named results, invoke `sqlnul()` as follows:
+
+```c
+sqlnul(&results->T[2], &typeCode, &isNull);
+```
+
+`I - indicator variables`
+
+ The `I` structure member points to an array of indicator variables. This array is allocated for you when your application calls the `sqlald()` function to allocate the descriptor.
+
+-   For a `SELECT`-list descriptor, each member of the `I` array indicates whether the corresponding column contains a NULL (non-zero) or non-NULL (zero) value.
+-   For a bind parameter, your application must set each member of the `I` array to indicate whether the corresponding parameter value is NULL.
+
+`F - number of entries`
+
+ The `F` structure member indicates how many values are described by the descriptor. The `N` structure member indicates the maximum number of values that the descriptor can describe. `F` indicates the actual number of values. The value of the `F` member is set by ECPGPlus when you execute a `DESCRIBE` statement. `F` can be positive, negative, or zero.
+
+-   For a `SELECT`-list descriptor, `F` contains a positive value if the number of columns in the result set is equal to or less than the maximum number of values permitted by the descriptor (as determined by the `N` structure member). It contains 0 if the statement isn't a `SELECT` statement. It contains a negative value if the query returns more columns than allowed by the `N` structure member.
+-   For a bind descriptor, `F` contains a positive number if the number of parameters found in the statement is less than or equal to the maximum number of values permitted by the descriptor (as determined by the `N` structure member). It contains 0 if the statement contains no parameters markers. It contains a negative value if the statement contains more parameter markers than allowed by the `N` structure member.
+
+If `F` contains a positive number (after executing a `DESCRIBE` statement), that number reflects the count of columns in the result set (for a `SELECT`-list descriptor) or the number of parameter markers found in the statement (for a bind descriptor). If `F` contains a negative value, you can compute the absolute value of `F` to discover how many values or parameter markers are required. For example, if `F` contains `-24` after describing a `SELECT` list, you know that the query returns 24 columns.
+
+`S - column/parameter names`
+
+ The `S` structure member points to an array of NULL-terminated strings.
+
+-   For a `SELECT`-list descriptor, the `DESCRIBE SELECT LIST` statement sets each member of this array to the name of the corresponding column in the result set.
+-   For a bind descriptor, the `DESCRIBE BIND VARIABLES` statement sets each member of this array to the name of the corresponding bind variable.
+
+In this release, the name of each bind variable is determined by the left-to-right order of the parameter marker within the query. For example, the name of the first parameter is always `?0`, the name of the second parameter is always `?1`, and so on.
+
+`M - maximum column/parameter name length`
+
+ The `M` structure member points to an array of lengths. Each member in this array specifies the maximum length of the corresponding member of the `S` array (that is, `M[0]` specifies the maximum length of the column/parameter name found at `S[0]`). This array is populated by the `sqlald()` function.
+
+`C - actual column/parameter name length`
+
+ The `C` structure member points to an array of lengths. Each member in this array specifies the actual length of the corresponding member of the `S` array (that is, `C[0]` specifies the actual length of the column/parameter name found at `S[0]`).
+
+ This array is populated by the `DESCRIBE` statement.
+
+`X - indicator variable names`
+
+ The `X` structure member points to an array of NULL-terminated strings. Each string represents the name of a NULL indicator for the corresponding value.
+
+ This array isn't used by ECPGPlus but is provided for compatibility with Pro\*C applications.
+
+`Y - maximum indicator name length`
+
+ The `Y` structure member points to an array of lengths. Each member in this array specifies the maximum length of the corresponding member of the `X` array (that is, `Y[0]` specifies the maximum length of the indicator name found at `X[0]`).
+
+ This array isn't used by ECPGPlus but is provided for compatibility with Pro\*C applications.
+
+`Z - actual indicator name length`
+
+ The `Z` structure member points to an array of lengths. Each member in this array specifies the actual length of the corresponding member of the `X` array (that is, `Z[0]` specifies the actual length of the indicator name found at `X[0]`).
+
+ This array isn't used by ECPGPlus but is provided for compatibility with Pro\*C applications.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/supported_c_data_types.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/supported_c_data_types.mdx
new file mode 100644
index 00000000000..3a9fd43129e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/supported_c_data_types.mdx
@@ -0,0 +1,36 @@
+---
+title: "Supported C data types"
+---
+
+<div id="supported_c_data_types" class="registered_link"></div>
+
+An ECPGPlus application must deal with two sets of data types: SQL data types (such as `SMALLINT`, `DOUBLE PRECISION`, and `CHARACTER VARYING`) and C data types (like `short`, `double`, and `varchar[n]`). When an application fetches data from the server, ECPGPlus maps each SQL data type to the type of the C variable into which the data is returned.
+
+In general, ECPGPlus can convert most SQL server types into similar C types, but not all combinations are valid. For example, ECPGPlus tries to convert a SQL character value into a C integer value, but the conversion might fail at execution time if the SQL character value contains non-numeric characters. 
+
+The reverse is also true. When an application sends a value to the server, ECPGPlus tries to convert the C data type into the required SQL type. Again, the conversion might fail at execution time if the C value can't be converted into the required SQL type.
+
+ECPGPlus can convert any SQL type into C character values (`char[n]` or `varchar[n]`). Although it's safe to convert any SQL type to or from `char[n]` or `varchar[n]`, it's often convenient to use more natural C types such as `int`, `double`, or `float`.
+
+The supported C data types are:
+
+-   `short`
+-   `int`
+-   `unsigned int`
+-   `long long int`
+-   `float`
+-   `double`
+-   `char[n+1]`
+-   `varchar[n+1]`
+-   `bool`
+-   Any equivalent created by a `typedef`
+
+In addition to the numeric and character types supported by C, the `pgtypeslib` runtime library offers custom data types, as well as functions to operate on those types, for dealing with date/time and exact numeric values:
+
+-   `timestamp`
+-   `interval`
+-   `date`
+-   `decimal`
+-   `numeric`
+
+To use a data type supplied by `pgtypeslib`, you must `#include` the proper header file.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/type_codes.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/type_codes.mdx
new file mode 100644
index 00000000000..f1680125d20
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/07_reference/type_codes.mdx
@@ -0,0 +1,40 @@
+---
+title: "Type codes"
+---
+
+## Type codes for external data types
+
+The following table contains the type codes for *external* data types. An external data type is used to indicate the type of a C host variable. When an application binds a value to a parameter or binds a buffer to a `SELECT`-list item, set the type code in the corresponding SQLDA descriptor `(descriptor->T[column])` to one of the following values:
+
+| Type code                                         | Host variable type (C data type)          |
+| ------------------------------------------------- | ----------------------------------------- |
+| `1, 2, 8, 11, 12, 15, 23, 24, 91, 94, 95, 96, 97` | `char[]`                                  |
+| `3`                                               | `int`                                     |
+| `4, 7, 21`                                        | `float`                                   |
+| `5, 6`                                            | `null-terminated string (char[length+1])` |
+| `9`                                               | `varchar`                                 |
+| `22`                                              | `double`                                  |
+| `68`                                              | `unsigned int`                            |
+
+## Type codes for internal data types
+
+The following table contains the type codes for *internal* data types. An internal type code is used to indicate the type of a value as it resides in the database. The `DESCRIBE SELECT LIST` statement populates the data type array `(descriptor->T[column])` using the following values.
+
+| Internal type code     | Server type              |
+| ---------------------- | ------------------------ |
+| `1`                    | `VARCHAR2`               |
+| `2`                    | `NUMBER`                 |
+| `8`                    | `LONG`                   |
+| `11`                   | `ROWID`                  |
+| `12`                   | `DATE`                   |
+| `23`                   | `RAW`                    |
+| `24`                   | `LONG RAW`               |
+| `96`                   | `CHAR`                   |
+| `100`                  | `BINARY FLOAT`           |
+| `101`                  | `BINARY DOUBLE`          |
+| `104`                  | `UROWID`                 |
+| `187`                  | `TIMESTAMP`              |
+| `188`                  | `TIMESTAMP W/TIMEZONE`   |
+| `189`                  | `INTERVAL YEAR TO MONTH` |
+| `190`                  | `INTERVAL DAY TO SECOND` |
+| `232`                  | `TIMESTAMP LOCAL_TZ`     |
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/index.mdx
new file mode 100644
index 00000000000..6cc9e065670
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "Application programmer reference"
+indexCards: simple
+description: "Contains reference information applicable to application programmer tasks, such as the layout of system catalog tables"
+---
+
+This reference information applies to application programmers.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx
new file mode 100644
index 00000000000..29207131d8b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/02_case_sensitivity.mdx
@@ -0,0 +1,26 @@
+---
+title: "Case sensitivity"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/02_case_sensitivity/
+---
+
+<div id="case_sensitivity" class="registered_link"></div>
+
+Keywords and user-defined identifiers that are used in an SPL program are case insensitive. For example, the statement `DBMS_OUTPUT.PUT_LINE('Hello World');` is interpreted the as `dbms_output.put_line('Hello World');` or `Dbms_Output.Put_Line('Hello World');` or `DBMS_output.Put_line('Hello World');`.
+
+Character and string constants, however, are case sensitive. Data retrieved from the EDB Postgres Advanced Server database or from other external sources is also case sensitive. 
+
+The statement `DBMS_OUTPUT.PUT_LINE('Hello World!');` produces the following output:
+
+```sql
+__OUTPUT__
+Hello World!
+```
+
+The statement `DBMS_OUTPUT.PUT_LINE('HELLO WORLD!');` produces this output:
+
+```sql
+__OUTPUT__
+HELLO WORLD!
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx
new file mode 100644
index 00000000000..7ebd112c630
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/03_identifiers.mdx
@@ -0,0 +1,21 @@
+---
+title: "Identifiers"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/03_identifiers/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/03_identifiers/
+---
+
+<div id="identifiers" class="registered_link"></div>
+
+*Identifiers* are user-defined names that identify elements of an SPL program including variables, cursors, labels, programs, and parameters. The syntax rules for valid identifiers are the same as for identifiers in the SQL language.
+
+An identifier can't be the same as an SPL keyword or a keyword of the SQL language. The following are some examples of valid identifiers:
+
+```text
+x
+last___name
+a_$_Sign
+Many$$$$$$$$signs_____
+THIS_IS_AN_EXTREMELY_LONG_NAME
+A1
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx
new file mode 100644
index 00000000000..209302b11f8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/04_qualifiers.mdx
@@ -0,0 +1,45 @@
+---
+title: "Qualifiers"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/04_qualifiers/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/04_qualifiers/
+---
+
+<div id="qualifiers" class="registered_link"></div>
+
+A *qualifier* is a name that specifies the owner or context of an entity that's the object of the qualifier. Specify a qualified object using these elements, in order:
+
+1. The qualifier name 
+2. A dot with no intervening white space
+3. The name of the object being qualified with no intervening white space
+
+This syntax is called *dot notation*.
+
+The following is the syntax of a qualified object.
+
+```text
+<qualifier>. [ <qualifier>. ]... <object>
+```
+
+`qualifier` is the name of the owner of the object. `object` is the name of the entity belonging to `qualifier`. You can have a chain of qualifications in which the preceding qualifier owns the entity identified by the subsequent qualifiers and object.
+
+You can qualify almost any identifier. How you qualify an identifier depends on what the identifier represents and its context.
+
+Some examples of qualification follow:
+
+-   Procedure and function names qualified by the schema to which they belong, e.g., `schema_name.procedure_name(...)`
+-   Trigger names qualified by the schema to which they belong, e.g., `schema_name.trigger_name`
+-   Column names qualified by the table to which they belong, e.g., `emp.empno`
+-   Table names qualified by the schema to which they belong, e.g., `public.emp`
+-   Column names qualified by table and schema, e.g., `public.emp.empno`
+
+As a general rule, where a name appears in the syntax of an SPL statement you can use its qualified name as well. Typically, a qualified name is used only if ambiguity is associated with the name. Examples of ambiguity include, for example:
+
+-  Two procedures with the same name belonging to two different schemas are invoked from a program.
+-  The same name is used for a table column and SPL variable in the same program.
+
+Avoid using qualified names if possible. We use the following conventions to avoid naming conflicts:
+
+-   All variables declared in the declaration section of an SPL program are prefixed by `v_`, e.g., `v_empno`.
+-   All formal parameters declared in a procedure or function definition are prefixed by `p_`, e.g., `p_empno`.
+-   Column names and table names don't have any special prefix conventions, e.g., column `empno` in table `emp`.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx
new file mode 100644
index 00000000000..563e959f122
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/05_constants.mdx
@@ -0,0 +1,17 @@
+---
+title: "Constants"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.041.html"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/05_constants/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/05_constants/
+---
+
+<div id="constants" class="registered_link"></div>
+
+*Constants* or *literals* are fixed values that you can use in SPL programs to represent values of various types such as numbers, strings, and dates. Constants come in the following types:
+
+-   Numeric (integer and real)
+-   Character and string
+-   Date/time
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx
new file mode 100644
index 00000000000..c8e67ed7ab6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/06_user_defined_pl_sql_subtypes.mdx
@@ -0,0 +1,118 @@
+---
+title: "User-defined PL/SQL subtypes"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.048.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.142.html"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/06_user_defined_pl_sql_subtypes/
+---
+
+<div id="user_defined_pl_sql_subtypes" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports user-defined PL/SQL subtypes and subtype aliases. 
+
+## About subtypes
+
+A subtype is a data type with an optional set of constraints that restrict the values that can be stored in a column of that type. The rules that apply to the type on which the subtype is based are still enforced, but you can use additional constraints to place limits on the precision or scale of values stored in the type.
+
+You can define a subtype in the declaration of a PL function, procedure, anonymous block, or package. The syntax is:
+
+```sql
+SUBTYPE <subtype_name> IS <type_name>[(<constraint>)] [NOT NULL]
+```
+
+Where `constraint` is:
+
+```text
+{<precision> [, <scale>]} | <length>
+```
+
+`subtype_name`
+
+ `subtype_name` specifies the name of the subtype.
+
+`type_name`
+
+ `type_name` specifies the name of the original type on which the subtype is based. `type_name` can be:
+
+-   The name of any of the types supported by EDB Postgres Advanced Server.
+-   The name of any composite type.
+-   A column anchored by a `%TYPE` operator.
+-   The name of another subtype.
+
+Include the `constraint` clause to define restrictions for types that support precision or scale.
+
+`precision`
+
+ `precision` specifies the total number of digits permitted in a value of the subtype.
+
+`scale`
+
+ `scale` specifies the number of fractional digits permitted in a value of the subtype.
+
+`length`
+
+ `length` specifies the total length permitted in a value of `CHARACTER`, `VARCHAR`, or `TEXT` base types.
+
+Include the `NOT NULL` clause to specify that you can't store `NULL` values in a column of the specified subtype.
+
+A subtype that is based on a column inherits the column size constraints, but the subtype doesn't inherit `NOT NULL` or `CHECK` constraints.
+
+## Unconstrained subtypes
+
+To create an unconstrained subtype, use the `SUBTYPE` command to specify the new subtype name and the name of the type on which the subtype is based. For example, the following command creates a subtype named `address` that has all of the attributes of the type `CHAR`:
+
+```sql
+SUBTYPE address IS CHAR;
+```
+
+You can also create a subtype (constrained or unconstrained) that's a subtype of another subtype:
+
+```sql
+SUBTYPE cust_address IS address NOT NULL;
+```
+
+This command creates a subtype named `cust_address` that shares all of the attributes of the `address` subtype. Include the `NOT NULL` clause to specify that a value of the `cust_address` can't be `NULL`.
+
+## Constrained subtypes
+
+Include a `length` value when creating a subtype that's based on a character type to define the maximum length of the subtype. For example:
+
+```sql
+SUBTYPE acct_name IS VARCHAR (15);
+```
+
+This example creates a subtype named `acct_name` that's based on a `VARCHAR` data type but is limited to 15 characters.
+
+Include values for `precision` to specify the maximum number of digits in a value of the subtype. Optionally, include values for `scale` to specify the number of digits to the right of the decimal point when constraining a numeric base type. For example:
+
+```sql
+SUBTYPE acct_balance IS NUMBER (5, 2);
+```
+
+This example creates a subtype named `acct_balance` that shares all of the attributes of a `NUMBER` type but that can't exceed three digits to the left of the decimal point and two digits to the right of the decimal.
+
+An argument declaration (in a function or procedure header) is a *formal argument*. The value passed to a function or procedure is an *actual argument*. When invoking a function or procedure, the caller provides 0 or more actual arguments. Each actual argument is assigned to a formal argument that holds the value in the body of the function or procedure.
+
+If a formal argument is declared as a constrained subtype, EDB Postgres Advanced Server:
+
+-   Enforces subtype constraints when assigning an actual argument to a formal argument when invoking a procedure.
+-   Doesn't enforce subtype constraints when assigning an actual argument to a formal argument when invoking a function.
+
+## Using the %TYPE operator
+
+You can use `%TYPE` notation to declare a subtype anchored to a column. For example:
+
+```sql
+SUBTYPE emp_type IS emp.empno%TYPE
+```
+
+This command creates a subtype named `emp_type` whose base type matches the type of the `empno` column in the `emp` table. A subtype that's based on a column shares the column size constraints. `NOT NULL` and `CHECK` constraints aren't inherited.
+
+## Subtype conversion
+
+Unconstrained subtypes are aliases for the type on which they are based. Any variable of type subtype (unconstrained) is interchangeable with a variable of the base type without conversion, and vice versa.
+
+You can interchange a variable of a constrained subtype with a variable of the base type without conversion. However, you can interchange a variable of the base type with a constrained subtype only if it complies with the constraints of the subtype. You can implicitly convert a variable of a constrained subtype to another subtype if it's based on the same subtype and the constraint values are within the values of the subtype to which it is being converted.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx
new file mode 100644
index 00000000000..31843d1f9c4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/07_character.mdx
@@ -0,0 +1,19 @@
+---
+title: "Character set"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/07_character/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/07_character/
+---
+
+<div id="character_set" class="registered_link"></div>
+
+Write identifiers, expressions, statements, control structures, and so on that comprise the SPL language using the following characters:
+
+-   Uppercase letters A&ndash;Z and lowercase letters a&ndash;z
+-   Digits 0&ndash;9`
+-   Symbols ( ) + - * / < > = ! ~ ^ ; : . ' @ % , " # $ & _ | { } ? [ ]
+-   Whitespace characters tab, space, and carriage return
+
+
+!!! Note
+    The data that can be manipulated by an SPL program is determined by the character set supported by the database encoding.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx
new file mode 100644
index 00000000000..764ec9c59d2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/01_basic_spl_elements/index.mdx
@@ -0,0 +1,15 @@
+---
+title: "Basic SPL elements"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.047.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.141.html"
+redirects:
+  - /epas/latest/epas_compat_spl/01_basic_spl_elements/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/01_basic_spl_elements/
+---
+
+<div id="basic_spl_elements" class="registered_link"></div>
+
+The basic programming elements of an SPL program include aspects such as as case sensitivity and the available character set.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx
new file mode 100644
index 00000000000..236e0ef1dd1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/01_assignment.mdx
@@ -0,0 +1,43 @@
+---
+title: "Assignment"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/01_assignment/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/01_assignment/
+---
+
+<div id="assignment" class="registered_link"></div>
+
+The assignment statement sets a variable or a formal parameter of mode `OUT` or `IN OUT` specified on the left side of the assignment `:=` to the evaluated expression specified on the right side of the assignment.
+
+```text
+<variable> := <expression>;
+```
+
+`variable` is an identifier for a previously declared variable, `OUT` formal parameter, or `IN OUT` formal parameter.
+
+`expression` is an expression that produces a single value. The value produced by the expression must have a data type compatible with that of `variable`.
+
+This example shows the typical use of assignment statements in the executable section of the procedure:
+
+```sql
+CREATE OR REPLACE PROCEDURE dept_salary_rpt (
+    p_deptno        NUMBER
+)
+IS
+    todays_date     DATE;
+    rpt_title       VARCHAR2(60);
+    base_sal        INTEGER;
+    base_comm_rate  NUMBER;
+    base_annual     NUMBER;
+BEGIN
+    todays_date := SYSDATE;
+    rpt_title := 'Report For Department # ' || p_deptno || ' on '
+        || todays_date;
+    base_sal := 35525;
+    base_comm_rate := 1.33333;
+    base_annual := ROUND(base_sal * base_comm_rate, 2);
+
+    DBMS_OUTPUT.PUT_LINE(rpt_title);
+    DBMS_OUTPUT.PUT_LINE('Base Annual Salary: ' || base_annual);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx
new file mode 100644
index 00000000000..aaad0506585
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/02_delete.mdx
@@ -0,0 +1,47 @@
+---
+title: "DELETE"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/02_delete/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/02_delete/
+---
+
+<div id="delete" class="registered_link"></div>
+
+You can use the `DELETE` command available in the SQL language in SPL programs.
+
+You can use an expression in the SPL language wherever an expression is allowed in the SQL `DELETE` command. Thus, you can use SPL variables and parameters to supply values to the delete operation.
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_delete (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+BEGIN
+    DELETE FROM emp WHERE empno = p_empno;
+
+    IF SQL%FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Deleted Employee # : ' || p_empno);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee # ' || p_empno || ' not found');
+    END IF;
+END;
+```
+
+The `SQL%FOUND` conditional expression returns `TRUE` if a row is deleted, `FALSE` otherwise. See [Obtaining the result status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions.
+
+This example deletes an employee using this procedure:
+
+```sql
+EXEC emp_delete(9503);
+
+Deleted Employee # : 9503
+
+SELECT * FROM emp WHERE empno = 9503;
+__OUTPUT__
+ empno | ename | job | mgr | hiredate | sal | comm | deptno
+-------+-------+-----+-----+----------+-----+------+--------
+(0 rows)
+```
+
+!!! Note
+    You can include the `DELETE` command in a `FORALL` statement. A `FORALL` statement allows a single `DELETE` command to delete multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx
new file mode 100644
index 00000000000..d85fcb25033
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/03_insert.mdx
@@ -0,0 +1,84 @@
+---
+title: "INSERT"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/03_insert/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/03_insert/
+---
+
+<div id="insert" class="registered_link"></div>
+
+You can use the `INSERT` command available in the SQL language in SPL programs.
+
+You can use an expression in the SPL language wherever an expression is allowed in the SQL `INSERT` command. Thus, you can use SPL variables and parameters to supply values to the insert operation.
+
+This example is a procedure that inserts a new employee using data passed from a calling program:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_insert (
+    p_empno         IN emp.empno%TYPE,
+    p_ename         IN emp.ename%TYPE,
+    p_job           IN emp.job%TYPE,
+    p_mgr           IN emp.mgr%TYPE,
+    p_hiredate      IN emp.hiredate%TYPE,
+    p_sal           IN emp.sal%TYPE,
+    p_comm          IN emp.comm%TYPE,
+    p_deptno        IN emp.deptno%TYPE
+)
+IS
+BEGIN
+    INSERT INTO emp VALUES (
+        p_empno,
+        p_ename,
+        p_job,
+        p_mgr,
+        p_hiredate,
+        p_sal,
+        p_comm,
+        p_deptno);
+
+    DBMS_OUTPUT.PUT_LINE('Added employee...');
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || p_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || p_job);
+    DBMS_OUTPUT.PUT_LINE('Manager    : ' || p_mgr);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || p_hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || p_sal);
+    DBMS_OUTPUT.PUT_LINE('Commission : ' || p_comm);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || p_deptno);
+    DBMS_OUTPUT.PUT_LINE('----------------------');
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('OTHERS exception on INSERT of employee # '
+            || p_empno);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE : ' || SQLCODE);
+        DBMS_OUTPUT.PUT_LINE('SQLERRM : ' || SQLERRM);
+END;
+```
+
+If an exception occurs, all database changes made in the procedure are rolled back. In this example, the `EXCEPTION` section with the `WHEN OTHERS` clause catches all exceptions. Two variables are displayed. `SQLCODE` is a number that identifies the specific exception that occurred. `SQLERRM` is a text message explaining the error. See [Exception handling](../05_control_structures/07_exception_handling/#exception_handling) for more information.
+
+The following shows the output when this procedure is executed:
+
+```sql
+EXEC emp_insert(9503,'PETERSON','ANALYST',7902,'31-MAR-05',5000,NULL,40);
+
+Added employee...
+Employee # : 9503
+Name       : PETERSON
+Job        : ANALYST
+Manager    : 7902
+Hire Date  : 31-MAR-05 00:00:00
+Salary     : 5000
+Dept #     : 40
+----------------------
+
+SELECT * FROM emp WHERE empno = 9503;
+__OUTPUT__
+ empno | ename  |  job   | mgr  |      hiredate     |   sal   | comm | deptno
+-------+--------+--------+------+-------------------+---------+------+-------
+  9503 |PETERSON| ANALYST| 7902 | 31-MAR-05 00:00:00| 5000.00 |      |   40
+(1 row)
+```
+
+!!! Note
+    You can include the `INSERT` command in a `FORALL` statement. A `FORALL` statement allows a single `INSERT` command to insert multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx
new file mode 100644
index 00000000000..68d330ab738
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/04_null.mdx
@@ -0,0 +1,40 @@
+---
+title: "NULL"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/04_null/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/04_null/
+---
+
+<div id="null" class="registered_link"></div>
+
+The simplest statement is the `NULL` statement. This statement is an executable statement that does nothing.
+
+```sql
+NULL;
+```
+
+The following is the simplest possible valid SPL program:
+
+```sql
+BEGIN
+    NULL;
+END;
+```
+
+The `NULL` statement can act as a placeholder where an executable statement is required such as in a branch of an `IF-THEN-ELSE` statement. For example:
+
+```sql
+CREATE OR REPLACE PROCEDURE divide_it (
+    p_numerator     IN  NUMBER,
+    p_denominator   IN  NUMBER,
+    p_result        OUT NUMBER
+)
+IS
+BEGIN
+    IF p_denominator = 0 THEN
+        NULL;
+    ELSE
+        p_result := p_numerator / p_denominator;
+    END IF;
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx
new file mode 100644
index 00000000000..b7d4467c968
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/05_using_the_returning_into_clause.mdx
@@ -0,0 +1,138 @@
+---
+title: "RETURNING INTO"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/05_using_the_returning_into_clause/
+---
+
+<div id="using_the_returning_into_clause" class="registered_link"></div>
+
+You can append the `INSERT`, `UPDATE`, and `DELETE` commands with the optional `RETURNING INTO` clause. This clause allows the SPL program to capture the newly added, modified, or deleted values from the results of an `INSERT`, `UPDATE`, or `DELETE` command, respectively.
+
+## Syntax 
+
+```sql
+{ <insert> | <update> | <delete> }
+   RETURNING { * | <expr_1> [, <expr_2> ] ...}
+     INTO { <record> | <field_1> [, <field_2> ] ...};
+```
+
+-  `insert` is a valid `INSERT` command. 
+-  `update` is a valid `UPDATE` command. 
+-  `delete` is a valid `DELETE` command. 
+-  If you specify `*`, then the values from the row affected by the `INSERT`, `UPDATE`, or `DELETE` command are made available for assignment to the record or fields to the right of the `INTO` keyword. (The use of `*` is an EDB Postgres Advanced Server extension and isn't compatible with Oracle databases.) 
+-  `expr_1, expr_2...` are expressions evaluated upon the row affected by the `INSERT`, `UPDATE`, or `DELETE` command. The evaluated results are assigned to the record or fields to the right of the `INTO` keyword. 
+-  `record` is the identifier of a record that must contain fields that match in number and order and are data-type compatible with the values in the `RETURNING` clause. 
+-  `field_1, field_2,...` are variables that must match in number and order and are data-type compatible with the set of values in the `RETURNING` clause.
+
+If the `INSERT`, `UPDATE`, or `DELETE` command returns a result set with more than one row, then an exception is thrown with `SQLCODE 01422, query returned more than one row`. If no rows are in the result set, then the variables following the `INTO` keyword are set to null.
+
+!!! Note
+    A variation of `RETURNING INTO` using the `BULK COLLECT` clause allows a result set of more than one row that's returned into a collection. See [Using the BULK COLLECT clause](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/#using_the_bulk_collect_clause) for more information.
+
+## Adding the RETURNING INTO clause
+
+This example modifies the `emp_comp_update` procedure introduced in [UPDATE](07_update/#update). It adds the `RETURNING INTO` clause:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_comp_update (
+    p_empno         IN emp.empno%TYPE,
+    p_sal           IN emp.sal%TYPE,
+    p_comm          IN emp.comm%TYPE
+)
+IS
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_comm          emp.comm%TYPE;
+    v_deptno        emp.deptno%TYPE;
+BEGIN
+    UPDATE emp SET sal = p_sal, comm = p_comm WHERE empno = p_empno
+    RETURNING
+        empno,
+        ename,
+        job,
+        sal,
+        comm,
+        deptno
+    INTO
+        v_empno,
+        v_ename,
+        v_job,
+        v_sal,
+        v_comm,
+        v_deptno;
+
+    IF SQL%FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Updated Employee # : ' || v_empno);
+        DBMS_OUTPUT.PUT_LINE('Name               : ' || v_ename);
+        DBMS_OUTPUT.PUT_LINE('Job                : ' || v_job);
+        DBMS_OUTPUT.PUT_LINE('Department         : ' || v_deptno);
+        DBMS_OUTPUT.PUT_LINE('New Salary         : ' || v_sal);
+        DBMS_OUTPUT.PUT_LINE('New Commission     : ' || v_comm);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee # ' || p_empno || ' not found');
+    END IF;
+END;
+```
+
+The following is the output from this procedure, assuming employee `9503` created by the `emp_insert` procedure still exists in the table:
+
+```sql
+EXEC emp_comp_update(9503, 6540, 1200);
+__OUTPUT__
+Updated Employee # : 9503
+Name               : PETERSON
+Job                : ANALYST
+Department         : 40
+New Salary         : 6540.00
+New Commission     : 1200.00
+```
+
+## Adding the RETURNING INTO clause using record types
+
+This example modifies the `emp_delete` procedure, adding the `RETURNING INTO` clause using record types:
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_delete (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+    r_emp           emp%ROWTYPE;
+BEGIN
+    DELETE FROM emp WHERE empno = p_empno
+    RETURNING
+        *
+    INTO
+        r_emp;
+
+    IF SQL%FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Deleted Employee # : ' || r_emp.empno);
+        DBMS_OUTPUT.PUT_LINE('Name               : ' || r_emp.ename);
+        DBMS_OUTPUT.PUT_LINE('Job                : ' || r_emp.job);
+        DBMS_OUTPUT.PUT_LINE('Manager            : ' || r_emp.mgr);
+        DBMS_OUTPUT.PUT_LINE('Hire Date          : ' || r_emp.hiredate);
+        DBMS_OUTPUT.PUT_LINE('Salary             : ' || r_emp.sal);
+        DBMS_OUTPUT.PUT_LINE('Commission         : ' || r_emp.comm);
+        DBMS_OUTPUT.PUT_LINE('Department         : ' || r_emp.deptno);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee # ' || p_empno || ' not found');
+    END IF;
+END;
+```
+
+The following is the output from this procedure:
+
+```sql
+EXEC emp_delete(9503);
+__OUTPUT__
+Deleted Employee # : 9503
+Name               : PETERSON
+Job                : ANALYST
+Manager            : 7902
+Hire Date          : 31-MAR-05 00:00:00
+Salary             : 6540.00
+Commission         : 1200.00
+Department         : 40
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx
new file mode 100644
index 00000000000..6c52566060c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/06_select_into.mdx
@@ -0,0 +1,107 @@
+---
+title: "SELECT INTO"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/06_select_into/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/06_select_into/
+---
+
+<div id="select_into" class="registered_link"></div>
+
+The `SELECT INTO` statement is an SPL variation of the SQL `SELECT` command. The differences are:
+
+-   `SELECT INTO` assigns the results to variables or records where they can then be used in SPL program statements.
+-   The accessible result set of `SELECT INTO` is at most one row.
+
+Other than these differences, all of the clauses of the `SELECT` command, such as `WHERE`, `ORDER BY`, `GROUP BY`, and `HAVING`, are valid for `SELECT INTO`. 
+
+## Syntax
+
+These examples show two variations of `SELECT INTO`:
+
+```sql
+SELECT <select_expressions> INTO <target> FROM ...;
+```
+
+`target` is a comma-separated list of simple variables. `select_expressions` and the remainder of the statement are the same as for the `SELECT` command. The selected values must exactly match in data type, number, and order the structure of the target or a runtime error occurs.
+
+```sql
+SELECT * INTO <record> FROM <table> ...;
+```
+
+`record` is a record variable that was previously declared.
+
+If the query returns zero rows, null values are assigned to the targets. If the query returns multiple rows, the first row is assigned to the targets and the rest are discarded. ("The first row" isn't well-defined unless you used `ORDER BY.`)
+
+!!! Note
+    -   In either case, where no row is returned or more than one row is returned, SPL throws an exception.
+
+    -   There is a variation of `SELECT INTO` using the `BULK COLLECT` clause that allows a result set of more than one row that's returned into a collection. See [SELECT BULK COLLECT](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/04_using_the_bulk_collect_clause/01_select_bulk_collect/#select_bulk_collect) for more information.
+
+## Including the WHEN NO_DATA_FOUND clause
+
+You can use the `WHEN NO_DATA_FOUND` clause in an `EXCEPTION` block to determine whether the assignment was successful, that is, at least one row was returned by the query.
+
+This version of the `emp_sal_query` procedure uses the variation of `SELECT INTO` that returns the result set into a record. It also uses the `EXCEPTION` block containing the `WHEN NO_DATA_FOUND` conditional expression.
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_sal_query (
+    p_empno         IN emp.empno%TYPE
+)
+IS
+    r_emp           emp%ROWTYPE;
+    v_avgsal        emp.sal%TYPE;
+BEGIN
+    SELECT * INTO r_emp
+        FROM emp WHERE empno = p_empno;
+    DBMS_OUTPUT.PUT_LINE('Employee # : ' || p_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || r_emp.ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || r_emp.job);
+    DBMS_OUTPUT.PUT_LINE('Hire Date  : ' || r_emp.hiredate);
+    DBMS_OUTPUT.PUT_LINE('Salary     : ' || r_emp.sal);
+    DBMS_OUTPUT.PUT_LINE('Dept #     : ' || r_emp.deptno);
+
+    SELECT AVG(sal) INTO v_avgsal
+        FROM emp WHERE deptno = r_emp.deptno;
+    IF r_emp.sal > v_avgsal THEN
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary is more than the '
+            || 'department average of ' || v_avgsal);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee''s salary does not exceed the '
+            || 'department average of ' || v_avgsal);
+    END IF;
+EXCEPTION
+    WHEN NO_DATA_FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Employee # ' || p_empno || ' not found');
+END;
+```
+
+If the query is executed with a nonexistent employee number, the results appear as follows:
+
+```sql
+EXEC emp_sal_query(0);
+
+Employee # 0 not found
+```
+
+## Including a TOO_MANY_ROWS exception
+
+Another conditional clause useful in the `EXCEPTION` section with `SELECT INTO` is the `TOO_MANY_ROWS` exception. If more than one row is selected by the `SELECT INTO` statement, SPL throws an exception.
+
+When the following block is executed, the `TOO_MANY_ROWS` exception is thrown since there are many employees in the specified department:
+
+```sql
+DECLARE
+    v_ename         emp.ename%TYPE;
+BEGIN
+    SELECT ename INTO v_ename FROM emp WHERE deptno = 20 ORDER BY ename;
+EXCEPTION
+    WHEN TOO_MANY_ROWS THEN
+        DBMS_OUTPUT.PUT_LINE('More than one employee found');
+        DBMS_OUTPUT.PUT_LINE('First employee returned is ' || v_ename);
+END;
+
+More than one employee found
+First employee returned is ADAMS
+```
+
+See [Exception handling](../05_control_structures/07_exception_handling/#exception_handling) for information on exception handling.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx
new file mode 100644
index 00000000000..6bd8e34c57f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/07_update.mdx
@@ -0,0 +1,54 @@
+---
+title: "UPDATE"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/07_update/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/07_update/
+---
+
+<div id="update" class="registered_link"></div>
+
+You can use the `UPDATE` command available in the SQL language in SPL programs.
+
+You can use an expression in the SPL language wherever an expression is allowed in the SQL `UPDATE` command. Thus, you can use SPL variables and parameters to supply values to the update operation.
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_comp_update (
+    p_empno         IN emp.empno%TYPE,
+    p_sal           IN emp.sal%TYPE,
+    p_comm          IN emp.comm%TYPE
+)
+IS
+BEGIN
+    UPDATE emp SET sal = p_sal, comm = p_comm WHERE empno = p_empno;
+
+    IF SQL%FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Updated Employee # : ' || p_empno);
+        DBMS_OUTPUT.PUT_LINE('New Salary         : ' || p_sal);
+        DBMS_OUTPUT.PUT_LINE('New Commission     : ' || p_comm);
+    ELSE
+        DBMS_OUTPUT.PUT_LINE('Employee # ' || p_empno || ' not found');
+    END IF;
+END;
+```
+
+The `SQL%FOUND` conditional expression returns `TRUE` if a row is updated, `FALSE` otherwise. See [Obtaining the result status](08_obtaining_the_result_status/#obtaining_the_result_status) for a discussion of `SQL%FOUND` and other similar expressions.
+
+This example shows the update on the employee:
+
+```sql
+EXEC emp_comp_update(9503, 6540, 1200);
+
+Updated Employee # : 9503
+New Salary         : 6540
+New Commission     : 1200
+
+SELECT * FROM emp WHERE empno = 9503;
+__OUTPUT__
+empno | ename  |  job   | mgr  |      hiredate     |  sal   | comm  | deptno
+------+--------+--------+------+-------------------+--------+-------+-------
+ 9503 |PETERSON| ANALYST| 7902 | 31-MAR-05 00:00:00|6540.00 |1200.00|  40
+(1 row)
+```
+
+!!! Note
+    You can include the `UPDATE` command in a `FORALL` statement. A `FORALL` statement allows a single `UPDATE` command to update multiple rows from values supplied in one or more collections. See [Using the FORALL statement](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/03_using_the_forall_statement/#using_the_forall_statement) for more information.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx
new file mode 100644
index 00000000000..c890897d3b6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/08_obtaining_the_result_status.mdx
@@ -0,0 +1,48 @@
+---
+title: "Obtaining the result status"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/08_obtaining_the_result_status/
+---
+
+<div id="obtaining_the_result_status" class="registered_link"></div>
+
+You can use several attributes to determine the effect of a command. `SQL%FOUND` is a Boolean that returns `TRUE` if at least one row was affected by an `INSERT`, `UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved one or more rows.
+
+This anonymous block inserts a row and then displays the fact that the row was inserted:
+
+```sql
+BEGIN
+    INSERT INTO emp (empno,ename,job,sal,deptno) VALUES (
+        9001, 'JONES', 'CLERK', 850.00, 40);
+    IF SQL%FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Row has been inserted');
+    END IF;
+END;
+
+Row has been inserted
+```
+
+`SQL%ROWCOUNT` provides the number of rows affected by an `INSERT`, `UPDATE`, `DELETE`, or `SELECT INTO` command. The `SQL%ROWCOUNT` value is returned as a `BIGINT` data type. The following example updates the row that was just inserted and displays `SQL%ROWCOUNT`:
+
+```sql
+BEGIN
+    UPDATE emp SET hiredate = '03-JUN-07' WHERE empno = 9001;
+    DBMS_OUTPUT.PUT_LINE('# rows updated: ' || SQL%ROWCOUNT);
+END;
+
+# rows updated: 1
+```
+
+`SQL%NOTFOUND` is the opposite of `SQL%FOUND`. `SQL%NOTFOUND` returns `TRUE` if no rows were affected by an `INSERT`, `UPDATE` or `DELETE` command or a `SELECT INTO` command retrieved no rows.
+
+```sql
+BEGIN
+    UPDATE emp SET hiredate = '03-JUN-07' WHERE empno = 9000;
+    IF SQL%NOTFOUND THEN
+        DBMS_OUTPUT.PUT_LINE('No rows were updated');
+    END IF;
+END;
+
+No rows were updated
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx
new file mode 100644
index 00000000000..4488f2a3dc4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/04_basic_statements/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Types of programming statements"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.061.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.155.html"
+redirects:
+  - /epas/latest/epas_compat_spl/04_basic_statements/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/04_basic_statements/
+---
+
+<div id="basic_statements" class="registered_link"></div>
+
+You can use several programming statements in an SPL program.
+
+<div class="toctree" maxdepth="3">
+
+assignment delete insert null using_the_returning_into_clause select_into update obtaining_the_result_status
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx
new file mode 100644
index 00000000000..4063d33e5d6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/01_if_then.mdx
@@ -0,0 +1,57 @@
+---
+title: "IF-THEN"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/01_if_statement/01_if_then/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/01_if_then/
+---
+
+<div id="if_then" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+IF boolean-expression THEN
+  <statements>
+END IF;
+```
+
+`IF-THEN` statements are the simplest form of `IF`. The statements between `THEN` and `END IF` are executed if the condition is `TRUE`. Otherwise, they are skipped.
+
+## Example 
+
+This example uses `IF-THEN` statement to test and display employees who have a commission:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_comm          emp.comm%TYPE;
+    CURSOR emp_cursor IS SELECT empno, comm FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    COMM');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_comm;
+        EXIT WHEN emp_cursor%NOTFOUND;
+--
+--  Test whether or not the employee gets a commission
+--
+        IF v_comm IS NOT NULL AND v_comm > 0 THEN
+            DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+            TO_CHAR(v_comm,'$99999.99'));
+        END IF;
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    COMM
+-----    -------
+7499     $300.00
+7521     $500.00
+7654    $1400.00
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx
new file mode 100644
index 00000000000..43036e577cb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/02_if_then_else.mdx
@@ -0,0 +1,72 @@
+---
+title: "IF-THEN-ELSE"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/02_if_then_else/
+---
+
+<div id="if_then_else" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+IF boolean-expression THEN
+  <statements>
+ELSE
+  <statements>
+END IF;
+```
+
+`IF-THEN-ELSE` statements add to `IF-THEN` by letting you specify an alternative set of statements to execute if the condition evaluates to false.
+
+## Example 
+
+This example shows an `IF-THEN-ELSE` statement being used to display the text `Non-commission` if an employee doesn't get a commission:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_comm          emp.comm%TYPE;
+    CURSOR emp_cursor IS SELECT empno, comm FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    COMM');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_comm;
+        EXIT WHEN emp_cursor%NOTFOUND;
+--
+--  Test whether or not the employee gets a commission
+--
+        IF v_comm IS NOT NULL AND v_comm > 0 THEN
+            DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+            TO_CHAR(v_comm,'$99999.99'));
+        ELSE
+            DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || 'Non-commission');
+        END IF;
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    COMM
+-----    -------
+7369     Non-commission
+7499  $   300.00
+7521  $   500.00
+7566     Non-commission
+7654  $  1400.00
+7698     Non-commission
+7782     Non-commission
+7788     Non-commission
+7839     Non-commission
+7844     Non-commission
+7876     Non-commission
+7900     Non-commission
+7902     Non-commission
+7934     Non-commission
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx
new file mode 100644
index 00000000000..42ee162582d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/03_if_then_else_if.mdx
@@ -0,0 +1,92 @@
+---
+title: "IF-THEN-ELSE IF"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/03_if_then_else_if/
+---
+
+<div id="if_then_else_if" class="registered_link"></div>
+
+You can nest `IF` statements. This allows you to invoke alternative `IF` statements once it's determined whether the conditional of an outer `IF` statement is `TRUE` or `FALSE`.
+
+In this example, the outer `IF-THEN-ELSE` statement tests whether an employee has a commission. The inner `IF-THEN-ELSE` statements then test whether the employee’s total compensation exceeds or is less than the company average.
+
+!!! Note
+    The logic in this program can be simplified by calculating the employee’s yearly compensation using the `NVL` function in the `SELECT` command of the cursor declaration. However, the purpose of this example is to show the use of `IF` statements.
+      
+```text
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_comm          emp.comm%TYPE;
+    v_avg           NUMBER(7,2);
+    CURSOR emp_cursor IS SELECT empno, sal, comm FROM emp;
+BEGIN
+--
+--  Calculate the average yearly compensation in the company
+--
+    SELECT AVG((sal + NVL(comm,0)) * 24) INTO v_avg FROM emp;
+    DBMS_OUTPUT.PUT_LINE('Average Yearly Compensation: ' ||
+        TO_CHAR(v_avg,'$999,999.99'));
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    YEARLY COMP');
+    DBMS_OUTPUT.PUT_LINE('-----    -----------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_sal, v_comm;
+        EXIT WHEN emp_cursor%NOTFOUND;
+--
+--  Test whether or not the employee gets a commission
+--
+        IF v_comm IS NOT NULL AND v_comm > 0 THEN
+--
+--  Test if the employee's compensation with commission exceeds the average
+--
+            IF (v_sal + v_comm) * 24 > v_avg THEN
+                DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+                    TO_CHAR((v_sal + v_comm) * 24,'$999,999.99') || ' Exceeds Average');
+            ELSE
+                DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+                    TO_CHAR((v_sal + v_comm) * 24,'$999,999.99') || ' Below Average');
+            END IF;
+        ELSE
+--
+--  Test if the employee's compensation without commission exceeds the
+average
+--
+            IF v_sal * 24 > v_avg THEN
+                DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+                    TO_CHAR(v_sal * 24,'$999,999.99') || ' Exceeds Average');
+            ELSE
+                DBMS_OUTPUT.PUT_LINE(v_empno || '  ' ||
+                    TO_CHAR(v_sal * 24,'$999,999.99') || ' Below Average');
+            END IF;
+        END IF;
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+Average Yearly Compensation: $  53,528.57
+EMPNO    YEARLY COMP
+-----    -----------
+7369  $  19,200.00 Below Average
+7499  $  45,600.00 Below Average
+7521  $  42,000.00 Below Average
+7566  $  71,400.00 Exceeds Average
+7654  $  63,600.00 Exceeds Average
+7698  $  68,400.00 Exceeds Average
+7782  $  58,800.00 Exceeds Average
+7788  $  72,000.00 Exceeds Average
+7839  $ 120,000.00 Exceeds Average
+7844  $  36,000.00 Below Average
+7876  $  26,400.00 Below Average
+7900  $  22,800.00 Below Average
+7902  $  72,000.00 Exceeds Average
+7934  $  31,200.00 Below Average
+```
+
+When you use this form, you're actually nesting an `IF` statement inside the `ELSE` part of an outer `IF` statement. Thus you need one `END IF` statement for each nested `IF` and one for the parent `IF-ELSE`.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx
new file mode 100644
index 00000000000..5be6ab73913
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/04_if_then_elseif_else.mdx
@@ -0,0 +1,77 @@
+---
+title: "IF-THEN-ELSIF-ELSE"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/04_if_then_elseif_else/
+---
+
+<div id="if_then_elseif_else" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+IF boolean-expression THEN
+  <statements>
+[ ELSIF boolean-expression THEN
+  <statements>
+[ ELSIF boolean-expression THEN
+  <statements> ] ...]
+[ ELSE
+  <statements> ]
+END IF;
+```
+
+`IF-THEN-ELSIF-ELSE` provides a method of checking many alternatives in one statement. Formally it is equivalent to nested `IF-THEN-ELSE-IF-THEN` commands, but only one `END IF` is needed.
+
+## Example 
+
+The following example uses an `IF-THEN-ELSIF-ELSE` statement to count the number of employees by compensation ranges of $25,000:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_comp          NUMBER(8,2);
+    v_lt_25K        SMALLINT := 0;
+    v_25K_50K       SMALLINT := 0;
+    v_50K_75K       SMALLINT := 0;
+    v_75K_100K      SMALLINT := 0;
+    v_ge_100K       SMALLINT := 0;
+    CURSOR emp_cursor IS SELECT empno, (sal + NVL(comm,0)) * 24 FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_comp;
+        EXIT WHEN emp_cursor%NOTFOUND;
+        IF v_comp < 25000 THEN
+            v_lt_25K := v_lt_25K + 1;
+        ELSIF v_comp < 50000 THEN
+            v_25K_50K := v_25K_50K + 1;
+        ELSIF v_comp < 75000 THEN
+            v_50K_75K := v_50K_75K + 1;
+        ELSIF v_comp < 100000 THEN
+            v_75K_100K := v_75K_100K + 1;
+        ELSE
+            v_ge_100K := v_ge_100K + 1;
+        END IF;
+    END LOOP;
+    CLOSE emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('Number of employees by yearly compensation');
+    DBMS_OUTPUT.PUT_LINE('Less than 25,000 : ' || v_lt_25K);
+    DBMS_OUTPUT.PUT_LINE('25,000 - 49,9999 : ' || v_25K_50K);
+    DBMS_OUTPUT.PUT_LINE('50,000 - 74,9999 : ' || v_50K_75K);
+    DBMS_OUTPUT.PUT_LINE('75,000 - 99,9999 : ' || v_75K_100K);
+    DBMS_OUTPUT.PUT_LINE('100,000 and over : ' || v_ge_100K);
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+Number of employees by yearly compensation
+Less than 25,000 : 2
+25,000 - 49,9999 : 5
+50,000 - 74,9999 : 6
+75,000 - 99,9999 : 0
+100,000 and over : 1
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx
new file mode 100644
index 00000000000..58abf3ff2d7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/01_if_statement/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "IF statement"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/01_if_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/01_if_statement/
+---
+
+<div id="if_statement" class="registered_link"></div>
+
+`IF` statements let you execute commands based on certain conditions. SPL has four forms of `IF`:
+
+-   `IF ... THEN`
+-   `IF ... THEN ... ELSE`
+-   `IF ... THEN ... ELSE IF`
+-   `IF ... THEN ... ELSIF ... THEN ... ELSE`
+
+<div class="toctree" maxdepth="3">
+
+if_then if_then_else if_then_else_if if_then_elseif_else
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx
new file mode 100644
index 00000000000..2cefb6d86dd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/02_return_statement.mdx
@@ -0,0 +1,45 @@
+---
+title: "RETURN statement"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.063.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.157.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/02_return_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/02_return_statement/
+---
+
+<div id="return_statement" class="registered_link"></div>
+
+The `RETURN` statement terminates the current function, procedure, or anonymous block and returns control to the caller.
+
+## Syntax 
+
+The `RETURN` statement has two forms. The first form of the `RETURN` statement terminates a procedure or function that returns `void`. The syntax of this form is:
+
+```sql
+RETURN;
+```
+
+The second form of `RETURN` returns a value to the caller. The syntax of this form is:
+
+```sql
+RETURN <expression>;
+```
+
+`expression` must evaluate to the same data type as the return type of the function.
+
+## Example 
+
+This example uses the `RETURN` statement and returns a value to the caller:
+
+```sql
+CREATE OR REPLACE FUNCTION emp_comp (
+    p_sal           NUMBER,
+    p_comm          NUMBER
+) RETURN NUMBER
+IS
+BEGIN
+    RETURN (p_sal + NVL(p_comm, 0)) * 24;
+END emp_comp;
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx
new file mode 100644
index 00000000000..95b9fab493d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/03_goto_statement.mdx
@@ -0,0 +1,101 @@
+---
+title: "GOTO statement"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.064.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.158.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/03_goto_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/03_goto_statement/
+---
+
+<div id="goto_statement" class="registered_link"></div>
+
+The `GOTO` statement causes the point of execution to jump to the statement with the specified label. 
+
+## Syntax 
+
+The syntax of a `GOTO` statement is:
+
+```sql
+GOTO <label>
+```
+
+`label` is a name assigned to an executable statement. `label` must be unique in the scope of the function, procedure, or anonymous block.
+
+To label a statement, use this syntax:
+
+```text
+<<label>> <statement>
+```
+
+`statement` is the point of execution that the program jumps to.
+
+## Statements eligible for labeling
+
+You can label assignment statements, any SQL statement (like `INSERT`, `UPDATE`, and `CREATE`), and selected procedural language statements. The procedural language statements that can be labeled are:
+
+-   `IF`
+-   `EXIT`
+-   `RETURN`
+-   `RAISE`
+-   `EXECUTE`
+-   `PERFORM`
+-   `GET DIAGNOSTICS`
+-   `OPEN`
+-   `FETCH`
+-   `MOVE`
+-   `CLOSE`
+-   `NULL`
+-   `COMMIT`
+-   `ROLLBACK`
+-   `GOTO`
+-   `CASE`
+-   `LOOP`
+-   `WHILE`
+-   `FOR`
+
+`exit` is considered a keyword and you can't use it as the name of a label.
+
+## Restrictions
+
+`GOTO` statements can't transfer control into a conditional block or sub-block. However, they can transfer control from a conditional block or sub-block.
+
+`GOTO` statements have the following restrictions:
+
+-   A `GOTO` statement can't jump to a declaration.
+-   A `GOTO` statement can't transfer control to another function, or procedure.
+-   Don't place a `label` at the end of a block, function, or procedure.
+
+## Example 
+
+This example verifies that an employee record contains a name, job description, and employee hire date. If any piece of information is missing, a `GOTO` statement transfers the point of execution to a statement that prints a message that the employee isn't valid.
+
+```sql
+CREATE OR REPLACE PROCEDURE verify_emp (
+    p_empno         NUMBER
+)
+IS
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+BEGIN
+    SELECT ename, job, hiredate
+        INTO v_ename, v_job, v_hiredate FROM emp
+        WHERE empno = p_empno;
+    IF v_ename IS NULL THEN
+        GOTO invalid_emp;
+    END IF;
+    IF v_job IS NULL THEN
+        GOTO invalid_emp;
+    END IF;
+    IF v_hiredate IS NULL THEN
+        GOTO invalid_emp;
+    END IF;
+    DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno ||
+        ' validated without errors.');
+    RETURN;
+    <<invalid_emp>> DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno ||
+        ' is not a valid employee.');
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx
new file mode 100644
index 00000000000..9c6ff4815a3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/01_selector_case_expression.mdx
@@ -0,0 +1,86 @@
+---
+title: "Selector CASE expression"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/04_case_expression/01_selector_case_expression/
+---
+
+<div id="selector_case_expression" class="registered_link"></div>
+
+The selector `CASE` expression attempts to match an expression, called the selector, to the expression specified in one or more `WHEN` clauses. `result` is an expression that is type-compatible in the context where the `CASE` expression is used. If a match is found, the value given in the corresponding `THEN` clause is returned by the `CASE` expression. If there are no matches, the value following `ELSE` is returned. If `ELSE` is omitted, the `CASE` expression returns null.
+
+## Syntax 
+
+```sql
+CASE <selector-expression>
+  WHEN <match-expression> THEN
+    <result>
+[ WHEN <match-expression> THEN
+    <result>
+[ WHEN <match-expression> THEN
+    <result> ] ...]
+[ ELSE
+    <result> ]
+END;
+```
+
+-  `match-expression` is evaluated in the order in which it appears in the `CASE` expression. 
+-  `result` is an expression that is type-compatible in the context where the `CASE` expression is used. 
+-  When the first `match-expression` is encountered that equals `selector-expression`, `result` in the corresponding `THEN` clause is returned as the value of the `CASE` expression. 
+-  If none of `match-expression` equals `selector-expression`, then `result` following `ELSE` is returned.
+-  If no `ELSE` is specified, the `CASE` expression returns null.
+
+## Example 
+
+This example uses a selector `CASE` expression to assign the department name to a variable based on the department number:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    CURSOR emp_cursor IS SELECT empno, ename, deptno FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME     DEPTNO    DNAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------   ------    ----------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_ename, v_deptno;
+        EXIT WHEN emp_cursor%NOTFOUND;
+        v_dname :=
+            CASE v_deptno
+                WHEN 10 THEN 'Accounting'
+                WHEN 20 THEN 'Research'
+                WHEN 30 THEN 'Sales'
+                WHEN 40 THEN 'Operations'
+                ELSE 'unknown'
+            END;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || RPAD(v_ename, 10) ||
+            '  ' || v_deptno || '      ' || v_dname);
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME     DEPTNO    DNAME
+-----    -------   ------    ----------
+7369     SMITH       20      Research
+7499     ALLEN       30      Sales
+7521     WARD        30      Sales
+7566     JONES       20      Research
+7654     MARTIN      30      Sales
+7698     BLAKE       30      Sales
+7782     CLARK       10      Accounting
+7788     SCOTT       20      Research
+7839     KING        10      Accounting
+7844     TURNER      30      Sales
+7876     ADAMS       20      Research
+7900     JAMES       30      Sales
+7902     FORD        20      Research
+7934     MILLER      10      Accounting
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx
new file mode 100644
index 00000000000..34624a67b4c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/02_searched_case_expression.mdx
@@ -0,0 +1,85 @@
+---
+title: "Searched CASE expression"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/04_case_expression/02_searched_case_expression/
+---
+
+<div id="searched_case_expression" class="registered_link"></div>
+
+A searched `CASE` expression uses one or more Boolean expressions to determine the resulting value to return.
+
+## Syntax 
+
+```sql
+CASE WHEN <boolean-expression> THEN
+    <result>
+[ WHEN <boolean-expression> THEN
+    <result>
+ [ WHEN <boolean-expression> THEN
+    <result> ] ...]
+[ ELSE
+    <result> ]
+END;
+```
+
+-  `boolean-expression` is evaluated in the order in which it appears in the `CASE` expression. 
+-  `result` is an expression that is type-compatible in the context where the `CASE` expression is used. 
+-  When the first `boolean-expression` is encountered that evaluates to `TRUE`, `result` in the corresponding `THEN` clause is returned as the value of the `CASE` expression. 
+-  If none of `boolean-expression` evaluates to true, then `result` following `ELSE` is returned. 
+-  If no `ELSE` is specified, the `CASE` expression returns null.
+
+## Example 
+
+This example uses a searched `CASE` expression to assign the department name to a variable based on the department number:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    CURSOR emp_cursor IS SELECT empno, ename, deptno FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME     DEPTNO    DNAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------   ------    ----------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_ename, v_deptno;
+        EXIT WHEN emp_cursor%NOTFOUND;
+        v_dname :=
+            CASE
+                WHEN v_deptno = 10 THEN 'Accounting'
+                WHEN v_deptno = 20 THEN 'Research'
+                WHEN v_deptno = 30 THEN 'Sales'
+                WHEN v_deptno = 40 THEN 'Operations'
+                ELSE 'unknown'
+            END;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || RPAD(v_ename, 10) ||
+            '  ' || v_deptno || '      ' || v_dname);
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME     DEPTNO    DNAME
+-----    -------   ------    ----------
+7369     SMITH       20      Research
+7499     ALLEN       30      Sales
+7521     WARD        30      Sales
+7566     JONES       20      Research
+7654     MARTIN      30      Sales
+7698     BLAKE       30      Sales
+7782     CLARK       10      Accounting
+7788     SCOTT       20      Research
+7839     KING        10      Accounting
+7844     TURNER      30      Sales
+7876     ADAMS       20      Research
+7900     JAMES       30      Sales
+7902     FORD        20      Research
+7934     MILLER      10      Accounting
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx
new file mode 100644
index 00000000000..0adf39b0f76
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/04_case_expression/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "CASE expression"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.065.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.159.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/04_case_expression/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/04_case_expression/
+---
+
+<div id="case_expression" class="registered_link"></div>
+
+The `CASE` expression returns a value that's substituted where the `CASE` expression is located in an expression.
+
+The two formats of the `CASE` expression are called a *searched* `CASE` and one that uses a *selector*.
+
+<div class="toctree" maxdepth="3">
+
+selector_case_expression searched_case_expression
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx
new file mode 100644
index 00000000000..146685dff31
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/01_selector_case_statement.mdx
@@ -0,0 +1,95 @@
+---
+title: "Selector CASE statement"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/01_selector_case_statement/
+---
+
+<div id="selector_case_statement" class="registered_link"></div>
+
+The selector `CASE` statement attempts to match an expression called the *selector* to the expression specified in one or more `WHEN` clauses. When a match is found, one or more corresponding statements are executed.
+
+## Syntax
+
+```sql
+CASE <selector-expression>
+WHEN <match-expression> THEN
+  <statements>
+[ WHEN <match-expression> THEN
+  <statements>
+[ WHEN <match-expression> THEN
+  <statements> ] ...]
+[ ELSE
+  <statements> ]
+END CASE;
+```
+
+-  `selector-expression` returns a value type-compatible with each `match-expression`. 
+-  `match-expression` is evaluated in the order in which it appears in the `CASE` statement. 
+-  `statements` are one or more SPL statements, each terminated by a semi-colon. 
+-  When the value of `selector-expression` equals the first `match-expression`, the statements in the corresponding `THEN` clause are executed, and control continues following the `END CASE` keywords. 
+-  If there are no matches, the statements following `ELSE` are executed. 
+-  If there are no matches and there is no `ELSE` clause, an exception is thrown.
+
+## Example 
+
+This example uses a selector `CASE` statement to assign a department name and location to a variable based on the department number:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_loc           dept.loc%TYPE;
+    CURSOR emp_cursor IS SELECT empno, ename, deptno FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME     DEPTNO    DNAME     '
+        || '     LOC');
+    DBMS_OUTPUT.PUT_LINE('-----    -------   ------    ----------'
+        || '     ---------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_ename, v_deptno;
+        EXIT WHEN emp_cursor%NOTFOUND;
+        CASE v_deptno
+            WHEN 10 THEN v_dname := 'Accounting';
+                         v_loc   := 'New York';
+            WHEN 20 THEN v_dname := 'Research';
+                         v_loc   := 'Dallas';
+            WHEN 30 THEN v_dname := 'Sales';
+                         v_loc   := 'Chicago';
+            WHEN 40 THEN v_dname := 'Operations';
+                         v_loc   := 'Boston';
+            ELSE v_dname := 'unknown';
+                         v_loc   := '';
+        END CASE;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || RPAD(v_ename, 10) ||
+            '  ' || v_deptno || '      ' || RPAD(v_dname, 14) || ' ' ||
+            v_loc);
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME     DEPTNO    DNAME          LOC
+-----    -------   ------    ----------     ---------
+7369     SMITH       20      Research       Dallas
+7499     ALLEN       30      Sales          Chicago
+7521     WARD        30      Sales          Chicago
+7566     JONES       20      Research       Dallas
+7654     MARTIN      30      Sales          Chicago
+7698     BLAKE       30      Sales          Chicago
+7782     CLARK       10      Accounting     New York
+7788     SCOTT       20      Research       Dallas
+7839     KING        10      Accounting     New York
+7844     TURNER      30      Sales          Chicago
+7876     ADAMS       20      Research       Dallas
+7900     JAMES       30      Sales          Chicago
+7902     FORD        20      Research       Dallas
+7934     MILLER      10      Accounting     New York
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx
new file mode 100644
index 00000000000..94a9bbfb688
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/02_searched_case_statement.mdx
@@ -0,0 +1,92 @@
+---
+title: "Searched CASE statement"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/02_searched_case_statement/
+---
+
+<div id="searched_case_statement" class="registered_link"></div>
+
+A searched `CASE` statement uses one or more Boolean expressions to determine the resulting set of statements to execute.
+
+## Syntax 
+
+```sql
+CASE WHEN <boolean-expression> THEN
+  <statements>
+[ WHEN <boolean-expression> THEN
+  <statements>
+[ WHEN <boolean-expression> THEN
+  <statements> ] ...]
+[ ELSE
+  <statements> ]
+END CASE;
+```
+
+-  `boolean-expression` is evaluated in the order in which it appears in the `CASE` statement. 
+-  When the first `boolean-expression` is encountered that evaluates to `TRUE`, the statements in the corresponding `THEN` clause are executed and control continues following the `END CASE` keywords. 
+-  If none of `boolean-expression` evaluates to `TRUE`, the statements following `ELSE` are executed. 
+-  If none of `boolean-expression` evaluates to `TRUE` and there is no `ELSE` clause, an exception is thrown.
+
+## Example 
+
+This example uses a searched `CASE` statement to assign a department name and location to a variable based on the department number:
+
+```sql
+DECLARE
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_loc           dept.loc%TYPE;
+    CURSOR emp_cursor IS SELECT empno, ename, deptno FROM emp;
+BEGIN
+    OPEN emp_cursor;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME     DEPTNO    DNAME     '
+        || '     LOC');
+    DBMS_OUTPUT.PUT_LINE('-----    -------   ------    ----------'
+        || '     ---------');
+    LOOP
+        FETCH emp_cursor INTO v_empno, v_ename, v_deptno;
+        EXIT WHEN emp_cursor%NOTFOUND;
+        CASE
+            WHEN v_deptno = 10 THEN v_dname := 'Accounting';
+                                    v_loc   := 'New York';
+            WHEN v_deptno = 20 THEN v_dname := 'Research';
+                                    v_loc   := 'Dallas';
+            WHEN v_deptno = 30 THEN v_dname := 'Sales';
+                                    v_loc   := 'Chicago';
+            WHEN v_deptno = 40 THEN v_dname := 'Operations';
+                                    v_loc   := 'Boston';
+            ELSE v_dname := 'unknown';
+                                    v_loc   := '';
+        END CASE;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || RPAD(v_ename, 10) ||
+            '  ' || v_deptno || '      ' || RPAD(v_dname, 14) || ' ' ||
+            v_loc);
+    END LOOP;
+    CLOSE emp_cursor;
+END;
+```
+
+The following is the output from this program:
+
+```sql
+__OUTPUT__
+EMPNO    ENAME     DEPTNO    DNAME          LOC
+-----    -------   ------    ----------     ---------
+7369     SMITH       20      Research       Dallas
+7499     ALLEN       30      Sales          Chicago
+7521     WARD        30      Sales          Chicago
+7566     JONES       20      Research       Dallas
+7654     MARTIN      30      Sales          Chicago
+7698     BLAKE       30      Sales          Chicago
+7782     CLARK       10      Accounting     New York
+7788     SCOTT       20      Research       Dallas
+7839     KING        10      Accounting     New York
+7844     TURNER      30      Sales          Chicago
+7876     ADAMS       20      Research       Dallas
+7900     JAMES       30      Sales          Chicago
+7902     FORD        20      Research       Dallas
+7934     MILLER      10      Accounting     New York
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx
new file mode 100644
index 00000000000..787b477c4b6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/05_case_statement/index.mdx
@@ -0,0 +1,23 @@
+---
+title: "CASE statement"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.066.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.160.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/05_case_statement/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/05_case_statement/
+---
+
+<div id="case_statement" class="registered_link"></div>
+
+The `CASE` statement executes a set of one or more statements when a specified search condition is `TRUE`. The `CASE` statement is a standalone statement while the `CASE` expression must appear as part of an expression.
+
+The two formats of the `CASE` statement are a *searched* `CASE` and one that uses a *selector*.
+
+<div class="toctree" maxdepth="3">
+
+selector_case_statement searched_case_statement
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx
new file mode 100644
index 00000000000..d6eef3065cb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/01_loop.mdx
@@ -0,0 +1,16 @@
+---
+title: "LOOP"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/01_loop/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/01_loop/
+---
+
+<div id="loop" class="registered_link"></div>
+
+```sql
+LOOP
+    <statements>
+END LOOP;
+```
+
+`LOOP` defines an unconditional loop that's repeated indefinitely until terminated by an `EXIT` or `RETURN` statement.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx
new file mode 100644
index 00000000000..c9265a39cf3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/02_exit.mdx
@@ -0,0 +1,53 @@
+---
+title: "EXIT"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/02_exit/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/02_exit/
+---
+
+<div id="exit" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+EXIT [ WHEN <expression> ];
+```
+
+The innermost loop is terminated, and the statement following `END LOOP` is executed next.
+
+If `WHEN` is present, loop exit occurs only if the specified condition is `TRUE`. Otherwise control passes to the statement after `EXIT`.
+
+You can use `EXIT` to cause early exit from all types of loops, not just unconditional loops.
+
+## Example 
+
+This example shows a loop that iterates 10 times and then uses the `EXIT` statement to terminate:
+
+```sql
+DECLARE
+    v_counter       NUMBER(2);
+BEGIN
+    v_counter := 1;
+    LOOP
+        EXIT WHEN v_counter > 10;
+        DBMS_OUTPUT.PUT_LINE('Iteration # ' || v_counter);
+        v_counter := v_counter + 1;
+    END LOOP;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+__OUTPUT__
+Iteration # 1
+Iteration # 2
+Iteration # 3
+Iteration # 4
+Iteration # 5
+Iteration # 6
+Iteration # 7
+Iteration # 8
+Iteration # 9
+Iteration # 10
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx
new file mode 100644
index 00000000000..93a190610cb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/03_continue.mdx
@@ -0,0 +1,43 @@
+---
+title: "CONTINUE"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/03_continue/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/03_continue/
+---
+
+<div id="continue" class="registered_link"></div>
+
+The `CONTINUE` statement provides a way to proceed with the next iteration of a loop while skipping intervening statements.
+
+When the `CONTINUE` statement is encountered, the next iteration of the innermost loop begins, skipping all statements following the `CONTINUE` statement until the end of the loop. That is, control is passed back to the loop control expression, if any, and the body of the loop is reevaluated.
+
+If you use the `WHEN` clause, then the next iteration of the loop begins only if the specified expression in the `WHEN` clause evaluates to `TRUE`. Otherwise, control is passed to the statement following the `CONTINUE` statement.
+
+You can use the `CONTINUE` statement only inside a loop.
+
+This example uses the `CONTINUE` statement to skip the display of the odd numbers:
+
+```sql
+DECLARE
+    v_counter       NUMBER(2);
+BEGIN
+    v_counter := 0;
+    LOOP
+        v_counter := v_counter + 1;
+        EXIT WHEN v_counter > 10;
+        CONTINUE WHEN MOD(v_counter,2) = 1;
+        DBMS_OUTPUT.PUT_LINE('Iteration # ' || v_counter);
+    END LOOP;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+__OUTPUT__
+Iteration # 2
+Iteration # 4
+Iteration # 6
+Iteration # 8
+Iteration # 10
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx
new file mode 100644
index 00000000000..9b5631fac6c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/04_while.mdx
@@ -0,0 +1,53 @@
+---
+title: "WHILE"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/04_while/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/04_while/
+---
+
+<div id="while" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+WHILE <expression> LOOP
+    <statements>
+END LOOP;
+```
+
+The `WHILE` statement repeats a sequence of statements when the condition expression evaluates to `TRUE`. The condition is checked just before each entry to the loop body.
+
+## Example 
+
+This example uses the `WHILE` statement instead of the `EXIT` statement to determine when to exit the loop:
+
+!!! Note
+    The conditional expression used to determine when to exit the loop differs when using `WHILE` versus `EXIT`. The `EXIT` statement terminates the loop when its conditional expression is true. The `WHILE` statement terminates the loop or never begins it when its conditional expression is false.
+
+```sql
+DECLARE
+    v_counter       NUMBER(2);
+BEGIN
+    v_counter := 1;
+    WHILE v_counter <= 10 LOOP
+        DBMS_OUTPUT.PUT_LINE('Iteration # ' || v_counter);
+        v_counter := v_counter + 1;
+    END LOOP;
+END;
+```
+
+The following is the output from this example:
+
+```sql
+__OUTPUT__
+Iteration # 1
+Iteration # 2
+Iteration # 3
+Iteration # 4
+Iteration # 5
+Iteration # 6
+Iteration # 7
+Iteration # 8
+Iteration # 9
+Iteration # 10
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx
new file mode 100644
index 00000000000..b8349fa4b88
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/05_for_integer_variant.mdx
@@ -0,0 +1,65 @@
+---
+title: "FOR (integer variant)"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/05_for_integer_variant/
+---
+
+<div id="for_integer_variant" class="registered_link"></div>
+
+## Syntax 
+
+```sql
+FOR <name> IN [REVERSE] <expression .. expression> LOOP
+    <statements>
+END LOOP;
+```
+
+This form of `FOR` creates a loop that iterates over a range of integer values. The variable `name` is of type `INTEGER` and exists only inside the loop. The two expressions giving the loop range are evaluated once when entering the loop. The iteration step is +1. 
+
+`name` begins with the value of `expression` to the left of `..` and terminates when `name` exceeds the value of `expression` to the right of `..`. Thus the two expressions take on the roles `start-value.. end-value`.
+
+The optional `REVERSE` clause specifies for the loop to iterate in reverse order. The first time through the loop, `name` is set to the value of the right-most `expression`. The loop terminates when the `name` is less than the left-most `expression`.
+
+## Example 
+
+This example uses a `FOR` loop that iterates from 1 to 10:
+
+```sql
+BEGIN
+    FOR i IN 1 .. 10 LOOP
+        DBMS_OUTPUT.PUT_LINE('Iteration # ' || i);
+    END LOOP;
+END;
+```
+
+The following is the output after using the `FOR` statement:
+
+```sql
+__OUTPUT__
+Iteration # 1
+Iteration # 2
+Iteration # 3
+Iteration # 4
+Iteration # 5
+Iteration # 6
+Iteration # 7
+Iteration # 8
+Iteration # 9
+Iteration # 10
+```
+
+If the start value is greater than the end value, the loop body doesn't execute. No error occurs, as shown by the following example:
+
+```sql
+BEGIN
+    FOR i IN 10 .. 1 LOOP
+        DBMS_OUTPUT.PUT_LINE('Iteration # ' || i);
+    END LOOP;
+END;
+```
+
+This example has no output as the loop body never executes.
+
+!!! Note
+    SPL also supports cursor `FOR` loops. See [Cursor FOR loop](/epas/latest/application_programming/epas_compat_spl/08_static_cursors/07_cursor_for_loop/).
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx
new file mode 100644
index 00000000000..ed9501a8741
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/06_loops/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Loops"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.067.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.161.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/06_loops/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/06_loops/
+---
+
+<div id="loops" class="registered_link"></div>
+
+When you use the `LOOP`, `EXIT`, `CONTINUE`, `WHILE`, and `FOR` statements, your SPL program can repeat a series of commands.
+
+<div class="toctree" maxdepth="3">
+
+loop exit continue while for_integer_variant
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx
new file mode 100644
index 00000000000..cb4aa78afa2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/07_exception_handling.mdx
@@ -0,0 +1,70 @@
+---
+title: "Exception handling"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.068.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.162.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/07_exception_handling/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/07_exception_handling/
+---
+
+<div id="exception_handling" class="registered_link"></div>
+
+By default, any error occurring in an SPL program stops the program from executing. You can trap errors and recover from them by using a `BEGIN` block with an `EXCEPTION` section. 
+
+## Syntax 
+
+The syntax is an extension of the normal syntax for a `BEGIN` block:
+
+```sql
+[ DECLARE
+    <declarations> ]
+  BEGIN
+    <statements>
+  EXCEPTION
+    WHEN <condition> [ OR <condition> ]... THEN
+      <handler_statements>
+  [ WHEN <condition> [ OR <condition> ]... THEN
+      <handler_statements> ]...
+END;
+```
+
+## Error handling process
+
+- If no error occurs, this form of block executes all the statements, and then control passes to the next statement after `END`. 
+- If an error occurs in the statements, further processing of the statements is abandoned, and control passes to the `EXCEPTION` list. The list is searched for the first condition matching the error. 
+- If a match is found, the corresponding `handler_statements` are executed, and then control passes to the next statement after `END`. 
+- If no match is found, the error propagates out as though the `EXCEPTION` clause wasn't there. You can catch the error by an enclosing block with `EXCEPTION`. If there is no enclosing block, it aborts the subprogram.
+
+The special condition named `OTHERS` matches every error type. Condition names aren't case sensitive.
+
+If a new error occurs in the selected `handler_statements`, this `EXCEPTION` clause can't catch it, but it is propagated out. A surrounding `EXCEPTION` clause might catch it.
+
+## Performance implications
+
+Heavy use of the `EXCEPTION` clause can have visible performance consequences. An `EXCEPTION` clause establishes a sub-transaction internally in the database server. If the code in the `EXCEPTION` clause completes without an error, the implicit sub-transaction commits. If an error occurs, it rolls back. 
+
+This process has some overhead. If the code protected by the `EXCEPTION` clause modifies the database, the transaction acquires another transaction ID (XID), increasing the overhead considerably. XID consumption is one factor determining how frequently each table in the database must be subject to VACUUM, so a very high rate of XID consumption leads to more VACUUM activity. Also, when any individual session has more than 64 XIDs assigned simultaneously, some tuple visibility checks incur more overhead. 
+
+## List of condition names to use
+
+| Condition name            | Description                                                                                                                                   |
+| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CASE_NOT_FOUND`          | The application encountered a situation where none of the cases in `CASE` statement evaluates to `TRUE` and there is no `ELSE` condition. |
+| `COLLECTION_IS_NULL`      | The application attempted to invoke a collection method on a null collection, such as an uninitialized nested table.                       |
+| `CURSOR_ALREADY_OPEN`     | The application attempted to open a cursor that's already open.                                                                          |
+| `DUP_VAL_ON_INDEX`        | The application attempted to store a duplicate value that currently exists in a constrained column.                                   |
+| `INVALID_CURSOR`          | The application attempted to access an unopened cursor.                                                                                   |
+| `INVALID_NUMBER`          | The application encountered a data exception equivalent to SQLSTATE class code 22. `INVALID_NUMBER` is an alias for `VALUE_ERROR`.      |
+| `NO_DATA_FOUND`           | No rows satisfy the selection criteria.                                                                                                       |
+| `OTHERS`                  | The application encountered an exception that wasn't caught by a prior condition in the exception section.                           |
+| `SUBSCRIPT_BEYOND_COUNT`  | The application attempted to reference a subscript of a nested table or varray beyond its initialized or extended size.                   |
+| `SUBSCRIPT_OUTSIDE_LIMIT` | The application attempted to reference a subscript or extend a varray beyond its maximum size limit.                                      |
+| `TOO_MANY_ROWS`           | The application encountered more than one row that satisfies the selection criteria where only one row is allowed to be returned.       |
+| `VALUE_ERROR`             | The application encountered a data exception equivalent to SQLSTATE class code 22. `VALUE_ERROR` is an alias for `INVALID_NUMBER`.      |
+| `ZERO_DIVIDE`             | The application tried to divide by zero.                                                                                                  |
+| `User-defined Exception`  | See [User-defined exceptions](08_user_defined_exceptions/#user_defined_exceptions).                                                           |
+
+!!! Note
+    Condition names `INVALID_NUMBER` and `VALUE_ERROR` aren't compatible with Oracle databases for which these condition names are used for exceptions that result only from a failed conversion of a string to a numeric literal. In addition, for Oracle databases, an `INVALID_NUMBER` exception applies only to SQL statements, while a `VALUE_ERROR` exception applies only to procedural statements.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx
new file mode 100644
index 00000000000..f7171ca2232
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/08_user_defined_exceptions.mdx
@@ -0,0 +1,87 @@
+---
+title: "User-defined exceptions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.069.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.163.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/08_user_defined_exceptions/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/08_user_defined_exceptions/
+---
+
+<div id="user_defined_exceptions" class="registered_link"></div>
+
+Any number of errors (referred to in PL/SQL as *exceptions*) can occur while a program executes. When an exception is *thrown*, normal execution of the program stops, and control of the program transfers to the error-handling portion of the program. An exception can be a predefined error that's generated by the server, or it can be a logical error that raises a user-defined exception.
+
+The server never raises user-defined exceptions. They are raised explicitly by a `RAISE` statement. A user-defined exception is raised when a developer-defined logical rule is broken. A common example of a logical rule being broken occurs when a check is presented against an account with insufficient funds. An attempt to cash a check against an account with insufficient funds causes a user-defined exception.
+
+You can define exceptions in functions, procedures, packages, or anonymous blocks. While you can't declare the same exception twice in the same block, you can declare the same exception in two different blocks.
+
+## Syntax 
+
+Before implementing a user-defined exception, you must declare the exception in the declaration section of a function, procedure, package, or anonymous block. You can then raise the exception using the `RAISE` statement:
+
+```sql
+DECLARE
+    <exception_name> EXCEPTION;
+
+BEGIN
+    ...
+    RAISE <exception_name>;
+    ...
+END;
+```
+
+`exception_name` is the name of the exception.
+
+Unhandled exceptions propagate back through the call stack. If the exception remains unhandled, the exception is eventually reported to the client application.
+
+User-defined exceptions declared in a block are considered to be local to that block and global to any blocks nested in the block. To reference an exception that resides in an outer block, you must assign a label to the outer block. Then, preface the name of the exception with `block_name.exception_name`.
+
+Outer blocks can't reference exceptions declared in nested blocks.
+
+The scope of a declaration is limited to the block in which it's declared unless it's created in a package and, when referenced, qualified by the package name. For example, to raise an exception named `out_of_stock` that resides in a package named `inventory_control`, a program must raise an error named `inventory_control.out_of_stock`.
+
+## Example 
+
+This example declares a user-defined exception in a package. The user-defined exception doesn't require a package qualifier when raised in `check_balance`, since it resides in the same package as the exception:
+
+```sql
+CREATE OR REPLACE PACKAGE ar AS
+  overdrawn EXCEPTION;
+  PROCEDURE check_balance(p_balance NUMBER, p_amount NUMBER);
+END;
+
+CREATE OR REPLACE PACKAGE BODY ar AS
+  PROCEDURE check_balance(p_balance NUMBER, p_amount  NUMBER)
+  IS
+  BEGIN
+      IF (p_amount > p_balance) THEN
+        RAISE overdrawn;
+      END IF;
+   END;
+```
+
+Here, the procedure `purchase` calls the `check_balance` procedure. If `p_amount` is greater than `p_balance`, `check_balance` raises an exception. `purchase` catches the `ar.overdrawn` exception. `purchase` must refer to the exception with a package-qualified name (`ar.overdrawn`) because `purchase` isn't defined in the `ar` package.
+
+```sql
+CREATE PROCEDURE purchase(customerID INT, amount NUMERIC)
+AS
+  BEGIN
+     ar.check_ balance(getcustomerbalance(customerid), amount);
+       record_purchase(customerid, amount);
+  EXCEPTION
+     WHEN ar.overdrawn THEN
+       raise_credit_limit(customerid, amount*1.5);
+  END;
+```
+
+When `ar.check_balance` raises an exception, execution jumps to the exception handler defined in `purchase`:
+
+```sql
+EXCEPTION
+     WHEN ar.overdrawn THEN
+       raise_credit_limit(customerid, amount*1.5);
+```
+
+The exception handler raises the customer’s credit limit and ends. When the exception handler ends, execution resumes with the statement that follows `ar.check_balance`.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx
new file mode 100644
index 00000000000..9b63b67fb90
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/09_pragma_exception_init.mdx
@@ -0,0 +1,110 @@
+---
+title: "PRAGMA EXCEPTION_INIT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.070.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.164.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/09_pragma_exception_init/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/09_pragma_exception_init/
+---
+
+<div id="pragma_exception_init" class="registered_link"></div>
+
+`PRAGMA EXCEPTION_INIT` associates a user-defined error code with an exception. You can include a `PRAGMA EXCEPTION_INIT` declaration in any block, sub-block, or package. You can assign an error code to an exception using `PRAGMA EXCEPTION_INIT` only after declaring the exception. 
+
+## Syntax 
+
+The format of a `PRAGMA EXCEPTION_INIT` declaration is:
+
+```sql
+PRAGMA EXCEPTION_INIT(<exception_name>,
+                      {<exception_number> | <exception_code>})
+```
+
+Where:
+
+`exception_name` is the name of the associated exception.
+
+`exception_number` is a user-defined error code associated with the pragma. If you specify an unmapped `exception_number`, the server returns a warning.
+
+`exception_code` is the name of a predefined exception. For a complete list of valid exceptions, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/errcodes-appendix.html).
+
+## Using a PRAGMA EXCEPTION_INIT declaration
+
+This example uses a `PRAGMA EXCEPTION_INIT` declaration:
+
+```sql
+CREATE OR REPLACE PACKAGE ar AS
+  overdrawn EXCEPTION;
+  PRAGMA EXCEPTION_INIT (overdrawn, -20100);
+  PROCEDURE check_balance(p_balance NUMBER, p_amount NUMBER);
+END;
+
+CREATE OR REPLACE PACKAGE BODY ar AS
+  PROCEDURE check_balance(p_balance NUMBER, p_amount  NUMBER)
+  IS
+  BEGIN
+      IF (p_amount > p_balance) THEN
+        RAISE overdrawn;
+      END IF;
+  END;
+END;
+```
+
+The following procedure calls the `check_balance` procedure. If `p_amount` is greater than `p_balance`, `check_balance` raises an exception. The `purchase` procedure catches the `ar.overdrawn` exception.
+
+```sql
+CREATE PROCEDURE purchase(customerID int, amount NUMERIC)
+AS
+  BEGIN
+     ar.check_balance(getcustomerbalance(customerid), amount);
+       record_purchase(customerid, amount);
+  EXCEPTION
+     WHEN ar.overdrawn THEN
+      DBMS_OUTPUT.PUT_LINE ('This account is overdrawn.');
+      DBMS_OUTPUT.PUT_LINE ('SQLCode :'||SQLCODE||' '||SQLERRM );
+END;
+```
+
+When `ar.check_balance` raises an exception, execution jumps to the exception handler defined in `purchase`:
+
+```sql
+EXCEPTION
+     WHEN ar.overdrawn THEN
+      DBMS_OUTPUT.PUT_LINE ('This account is overdrawn.');
+      DBMS_OUTPUT.PUT_LINE ('SQLCode :'||SQLCODE||' '||SQLERRM );
+```
+
+The exception handler returns an error message, followed by `SQLCODE` information:
+
+```sql
+This account is overdrawn.
+SQLCODE: -20100 User-Defined Exception
+```
+
+## Using a predefined exception
+
+This example uses a predefined exception. The code creates a more meaningful name for the `no_data_found exception`. If the given customer doesn't exist, the code catches the exception, calls `DBMS_OUTPUT.PUT_LINE` to report the error, and then raises the original exception again:
+
+```sql
+CREATE OR REPLACE PACKAGE ar AS
+  unknown_customer EXCEPTION;
+  PRAGMA EXCEPTION_INIT (unknown_customer, no_data_found);
+  PROCEDURE check_balance(p_customer_id NUMBER);
+END;
+
+CREATE OR REPLACE PACKAGE BODY ar AS
+   PROCEDURE check_balance(p_customer_id NUMBER)
+   IS
+   DECLARE
+     v_balance NUMBER;
+   BEGIN
+     SELECT balance INTO v_balance FROM customer
+       WHERE cust_id = p_customer_id;
+   EXCEPTION WHEN unknown_customer THEN
+     DBMS_OUTPUT.PUT_LINE('invalid customer id');
+     RAISE;
+   END;
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx
new file mode 100644
index 00000000000..ea89a571134
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/10_raise_application_error.mdx
@@ -0,0 +1,75 @@
+---
+title: "RAISE_APPLICATION_ERROR"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.071.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.165.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/10_raise_application_error/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/10_raise_application_error/
+---
+
+<div id="raise_application_error" class="registered_link"></div>
+
+The procedure `RAISE_APPLICATION_ERROR` allows you to abort processing in an SPL program by causing an exception. The exception is handled in the same manner as described in [Exception handling](07_exception_handling/#exception_handling). In addition, the `RAISE_APPLICATION_ERROR` procedure makes a user-defined code and error message available to the program, which you can then use to identify the exception.
+
+## Syntax
+
+```sql
+RAISE_APPLICATION_ERROR(<error_number>, <message>);
+```
+
+Where:
+
+`error_number` is an integer value or expression returned in a variable named `SQLCODE` when the procedure is executed. The value is between `‑20000` and `-20999`.
+
+`message` is a string literal or expression returned in a variable named `SQLERRM`.
+
+For more information on the `SQLCODE` and `SQLERRM` variables, see [Errors and messages](/epas/latest/application_programming/epas_compat_spl/12_working_with_collections/05_errors_and_messages/).
+
+## Example
+
+This example uses the `RAISE_APPLICATION_ERROR` procedure to display a different code and message depending on the information missing from an employee:
+
+```sql
+CREATE OR REPLACE PROCEDURE verify_emp (
+    p_empno         NUMBER
+)
+IS
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+    v_mgr           emp.mgr%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+BEGIN
+    SELECT ename, job, mgr, hiredate
+        INTO v_ename, v_job, v_mgr, v_hiredate FROM emp
+        WHERE empno = p_empno;
+    IF v_ename IS NULL THEN
+        RAISE_APPLICATION_ERROR(-20010, 'No name for ' || p_empno);
+    END IF;
+    IF v_job IS NULL THEN
+        RAISE_APPLICATION_ERROR(-20020, 'No job for' || p_empno);
+    END IF;
+    IF v_mgr IS NULL THEN
+        RAISE_APPLICATION_ERROR(-20030, 'No manager for ' || p_empno);
+    END IF;
+    IF v_hiredate IS NULL THEN
+        RAISE_APPLICATION_ERROR(-20040, 'No hire date for ' || p_empno);
+    END IF;
+    DBMS_OUTPUT.PUT_LINE('Employee ' || p_empno ||
+        ' validated without errors');
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+END;
+```
+
+The following shows the output in a case where the manager number is missing from an employee record:
+
+```sql
+EXEC verify_emp(7839);
+__OUTPUT__
+SQLCODE: -20030
+SQLERRM: EDB-20030: No manager for 7839
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx
new file mode 100644
index 00000000000..c097662e079
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/05_control_structures/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Types of control structures"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.062.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.156.html"
+redirects:
+  - /epas/latest/epas_compat_spl/05_control_structures/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/05_control_structures/
+---
+
+<div id="control_structures" class="registered_link"></div>
+
+SPL includes programming statements that make it a full procedural complement to SQL.
+
+<div class="toctree" maxdepth="3">
+
+if_statement return_statement goto_statement case_expression case_statement loops exception_handling user_defined_exceptions pragma_exception_init raise_application_error
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx
new file mode 100644
index 00000000000..97359ddfa98
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/01_count.mdx
@@ -0,0 +1,47 @@
+---
+title: "COUNT"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/01_count/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/01_count/
+---
+
+<div id="count" class="registered_link"></div>
+
+`COUNT` is a method that returns the number of elements in a collection. 
+
+## Syntax 
+
+The syntax for using `COUNT` is:
+
+```sql
+<collection>.COUNT
+```
+
+Where `collection` is the name of a collection.
+
+For a varray, `COUNT` always equals `LAST`.
+
+## Example
+
+This example shows that an associative array can be sparsely populated, with gaps in the sequence of assigned elements. `COUNT` includes only the elements that were assigned a value.
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+END;
+```
+
+The following output shows that there are five populated elements included in `COUNT`:
+
+```sql
+__OUTPUT__
+COUNT: 5
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx
new file mode 100644
index 00000000000..4be94b94738
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/02_deletes.mdx
@@ -0,0 +1,75 @@
+---
+title: "DELETE"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/02_deletes/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/02_deletes/
+---
+
+<div id="deletes" class="registered_link"></div>
+
+The `DELETE` method deletes entries from a collection. You can call the `DELETE` method in three different ways.
+
+## Removing all entries from a collection
+
+Use this form of the `DELETE` method to remove all entries from a collection:
+
+```sql
+<collection>.DELETE
+```
+
+## Removing a specified entry from a collection
+
+Use this form of the `DELETE` method to remove the specified entry from a collection:
+
+```sql
+<collection>.DELETE(<subscript>)
+```
+## Removing all entries in a range
+
+Use this form of the `DELETE` method to remove the entries that fall in the range specified by `first_subscript` and `last_subscript` (including the entries for the `first_subscript` and the `last_subscript`) from a collection.
+
+```sql
+<collection>.DELETE(<first_subscript>, <last_subscript>)
+```
+
+If `first_subscript` and `last_subscript` refer to elements that don't exist, elements that are in the range between the specified subscripts are deleted. If `first_subscript` is greater than `last_subscript`, or if you specify a value of `NULL` for one of the arguments, `DELETE` has no effect.
+
+When you delete an entry, the subscript remains in the collection. You can reuse the subscript with an alternate entry. If you specify a subscript that doesn't exist in the call to the `DELETE` method, `DELETE` doesn't raise an exception.
+
+## Example 
+
+This example uses the `DELETE` method to remove the element with subscript `0` from the collection:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+    v_results       VARCHAR2(50);
+    v_sub           NUMBER;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.DELETE(0);
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    v_sub := sparse_arr.FIRST;
+    WHILE v_sub IS NOT NULL LOOP
+        IF sparse_arr(v_sub) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || sparse_arr(v_sub) || ' ';
+        END IF;
+        v_sub := sparse_arr.NEXT(v_sub);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+COUNT: 4
+Results: -100 -10 10 100
+```
+
+`COUNT` indicates that before the `DELETE` method, there were five elements in the collection. After the `DELETE` method is invoked, the collection contains four elements.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx
new file mode 100644
index 00000000000..e064e6413c2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/03_exists.mdx
@@ -0,0 +1,47 @@
+---
+title: "EXISTS"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/03_exists/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/03_exists/
+---
+
+<div id="exists" class="registered_link"></div>
+
+The `EXISTS` method verifies that a subscript exists in a collection. `EXISTS` returns `TRUE` if the subscript exists. If the subscript doesn't exist, `EXISTS` returns `FALSE`. 
+
+## Syntax 
+
+The method takes a single argument: the `subscript` that you are testing for. The syntax is:
+
+```sql
+<collection>.EXISTS(<subscript>)
+```
+
+Where:
+
+`collection` is the name of the collection.
+
+`subscript` is the value that you are testing for. If you specify a value of `NULL`, `EXISTS` returns `false`.
+
+## Example 
+
+This example verifies that subscript number `10` exists in the associative array:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('The index exists: ' ||
+        CASE WHEN sparse_arr.exists(10) = TRUE THEN 'true' ELSE 'false' END);
+END;
+
+The index exists: true
+```
+
+Some collection methods raise an exception if you call them with a subscript that doesn't exist in the specified collection. Rather than raising an error, the `EXISTS` method returns a value of `FALSE`.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx
new file mode 100644
index 00000000000..602e4fdd349
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/04_extend.mdx
@@ -0,0 +1,137 @@
+---
+title: "EXTEND"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/04_extend/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/04_extend/
+---
+
+<div id="extend" class="registered_link"></div>
+
+The `EXTEND` method increases the size of a collection. The `EXTEND` method has three variations. 
+
+## Variation 1: Appending a single element
+
+The first variation appends a single `NULL` element to a collection. The syntax for this variation is:
+
+```sql
+<collection>.EXTEND
+```
+
+Where `collection` is the name of a collection.
+
+This example uses the `EXTEND` method to append a single, null element to a collection:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER;
+    sparse_arr      sparse_arr_typ := sparse_arr_typ(-100,-10,0,10,100);
+    v_results       VARCHAR2(50);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.EXTEND;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    FOR i IN sparse_arr.FIRST .. sparse_arr.LAST LOOP
+        IF sparse_arr(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || sparse_arr(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+COUNT: 6
+Results: -100 -10 0 10 100 NULL
+```
+
+`COUNT` indicates that before the `EXTEND` method, there were five elements in the collection. After the `EXTEND` method is invoked, the collection contains six elements.
+
+## Variation 2: Appending a specified number of elements
+
+This variation of the `EXTEND` method appends a specified number of elements to the end of a collection:
+
+```sql
+<collection>.EXTEND(<count>)
+```
+
+Where: 
+
+`collection` is the name of a collection.
+
+`count` is the number of null elements added to the end of the collection.
+
+This example uses the `EXTEND` method to append multiple null elements to a collection:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER;
+    sparse_arr      sparse_arr_typ := sparse_arr_typ(-100,-10,0,10,100);
+    v_results       VARCHAR2(50);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.EXTEND(3);
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    FOR i IN sparse_arr.FIRST .. sparse_arr.LAST LOOP
+        IF sparse_arr(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || sparse_arr(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+COUNT: 8
+Results: -100 -10 0 10 100 NULL NULL NULL
+```
+
+`COUNT` indicates that before the `EXTEND` method, there were five elements in the collection. After the `EXTEND` method is invoked, the collection contains eight elements.
+
+## Variation 3: Appending copies of an element
+
+This variation of the `EXTEND` method appends a specified number of copies of a particular element to the end of a collection:
+
+```sql
+<collection>.EXTEND(<count>, <index_number>)
+```
+
+Where:
+
+`collection` is the name of a collection.
+
+`count` is the number of elements added to the end of the collection.
+
+`index_number` is the subscript of the element that's being copied to the collection.
+
+This example uses the `EXTEND` method to append multiple copies of the second element to the collection:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER;
+    sparse_arr      sparse_arr_typ := sparse_arr_typ(-100,-10,0,10,100);
+    v_results       VARCHAR2(50);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.EXTEND(3, 2);
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    FOR i IN sparse_arr.FIRST .. sparse_arr.LAST LOOP
+        IF sparse_arr(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || sparse_arr(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+COUNT: 8
+Results: -100 -10 0 10 100 -10 -10 -10
+```
+
+`COUNT` indicates that before the `EXTEND` method, there were five elements in the collection. After the `EXTEND` method is invoked, the collection contains eight elements.
+
+!!! Note
+    You can't use the `EXTEND` method on a null or empty collection.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx
new file mode 100644
index 00000000000..510dea63eba
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/05_first.mdx
@@ -0,0 +1,40 @@
+---
+title: "FIRST"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/05_first/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/05_first/
+---
+
+<div id="first" class="registered_link"></div>
+
+`FIRST` is a method that returns the subscript of the first element in a collection. 
+
+## Syntax 
+
+The syntax for using `FIRST` is as follows:
+
+```sql
+<collection>.FIRST
+```
+
+Where `collection` is the name of a collection.
+
+## Example 
+
+This example displays the first element of the associative array:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('FIRST element: ' || sparse_arr(sparse_arr.FIRST));
+END;
+
+FIRST element: -100
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx
new file mode 100644
index 00000000000..3b8f4c14d09
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/06_last.mdx
@@ -0,0 +1,40 @@
+---
+title: "LAST"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/06_last/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/06_last/
+---
+
+<div id="last" class="registered_link"></div>
+
+`LAST` is a method that returns the subscript of the last element in a collection. 
+
+## Syntax 
+
+The syntax for using `LAST` is as follows:
+
+```sql
+<collection>.LAST
+```
+
+Where `collection` is the name of a collection.
+
+## Example 
+
+This example displays the last element of the associative array:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('LAST element: ' || sparse_arr(sparse_arr.LAST));
+END;
+
+LAST element: 100
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx
new file mode 100644
index 00000000000..365f0bf3fb8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/07_limit.mdx
@@ -0,0 +1,20 @@
+---
+title: "LIMIT"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/07_limit/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/07_limit/
+---
+
+<div id="limit" class="registered_link"></div>
+
+`LIMIT` is a method that returns the maximum number of elements permitted in a collection. `LIMIT` applies only to varrays. The syntax for using `LIMIT` is:
+
+```sql
+<collection>.LIMIT
+```
+
+Where `collection` is the name of a collection.
+
+For an initialized varray, `LIMIT` returns the maximum size limit determined by the varray type definition. If the varray is uninitialized (that is, it's a null varray), an exception is thrown.
+
+For an associative array or an initialized nested table, `LIMIT` returns `NULL`. If the nested table is uninitialized (that is, it's a null nested table), an exception is thrown.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx
new file mode 100644
index 00000000000..60f95cc1d2e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/08_next.mdx
@@ -0,0 +1,42 @@
+---
+title: "NEXT"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/08_next/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/08_next/
+---
+
+<div id="next" class="registered_link"></div>
+
+`NEXT` is a method that returns the subscript that follows a specified subscript. 
+
+## Syntax 
+
+The method takes a single argument: the `subscript` that you are testing for. The syntax is:
+
+```sql
+<collection>.NEXT(<subscript>)
+```
+
+Where `collection` is the name of the collection.
+
+If the specified subscript is less than the first subscript in the collection, the function returns the first subscript. If the subscript doesn't have a successor, `NEXT` returns `NULL`. If you specify a `NULL` subscript, `PRIOR` doesn't return a value.
+
+## Example 
+
+This example uses `NEXT` to return the subscript that follows subscript `10` in the associative array, `sparse_arr:`
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('NEXT element: ' || sparse_arr.next(10));
+END;
+
+NEXT element: 100
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx
new file mode 100644
index 00000000000..073899c5ec7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/09_prior.mdx
@@ -0,0 +1,41 @@
+---
+title: "PRIOR"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/09_prior/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/09_prior/
+---
+
+<div id="prior" class="registered_link"></div>
+
+The `PRIOR` method returns the subscript that precedes a specified subscript in a collection. 
+
+## Syntax 
+
+The method takes a single argument: the `subscript` that you are testing for. The syntax is:
+
+```sql
+<collection>.PRIOR(<subscript>)
+```
+
+Where `collection` is the name of the collection.
+
+If the subscript specified doesn't have a predecessor, `PRIOR` returns `NULL`. If the specified subscript is greater than the last subscript in the collection, the method returns the last subscript. If you specify a `NULL` subscript, `PRIOR` doesn't return a value.
+ ## Example 
+ 
+This example returns the subscript that precedes subscript `100` in the associative array `sparse_arr:`
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER INDEX BY BINARY_INTEGER;
+    sparse_arr      sparse_arr_typ;
+BEGIN
+    sparse_arr(-100)  := -100;
+    sparse_arr(-10)   := -10;
+    sparse_arr(0)     := 0;
+    sparse_arr(10)    := 10;
+    sparse_arr(100)   := 100;
+    DBMS_OUTPUT.PUT_LINE('PRIOR element: ' || sparse_arr.prior(100));
+END;
+
+PRIOR element: 10
+```
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx
new file mode 100644
index 00000000000..87fd5e19648
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/10_trim.mdx
@@ -0,0 +1,72 @@
+---
+title: "TRIM"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/10_trim/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/10_trim/
+---
+
+<div id="trim" class="registered_link"></div>
+
+The `TRIM` method removes one or more elements from the end of a collection. 
+
+## Syntax 
+
+The syntax for the `TRIM` method is:
+
+```sql
+<collection>.TRIM[(<count>)]
+```
+
+Where: 
+
+`collection` is the name of a collection.
+
+`count` is the number of elements removed from the end of the collection. EDB Postgres Advanced Server returns an error if `count` is less than `0` or greater than the number of elements in the collection.
+
+## Example 
+
+This example uses the `TRIM` method to remove an element from the end of a collection:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER;
+    sparse_arr      sparse_arr_typ := sparse_arr_typ(-100,-10,0,10,100);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.TRIM;
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+END;
+
+COUNT: 5
+COUNT: 4
+```
+
+`COUNT` indicates that before the `TRIM` method, there were five elements in the collection. After the `TRIM` method is invoked, the collection contains four elements.
+
+You can also specify the number of elements to remove from the end of the collection using the `TRIM` method:
+
+```sql
+DECLARE
+    TYPE sparse_arr_typ IS TABLE OF NUMBER;
+    sparse_arr      sparse_arr_typ := sparse_arr_typ(-100,-10,0,10,100);
+    v_results       VARCHAR2(50);
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    sparse_arr.TRIM(2);
+    DBMS_OUTPUT.PUT_LINE('COUNT: ' || sparse_arr.COUNT);
+    FOR i IN sparse_arr.FIRST .. sparse_arr.LAST LOOP
+        IF sparse_arr(i) IS NULL THEN
+            v_results := v_results || 'NULL ';
+        ELSE
+            v_results := v_results || sparse_arr(i) || ' ';
+        END IF;
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Results: ' || v_results);
+END;
+
+COUNT: 5
+COUNT: 3
+Results: -100 -10 0
+```
+
+`COUNT` indicates that before the `TRIM` method, there were five elements in the collection. After the `TRIM` method is invoked, the collection contains three elements.
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx
new file mode 100644
index 00000000000..a0ab3523ea5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/11_collection_methods/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "Collection methods"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.079.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.173.html"
+redirects:
+  - /epas/latest/epas_compat_spl/11_collection_methods/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/11_collection_methods/
+---
+
+<div id="collection_methods" class="registered_link"></div>
+
+*Collection methods* are functions and procedures that provide useful information about a collection that can aid in the processing of data in the collection. 
+
+
+<div class="toctree" maxdepth="3">
+
+count deletes exists extend first last limit next prior trim
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx
new file mode 100644
index 00000000000..f295df138fe
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/17_advanced_server_keywords.mdx
@@ -0,0 +1,93 @@
+---
+title: "EDB Postgres Advanced Server exceptions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.80.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.264.html"
+redirects:
+  - /epas/latest/epas_guide/17_advanced_server_keywords/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/application_programming/epas_compat_spl/17_advanced_server_keywords/
+---
+
+<div id="advanced_server_exceptions" class="registered_link"></div>
+
+## List of server exceptions
+
+The following table lists the predefined exceptions, the SQLstate values, associated redwood error code, and descriptions of the exceptions.
+
+| Exception name                | SQLState     | Redwood error code     | Description                                                                                                                                                |
+| ----------------------------- | ------------ | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `value_error`                 | 22000        | -6502                  | The exception occurs when the conversion of a character string to a number fails.                                                                              |
+| `invalid_number`              | 22000        | -6502                  | The exception is raised in PL statement when the conversion of a character string to number fails.                                                            |
+| `datetime_value_out_of_range` | 22008        | -1863                  | The exception occurs while writing a field in date format that is outside the valid range.                                                                   |
+| `divide_by_zero`              | 22012        | -1476                  | The exception occurs when a program attempts to divide a number by zero.                                                                                       |
+| `zero_divide`                 | 22012        | -1476                  | The exception occurs when a program attempts to divide a number by zero.                                                                                       |
+| `dup_val_on_index`            | 23505        | -1                     | The exception occurs when a program attempts to store duplicate values in a column that's constrained by a unique index.                                      |
+| `invalid_cursor`              | 34000        | -1001                  | The exception occurs when a program attempts a cursor operation on an invalid cursor, such as closing an unopened cursor.                                      |
+| `cursor_already_open`         | 42P03        | -6511                  | The exception occurs when a program attempts to open an already open cursor.                                                                                   |
+| `collection_is_null`          | P1403        | -6531                  | The exception occurs when a program attempts to assign values to the elements of nested table or varray that are uninitialized.                                |
+| `subscript_beyond_count`      | P1404        | -6533                  | The exception occurs when a program attempts to reference a nested table or varray using an index number larger than the number of elements in the collection. |
+| `subscript_outside_limit`     | P1405        | -6532                  | The exception occurs when a program attempts to reference a nested table or varray element using an index number that's outside the range.                    |
+
+
+| DBMS_CRYPTO package       |             |        |                                                                                                            |
+| ------------------------- | ----------- | ------ | ---------------------------------------------------------------------------------------------------------- |
+| `ciphersuiteinvalid`      | 00009       | -28827 | The exception occurs when the cipher suite isn't defined.                                                 |
+| `ciphersuitenull`         | 00009       | -28829 | The exception occurs when no value is specified for the cipher suite or it contains a `NULL` value.           |
+| `keybadsize`              | 00009       | 0      | The exception occurs when the specified key size is bad.                                                   |
+| `keynull`                 | 00009       | -28239 | The exception occurs when the key isn't specified.                                                        |
+| **UTL_FILE package**      |             |        |                                                                                                            |
+| `invalid_filehandle`      | P0001 00009 | -29282 | The exception occurs when file handle is invalid.                                                          |
+| `invalid_maxlinesize`     | P0001 00009 | -29287 | The exception occurs when the max line size is invalid or the max line size value isn't within the range. |
+| `invalid_mode`            | P0001 00009 | -29281 | The exception occurs when the `open_mode` parameter in `FOPEN` is invalid.                                 |
+| `invalid_operation`       | P0001 00009 | -29283 | The exception occurs when the file can't be opened or used upon request.                               |
+| `invalid_path`            | P0001 00009 | -29280 | The exception occurs when the file location or file name is invalid.                                        |
+| `read_error`              | P0001 00009 | -29284 | The exception occurs when the operating system error occurred during the read operation.                   |
+| `write_error`             | P0001 00009 | -29285 | The exception occurs when the operating system error occurred during the write operation.                  |
+| **UTL_HTTP package**      |             |        |                                                                                                            |
+| `end_of_body`             | P0001 00009 | -29266 | The exception occurs when the end of HTTP response body is reached.                                        |
+| **UTL_URL package**       |             |        |                                                                                                            |
+| `bad_fixed_width_charset` | 00009       | -29274 | The exception occurs when the fixed-width multibyte character isn't allowed as a URL character set.       |
+| `bad_url`                 | P0001 00009 | -29262 | The exception occurs when the URL includes badly formed escape-code sequences.                             |
+
+<div id="advanced_server_keywords" class="registered_link"></div>
+
+## EDB Postgres Advanced Server keywords
+
+A keyword is a word that's recognized by the EDB Postgres Advanced Server parser as having a special meaning or association. You can use the `pg_get_keywords()` function to retrieve an up-to-date list of the EDB Postgres Advanced Server keywords:
+
+```sql
+acctg=#
+acctg=# SELECT * FROM pg_get_keywords();
+__OUTPUT__
+        word         | catcode |          catdesc
+---------------------+---------+---------------------------------
+ abort               | U       | unreserved
+ absolute            | U       | unreserved
+ access              | U       | unreserved
+...
+```
+
+`pg_get_keywords` returns a table containing the keywords recognized by EDB Postgres Advanced Server:
+
+-   The `word` column displays the keyword.
+-   The `catcode` column displays a category code.
+-   The `catdesc` column displays a brief description of the category to which the keyword belongs.
+
+You can use any character in an identifier if the name is enclosed in double quotes. You can selectively query the `pg_get_keywords()` function to retrieve an up-to-date list of the EDB Postgres Advanced Server keywords that belong to a specific category:
+
+```sql
+SELECT * FROM pg_get_keywords() WHERE catcode = 'code';
+```
+
+Where `code` is:
+
+`R` &mdash; The word is reserved. You can never use reserved keywords as an identifier. They are reserved for use by the server.
+
+`U` &mdash; The word is unreserved. Unreserved words are used internally in some contexts, but you can use them as a name for a database object.
+
+`T` &mdash; The word is used internally but can be used as a name for a function or type.
+
+`C` &mdash; The word is used internally and can't be used as a name for a function or type.
+
+For more information about EDB Postgres Advanced Server identifiers and keywords, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html).
diff --git a/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx
new file mode 100644
index 00000000000..9ef7783a817
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/application_programmer_reference/stored_procedural_language_reference/index.mdx
@@ -0,0 +1,8 @@
+---
+navTitle: SPL reference
+title: "Stored procedural language (SPL) reference"
+indexCards: simple
+description: "Provides reference content about SPL procedures, functions, triggers, and packages"
+---
+
+EDB Postgres Advanced Server's stored procedural language (SPL) is a highly productive, procedural programming language for writing custom procedures, functions, triggers, and packages for EDB Postgres Advanced Server.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx
new file mode 100644
index 00000000000..3730ee5311c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_audit_logging_configuration_parameters.mdx
@@ -0,0 +1,126 @@
+---
+title: "Audit logging configuration parameters"
+description: "Describes the configuration parameters you can use to control database auditing"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/01_audit_logging_configuration_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_security_guide/05_edb_audit_logging/01_audit_logging_configuration_parameters/
+---
+
+Use the following configuration parameters to control database auditing. See [Summary of configuration parameters](/epas/latest/reference/database_administrator_reference/02_summary_of_configuration_parameters/) to determine if a change to the configuration parameter:
+
+- Takes effect immediately 
+- Requires reloading the configuration
+- Requires restarting the database server
+
+## edb_audit
+
+ Enables or disables database auditing. The values `xml` or `csv` enable database auditing. These values represent the file format in which to capture auditing information. `none` disables database auditing and is the default.
+
+!!! Note
+    Set the `logging_collector` parameter to `on` to enable the `edb_audit` parameter.
+
+## edb_audit_archiver 
+
+ Enables or disables database audit archiving.
+
+## edb_audit_archiver_timeout 
+
+ Enforces a timeout in seconds when a database attempts to archive a log file. The valid range is 30 seconds to one day.
+
+## edb_audit_archiver_filename_prefix
+
+ Specifies the file name of an audit log file that needs to be archived. The file name must align with the `edb_audit_filename` parameter. The default value for `edb_audit_archiver_filename_prefix` is `audit-`. The audit files with `edb_audit_archiver_filename_prefix` in the `edb_audit_directory` are eligible for compression and expiration.
+
+## edb_audit_archiver_compress_time_limit
+
+ Specifies the time in seconds after which audit logs are eligible for compression. The possible values are: 
+ 
+ - `0` &mdash; Compression starts as soon as the log file isn't a current file. 
+ - `-1` &mdash; Compression of the log file on a timely basis doesn't occur.
+
+## edb_audit_archiver_compress_size_limit
+
+Specifies a file size threshold, in megabytes, after which audit logs are eligible for compression. If you have multiple audit logs whose combined size exceeds the threshold, the individual files are eligible for compression even though the size of each individual audit log may not meet the threshold. 
+ 
+If the parameter is set to `-1`, compression of the log file on a size basis doesn't occur. 
+
+## edb_audit_archiver_compress_command
+
+ Specifies the command to execute compression of the audit log files. The default value for `edb_audit_archiver_compress_command` is `gzip %p`. The `gzip` provides a standard method of compressing files. The `%p` in the string is replaced with the path name of the file to archive.
+
+## edb_audit_archiver_compress_suffix
+
+ Specifies the file name of an already compressed log file. The file name must align with `edb_audit_archiver_compress_command`. The default file name is `.gz`.
+
+## edb_audit_archiver_expire_time_limit
+
+ Specifies the time, in seconds, after which audit logs are eligible to expire. The possible values to set this parameter are: 
+ 
+ - `0` &mdash; Expiration starts as soon as the log file isn't a current file. 
+ - `-1` &mdash; Expiration of the log file on a timely basis doesn't occur.
+
+## edb_audit_archiver_expire_size_limit 
+
+ Specifies a file size threshold in megabytes, after which audit logs are eligible to expire. If you have multiple audit logs whose combined size exceeds the threshold, the individual files are eligible for expiration even though the size of each individual audit log may not meet the threshold.
+ 
+ If the parameter is set to `-1`, expiration of a log file on the size basis doesn't occur. 
+
+## edb_audit_archiver_expire_command
+
+ Specifies the command to execute on an expired audit log file before removal.
+
+## edb_audit_archiver_sort_file
+
+ Identifies the oldest log file to sort alphabetically or based on `mtime`. `mtime` indicates sorting of files based on file modification time. `alphabetic` indicates sorting of files alphabetically based on the file name.
+
+## edb_audit_directory
+
+ Specifies the directory where the log files are created. The path of the directory can be relative to the data folder or absolute. The default is the `PGDATA/edb_audit` directory.
+
+## edb_audit_filename
+
+ Specifies the file name of the audit file where the auditing information are stored. The default file name is `audit-%Y%m%d_%H%M%S`. The escape sequences `%Y`, `%m`, and so on are replaced by the appropriate current values according to the system date and time.
+
+## edb_audit_rotation_day
+
+ Specifies the day of the week on which to rotate the audit files. Valid values are `sun`, `mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `every`, and `none`. To disable rotation, set the value to `none`. To rotate the file every day, set the `edb_audit_rotation_day` value to `every`. To rotate the file on a specific day of the week, set the value to the desired day of the week. `every` is the default value.
+
+## edb_audit_rotation_size
+
+ Specifies a file size threshold, in megabytes, when file rotation is forced to occur. The default value is 0 MB. If the parameter is commented out or set to 0, rotation of the file on a size basis doesn't occur.
+
+## edb_audit_rotation_seconds
+
+ Specifies the rotation time in seconds to create a log file. To disable this feature, set this parameter to `0`, which is the default.
+
+## edb_audit_connect
+
+ Enables auditing of database connection attempts by users. To disable auditing of all connection attempts, set `edb_audit_connect` to `none`. To audit all connection attempts, set the value to `all`. To audit all failed connection attempts, set the value to `failed`, which is the default. 
+
+## edb_audit_disconnect
+
+ Enables auditing of database disconnections by connected users. To enable auditing of disconnections, set the value to `all`. To disable, set the value to `none`, which is the default.
+
+## edb_audit_statement
+
+ Specifies auditing of different categories of SQL statements. You can specify various combinations of the following values: `none`, `dml`, `insert`, `update`, `delete`, `truncate`, `select`, `error`, `rollback`, `ddl`, `create`, `drop`, `alter`, `grant`, `revoke`, `set`, `all`, and `{ select | update | delete | insert }@groupname`. The default is `ddl` and `error`. See [Selecting SQL statements to audit](/epas/latest/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit/) for information about setting this parameter.
+
+## edb_audit_tag
+
+ Specifies a string value to include in the audit log file for each entry as a tracking tag.
+
+## edb_log_every_bulk_value
+
+ Bulk processing logs the resulting statements into both the EDB Postgres Advanced Server log file and the EDB Audit log file. However, logging every statement in bulk processing is costly. You can control this with the `edb_log_every_bulk_value` configuration parameter. When set to `true`, every statement in bulk processing is logged. During bulk execution, when `edb_log_every_bulk_value` is set to `false`, a log message is recorded once per bulk processing along with the number of rows processed. In addition, the duration is emitted once per bulk processing. Default is `false`.
+
+## edb_audit_destination
+
+ Specifies whether to record the audit log information in the directory as given by the `edb_audit_directory` parameter or to the directory and file managed by the `syslog` process. Set to `file` to use the directory specified by `edb_audit_directory`, which is the default setting.
+
+ Set to `syslog` to use the syslog process and its location as configured in the `/etc/syslog.conf` file. The `syslog` setting is valid for EDB Postgres Advanced Server running on a Linux host and isn't supported on Windows systems. 
+ 
+ !!! Note
+    In recent Linux versions, syslog was replaced with `rsyslog`, and the configuration file is in `/etc/rsyslog.conf`.
+
+!!! Note
+    EDB Postgres Advanced Server allows administrative users associated with administrative privileges to audit statements by any user, group, or role. By auditing specific users, you can minimize the number of audit records generated. For information, see the examples under [Selecting SQL statements to audit](/epas/latest/epas_security_guide/05_edb_audit_logging/02_selecting_sql_statements_to_audit/).
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_index_advisor_components.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_index_advisor_components.mdx
new file mode 100644
index 00000000000..12bb55f63f9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_index_advisor_components.mdx
@@ -0,0 +1,42 @@
+---
+title: "Index Advisor components"
+description: "Description of the components of the Index Advisor shared library"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/02_index_advisor/01_index_advisor_components/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/managing_performance/02_index_advisor/01_index_advisor_components/
+---
+
+<div id="index_advisor_components" class="registered_link"></div>
+
+The Index Advisor shared library interacts with the query planner to make indexing recommendations. 
+
+On Windows, the EDB Postgres Advanced Server installer creates the shared library in the `libdir` subdirectory of your EDB Postgres Advanced Server home directory. The shared library is:
+
+## index_advisor.dll
+
+For Linux, install the `edb-as<xx>-server-indexadvisor` RPM package, where `<xx>` is the EDB Postgres Advanced Server version number. The shared library is:
+
+## index_advisor.so
+
+Only a superuser can load libraries in the `libdir` directory. A database administrator can allow a non-superuser to use Index Advisor by manually copying the Index Advisor file from the `libdir` directory into the `libdir/plugins` directory under your EDB Postgres Advanced Server home directory. Only allow a trusted non-superuser to have access to the plugin. This is an unsafe practice in a production environment.
+
+The installer also creates the Index Advisor utility program and setup script:
+
+## pg_advise_index
+
+ A utility program that reads a user-supplied input file containing SQL queries and produces a text file containing `CREATE INDEX` statements. You can use these statements to create the indexes recommended by the Index Advisor. The `pg_advise_index` program is located in the `bin` subdirectory of the EDB Postgres Advanced Server home directory.
+
+!!! Note
+    `pg_advise_index` asks the backend process to load the index_advisor plugin first from `$libdir/plugins`. If not found, then it writes the error in the server log file and attempts to load from `$libdir`.
+
+## index_advisor_log
+
+ Index Advisor logs indexing recommendations in the `index_advisor_log` table. If Index Advisor doesn't find the `index_advisor_log` table in the user's search path, it stores any indexing recommendations in a temporary table of the same name. The temporary table exists only for rest of the current session.
+
+## show_index_recommendations()
+
+ A PL/pgSQL function that interprets and displays the recommendations made during a specific Index Advisor session, as identified by its backend process ID.
+
+## index_recommendations
+
+ Index Advisor creates the `index_recommendations` view based on information stored in the `index_advisor_log` table during a query analysis. The view produces output in the same format as the `show_index_recommendations()` function but contains Index Advisor recommendations for all stored sessions. The result set returned by the `show_index_recommendations()` function is limited to a specified session.
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/01_edb_redwood_date.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/01_edb_redwood_date.mdx
new file mode 100644
index 00000000000..f5f9d472722
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/01_edb_redwood_date.mdx
@@ -0,0 +1,17 @@
+---
+title: "edb_redwood_date"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.006.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.006.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/01_edb_redwood_date/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_redwood_date" class="registered_link"></div>
+
+`DATE` can appear as the data type of a column in the commands. To translate it to `TIMESTAMP` when the table definition is stored in the database, set the configuration parameter `edb_redwood_date` to `TRUE`. In this case, a time component is stored in the column with the date. This is consistent with Oracle’s `DATE` data type.
+
+If `edb_redwood_date` is set to `FALSE`, the column’s data type in a `CREATE TABLE` or `ALTER TABLE` command remains as a native PostgreSQL `DATE` data type. It's stored as such in the database. The PostgreSQL `DATE` data type stores only the date without a time component in the column.
+
+Regardless of the setting of `edb_redwood_date`, when `DATE` appears as a data type in any other context, it's always internally translated to a `TIMESTAMP` and thus can handle a time component if present. These contexts include the data type of a variable in an SPL declaration section or the data type of a formal parameter in an SPL procedure or SPL function or the return type of an SPL function. 
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/02_edb_redwood_raw_names.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/02_edb_redwood_raw_names.mdx
new file mode 100644
index 00000000000..6605e3ff791
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/02_edb_redwood_raw_names.mdx
@@ -0,0 +1,74 @@
+---
+title: "edb_redwood_raw_names"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/02_edb_redwood_raw_names/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_redwood_raw_names" class="registered_link"></div>
+
+## About database object name display
+
+When `edb_redwood_raw_names` is set to its default value of `FALSE`, database object names such as table names, column names, trigger names, program names, and user names appear in uppercase letters when viewed from Oracle catalogs. For a complete list of supported catalog views, see [Catalog views](../../oracle_compatibility_reference/epas_compat_cat_views/). In addition, quotation marks enclose names that were created with enclosing quotation marks.
+
+When `edb_redwood_raw_names` is set to `TRUE`, the database object names are displayed exactly as stored in the PostgreSQL system catalogs when viewed from the Oracle catalogs. Thus, names created without quotation marks appear in lowercase as expected in PostgreSQL. Names created in quotation marks appear exactly as they were created but without the quotation marks.
+
+## Example
+
+For example, the following user name is created, and then a session is started with that user:
+
+```sql
+CREATE USER reduser IDENTIFIED BY password;
+edb=# \c - reduser
+Password for user reduser:
+You are now connected to database "edb" as user "reduser".
+```
+
+When connected to the database as `reduser`, the following tables are created:
+
+```sql
+CREATE TABLE all_lower (col INTEGER);
+CREATE TABLE ALL_UPPER (COL INTEGER);
+CREATE TABLE "Mixed_Case" ("Col" INTEGER);
+```
+
+When viewed from the Oracle catalog `USER_TABLES` with `edb_redwood_raw_names` set to the default value `FALSE`, the names appear in upper case. The exception is the `Mixed_Case` name, which appears as created and also in quotation marks.
+
+```sql
+edb=> SELECT * FROM USER_TABLES;
+__OUTPUT__
+ schema_name  |  table_name  | tablespace_name | status | temporary
+--------------+--------------+-----------------+--------+-----------
+ REDUSER      | ALL_LOWER    |                 | VALID  | N
+ REDUSER      | ALL_UPPER    |                 | VALID  | N
+ REDUSER      | "Mixed_Case" |                 | VALID  | N
+(3 rows)
+```
+
+When viewed with `edb_redwood_raw_names` set to `TRUE`, the names appear in lower case except for the `Mixed_Case` name. That name appears as created but without the quotation marks.
+
+```sql
+edb=> SET edb_redwood_raw_names TO true;
+SET
+edb=> SELECT * FROM USER_TABLES;
+__OUTPUT__
+ schema_name  | table_name | tablespace_name | status | temporary
+--------------+------------+-----------------+--------+-----------
+ reduser      | all_lower  |                 | VALID  | N
+ reduser      | all_upper  |                 | VALID  | N
+ reduser      | Mixed_Case |                 | VALID  | N
+(3 rows)
+```
+
+These names now match the case when viewed from the PostgreSQL `pg_tables` catalog.
+
+```sql
+edb=> SELECT schemaname, tablename, tableowner FROM pg_tables WHERE
+tableowner = 'reduser';
+__OUTPUT__
+ schemaname  | tablename  | tableowner
+-------------+------------+------------
+ reduser     | all_lower  | reduser
+ reduser     | all_upper  | reduser
+ reduser     | Mixed_Case | reduser
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/03_edb_redwood_strings.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/03_edb_redwood_strings.mdx
new file mode 100644
index 00000000000..91711b3b21f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/03_edb_redwood_strings.mdx
@@ -0,0 +1,69 @@
+---
+title: "edb_redwood_strings"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/03_edb_redwood_strings/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_redwood_strings" class="registered_link"></div>
+
+## About string display after concatenation
+
+In Oracle, when a string is concatenated with a null variable or null column, the result is the original string. However, in PostgreSQL, concatenation of a string with a null variable or null column gives a null result. 
+
+If the `edb_redwood_strings` parameter is set to `TRUE`, the concatenation operation results in the original string as done by Oracle. If `edb_redwood_strings` is set to `FALSE`, the native PostgreSQL behavior is maintained.
+
+## Example
+
+The sample application contains a table of employees. This table has a column named `comm` that's null for most employees. The following query is run with `edb_redwood_string` set to `FALSE`. The concatenation of a null column with non-empty strings produces a final result of null, so only employees that have a commission appear in the query result. The output line for all other employees is null.
+
+```sql
+SET edb_redwood_strings TO off;
+
+SELECT RPAD(ename,10) || ' ' || TO_CHAR(sal,'99,999.99') || ' ' ||
+TO_CHAR(comm,'99,999.99') "EMPLOYEE COMPENSATION" FROM emp;
+__OUTPUT__
+    EMPLOYEE COMPENSATION
+----------------------------------
+
+ ALLEN        1,600.00     300.00
+ WARD         1,250.00     500.00
+
+ MARTIN       1,250.00   1,400.00
+
+
+
+
+ TURNER       1,500.00        .00
+
+
+
+
+(14 rows)
+```
+
+The following is the same query executed when `edb_redwood_strings` is set to `TRUE`. Here, the value of a null column is treated as an empty string. The concatenation of an empty string with a non-empty string produces the non-empty string. This result is consistent with the results produced by Oracle for the same query.
+
+```sql
+SET edb_redwood_strings TO on;
+
+SELECT RPAD(ename,10) || ' ' || TO_CHAR(sal,'99,999.99') || ' ' ||
+TO_CHAR(comm,'99,999.99') "EMPLOYEE COMPENSATION" FROM emp;
+__OUTPUT__
+   EMPLOYEE COMPENSATION
+----------------------------------
+SMITH          800.00
+ALLEN        1,600.00     300.00
+WARD         1,250.00     500.00
+JONES        2,975.00
+MARTIN       1,250.00   1,400.00
+BLAKE        2,850.00
+CLARK        2,450.00
+SCOTT        3,000.00
+KING         5,000.00
+TURNER       1,500.00        .00
+ADAMS        1,100.00
+JAMES          950.00
+FORD         3,000.00
+MILLER       1,300.00
+(14 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/04_edb_stmt_level_tx.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/04_edb_stmt_level_tx.mdx
new file mode 100644
index 00000000000..9be75eb7c98
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/04_edb_stmt_level_tx.mdx
@@ -0,0 +1,64 @@
+---
+title: "edb_stmt_level_tx"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/04_edb_stmt_level_tx/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="edb_stmt_level_tx" class="registered_link"></div>
+
+## About statement level transaction isolation
+
+In Oracle, when a runtime error occurs in a SQL command, all the updates on the database caused by that single command are rolled back. This is called *statement level transaction isolation*. For example, if a single `UPDATE` command successfully updates five rows but an attempt to update a sixth row results in an exception, the updates to all six rows made by this `UPDATE` command are rolled back. The effects of prior SQL commands that weren't yet committed or rolled back are pending until a `COMMIT` or `ROLLBACK` command is executed.
+
+In PostgreSQL, if an exception occurs while executing a SQL command, all the updates on the database since the start of the transaction are rolled back. In addition, the transaction is left in an aborted state, and either a `COMMIT` or `ROLLBACK` command must be issued before another transaction can start.
+
+If `edb_stmt_level_tx` is set to `TRUE`, then an exception doesn't automatically roll back prior uncommitted database updates, emulating the Oracle behavior. If `edb_stmt_level_tx` is set to `FALSE`, then an exception rolls back uncommitted database updates.
+
+!!! Note
+    Use `edb_stmt_level_tx` set to `TRUE` only when necessary, as this setting can have a negative performance impact.
+
+## Example 
+
+The following example run in PSQL shows that when `edb_stmt_level_tx` is `FALSE`, the abort of the second `INSERT` command also rolls back the first `INSERT` command. In PSQL, the command `\set AUTOCOMMIT off` must be issued, otherwise every statement commits automatically, which defeats the purpose of showing the effect of `edb_stmt_level_tx`.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO off;
+
+INSERT INTO emp (empno,ename,deptno) VALUES (9001, 'JONES', 40);
+INSERT INTO emp (empno,ename,deptno) VALUES (9002, 'JONES', 00);
+ERROR:  insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+DETAIL:  Key (deptno)=(0) is not present in table "dept".
+
+COMMIT;
+SELECT empno, ename, deptno FROM emp WHERE empno > 9000;
+__OUTPUT__
+empno  | ename | deptno
+-------+-------+--------
+(0 rows)
+```
+
+In the following example, with `edb_stmt_level_tx` set to `TRUE`, the first `INSERT` command wasn't rolled back after the error on the second `INSERT` command. At this point, the first `INSERT` command can either be committed or rolled back.
+
+```sql
+\set AUTOCOMMIT off
+SET edb_stmt_level_tx TO on;
+
+INSERT INTO emp (empno,ename,deptno) VALUES (9001, 'JONES', 40);
+INSERT INTO emp (empno,ename,deptno) VALUES (9002, 'JONES', 00);
+ERROR:  insert or update on table "emp" violates foreign key constraint
+"emp_ref_dept_fk"
+DETAIL:  Key (deptno)=(0) is not present in table "dept".
+
+SELECT empno, ename, deptno FROM emp WHERE empno > 9000;
+__OUTPUT__
+empno  | ename | deptno
+-------+-------+--------
+9001   | JONES |     40
+(1 row)
+
+COMMIT;
+```
+
+You can issue a `ROLLBACK` command instead of the `COMMIT` command. In that case, the insertion of employee number `9001` is rolled back as well.
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/05_oracle_home.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/05_oracle_home.mdx
new file mode 100644
index 00000000000..7dc696c1448
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/05_oracle_home.mdx
@@ -0,0 +1,30 @@
+---
+title: "oracle_home"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/05_oracle_home/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+
+Before creating a link to an Oracle server, you must direct EDB Postgres Advanced Server to the correct Oracle home directory. Set the `LD_LIBRARY_PATH` environment variable on Linux (or `PATH` on Windows) to the `lib` directory of the Oracle client installation directory.
+
+Alternatively, you can also set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The value specified in the `oracle_home` configuration parameter overrides the `LD_LIBRARY_PATH` environment variable in Linux and `PATH` environment variable in Windows.
+
+!!! Note
+    The `oracle_home` configuration parameter must provide the correct path to the Oracle client, i.e., `OCI` library.
+    
+## Setting the configuration parameter
+
+To set the `oracle_home` configuration parameter in the `postgresql.conf` file, add the following line:
+
+```ini
+oracle_home = 'lib_directory'
+```
+
+Substitute the name of the `oracle_home` path to the Oracle client installation directory that contains `libclntsh.so` in Linux and `oci.dll` in Windows for `lib_directory`.
+
+## Restarting the server
+
+After setting the `oracle_home` configuration parameter, you must restart the server for the changes to take effect. Restart the server:
+
+-   On Linux, using the `systemctl` command or `pg_ctl` services.
+-   On Windows, from the Windows Services console.
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/index.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/index.mdx
new file mode 100644
index 00000000000..54db634eee8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/01_introduction/index.mdx
@@ -0,0 +1,27 @@
+---
+title: "Configuration parameters compatible with Oracle databases"
+indexCards: simple
+description: "Descriptions of the configuration parameters used to control system behaviors to act more like PostgreSQL or more like Oracle"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.005.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.005.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/01_introduction/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="configuration_parameters_compatible_with_oracle_databases" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports developing and running applications compatible with PostgreSQL and Oracle. You can alter some system behaviors to act in a more PostgreSQL- or in a more Oracle-compliant manner. You control these behaviors by using configuration parameters. 
+
+-   `edb_redwood_date` &mdash; Controls whether or not a time component is stored in `DATE` columns. For behavior compatible with Oracle databases, set `edb_redwood_date` to `TRUE`. See [edb_redwood_date](01_edb_redwood_date/#edb_redwood_date).
+-   `edb_redwood_raw_names` &mdash; Controls whether database object names appear in uppercase or lowercase letters when viewed from Oracle system catalogs. For behavior compatible with Oracle databases, `edb_redwood_raw_names` is set to its default value of `FALSE`. To view database object names as they are actually stored in the PostgreSQL system catalogs, set `edb_redwood_raw_names` to `TRUE`. See [edb_redwood_raw_names](02_edb_redwood_raw_names/#edb_redwood_raw_names).
+-   `edb_redwood_strings` &mdash; Equates `NULL` to an empty string for purposes of string concatenation operations. For behavior compatible with Oracle databases, set `edb_redwood_strings` to `TRUE`. See [edb_redwood_strings](03_edb_redwood_strings/#edb_redwood_strings).
+-   `edb_stmt_level_tx` &mdash; Isolates automatic rollback of an aborted SQL command to statement level rollback only – the entire, current transaction is not automatically rolled back as is the case for default PostgreSQL behavior. For behavior compatible with Oracle databases, set `edb_stmt_level_tx` to `TRUE`; however, use only when absolutely necessary. See [edb_stmt_level_tx](04_edb_stmt_level_tx/#edb_stmt_level_tx).
+-   `oracle_home` &mdash; Point EDB Postgres Advanced Server to the correct Oracle installation directory. See [oracle_home](05_oracle_home).
+
+<div class="toctree" maxdepth="3">
+
+edb_redwood_date edb_redwood_raw_names edb_redwood_strings edb_stmt_level_tx oracle_home
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx
new file mode 100644
index 00000000000..0f25b2e1d05
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/02_summary_of_configuration_parameters.mdx
@@ -0,0 +1,363 @@
+---
+title: "Summary of configuration parameters"
+description: "Provides a list of all available configuration parameters"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.10.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.010.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../database_administration/01_configuration_parameters/02_summary_of_configuration_parameters/
+---
+
+<div id="summary_of_configuration_parameters" class="registered_link"></div>
+
+This summary table list all EDB Postgres Advanced Server configuration parameters along with a number of key attributes of the parameters.
+
+These attributes are described by the following columns of the summary table:
+
+-   **Parameter** &mdash; Configuration parameter name and a brief description of the configuration parameter. Parameters for use only with EDB Postgres Advanced Server (EPAS) are denoted by (EPAS only).
+
+-   **Scope** &mdash; Scope of effect of the configuration parameter setting:
+
+    -  `Cluster` &mdash; Setting affects the entire database cluster, that is, all databases managed by the database server instance.
+    -  `Database` &mdash; Setting can vary by database and is established when the database is created. Applies to a small number of parameters related to locale settings.
+    -  `Session` &mdash; Setting can vary down to the granularity of individual sessions.
+
+    In other words, different settings can be made for the following entities in which the latter settings in this list override prior ones: 
+    
+    -  The entire database cluster 
+    -  Specific databases in the database cluster
+    -  Specific roles
+    -  Specific roles when connected to specific databases
+    -  A specific session
+
+-   **In effect** &mdash; When a changed parameter setting takes effect:
+
+    -  `Preset` &mdash; Established when the EDB Postgres Advanced Server product is built or a particular database is created. This is a read-only parameter and can't be changed.
+    -  `Restart` &mdash; You must restart the database server.
+    -  `Reload` &mdash; You must reload configuration file or restart the database server.
+    -  `Immediately` &mdash; Immediately effective in a session if the `PGOPTIONS` environment variable or the `SET` command is used to change the setting in the current session. Effective in new sessions if `ALTER DATABASE`, `ALTER ROLE`, or `ALTER ROLE IN DATABASE` commands are used to change the setting.
+
+-   **Used by** &mdash; Type of operating system account or database role that must be used to put the parameter setting into effect.
+
+    -  `EPAS account` &mdash; The EDB Postgres Advanced Server service account (`enterprisedb` for an installation compatible with Oracle databases, `postgres` for a PostgreSQL compatible mode installation).
+    -  `Superuser` &mdash; Database role with superuser privileges.
+    -  `User` &mdash; Any database role with permissions on the affected database object, that is, the database or role to alter with the `ALTER` command.
+    -  `n/a` &mdash; No user can change the parameter setting.
+
+!!! Note
+    Some parameters can never be altered. These are designated as **Note: For internal use only** in the description.
+
+
+| Parameter | Scope | In effect | Used by |
+| --------- | ----- | --------- | ------- |
+| `allow_system_table_mods` &mdash; Allows modifications of the structure of system tables. | Cluster         | Restart                                | EPAS account       |
+| `application_name` &mdash; Sets the application name to be reported in statistics and logs.  | Session         | Immediately                              | User                       |
+| `archive_command` &mdash; Sets the shell command called to archive a WAL file.  | Cluster         | Reload                                 | EPAS account       |
+| `archive_mode` &mdash; Allows archiving of WAL files using `archive_command`. | Cluster         | Restart                                | EPAS account       |
+| `archive_timeout` &mdash; Forces a switch to the next xlog file if a new file has not been started within N seconds. | Cluster         | Reload                                 | EPAS account       |
+| `array_nulls` &mdash; Enables input of NULL elements in arrays.  | Session         | Immediately                              | User                       |
+| `authentication_timeout` &mdash; Sets the maximum allowed time to complete client authentication.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum` &mdash; Starts the autovacuum subprocess.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_analyze_scale_factor` &mdash; Number of tuple inserts, updates, or deletes prior to analyze as a fraction of `reltuples`. | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_analyze_threshold` &mdash; Minimum number of tuple inserts, updates, or deletes prior to analyze.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_freeze_max_age` &mdash; Age at which to autovacuum a table to prevent transaction ID wraparound.  | Cluster         | Restart                                | EPAS account       |
+| `autovacuum_max_workers` &mdash; Sets the maximum number of simultaneously running autovacuum worker processes. | Cluster         | Restart                                | EPAS account       |
+| `autovacuum_multixact_freeze_max_age` &mdash; Multixact age at which to autovacuum a table to prevent multixact wraparound. | Cluster         | Restart                                | EPAS account       |
+| `autovacuum_naptime` &mdash; Time to sleep between autovacuum runs.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_vacuum_cost_delay` &mdash; Vacuum cost delay in milliseconds, for autovacuum.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_vacuum_cost_limit` &mdash; Vacuum cost amount available before napping, for autovacuum.  | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_vacuum_scale_factor` &mdash; Number of tuple updates or deletes prior to vacuum as a fraction of `reltuples`. | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_vacuum_threshold` &mdash; Minimum number of tuple updates or deletes prior to vacuum. | Cluster         | Reload                                 | EPAS account       |
+| `autovacuum_work_mem` &mdash; Sets the maximum memory to be used by each autovacuum worker process.  | Cluster         | Reload                                 | EPAS account       |
+| `backslash_quote` &mdash; Sets whether `"\'"` is allowed in string literals.  | Session         | Immediately                              | User                       |
+| `bgwriter_delay` &mdash; Background writer sleep time between rounds.  | Cluster         | Reload                                 | EPAS account       |
+| `bgwriter_lru_maxpages`&mdash; Background writer maximum number of LRU pages to flush per round.  | Cluster         | Reload                                 | EPAS account       |
+| `bgwriter_lru_multiplier` &mdash; Multiple of the average buffer usage to free per round. | Cluster         | Reload                                 | EPAS account       |
+| `block_size` &mdash; Shows the size of a disk block.  | Cluster         | Preset                                 | n/a                        |
+| `bonjour` &mdash; Enables advertising the server via Bonjour. | Cluster         | Restart                                | EPAS account       |
+| `bonjour_name` &mdash; Sets the Bonjour service name. | Cluster         | Restart                                | EPAS account       |
+| `bytea_output` &mdash; Sets the output format for `bytea`.  | Session         | Immediately                              | User                       |
+| `check_function_bodies` &mdash; Checks function bodies during `CREATE FUNCTION`. | Session         | Immediately                              | User                       |
+| `checkpoint_completion_target` &mdash; Time spent flushing dirty buffers during checkpoint, as fraction of checkpoint interval.  | Cluster         | Reload                                 | EPAS account       |
+| `checkpoint_segments` (Deprecated) &mdash; Specifies a value for the parameter prevents the server from starting. | -                 |
+| `checkpoint_timeout` &mdash; Sets the maximum time between automatic WAL checkpoints. | Cluster         | Reload                                 | EPAS account       |
+| `checkpoint_warning` &mdash; Enables warnings if checkpoint segments are filled more frequently than this.  | Cluster         | Reload                                 | EPAS account       |
+| `client_encoding` &mdash; Sets the client's character set encoding. | Session         | Immediately                              | User                       |
+| `client_min_messages` &mdash; Sets the message levels that are sent to the client.  | Session         | Immediately                              | User                       |
+| `commit_delay` &mdash; Sets the delay in microseconds between transaction commit and flushing WAL to disk. | Session         | Immediately                              | Superuser                  |
+| `commit_siblings` &mdash; Sets the minimum concurrent open transactions before performing `commit_delay`. | Session         | Immediately                              | User                       |
+| `config_file` &mdash; Sets the server's main configuration file. | Cluster         | Restart                                | EPAS account       |
+| `constraint_exclusion` &mdash; Enables the planner to use constraints to optimize queries. | Session         | Immediately                              | User                       |
+| `cpu_index_tuple_cost` &mdash; Sets the planner's estimate of the cost of processing each index entry during an index scan. | Session         | Immediately                              | User                       |
+| `cpu_operator_cost` &mdash; Sets the planner's estimate of the cost of processing each operator or function call. | Session         | Immediately                              | User                       |
+| `cpu_tuple_cost` &mdash; Sets the planner's estimate of the cost of processing each tuple (row). | Session         | Immediately                              | User                       |
+| `cursor_tuple_fraction` &mdash; Sets the planner's estimate of the fraction of a cursor's rows to retrieve. | Session         | Immediately                              | User                       |
+| `custom_variable_classes`(EPAS only) &mdash; Deprecated in EDB Postgres Advanced Server 9.2. | Cluster         | Reload                                 | EPAS account       |
+| `data_checksums` &mdash; Shows whether data checksums are turned on for this cluster. | Cluster         | Preset                                 | n/a                        |
+| `data_directory` &mdash; Sets the server's data directory.  | Cluster         | Restart                                | EPAS account       |
+| `datestyle` &mdash; Sets the display format for date and time values. | Session         | Immediately                              | User                       |
+| `db_dialect`(EPAS only) &mdash; Sets the precedence of built-in namespaces. | Session         | Immediately                              | User                       |
+| `dbms_alert.max_alerts`(EPAS only) &mdash; Sets maximum number of alerts. | Cluster         | Restart                                | EPAS account       |
+| `dbms_pipe.total_message_buffer`(EPAS only) &mdash; Specifies the total size of the buffer used for the `DBMS_PIPE` package. | Cluster         | Restart                                | EPAS account       |
+| `db_user_namespace` &mdash; Enables per-database user names.  | Cluster         | Reload                                 | EPAS account       |
+| `deadlock_timeout` &mdash; Sets the time to wait on a lock before checking for deadlock. | Session         | Immediately                              | Superuser                  |
+| `debug_assertions` &mdash; Turns on various assertion checks. (Not supported in EPAS builds.) | Cluster         | Preset                                 | n/a                        |
+| `debug_pretty_print` &mdash; Indents parse and plan tree displays. | Session         | Immediately                              | User                       |
+| `debug_print_parse` &mdash; Logs each query's parse tree.  | Session         | Immediately                              | User                       |
+| `debug_print_plan` &mdash; Logs each query's execution plan. | Session         | Immediately                              | User                       |
+| `debug_print_rewritten` &mdash; Logs each query's rewritten parse tree. | Session         | Immediately                              | User                       |
+| `default_heap_fillfactor`(EPAS only) &mdash; Creates new tables with this heap fill factor by default. | Session         | Immediately                              | User                       |
+| `default_statistics_target` &mdash; Sets the default statistics target. | Session         | Immediately                              | User                       |
+| `default_tablespace` &mdash; Sets the default tablespace to create tables and indexes in. | Session         | Immediately                              | User                       |
+| `default_text_search_config` &mdash; Sets default text search configuration. | User                       |
+| `default_transaction_deferrable` &mdash; Sets the default deferrable status of new transactions.  | Session         | Immediately                              | User                       |
+| `default_transaction_isolation` &mdash; Sets the transaction isolation level of each new transaction. | Session         | Immediately                              | User                       |
+| `default_transaction_read_only` &mdash; Sets the default read-only status of new transactions. | Session         | Immediately                              | User                       |
+| `default_with_oids` &mdash; Creates new tables with OIDs by default. | Session         | Immediately                              | User                       |
+| `default_with_rowids`(EPAS only) &mdash; Creates new tables with ROWID support (ROWIDs with indexes) by default. | Session         | Immediately                              | User                       |
+| `dynamic_library_path` &mdash; Sets the path for dynamically loadable modules. | Session         | Immediately                              | Superuser                  |
+| `dynamic_shared_memory_type` &mdash; Selects the dynamic shared memory implementation used. | Cluster         | Restart                                | EPAS account       |
+| `edb_audit`(EPAS only) &mdash; Enables EDB Auditing to create audit reports in XML or CSV format. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver`(EPAS only) &mdash; Enables audit log archiver process. | Cluster         | Restart                                | EPAS account       |
+| `edb_audit_archiver_timeout`(EPAS only) &mdash; Checks the audit log files based on the `edb_audit_archiver_timeout` parameter. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_filename_prefix`(EPAS only) &mdash; Determines audit log files with `edb_audit_archiver_filename_prefix` in `edb_audit_directory` are eligible for compression and/or expiration; the parameter must align with `edb_audit_filename`.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_compress_time_limit`(EPAS only) &mdash; Shows time in seconds after which the audit logs are eligible for compression.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_compress_size_limit`(EPAS only) &mdash; Shows total size in megabytes after which the audit logs are eligible for compression. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_compress_command`(EPAS only) &mdash; Compresses the audit log files.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_compress_suffix`(EPAS only) &mdash; Determines suffix for an already compressed log file. The parameter must align with `edb_audit_archiver_compress_command`. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_expire_time_limit`(EPAS only) &mdash; Shows time in seconds after which the audit logs are eligible for expiration.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_expire_size_limit`(EPAS only) &mdash; Shows total size in megabytes after which the audit logs are eligible for expiration.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_expire_command`(EPAS only) &mdash; Execute on an expired audit log before removing it. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_archiver_sort_file`(EPAS only) &mdash; Identifies the oldest log file and sorts them alphabetically or based on `mtime`.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_connect`(EPAS only) &mdash; Audits each successful connection.  | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_destination`(EPAS only) &mdash; Sets `edb_audit_directory` or syslog as the destination directory for audit files. The syslog setting is only valid for a Linux system. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_directory`(EPAS only) &mdash; Sets the destination directory for audit files. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_disconnect`(EPAS only) &mdash; Audits end of a session. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_filename`(EPAS only) &mdash; Sets the file name pattern for audit files. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_rotation_day`(EPAS only) &mdash; Automatic rotation of log files based on day of week. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_rotation_seconds`(EPAS only) &mdash; Automatic log file rotation occurs after N seconds. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_rotation_size`(EPAS only) &mdash; Automatic log file rotation occurs after N Megabytes. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_statement`(EPAS only) &mdash; Sets the type of statements to audit. | Cluster         | Reload                                 | EPAS account       |
+| `edb_audit_tag`(EPAS only) &mdash; Specifies a tag to include in the audit log. | Session         | Immediately                              | User                       |
+| `edb_connectby_order`(EPAS only) &mdash; Sorts results of `CONNECT BY` queries with no `ORDER BY` to depth-first order. Note: For internal use only.  | Session         | Immediately                              | User                       |
+| `edb_data_redaction`(EPAS only) &mdash; Enables data redaction. | Session         | Immediately                              | User                       |
+| `edb_dynatune`(EPAS only) &mdash; Sets the edb utilization percentage. | Cluster         | Restart                                | EPAS account       |
+| `edb_dynatune_profile`(EPAS only) &mdash; Sets the workload profile for dynatune. | Cluster         | Restart                                | EPAS account       |
+| `edb_enable_pruning`(EPAS only) &mdash; Enables the planner to early-prune partitioned tables. | Session         | Immediately                              | User                       |
+| `edb_log_every_bulk_value`(EPAS only) &mdash; Sets the statements logged for bulk processing. | Session         | Immediately                              | Superuser                  |
+| `edb_max_resource_groups`(EPAS only) &mdash; Specifies the maximum number of resource groups for simultaneous use.  | Cluster         | Restart                                | EPAS account       |
+| `edb_max_spins_per_delay`(EPAS only) &mdash; Specifies the number of times a session spins while waiting for a lock. | Cluster         | Restart                                | EPAS account       |
+| `edb_redwood_date`(EPAS only) &mdash; Determines whether `DATE` should behave like a `TIMESTAMP` or not.  | Session         | Immediately                              | User                       |
+| `edb_redwood_greatest_least`(EPAS only) &mdash; Determines how `GREATEST` and `LEAST` functions should handle NULL parameters. | Session         | Immediately                              | User                       |
+| `edb_redwood_raw_names`(EPAS only) &mdash; Returns the unmodified name stored in the PostgreSQL system catalogs from Redwood interfaces. | Session         | Immediately                              | User                       |
+| `edb_redwood_strings`(EPAS only) &mdash; Treats `NULL` as an empty string when concatenated with a text value. | Session         | Immediately                              | User                       |
+| `edb_resource_group`(EPAS only) &mdash; Specifies the resource group to be used by the current process. | Session         | Immediately                              | User                       |
+| `edb_sql_protect.enabled`(EPAS only) &mdash; Defines whether SQL/Protect should track queries or not. | Cluster         | Reload                                 | EPAS account       |
+| `edb_sql_protect.level`(EPAS only) &mdash; Defines the behavior of SQL/Protect when an event is found. | Cluster         | Reload                                 | EPAS account       |
+| `edb_sql_protect.max_protected_relations`(EPAS only) &mdash; Sets the maximum number of relations protected by SQL/Protect per role. | Cluster         | Restart                                | EPAS account       |
+| `edb_sql_protect.max_protected_roles`(EPAS only) &mdash; Sets the maximum number of roles protected by SQL/Protect. | Cluster         | Restart                                | EPAS account       |
+| `edb_sql_protect.max_queries_to_save`(EPAS only) &mdash; Sets the maximum number of offending queries to save by SQL/Protect. | Cluster         | Restart                                | EPAS account       |
+| `edb_stmt_level_tx`(EPAS only) &mdash; Allows continuing on errors instead of requiring a transaction abort. | Session         | Immediately                              | User                       |
+| `edb_wait_states.directory`(EPAS only) &mdash; Stores the EDB wait states logs in this directory. | Cluster         | Restart                                | EPAS account       |
+| `edb_wait_states.retention_period`(EPAS only) &mdash; Deletes EDB wait state log files after retention period. | Cluster         | Reload                                 | EPAS account       |
+| `edb_wait_states.sampling_interval`(EPAS only) &mdash; The interval between two EDB wait state sampling cycles. | Cluster         | Reload                                 | EPAS account       |
+| `edbldr.empty_csv_field`(EPAS only) &mdash; Specifies how EDB\*Loader handles empty strings. | Session         | Immediately                              | Superuser                  |
+| `effective_cache_size` &mdash; Sets the planner's assumption about the size of the disk cache. | Session         | Immediately                              | User                       |
+| `effective_io_concurrency` &mdash; Number of simultaneous requests that can be handled efficiently by the disk subsystem. | Session         | Immediately                              | User                       |
+| `enable_bitmapscan` &mdash; Enables the planner's use of bitmap-scan plans.  | Session         | Immediately                              | User                       |
+| `enable_hashagg` &mdash; Enables the planner's use of hashed aggregation plans. | Session         | Immediately                              | User                       |
+| `enable_hashjoin` &mdash; Enables the planner's use of hash join plans.  | Session         | Immediately                              | User                       |
+| `enable_hints`(EPAS only) &mdash; Enables optimizer hints in SQL statements. | Session         | Immediately                              | User                       |
+| `enable_indexonlyscan` &mdash; Enables the planner’s use of index-only-scan plans. | Session         | Immediately                              | User                       |
+| `enable_indexscan` &mdash; Enables the planner's use of index-scan plans. | Session         | Immediately                              | User                       |
+| `enable_material` &mdash; Enables the planner's use of materialization. | Session         | Immediately                              | User                       |
+| `enable_mergejoin` &mdash; Enables the planner's use of merge join plans. | Session         | Immediately                              | User                       |
+| `enable_nestloop` &mdash; Enables the planner's use of nested-loop join plans. | Session         | Immediately                              | User                       |
+| `enable_seqscan` &mdash; Enables the planner's use of sequential-scan plans. | Session         | Immediately                              | User                       |
+| `enable_sort` &mdash; Enables the planner's use of explicit sort steps. | Session         | Immediately                              | User                       |
+| `enable_tidscan` &mdash; Enables the planner's use of TID scan plans. | Session         | Immediately                              | User                       |
+| `escape_string_warning` &mdash; Warns about backslash escapes in ordinary string literals. | Session         | Immediately                              | User                       |
+| `event_source` &mdash; Sets the application name used to identify PostgreSQL messages in the event log.  | Cluster         | Restart                                | EPAS account       |
+| `exit_on_error` &mdash; Terminates session on any error. | Session         | Immediately                              | User                       |
+| `external_pid_file` &mdash; Writes the postmaster PID to the specified file.  | Cluster         | Restart                                | EPAS account       |
+| `extra_float_digits` &mdash; Sets the number of digits displayed for floating-point values. | Session         | Immediately                              | User                       |
+| `from_collapse_limit` &mdash; Sets the `FROM`-list size beyond which subqueries are not collapsed. | Session         | Immediately                              | User                       |
+| `fsync` &mdash; Forces synchronization of updates to disk. | Cluster         | Reload                                 | EPAS account       |
+| `full_page_writes` &mdash; Writes full pages to WAL when first modified after a checkpoint. | Cluster         | Reload                                 | EPAS account       |
+| `geqo` &mdash; Enables genetic query optimization. | Session         | Immediately                              | User                       |
+| `geqo_effort` &mdash; GEQO: effort is used to set the default for other GEQO parameters. | Session         | Immediately                              | User                       |
+| `geqo_generations` &mdash; GEQO: number of iterations of the algorithm. | Session         | Immediately                              | User                       |
+| `geqo_pool_size` &mdash; GEQO: number of individuals in the population. | Session         | Immediately                              | User                       |
+| `geqo_seed` &mdash; GEQO: seed for random path selection. | Session         | Immediately                              | User                       |
+| `geqo_selection_bias` &mdash; GEQO: selective pressure within the population. | Session         | Immediately                              | User                       |
+| `geqo_threshold` &mdash; Sets the threshold of `FROM` items beyond which GEQO is used. | Session         | Immediately                              | User                       |
+| `gin_fuzzy_search_limit` &mdash; Sets the maximum allowed result for exact search by GIN. | Session         | Immediately                              | User                       |
+| `hba_file` &mdash; Sets the server's "hba" configuration file. | Cluster         | Restart                                | EPAS account       |
+| `hot_standby` &mdash; Allows connections and queries during recovery. | Cluster         | Restart                                | EPAS account       |
+| `hot_standby_feedback` &mdash; Allows feedback from a hot standby to the primary that avoids query conflicts. | Cluster         | Reload                                 | EPAS account       |
+| `huge_pages` &mdash; Uses huge pages on Linux. | Cluster         | Restart                                | EPAS account       |
+| `icu_short_form`(EPAS only) &mdash; Shows the ICU collation order configuration. | Database        | Preset                                 | n/a                        |
+| `ident_file` &mdash; Sets the server's "ident" configuration file. | Cluster         | Restart                                | EPAS account       |
+| `ignore_checksum_failure` &mdash; Continues processing after a checksum failure. | Session         | Immediately                              | Superuser                  |
+| `ignore_system_indexes` &mdash; Disables reading from system indexes. (Can also be set with `PGOPTIONS` at session start.)  | Cluster<br/>Session | Reload<br/>Immediately                       | EPAS account<br/>User  |
+| `index_advisor.enabled`(EPAS only) &mdash; Enables Index Advisor plugin. | Session         | Immediately                              | User                       |
+| `integer_datetimes` &mdash; Datetimes are integer based.  | Cluster         | Preset                                 | n/a                        |
+| `intervalStyle` &mdash; Sets the display format for interval values.  | Session         | Immediately                              | User                       |
+| `join_collapse_limit` &mdash; Sets the `FROM`-list size beyond which `JOIN` constructs are not flattened. | Session         | Immediately                              | User                       |
+| `krb_caseins_users` &mdash; Sets whether Kerberos and GSSAPI user names should be treated as case-insensitive. | Cluster         | Reload                                 | EPAS account       |
+| `krb_server_keyfile` &mdash; Sets the location of the Kerberos server key file. | Cluster         | Reload                                 | EPAS account       |
+| `lc_collate` &mdash; Shows the collation order locale. | Database        | Preset                                 | n/a                        |
+| `lc_ctype` &mdash; Shows the character classification and case conversion locale. | Database        | Preset                                 | n/a                        |
+| `lc_messages` &mdash; Sets the language in which messages are displayed. | Session         | Immediately                              | Superuser                  |
+| `lc_monetary` &mdash; Sets the locale for formatting monetary amounts. | Session         | Immediately                              | User                       |
+| `lc_numeric` &mdash; Sets the locale for formatting numbers. | Session         | Immediately                              | User                       |
+| `lc_time` &mdash; Sets the locale for formatting date and time values. | Session         | Immediately                              | User                       |
+| `listen_addresses` &mdash; Sets the host name or IP address(es) to listen to. | Cluster         | Restart                                | EPAS account       |
+| `local_preload_libraries` &mdash; Lists shared libraries to preload into each backend. (Can also be set with `PGOPTIONS` at session start.)  | Cluster<br/>Session | Reload<br/>Immediately                       | EPAS account  |
+| `lock_timeout` &mdash; Sets the maximum time allowed that a statement may wait for a lock. | Session         | Immediately                              | User                       |
+| `lo_compat_privileges` &mdash; Enables backward compatibility mode for privilege checks on large objects. | Session         | Immediately                              | Superuser                  |
+| `log_autovacuum_min_duration` &mdash; Sets the minimum execution time above which autovacuum actions are logged. | Cluster         | Reload                                 | EPAS account       |
+| `log_checkpoints` &mdash; Logs each checkpoint. | Cluster         | Reload                                 | EPAS account       |
+| `log_connections` &mdash; Logs each successful connection. (Can also be set with `PGOPTIONS` at session start.) | Cluster<br/>Session| Reload<br/>Immediately                       | EPAS account  |
+| `log_destination` &mdash; Sets the destination for server log output. | Cluster         | Reload                                 | EPAS account       |
+| `log_directory` &mdash; Sets the destination directory for log files. | Cluster         | Reload                                 | EPAS account       |
+| `log_disconnections` &mdash; Logs end of a session, including duration. (Can also be set with `PGOPTIONS` at session start.) | Cluster<br/>Session | Reload<br/>Immediately                       | EPAS account  |
+| `log_duration` &mdash; Logs the duration of each completed SQL statement. | Session         | Immediately                              | Superuser                  |
+| `log_error_verbosity` &mdash; Sets the verbosity of logged messages. | Session         | Immediately                              | Superuser                  |
+| `log_executor_stats` &mdash; Writes executor performance statistics to the server log. | Session         | Immediately                              | Superuser                  |
+| `log_file_mode` &mdash; Sets the file permissions for log files. | Cluster         | Reload                                 | EPAS account       |
+| `log_filename` &mdash; Sets the file name pattern for log files. | Cluster         | Reload                                 | EPAS account       |
+| `log_hostname` &mdash; Logs the host name in the connection logs.  | Cluster         | Reload                                 | EPAS account       |
+| `log_line_prefix` &mdash; Controls information prefixed to each log line. | Cluster         | Reload                                 | EPAS account       |
+| `log_lock_waits` &mdash; Logs long lock waits. | Session         | Immediately                              | Superuser                  |
+| `log_min_duration_statement` &mdash; Sets the minimum execution time above which statements are logged.  | Session         | Immediately                              | Superuser                  |
+| `log_min_error_statement` &mdash; Causes all statements generating error at or above this level to be logged. | Session         | Immediately                              | Superuser                  |
+| `log_min_messages` &mdash; Sets the message levels that are logged.  | Session         | Immediately                              | Superuser                  |
+| `log_parser_stats` &mdash; Writes parser performance statistics to the server log. | Session         | Immediately                              | Superuser                  |
+| `log_planner_stats` &mdash; Writes planner performance statistics to the server log.  | Session         | Immediately                              | Superuser                  |
+| `log_rotation_age` &mdash; Automatic log file rotation occurs after N minutes. | Cluster         | Reload                                 | EPAS account       |
+| `log_rotation_size` &mdash; Automatic log file rotation occurs after N kilobytes. | Cluster         | Reload                                 | EPAS account       |
+| `log_statement` &mdash; Sets the type of statements logged. | Session         | Immediately                              | Superuser                  |
+| `log_statement_stats` &mdash; Writes cumulative performance statistics to the server log. | Session         | Immediately                              | Superuser                  |
+| `log_temp_files` &mdash; Logs the use of temporary files larger than this number of kilobytes.  | Session         | Immediately                              | Superuser                  |
+| `log_timezone` &mdash; Sets the time zone to use in log messages.  | Cluster         | Reload                                 | EPAS account       |
+| `log_truncate_on_rotation` &mdash; Truncates existing log files of same name during log rotation. | Cluster         | Reload                                 | EPAS account       |
+| `logging_collector` &mdash; Starts a subprocess to capture stderr output and/or csv logs into log files. | Cluster         | Restart                                | EPAS account       |
+| `maintenance_work_mem` &mdash; Sets the maximum memory to be used for maintenance operations.  | Session         | Immediately                              | User                       |
+| `max_connections` &mdash; Sets the maximum number of concurrent connections.  | Cluster         | Restart                                | EPAS account       |
+| `max_files_per_process` &mdash; Sets the maximum number of simultaneously open files for each server process. | Cluster         | Restart                                | EPAS account       |
+| `max_function_args` &mdash; Shows the maximum number of function arguments. | Cluster         | Preset                                 | n/a                        |
+| `max_identifier_length` &mdash; Shows the maximum identifier length.  | Cluster         | Preset                                 | n/a                        |
+| `max_index_keys` &mdash; Shows the maximum number of index keys. | Cluster         | Preset                                 | n/a                        |
+| `max_locks_per_transaction` &mdash; Sets the maximum number of locks per transaction. | Cluster         | Restart                                | EPAS account       |
+| `max_pred_locks_per_transaction` &mdash; Sets the maximum number of predicate locks per transaction. | Cluster         | Restart                                | EPAS account       |
+| `max_prepared_transactions` &mdash; Sets the maximum number of simultaneously prepared transactions.  | Cluster         | Restart                                | EPAS account       |
+| `max_replication_slots` &mdash; Sets the maximum number of simultaneously defined replication slots.  | Cluster         | Restart                                | EPAS account       |
+| `max_stack_depth` &mdash; Sets the maximum stack depth, in kilobytes. | Session         | Immediately                              | Superuser                  |
+| `max_standby_archive_delay` &mdash; Sets the maximum delay before canceling queries when a hot standby server is processing archived WAL data.  | Cluster         | Reload                                 | EPAS account       |
+| `max_standby_streaming_delay` &mdash; Sets the maximum delay before canceling queries when a hot standby server is processing streamed WAL data.  | Cluster         | Reload                                 | EPAS account       |
+| `max_wal_senders` &mdash; Sets the maximum number of simultaneously running WAL sender processes. | Cluster         | Restart                                | EPAS account       |
+| `max_wal_size` &mdash; Sets the maximum size to which the WAL grows between automatic WAL checkpoints. The default is 1GB. | Cluster         | Reload                                 | EPAS account       |
+| `max_worker_processes` &mdash; Maximum number of concurrent worker processes.  | Cluster         | Restart                                | EPAS account       |
+| `min_wal_size` &mdash; Sets the threshold at which WAL logs is recycled rather than removed. The default is 80 MB.  | Cluster         | Reload                                 | EPAS account       |
+| `nls_length_semantics`(EPAS only) &mdash; Sets the semantics to use for char, varchar, varchar2 and long columns. | Session         | Immediately                              | Superuser                  |
+| `odbc_lib_path`(EPAS only) &mdash; Sets the path for ODBC library. | Cluster         | Restart                                | EPAS account       |
+| `optimizer_mode`(EPAS only) &mdash; Default optimizer mode. | Session         | Immediately                              | User                       |
+| `oracle_home`(EPAS only) &mdash; Sets the path for the Oracle home directory.  | Cluster         | Restart                                | EPAS account       |
+| `password_encryption` &mdash; Encrypts passwords.  | Session         | Immediately                              | User                       |
+| `pg_prewarm.autoprewarm`(EPAS only) &mdash; Enables the `autoprewarm` background worker.  | Cluster         | Restart                                | EPAS account       |
+| `pg_prewarm.autoprewarm_interval`(EPAS only) &mdash; Sets the minimum number of seconds after which `autoprewarm` dumps shared buffers.  | Cluster         | Reload                                 | EPAS account       |
+| `port` &mdash; Sets the TCP port on which the server listens.  | Cluster         | Restart                                | EPAS account       |
+| `post_auth_delay` &mdash; Waits N seconds on connection startup after authentication. (Can also be set with `PGOPTIONS` at session start.)  | Cluster<br/>Session | Reload<br/>Immediately                       | EPAS account  |
+| `pre_auth_delay` &mdash; Waits N seconds on connection startup before authentication.  | Cluster         | Reload                                 | EPAS account       |
+| `qreplace_function`(EPAS only) &mdash; The function to be used by Query Replace feature. Note: For internal use only.  | Session         | Immediately                              | Superuser                  |
+| `query_rewrite_enabled`(EPAS only) &mdash; Skils child table scans if their constraints guarantee that no rows match the query.  | Session         | Immediately                              | User                       |
+| `query_rewrite_integrity`(EPAS only) &mdash; Sets the degree to which query rewriting must be enforced.  | Session         | Immediately                              | Superuser                  |
+| `quote_all_identifiers` &mdash; When generating SQL fragments, quotes all identifiers. | Session         | Immediately                              | User                       |
+| `random_page_cost` &mdash; Sets the planner's estimate of the cost of a nonsequentially fetched disk page. | Session         | Immediately                              | User                       |
+| `restart_after_crash` &mdash; Reinitializes server after backend crash.  | Cluster         | Reload                                 | EPAS account       |
+| `search_path` &mdash; Sets the schema search order for names that are not schema-qualified. | Session         | Immediately                              | User                       |
+| `segment_size` &mdash; Shows the number of pages per disk file.  | Cluster         | Preset                                 | n/a                        |
+| `seq_page_cost` &mdash; Sets the planner's estimate of the cost of a sequentially fetched disk page.  | Session         | Immediately                              | User                       |
+| `server_encoding` &mdash; Sets the server (database) character set encoding.  | Database      | Preset                                 | n/a                        |
+| `server_version` &mdash; Shows the server version. | Cluster         | Preset                                 | n/a                        |
+| `server_version_num` &mdash; Shows the server version as an integer. | Cluster         | Preset                                 | n/a                        |
+| `session_preload_libraries` &mdash; Lists shared libraries to preload into each backend.  | Session         | Immediately <br/>but only at connection start  | Superuser                  |
+| `session_replication_role` &mdash; Sets the session's behavior for triggers and rewrite rules. | Session         | Immediately                              | Superuser                  |
+| `shared_buffers` &mdash; Sets the number of shared memory buffers used by the server.  | Cluster         | Restart                                | EPAS account       |
+| `shared_preload_libraries` &mdash; Lists shared libraries to preload into server.  | Cluster         | Restart                                | EPAS account       |
+| `sql_inheritance` &mdash; Causes subtables to be included by default in various commands. | Session         | Immediately                              | User                       |
+| `ssl` &mdash; Enables SSL connections.  | Cluster         | Reload                                 | EPAS account       |
+| `ssl_ca_file` &mdash; Location of the SSL certificate authority file. | Cluster         | Reload                                 | EPAS account       |
+| `ssl_cert_file` &mdash; Location of the SSL server certificate file.  | Cluster         | Reload                                 | EPAS account       |
+| `ssl_ciphers` &mdash; Sets the list of allowed SSL ciphers. | Cluster         | Reload                                 | EPAS account       |
+| `ssl_crl_file` &mdash; Location of the SSL certificate revocation list file. | Cluster         | Reload                                 | EPAS account       |
+| `ssl_ecdh_curve` &mdash; Sets the curve to use for ECDH. | Cluster         | Reload                                 | EPAS account       |
+| `ssl_key_file` &mdash; Location of the SSL server private key file.  | Cluster         | Reload                                 | EPAS account       |
+| `ssl_prefer_server_ciphers` &mdash; Gives priority to server ciphersuite order.  | Cluster         | Reload                                 | EPAS account       |
+| `ssl_renegotiation_limit` &mdash; Sets the amount of traffic to send and receive before renegotiating the encryption keys. | Session         | Immediately                              | User                       |
+| `standard_conforming_strings` &mdash; Causes '...' strings to treat backslashes literally.  | Session         | Immediately                              | User                       |
+| `statement_timeout` &mdash; Sets the maximum allowed duration of any statement. | Session         | Immediately                              | User                       |
+| `stats_temp_directory` &mdash; Writes temporary statistics files to the specified directory. | Cluster         | Reload                                 | EPAS account       |
+| `superuser_reserved_connections` &mdash; Sets the number of connection slots reserved for superusers.  | Cluster         | Restart                                | EPAS account       |
+| `synchronize_seqscans` &mdash; Enables synchronized sequential scans. | Session         | Immediately                              | User                       |
+| `synchronous_commit` &mdash; Sets immediate fsync at commit. | Session         | Immediately                              | User                       |
+| `synchronous_standby_names` &mdash; Lists names of potential synchronous standbys.  | Cluster         | Reload                                 | EPAS account       |
+| `syslog_facility` &mdash; Sets the syslog "facility" to be used when syslog enabled.  | Cluster         | Reload                                 | EPAS account       |
+| `syslog_ident` &mdash; Sets the program name used to identify PostgreSQL messages in syslog. | Cluster         | Reload                                 | EPAS account       |
+| `tcp_keepalives_count` &mdash; Maximum number of TCP keepalive retransmits.  | Session         | Immediately                              | User                       |
+| `tcp_keepalives_idle` &mdash; Time between issuing TCP keepalives.  | Session         | Immediately                              | User                       |
+| `tcp_keepalives_interval` &mdash; Time between TCP keepalive retransmits. | Session         | Immediately                              | User                       |
+| `temp_buffers` &mdash; Sets the maximum number of temporary buffers used by each session.  | Session         | Immediately                              | User                       |
+| `temp_file_limit` &mdash; Limits the total size of all temporary files used by each session.  | Session         | Immediately                              | Superuser                  |
+| `temp_tablespaces` &mdash; Sets the tablespace(s) to use for temporary tables and sort files.  | Session         | Immediately                              | User                       |
+| `timed_statistics`(EPAS only) &mdash; Enables the recording of timed statistics.  | Session         | Immediately                              | User                       |
+| `timezone` &mdash; Sets the time zone for displaying and interpreting time stamps. | Session         | Immediately                              | User                       |
+| `timezone_abbreviations` &mdash; Selects a file of time zone abbreviations.  | Session         | Immediately                              | User                       |
+| `trace_hints`(EPAS only) &mdash; Emits debug info about hints being honored.  | Session         | Immediately                              | User                       |
+| `trace_notify` &mdash; Generates debugging output for `LISTEN` and `NOTIFY`. | Session         | Immediately                              | User                       |
+| `trace_recovery_messages` &mdash; Enables logging of recovery-related debugging information.  | Cluster         | Reload                                 | EPAS account       |
+| `trace_sort` &mdash; Emits information about resource usage in sorting. | Session         | Immediately                              | User                       |
+| `track_activities` &mdash; Collects information about executing commands. | Session         | Immediately                              | Superuser                  |
+| `track_activity_query_size` &mdash; Sets the size reserved for `pg_stat_activity.current_query`, in bytes.  | Cluster         | Restart                                | EPAS account       |
+| `track_counts` &mdash; Collects statistics on database activity. | Session         | Immediately                              | Superuser                  |
+| `track_functions` &mdash; Collects function-level statistics on database activity.  | Session         | Immediately                              | Superuser                  |
+| `track_io_timing` &mdash; Collects timing statistics for database I/O activity. | Session         | Immediately                              | Superuser                  |
+| `transaction_deferrable` &mdash; Specifies whether to defer a read-only serializable transaction until it can be executed with no possible serialization failures. | Session         | Immediately                              | User                       |
+| `transaction_isolation` &mdash; Sets the current transaction's isolation level. | Session         | Immediately                              | User                       |
+| `transaction_read_only` &mdash; Sets the current transaction's read-only status.  | Session         | Immediately                              | User                       |
+| `transform_null_equals` &mdash; Treats `"expr=NULL"` as `"expr IS NULL"`. | Session         | Immediately                              | User                       |
+| `unix_socket_directories` &mdash; Sets the directory where the Unix-domain socket is created.  | Cluster         | Restart                                | EPAS account       |
+| `unix_socket_group` &mdash; Sets the owning group of the Unix-domain socket.  | Cluster         | Restart                                | EPAS account       |
+| `unix_socket_permissions` &mdash; Sets the access permissions of the Unix-domain socket.  | Cluster         | Restart                                | EPAS account       |
+| `update_process_title` &mdash; Updates the process title to show the active SQL command. | Session         | Immediately                              | Superuser                  |
+| `utl_encode.uudecode_redwood`(EPAS only) &mdash; Allows decoding of Oracle-created uuencoded data. | Session         | Immediately                              | User                       |
+| `utl_file.umask`(EPAS only) &mdash; Umask used for files created through the `UTL_FILE` package.  | Session         | Immediately                              | User                       |
+| `vacuum_cost_delay` &mdash; Vacuum cost delay in milliseconds.  | Session         | Immediately                              | User                       |
+| `vacuum_cost_limit` &mdash; Vacuum cost amount available before napping.  | Session         | Immediately                              | User                       |
+| `vacuum_cost_page_dirty` &mdash; Vacuum cost for a page dirtied by vacuum. | Session         | Immediately                              | User                       |
+| `vacuum_cost_page_hit` &mdash; Vacuum cost for a page found in the buffer cache. | Session         | Immediately                              | User                       |
+| `vacuum_cost_page_miss` &mdash; Vacuum cost for a page not found in the buffer cache. | Session         | Immediately                              | User                       |
+| `vacuum_defer_cleanup_age` &mdash; Number of transactions by which `VACUUM` and `HOT` cleanup should be deferred, if any.  | Cluster         | Reload                                 | EPAS account       |
+| `vacuum_freeze_min_age` &mdash; Minimum age at which `VACUUM` should freeze a table row.  | Session         | Immediately                              | User                       |
+| `vacuum_freeze_table_age` &mdash; Age at which `VACUUM` should scan whole table to freeze tuples. | Session         | Immediately                              | User                       |
+| `vacuum_multixact_freeze_min_age` &mdash; Minimum age at which `VACUUM` should freeze a MultiXactId in a table row. | Session         | Immediately                              | User                       |
+| `vacuum_multixact_freeze_table_age` &mdash; Multixact age at which `VACUUM` should scan whole table to freeze tuples. | Session         | Immediately                              | User                       |
+| `wal_block_size` &mdash; Shows the block size in the write ahead log.  | Cluster         | Preset                                 | n/a                        |
+| `wal_buffers` &mdash; Sets the number of disk-page buffers in shared memory for WAL.  | Cluster         | Restart                                | EPAS account       |
+| `wal_keep_segments` &mdash; Sets the number of WAL files held for standby servers.  | Cluster         | Reload                                 | EPAS account       |
+| `wal_level` &mdash; Set the level of information written to the WAL.  | Cluster         | Restart                                | EPAS account       |
+| `wal_log_hints` &mdash; Writes full pages to WAL when first modified after a checkpoint, even for non-critical modifications. | Cluster         | Restart                                | EPAS account       |
+| `wal_receiver_status_interval` &mdash; Sets the maximum interval between WAL receiver status reports to the primary. | Cluster         | Reload                                 | EPAS account       |
+| `wal_receiver_timeout` &mdash; Sets the maximum wait time to receive data from the primary.  | Cluster         | Reload                                 | EPAS account       |
+| `wal_segment_size` &mdash; Shows the number of pages per write ahead log segment.  | Cluster         | Preset                                 | n/a                        |
+| `wal_sender_timeout` &mdash; Sets the maximum time to wait for WAL replication.  | Cluster         | Reload                                 | EPAS account       |
+| `wal_sync_method` &mdash; Selects the method used for forcing WAL updates to disk.  | Cluster         | Reload                                 | EPAS account       |
+| `wal_writer_delay` &mdash; WAL writer sleep time between WAL flushes.  | Cluster         | Reload                                 | EPAS account       |
+| `work_mem` &mdash; Sets the maximum memory to be used for query workspaces.  | Session         | Immediately                              | User                       |
+| `xloginsert_locks` &mdash; Sets the number of locks used for concurrent xlog insertions. | Cluster         | Restart                                | EPAS account       |
+| `xmlbinary` &mdash; Sets how binary values are to be encoded in XML.  | Session         | Immediately                              | User                       |
+| `xmloption` &mdash; Sets whether XML data in implicit parsing and serialization operations is to be considered as documents or content fragments. | Session         | Immediately                              | User                       |
+| `zero_damaged_pages` &mdash; Continues processing past damaged page headers. | Session         | Immediately                              | Superuser                  |
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/04_audit_log_file.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/04_audit_log_file.mdx
new file mode 100644
index 00000000000..d7bd2b5d782
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/04_audit_log_file.mdx
@@ -0,0 +1,278 @@
+---
+title: "Audit log files"
+description: "Describes the fields in an audit log file"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/05_edb_audit_logging/04_audit_log_file/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../epas_security_guide/epas_security_guide/05_edb_audit_logging/04_audit_log_file/
+---
+
+<div id="audit_log_file" class="registered_link"></div>
+
+You can generate the audit log file in CSV or XML format. The format is determined by the `edb_audit` configuration parameter.
+
+The information in the audit log is based on the logging performed by PostgreSQL, as described in "Using CSV-Format Log Output” under “Error Reporting and Logging” in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/runtime-config-logging.html).
+
+## Overview of the CSV audit log format
+
+The following table lists the fields in the order they appear in the CSV audit log format. The table contains the following information:
+
+-   **Field** &mdash; Name of the field as shown in the sample table definition in the PostgreSQL documentation.
+-   **XML element/attribute** &mdash; For the XML format, name of the XML element and its attribute (if used), referencing the value.  
+-   **Data type** &mdash; Data type of the field as given by the PostgreSQL sample table definition.
+-   **Description** &mdash; Description of the field. 
+
+The fields that don't have any values for logging appear as consecutive commas (,,) in the CSV format.
+
+| Field                    | XML element/attribute          | Data type                  | Description                                                                                                                |
+| ------------------------ | ------------------------------ | -------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
+| `log_time`               | `event/log_time`               | `timestamp with time zone` | Log date/time of the statement.                                                                                            |
+| `user_name`              | `event/user`                   | `text`                     | Database user who executed the statement.                                                                                  |
+| `database_name`          | `event/database`               | `text`                     | Database in which the statement was executed.                                                                              |
+| `process_id`             | `event/process_id`             | `integer`                  | Operating system process ID in which the statement was executed.                                                           |
+| `connection_from`        | `event/remote_host`            | `text`                     | Host and port location from where the statement was executed.                                                              |
+| `session_id`             | `event/session_id`             | `text`                     | Session ID in which the statement was executed.                                                                            |
+| `session_line_num`       | `event/session_line_num`       | `bigint`                   | Order of the statement within the session.                                                                                 |
+| `process_status`         | `event/process_status`         | `text`                     | Processing status.                                                                                                         |
+| `session_start_time`     | `event/session_start_time`     | `timestamp with time zone` | Date/time when the session was started.                                                                                    |
+| `virtual_transaction_id` | `event/virtual_transaction_id` | `text`                     | Virtual transaction ID of the statement.                                                                                   |
+| `transaction_id`         | `event/transaction_id`         | `bigint`                   | Regular transaction ID of the statement.                                                                                   |
+| `error_severity`         | `error_severity`               | `text`                     | Statement severity. Values are `AUDIT` for audited statements and `ERROR` for any resulting error messages.                |
+| `sql_state_code`         | `event/sql_state_code`         | `text`                     | SQL state code returned for the statement. The `sql_state_code` isn't logged when its value is 00000 for XML log format.  |
+| `message`                | `message`                      | `text`                     | The SQL statement that was attempted for execution.                                                                        |
+| `detail`                 | `detail`                       | `text`                     | Error message detail.                                                                                                      |
+| `hint`                   | `hint`                         | `text`                     | Hint for error.                                                                                                            |
+| `internal_query`         | `internal_query`               | `text`                     | Internal query that led to the error, if any.                                                                              |
+| `internal_query_pos`     | `internal_query_pos`           | `integer`                  | Character count of the error position therein.                                                                             |
+| `context`                | `context`                      | `text`                     | Error context.                                                                                                             |
+| `query`                  | `query`                        | `text`                     | User query that led to the error. For errors only.                                                                        |
+| `query_pos`              | `query_pos`                    | `integer`                  | Character count of the error position therein. For errors only.                                                           |
+| `location`               | `location`                     | `text`                     | Location of the error in the source code. The location field is populated if `log_error_verbosity` is set to verbose.      |
+| `application_name`       | `event/application_name`       | `text`                     | Name of the application from which the statement was executed, for example, `psql.bin`.                                  |
+| `backend_type`           | `event/backend_type`           | `text`                     | The `backend_type` corresponds to what `pg_stat_activity.backend_type` shows and is added as a column to the csv log.      |
+| `leader_pid`             | `event/leader_pid`             | `integer`                  | Process ID of leader for active parallel workers.                                                                          |
+| `query_id`               | `event/query_id`               | `long`                     | Identifier of this backend's most recent query.                                                                            |
+| `command_tag`            | `event/command_tag`            | `text`                     | SQL command of the statement.                                                                                              |
+| `audit_tag`              | `event/audit_tag`              | `text`                     | Value specified by the `audit_tag` parameter in the configuration file.                                                    |
+| `type`                   | `event/type`                   | `text`                     | Determines the audit `event_type` to identify messages in the log.                                                         |
+
+The following examples are generated in the CSV and XML formats.
+
+The non-default audit settings in the `postgresql.conf` file are as follows:
+
+```ini
+logging_collector = 'on'
+edb_audit = 'csv'
+edb_audit_connect = 'all'
+edb_audit_disconnect = 'all'
+edb_audit_statement = 'ddl, dml, select, error'
+edb_audit_tag = 'edbaudit'
+```
+
+The `edb_audit parameter` is changed to `xml` when generating the XML format.
+
+The following is the audited session:
+
+```sql
+$ psql edb enterprisedb
+Password for user enterprisedb:
+psql.bin (14.0.0)
+Type "help" for help.
+
+edb=# CREATE SCHEMA edb;
+CREATE SCHEMA
+edb=# SET search_path TO edb;
+SET
+edb=# CREATE TABLE dept (
+edb(#     deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+edb(#     dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+edb(#     loc             VARCHAR2(13)
+edb(# );
+CREATE TABLE
+edb=# INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');
+INSERT 0 1
+edb=# UPDATE department SET loc = 'BOSTON' WHERE deptno = 10;
+ERROR:  relation "department" does not exist
+LINE 1: UPDATE department SET loc = 'BOSTON' WHERE deptno = 10;
+            ^
+edb=# UPDATE dept SET loc = 'BOSTON' WHERE deptno = 10;
+UPDATE 1
+edb=# SELECT * FROM dept;
+__OUTPUT__
+ deptno |   dname    |  loc
+--------+------------+--------
+     10 | ACCOUNTING | BOSTON
+(1 row)
+
+edb=# \q
+```
+
+## CSV audit log file
+
+The following is the CSV format of the audit log file. (Each audit log entry was split and displays across multiple lines. A blank line was inserted between the audit log entries for visual clarity.)
+
+```text
+2022-12-14 12:19:01.035 UTC,"enterprisedb","edb",9290,"[local]",
+6399bf35.244a,1,"authentication",2022-12-14 12:19:01 UTC,4/19,0,
+AUDIT,00000,"connection authorized: user=enterprisedb database=edb",
+,,,,,,,,"","client backend",,0,"","edbaudit","connect"
+
+2022-12-14 12:19:12.599 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,1,"authentication",2022-12-14 12:19:12 UTC,5/1,0,
+AUDIT,00000,"connection authorized: user=enterprisedb database=edb",
+,,,,,,,,"","client backend",,0,"","edbaudit","connect"
+
+2022-12-14 12:19:21.351 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,2,"idle",2022-12-14 12:19:12 UTC,5/3,0,AUDIT,00000,
+"statement: CREATE SCHEMA edb;",,,,,,,,,"psql","client backend",,
+0,"CREATE SCHEMA","edbaudit","create"
+
+2022-12-14 12:19:27.817 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,3,"idle",2022-12-14 12:19:12 UTC,5/4,0,AUDIT,00000,
+"statement: CREATE SCHEMA edb;",,,,,,,,,"psql","client backend",,
+0,"CREATE SCHEMA","edbaudit","create"
+
+2022-12-14 12:19:27.820 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,4,"CREATE SCHEMA",2022-12-14 12:19:12 UTC,5/4,0,ERROR,
+42P06,"schema ""edb"" already exists",,,,,,"CREATE SCHEMA edb;",,,
+"psql","client backend",,0,"CREATE SCHEMA","edbaudit","error"
+
+2022-12-14 12:20:15.407 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,5,"idle",2022-12-14 12:19:12 UTC,5/6,0,AUDIT,00000,
+"statement: CREATE TABLE dept (
+    deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+    dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+    loc             VARCHAR2(13)
+ );",,,,,,,,,"psql","client backend",,0,"CREATE TABLE","edbaudit",
+ "create"
+
+2022-12-14 12:20:24.433 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,6,"idle",2022-12-14 12:19:12 UTC,5/7,0,AUDIT,00000,
+"statement: INSERT INTO dept VALUES (10,'ACCOUNTING','NEW YORK');",
+,,,,,,,,"psql","client backend",,0,"INSERT","edbaudit","insert"
+
+2022-12-14 12:20:34.393 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,7,"idle",2022-12-14 12:19:12 UTC,5/8,0,AUDIT,00000,
+"statement: UPDATE department SET loc = 'BOSTON' WHERE deptno = 10;",
+,,,,,,,,"psql","client backend",,0,"UPDATE","edbaudit","update"
+
+2022-12-14 12:20:34.394 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,8,"UPDATE",2022-12-14 12:19:12 UTC,5/8,0,ERROR,
+42P01,"relation ""department"" does not exist",,,,,,
+"UPDATE department SET loc = 'BOSTON' WHERE deptno = 10;",8,,
+"psql","client backend",,0,"UPDATE","edbaudit","error"
+
+2022-12-14 12:20:43.721 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,9,"idle",2022-12-14 12:19:12 UTC,5/9,0,AUDIT,00000,
+"statement: UPDATE dept SET loc = 'BOSTON' WHERE deptno = 10;",
+,,,,,,,,"psql","client backend",,0,"UPDATE","edbaudit","update"
+
+2022-12-14 12:20:51.231 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,10,"idle",2022-12-14 12:19:12 UTC,5/10,0,AUDIT,00000,
+"statement: SELECT * FROM dept;",,,,,,,,,"psql","client backend",,0,
+"SELECT","edbaudit","select"
+
+2022-12-14 12:20:53.940 UTC,"enterprisedb","edb",9293,"[local]",
+6399bf40.244d,11,"idle",2022-12-14 12:19:12 UTC,,0,AUDIT,00000,
+"disconnection: session time: 0:01:41.344 user=enterprisedb database=edb 
+host=[local]",,,,,,,,,"psql","client backend",,0,"","edbaudit","disconnect"
+```
+
+## XML audit log file
+
+The following is the XML format of the audit log file. (The output was formatted for visual clarity.)
+
+```xml
+<event user="amul" database="edb" process_id="110405" 
+       remote_host="[local]" session_id="63e1f4cf.1af45" 
+       session_line_num="1" process_status="idle" 
+       session_start_time="2023-02-07 12:20:56.920 IST" 
+       log_time="2023-02-07 12:20:55 IST" virtual_transaction_id="4/22" 
+       type="create" command_tag="CREATE ROLE" application_name="psql" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: create user edb superuser;</message>
+</event>
+<event user="edb" database="postgres" process_id="110424" 
+       remote_host="[local]" session_id="63e1f4d4.1af58" 
+       session_line_num="1" process_status="idle" 
+       session_start_time="2023-02-07 12:21:00.561 IST" 
+       log_time="2023-02-07 12:21:00 IST" virtual_transaction_id="4/25" 
+       type="set" command_tag="SET" application_name="pg_regress" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: SET client_min_messages = warning</message>
+</event>
+<event user="edb" database="postgres" process_id="110424" 
+       remote_host="[local]" session_id="63e1f4d4.1af58" 
+       session_line_num="2" process_status="idle" 
+       session_start_time="2023-02-07 12:21:00.561 IST" 
+       log_time="2023-02-07 12:21:00 IST" virtual_transaction_id="4/26" 
+       type="drop" command_tag="DROP DATABASE" application_name="pg_regress" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: DROP DATABASE IF EXISTS &quot;regression&quot;</message>
+</event>
+<event user="edb" database="postgres" process_id="110426" 
+       remote_host="[local]" session_id="63e1f4d4.1af5a" 
+       session_line_num="1" process_status="idle" 
+       session_start_time="2023-02-07 12:21:00.568 IST" 
+       log_time="2023-02-07 12:21:00 IST" virtual_transaction_id="4/29" 
+       type="create" command_tag="CREATE DATABASE" application_name="pg_regress" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: CREATE DATABASE &quot;regression&quot; TEMPLATE=template0</message>
+</event>
+<event user="edb" database="postgres" process_id="110426" 
+       remote_host="[local]" session_id="63e1f4d4.1af5a" 
+       session_line_num="2" process_status="idle" 
+       session_start_time="2023-02-07 12:21:00.983 IST" 
+       log_time="2023-02-07 12:21:00 IST" virtual_transaction_id="4/30" 
+       type="alter" command_tag="ALTER DATABASE" application_name="pg_regress" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: ALTER DATABASE &quot;regression&quot; SET lc_messages TO &apos;C&apos;;ALTER DATABASE &quot;regression&quot; SET lc_monetary TO &apos;C&apos;;ALTER DATABASE &quot;regression&quot; SET lc_numeric TO &apos;C&apos;;ALTER DATABASE &quot;regression&quot; SET lc_time TO &apos;C&apos;;ALTER DATABASE &quot;regression&quot; SET bytea_output TO &apos;hex&apos;;ALTER DATABASE &quot;regression&quot; SET timezone_abbreviations TO &apos;Default&apos;;</message>
+</event>
+<event user="edb" database="regression" process_id="110429" 
+       remote_host="[local]" session_id="63e1f4d5.1af5d" 
+       session_line_num="1" process_status="idle" 
+       session_start_time="2023-02-07 12:21:01.152 IST" 
+       log_time="2023-02-07 12:21:01 IST" virtual_transaction_id="4/33" 
+       type="set" command_tag="SET" application_name="pg_regress/test_setup" 
+       backend_type="client backend" query_id="0">
+	<error_severity>AUDIT</error_severity>
+	<message>statement: SET synchronous_commit = on;</message>
+</event>
+<event user="enterprisedb" database="edb" process_id="5942" remote_host=
+"[local]"
+       session_id="5ec7ac4d.1735" session_line_num="8" process_status="idle"
+       session_start_time="2023-02-07 16:11:17 IST" log_time="2023-02-07
+       16:12:45.471 IST" virtual_transaction_id="4/27" type="select" 
+       command_tag="SELECT" audit_tag="edbaudit" application_name="psql" 
+       backend_type="parallel worker" leader_pid="5940" query_id="0">
+          <error_severity>AUDIT</error_severity>
+          <message>statement: SELECT * FROM dept;</message>
+</event>
+<event process_id="112399" session_id="63e1f4e2.1b70f" session_line_num="1" 
+       session_start_time="2023-02-07 12:21:14.150 IST" 
+       log_time="2023-02-07 12:21:14 IST" virtual_transaction_id="5/2012" 
+       type="error" sql_state_code="42601" command_tag="SELECT" 
+       application_name="pg_regress/timestamptz" backend_type="parallel worker" 
+       leader_pid="112317" query_id="0">
+	<error_severity>ERROR</error_severity>
+	<message>date format not recognized</message>
+	<query>SELECT to_char(d1, E&apos;&quot;HH:MI:SS is&quot; 
+   HH:MI:SS &quot;\\&quot;text between quote marks\\&quot;&quot;&apos;)
+		   FROM TIMESTAMPTZ_TBL;</query>
+</event>
+<event process_id="112402" session_id="63e1f4e2.1b712" session_line_num="1" 
+       session_start_time="2023-02-07 12:21:14.156 IST" log_time="2023-02-07 
+       12:21:14 IST" virtual_transaction_id="5/2015" type="error" 
+       sql_state_code="42601" command_tag="SELECT" 
+       application_name="pg_regress/timestamptz" backend_type="parallel worker" 
+       leader_pid="112317" query_id="0">
+	<error_severity>ERROR</error_severity>
+	<message>date format not recognized</message>
+	<query>SELECT to_char(d1, &apos;HH24--text--MI--text--SS&apos;)
+		   FROM TIMESTAMPTZ_TBL;</query>
+</event>
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx
new file mode 100644
index 00000000000..4bd803fc9ef
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/edb_loader_control_file_parameters.mdx
@@ -0,0 +1,311 @@
+---
+title: "EDB*Loader control file parameters"
+description: "Describes the parameters for each clause used in the control file"
+---
+
+Use the following parameters when [building the EDB\*Loader control file](/epas/latest/database_administration/02_edb_loader/building_the_control_file/).
+
+## OPTIONS param=value
+
+ Use the `OPTIONS` clause to specify `param=value` pairs that represent an EDB\*Loader directive. If you specify a parameter in the `OPTIONS` clause and on the command line when `edbldr` is invoked, the command line setting takes effect.
+
+ Specify one or more of the following parameter/value pairs:
+
+-   `DIRECT= { FALSE | TRUE }`
+
+    With `DIRECT` set to `TRUE`, EDB\*Loader performs a direct path load instead of a conventional path load. The default value of `DIRECT` is `FALSE`.
+
+    Don't set `DIRECT=true` when loading the data into a replicated table. If you're using EDB\*Loader to load data into a replicated table and set `DIRECT=true`, indexes might omit rows that are in a table or can potentially contain references to rows that were deleted. Direct inserts to load data into replicated tables aren't supported.
+
+    For information on direct path loads see, [Direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load/).
+
+-   `ERRORS=error_count`
+
+    `error_count` specifies the number of errors permitted before aborting the EDB\*Loader session. The default is `50`.
+
+-   `FREEZE= { FALSE | TRUE }`
+
+    Set `FREEZE` to `TRUE` to copy the data with the rows `frozen`. A tuple guaranteed to be visible to all current and future transactions is marked as frozen to prevent transaction ID wraparound. For more information about frozen tuples, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/routine-vacuuming.html).
+
+    You must specify a data-loading type of `TRUNCATE` in the control file when using the `FREEZE` option. `FREEZE` isn't supported for direct loading.
+
+    By default, `FREEZE` is `FALSE`.
+
+-   `PARALLEL= { FALSE | TRUE }`
+
+    Set `PARALLEL` to `TRUE` to indicate that this EDB\*Loader session is one of a number of concurrent EDB\*Loader sessions participating in a parallel direct path load. The default value of `PARALLEL` is `FALSE`.
+
+    When `PARALLEL` is `TRUE`, you must also set the `DIRECT` parameter to `TRUE`. For more information about parallel direct path loads, see [Parallel direct path load](/epas/latest/database_administration/02_edb_loader/invoking_edb_loader/parallel_direct_path_load).
+
+-   `ROWS=n`
+
+    `n` specifies the number of rows that EDB\*Loader commits before loading the next set of `n` rows.
+
+    If EDB\*Loader encounters an invalid row during a load in which the `ROWS` parameter is specified, those rows committed prior to encountering the error remain in the destination table.
+
+-   `SKIP=skip_count`
+
+    `skip_count` specifies the number of records at the beginning of the input data file to skip before loading begins. The default is `0`.
+
+-   `SKIP_INDEX_MAINTENANCE={ FALSE | TRUE }`
+
+    If `SKIP_INDEX_MAINTENANCE` is `TRUE`, index maintenance isn't performed as part of a direct path load, and indexes on the loaded table are marked as invalid. The default value of `SKIP_INDEX_MAINTENANCE` is `FALSE`.
+
+    !!! Note
+        During a parallel direct path load, target table indexes aren't updated. They are marked as invalid after the load is complete.
+
+    You can use the `REINDEX` command to rebuild an index. For more information about the `REINDEX` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-reindex.html).
+
+## charset
+
+ Use the `CHARACTERSET` clause to identify the character set encoding of `data_file`, where `charset` is the character set name. This clause is required if the data file encoding differs from the control file encoding. The control file encoding must always be in the encoding of the client where `edbldr` is invoked.
+
+ Examples of `charset` settings are `UTF8`, `SQL_ASCII`, and `SJIS`.
+
+ For more information about client-to-database character-set conversion, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/multibyte.html).
+
+## data_file
+
+ File containing the data to load into `target_table`. Each record in the data file corresponds to a row to insert into `target_table`.
+
+ If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.dat`, for example, `mydatafile.dat`.
+
+ !!! Note
+    If you specify the `DATA` parameter on the command line when invoking `edbldr`, the file given by the command line `DATA` parameter is used instead.
+
+ If you omit the `INFILE` clause and the command line `DATA` parameter, then the data file name is assumed to be the same as the control file name but with the extension `.dat`.
+
+## stdin
+
+ Specify `stdin` (all lowercase letters) if you want to use standard input to pipe the data to load directly to EDB\*Loader. This technique is useful for data sources generating a large number of records to load.
+
+## bad_file
+
+ A file that receives `data_file` records that can't load due to errors. The bad file is generated for collecting rejected or bad records.
+
+ For EDB Postgres Advanced Server version 12 and later, a bad file is generated only if there are any bad or rejected records. However, if an existing bad file has the same name and location, and no bad records are generated after invoking a new version of `edbldr`, the existing bad file remains intact.
+
+ If you don't include an extension in the file name, EDB\*Loader assumes the file has an extension of `.bad`, for example, `mybadfile.bad`.
+
+ !!! Note
+    If you specify the `BAD` parameter on the command line when invoking `edbldr`, the file given with the command line `BAD` parameter is used instead.
+
+## discard_file
+
+ File that receives input data records that aren't loaded into any table. This input data records are discarded because none of the selection criteria are met for tables with the `WHEN` clause and there are no tables without a `WHEN` clause. All records meet the selection criteria of a table without a `WHEN` clause.
+
+ If you don't include an extension with the file name, EDB\*Loader assumes the file has an extension of `.dsc`, for example, `mydiscardfile.dsc`.
+
+ !!! Note
+    If you specify the `DISCARD` parameter on the command line when invoking `edbldr`, the file given with the command line `DISCARD` parameter is used instead.
+
+## max_discard_recs
+
+ Maximum number of discarded records that the input data records can encounter before terminating the EDB\*Loader session. You can use either keyword `DISCARDMAX` or `DISCARDS` preceding the integer value specified by `max_discard_recs`.
+
+ For example, if `max_discard_recs` is `0`, then the EDB\*Loader session is terminated when a first discarded record is encountered. If `max_discard_recs` is `1`, then the EDB\*Loader session is terminated when a second discarded record is encountered.
+
+ When the EDB\*Loader session is terminated due to exceeding `max_discard_recs`, prior input data records that were loaded into the database are retained. They aren't rolled back.
+
+## INSERT, APPEND, REPLACE, TRUNCATE
+
+ Specifies how to load data into the target tables. Specifying one of `INSERT`, `APPEND`, `REPLACE`, or `TRUNCATE` establishes the default action for all tables, overriding the default of `INSERT`.
+
+-   `INSERT`
+
+    Data is loaded into an empty table. EDB\*Loader throws an exception and doesn't load any data if the table isn't initially empty.
+
+    !!! Note
+        If the table contains rows, you must use the `TRUNCATE` command to empty the table before invoking EDB\*Loader. EDB\*Loader throws an exception if you use the `DELETE` command to empty the table instead of the `TRUNCATE` command. Oracle SQL\*Loader allows you to empty the table by using either the `DELETE` or `TRUNCATE` command.
+
+-   `APPEND`
+
+    Data is added to any existing rows in the table. The table also can be empty initially.
+
+-   `REPLACE`
+
+    The `REPLACE` keyword and `TRUNCATE` keywords are functionally identical. The table is truncated by EDB\*Loader before loading the new data.
+
+    !!! Note
+        Delete triggers on the table aren't fired as a result of the `REPLACE` operation.
+
+-   `TRUNCATE`
+
+    The table is truncated by EDB\*Loader before loading the new data. Delete triggers on the table aren't fired as a result of the `TRUNCATE` operation.
+
+## PRESERVE BLANKS
+
+ The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause. It retains leading and trailing whitespaces for both delimited and predetermined size fields. 
+ 
+ In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted. Any leading whitespaces are left intact. 
+
+ !!! Note
+    If you don't explicitly provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. 
+ 
+## target_table
+
+ Name of the table into which to load data. The table name can be schema-qualified (for example, `enterprisedb.emp`). The specified target can't be a view.
+
+## field_condition
+
+ Conditional clause taking the following form:
+
+```text
+[ ( ] { (start:end) | column_name } { = | != | <> } 'val' [ ) ]
+```
+
+ This conditional clause is used for the `WHEN` clause, which is part of the `INTO TABLE target_table` clause. It's also used for the `NULLIF` clause, which is part of the field definition denoted as `field_def` in the syntax diagram.
+
+ `start` and `end` are positive integers specifying the column positions in `data_file` that mark the beginning and end of a field to compare with the constant `val`. The first character in each record begins with a `start` value of `1`.
+
+ `column_name` specifies the name assigned to a field definition of the data file as defined by `field_def` in the syntax diagram.
+
+ Using (`start`:`end`) or `column_name` defines the portion of the record in `data_file` to compare with the value specified by `val` to evaluate as either true or false.
+
+ All characters used in the `field_condition` text (particularly in the `val` string) must be valid in the database encoding. For performing data conversion, EDB\*Loader first converts the characters in `val` string to the database encoding and then to the data file encoding.
+
+ In the `WHEN field_condition [ AND field_condition ]` clause, if all such conditions evaluate to `TRUE` for a given record, then EDB\*Loader attempts to insert that record into `target_table`. If the insert operation fails, the record is written to `bad_file`.
+
+ Suppose, for a given record, that none of the `WHEN` clauses evaluate to `TRUE` for all `INTO TABLE` clauses. The record is written to `discard_file` if a discard file was specified for the EDB\*Loader session.
+
+ See the description of the `NULLIF` clause in this parameters list for the effect of `field_condition` on this clause.
+
+## termstring
+
+ String of one or more characters that separates each field in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `termstring` with no intervening character results in the corresponding column being set to null.
+
+## enclstring
+
+ String of one or more characters used to enclose a field value in `data_file`. The characters can be single byte or multibyte, However, they must be valid in the database encoding. Use `enclstring` on fields where `termstring` appears as part of the data.
+
+## delimstring
+
+ String of one or more characters that separates each record in `data_file`. The characters can be single byte or multibyte. However, they must be valid in the database encoding. Two consecutive appearances of `delimstring` with no intervening character results in no corresponding row being loaded into the table. You must also terminate the last record (that is, the end of the data file) with the `delimstring` characters. Otherwise, the final record isn't loaded into the table.
+
+ !!! Note
+    The `RECORDS DELIMITED BY 'delimstring'` clause isn't compatible with Oracle databases.
+
+## TRAILING NULLCOLS
+
+ If you specify `TRAILING NULLCOLS`, then the columns in the column list for which there's no data in `data_file` for a given record are set to null when the row is inserted. This option applies only to one or more consecutive columns at the end of the column list.
+
+ If fields are omitted at the end of a record and you don't specify `TRAILING NULLCOLS`, EDB\*Loader assumes the record contains formatting errors and writes it to the bad file.
+
+## column_name
+
+ Name of a column in `target_table` into which to insert a field value defined by `field_def`. If the field definition includes the `FILLER` or `BOUNDFILLER` clause, then `column_name` isn't required as the name of a column in the table. It can be any identifier name since the `FILLER` and `BOUNDFILLER` clauses prevent loading the field data into a table column.
+
+## CONSTANT val
+
+ Specifies a constant that's type-compatible with the column data type to which it's assigned in a field definition. You can use single or double quotes around `val`. If `val` contains white space, then you must use quotation marks around it.
+
+ The use of the `CONSTANT` clause determines the value to assign to a column in each inserted row. No other clause can appear in the same field definition.
+
+ If you use the `TERMINATED BY` clause to delimit the fields in `data_file`, there must be no delimited field in `data_file` corresponding to any field definition with a `CONSTANT` clause. In other words, EDB\*Loader assumes there's no field in `data_file` for any field definition with a `CONSTANT` clause.
+
+## FILLER
+
+ Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name.
+
+ Unlike the `BOUNDFILLER` clause, you can't reference an identifier defined with the `FILLER` clause in a SQL expression. See the discussion of the `expr` parameter.
+
+## BOUNDFILLER
+
+ Specifies not to load the data in the field defined by the field definition into the associated column if the identifier of the field definition is an actual column name in the table. In this case, the column is set to null. Use of the `FILLER` or `BOUNDFILLER` clause is the only circumstance in which you don't have to identify the field definition with an actual column name.
+
+ Unlike the `FILLER` clause, a SQL expression can reference an identifier defined with the `BOUNDFILLER` clause. See the discussion of the `expr` parameter.
+
+## POSITION (start:end)
+
+ Defines the location of the field in a record in a fixed-width field data file. `start` and `end` are positive integers. The first character in the record has a start value of `1`.
+
+```sql
+CHAR [(<length>)] | DATE [(<length>)] | TIMESTAMP [(<length>)] [ "<datemask>" ] | 
+INTEGER EXTERNAL [(<length>)] |
+FLOAT EXTERNAL [(<length>)] | DECIMAL EXTERNAL [(<length>)] |
+ZONED EXTERNAL [(<length>)] | ZONED [(<precision>[,<scale>])]
+```
+
+ Field type that describes the format of the data field in `data_file`.
+
+ !!! Note 
+    Specifying a field type is optional for descriptive purposes and has no effect on whether EDB\*Loader successfully inserts the data in the field into the table column. Successful loading depends on the compatibility of the column data type and the field value. For example, a column with data type `NUMBER(7,2)` successfully accepts a field containing `2600`. However, if the field contains a value such as `26XX`, the insertion fails, and the record is written to `bad_file`.
+
+`ZONED` data is not human readable. `ZONED` data is stored in an internal format where each digit is encoded in a separate nibble/nybble/4-bit field. In each `ZONED` value, the last byte contains a single digit in the high-order 4 bits and the sign in the low-order 4 bits.
+
+## length
+
+ Specifies the length of the value to load into the associated column.
+
+ If you specify the `POSITION` (`start`:`end`) clause with a `fieldtype(length)` clause, then the ending position of the field is overridden by the specified `length` value. That is, the length of the value to load into the column is determined by the `length` value beginning at the `start` position and not by the `end` position of the `POSITION` (`start`:`end`) clause. Thus, the value to load into the column might be shorter than the field defined by `POSITION` (`start`:`end`). Or, it might go beyond the end position, depending on the specified `length` size.
+
+ If you specify the `FIELDS TERMINATED BY 'termstring'` clause as part of the `INTO TABLE` clause, and a field definition contains the `fieldtype(length)` clause, then a record is accepted. However, the specified `length` values must be greater than or equal to the field lengths as determined by the `termstring` characters enclosing all such fields of the record. If the specified `length` value is less than a field length as determined by the enclosing `termstring` characters for any such field, then the record is rejected.
+
+ If you don't specify the `FIELDS TERMINATED BY 'termstring'` clause, and you don't include the `POSITION` (`start`:`end`) clause with a field containing the `fieldtype(length)` clause, then the starting position of this field begins with the next character following the ending position of the preceding field. The ending position of the preceding field is either:
+
+ -  The end of its `length` value if the preceding field contains the `fieldtype(length)` clause
+ -  Its `end` parameter if the field contains the `POSITION` (`start`:`end`) clause without the `fieldtype(length)` clause
+
+## precision
+
+ Use `precision` to specify the length of the `ZONED` value.
+
+ If the `precision` value specified for `ZONED` conflicts with the length calculated by the server based on information provided with the `POSITION` clause, EDB\*Loader uses the value specified for `precision`.
+
+## scale
+
+ Specifies the number of digits to the right of the decimal point in a `ZONED` value.
+
+## datemask
+
+ Specifies the ordering and abbreviation of the day, month, and year components of a date field.
+
+ !!! Note
+    If you specify the `DATE` or `TIMESTAMP` field type with a SQL expression for the column, then you must specify `datemask` after `DATE` or `TIMESTAMP` and before the SQL expression. See the discussion of the `expr` parameter.
+
+ When using the `TIMESTAMP` field datatype, if you specify `time_stamp timestamp "yyyymmddhh24miss"`, the `datemask` is converted to the SQL expression. However, in the case of `time_stamp timestamp "select to_timestamp(:time_stamp, 'yyyymmddhh24miss')"`, EDB\*Loader can't differentiate between datemask and the SQL expression. It treats the third field (SQL expression in the example) as datemask and prepares the SQL expression, which isn't valid. Where:
+ 
+-   `first field` specifies the column name. 
+-   `second field` specifies the datatype.
+-   `third field` specifies the datemask.
+
+If you want to provide an SQL expression, then a workaround is to specify the datemask and SQL expression using the `TO_CHAR` function as:
+ 
+ ```sql
+ time_stamp timestamp "yyyymmddhh24miss" "to_char(to_timestamp(:time_stamp, 'yyyymmddhh24miss'), 'yyyymmddhh24miss')"
+ ```
+
+`NULLIF field_condition [ AND field_condition ] ...`
+
+ See the description of `field_condition` in this parameter list for the syntax of `field_condition`.
+
+ If all field conditions evaluate to `TRUE`, then the column identified by `column_name` in the field definition is set to null. If any field condition evaluates to `FALSE`, then the column is set to the appropriate value as normally occurs according to the field definition.
+
+## PRESERVE BLANKS
+
+ The `PRESERVE BLANKS` option works only with the `OPTIONALLY ENCLOSED BY` clause and retains leading and trailing whitespaces for both delimited and predetermined size fields. 
+ 
+ In case of `NO PRESERVE BLANKS`, if the fields are delimited, then only leading whitespaces are omitted. If any trailing whitespaces are present, they are left intact. In the case of predetermined-sized fields with `NO PRESERVE BLANKS`, the trailing whitespaces are omitted, and any leading whitespaces are left intact. 
+
+ !!! Note
+    If you don't provide `PRESERVE BLANKS` or `NO PRESERVE BLANKS`, then the behavior defaults to `NO PRESERVE BLANKS`. This option doesn't work for ideographic whitespaces. 
+ 
+## expr
+
+ A SQL expression returning a scalar value that's type-compatible with the column data type to which it's assigned in a field definition. Use double quotes around `expr`. `expr` can contain a reference to any column in the field list except for fields with the `FILLER` clause. Prefix the column name using a colon (`:`).
+
+ `expr` can also consist of a SQL `SELECT` statement. If you use a `SELECT` statement:
+
+-   Enclose the `SELECT` statement in parentheses, that is, `(SELECT ...)`.
+-   The select list must consist of one expression following the `SELECT` keyword.
+-   The result set must not return more than one row. If no rows are returned, then the returned value of the resulting expression is null.
+
+    The following is the syntax for a `SELECT` statement:
+
+    ```sql
+    "(SELECT <expr> [ FROM <table_list> [ WHERE <condition> ] ])"
+    ```
+
+    !!! Note
+        Omitting the `FROM table_list` clause isn't compatible with Oracle databases. If you don't need to specify any tables, using the `FROM DUAL` clause is compatible with Oracle databases.
+
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx
new file mode 100644
index 00000000000..153426d3204
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/edb_resource_manager_system_catalogs.mdx
@@ -0,0 +1,34 @@
+---
+title: "System catalogs"
+description: "Describes the system catalogs that store the resource group information used by EDB Resource Manager"
+redirects:
+  - ../../../database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs/
+  - /epas/latest/database_administration/10_edb_resource_manager/edb_resource_manager_system_catalogs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+System catalogs store the resource group information used by EDB Resource Manager.
+
+## edb_all_resource_groups
+
+The following table lists the information available in the `edb_all_resource_groups` catalog.
+
+| Column                         | Type      | Description                                                                  |
+| ------------------------------ | --------- | ---------------------------------------------------------------------------- |
+| `group_name`                   | `name`    | The name of the resource group.                                              |
+| `active_processes`             | `integer` | Number of currently active processes in the resource group.                  |
+| `cpu_rate_limit`               | `float8`  | Maximum CPU rate limit for the resource group. `0` means no limit.           |
+| `per_process_cpu_rate_limit`   | `float8`  | Maximum CPU rate limit per currently active process in the resource group.   |
+| `dirty_rate_limit`             | `float8`  | Maximum dirty rate limit for a resource group. `0` means no limit.           |
+| `per_process_dirty_rate_limit` | `float8`  | Maximum dirty rate limit per currently active process in the resource group. |
+
+<div id="edb_resource_group-1" class="registered_link"></div>
+
+## edb_resource_group
+
+The following table lists the information available in the `edb_resource_group` catalog.
+
+| Column               | Type     | Description                                                        |
+| -------------------- | -------- | ------------------------------------------------------------------ |
+| `rgrpname`           | `name`   | The name of the resource group.                                    |
+| `rgrpcpuratelimit`   | `float8` | Maximum CPU rate limit for a resource group. `0` means no limit.   |
+| `rgrpdirtyratelimit` | `float8` | Maximum dirty rate limit for a resource group. `0` means no limit. |
diff --git a/product_docs/docs/epas/16/reference/database_administrator_reference/index.mdx b/product_docs/docs/epas/16/reference/database_administrator_reference/index.mdx
new file mode 100644
index 00000000000..165b3e8de5b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/database_administrator_reference/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "Database administrator reference"
+indexCards: simple
+description: "Contains reference information applicable to database administrator tasks, such as configuration parameters"
+---
+
+This reference information applies to database administrators.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/index.mdx b/product_docs/docs/epas/16/reference/index.mdx
new file mode 100644
index 00000000000..da349ae9834
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Reference"
+indexCards: simple
+navigation:
+- sql_reference
+
+---
+
+This reference material contains descriptive content needed by application programmers and database administrators. It also includes information that applies to organizations migrating their Oracle applications to use EDB Postgres Advanced Server as well as a SQL reference.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx
new file mode 100644
index 00000000000..ce45447f6e1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect.mdx
@@ -0,0 +1,53 @@
+---
+title: "dblink_ora_connect()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/01_dblink_ora_connect/
+---
+
+<div id="dblink_ora_connect" class="registered_link"></div>
+
+The `dblink_ora_connect()` function establishes a connection to an Oracle database with user-specified connection information. The function comes in two forms. 
+
+The signature of the first form is:
+
+```c
+dblink_ora_connect(<conn_name>, <server_name>, <service_name>, <user_name>,
+<password>, <port>, <asDBA>)
+```
+
+Where:
+
+-   `conn_name` specifies the name of the link.
+
+-   `server_name` specifies the name of the host.
+
+-   `service_name` specifies the name of the service.
+
+-   `user_name` specifies the name used to connect to the server.
+
+-   `password` specifies the password associated with the user name.
+
+-   `port` specifies the port number.
+
+-   `asDBA` is `True` if you want to request `SYSDBA` privileges on the Oracle server. This parameter is optional. If omitted, the value is `FALSE`.
+
+The first form of `dblink_ora_connect()` returns a `TEXT` value.
+
+The signature of the second form of the `dblink_ora_connect()` function is:
+
+```c
+dblink_ora_connect(<foreign_server_name>, <asDBA>)
+```
+
+Where:
+
+-   `foreign_server_name` specifies the name of a foreign server.
+
+-   `asDBA` is `True` if you want to request `SYSDBA` privileges on the Oracle server. This parameter is optional. If omitted, the value is `FALSE`.
+
+The second form of the `dblink_ora_connect()` function allows you to use the connection properties of a predefined foreign server when connecting to the server.
+
+Before invoking the second form of the `dblink_ora_connect()` function, use the `CREATE SERVER` command to store the connection properties for the link to a system table. When you call the `dblink_ora_connect()` function, substitute the server name specified in the `CREATE SERVER` command for the name of the link.
+
+The second form of `dblink_ora_connect()` returns a `TEXT` value.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx
new file mode 100644
index 00000000000..12741fb1863
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/02_dblink_ora_status.mdx
@@ -0,0 +1,20 @@
+---
+title: "dblink_ora_status()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/02_dblink_ora_status/
+---
+
+<div id="dblink_ora_status" class="registered_link"></div>
+
+The `dblink_ora_status()` function returns the database connection status. The signature is:
+
+```c
+dblink_ora_status(<conn_name>)
+```
+
+Where:
+
+`conn_name` specifies the name of the link.
+
+If the specified connection is active, the function returns a `TEXT` value of `OK`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx
new file mode 100644
index 00000000000..9de3100f361
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect.mdx
@@ -0,0 +1,20 @@
+---
+title: "dblink_ora_disconnect()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/03_dblink_ora_disconnect/
+---
+
+<div id="dblink_ora_disconnect" class="registered_link"></div>
+
+The `dblink_ora_disconnect()` function closes a database connection. The signature is:
+
+```c
+dblink_ora_disconnect(<conn_name>)
+```
+
+Where:
+
+`conn_name` specifies the name of the link.
+
+The function returns a `TEXT` value.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx
new file mode 100644
index 00000000000..13b24c2755c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/04_dblink_ora_record.mdx
@@ -0,0 +1,22 @@
+---
+title: "dblink_ora_record()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/04_dblink_ora_record/
+---
+
+<div id="dblink_ora_record" class="registered_link"></div>
+
+The `dblink_ora_record()` function retrieves information from a database. The signature is:
+
+```c
+dblink_ora_record(<conn_name>, <query_text>)
+```
+
+Where:
+
+-   `conn_name` specifies the name of the link.
+
+-   `query_text` specifies the text of the SQL `SELECT` statement invoked on the Oracle server.
+
+The function returns a `SETOF` record.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx
new file mode 100644
index 00000000000..16e1290d4f9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/05_dblink_ora_call.mdx
@@ -0,0 +1,24 @@
+---
+title: "dblink_ora_call()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/05_dblink_ora_call/
+---
+
+<div id="dblink_ora_call" class="registered_link"></div>
+
+The `dblink_ora_call()` function executes a non-`SELECT` statement on an Oracle database and returns a result set. The signature is:
+
+```c
+dblink_ora_call(<conn_name>, <command>, <iterations>)
+```
+
+Where:
+
+-   `conn_name` specifies the name of the link.
+
+-   `command` specifies the text of the SQL statement invoked on the Oracle server.
+
+-   `iterations` specifies the number of times the statement is executed.
+
+The function returns a `SETOF` record.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx
new file mode 100644
index 00000000000..c44bd426c3d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec.mdx
@@ -0,0 +1,22 @@
+---
+title: "dblink_ora_exec()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/06_dblink_ora_exec/
+---
+
+<div id="dblink_ora_exec" class="registered_link"></div>
+
+The `dblink_ora_exec()` procedure executes a DML or DDL statement in the remote database. The signature is:
+
+```c
+dblink_ora_exec(<conn_name>, <command>)
+```
+
+Where:
+
+-   `conn_name` specifies the name of the link.
+
+-   `command` specifies the text of the `INSERT`, `UPDATE`, or `DELETE` SQL statement invoked on the Oracle server.
+
+The function returns a `VOID`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx
new file mode 100644
index 00000000000..aa1a34e9662
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy.mdx
@@ -0,0 +1,29 @@
+---
+title: "dblink_ora_copy()"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/07_dblink_ora_copy/
+---
+
+<div id="dblink_ora_copy" class="registered_link"></div>
+
+The `dblink_ora_copy()` function copies an Oracle table to an EDB table. The `dblink_ora_copy()` function returns a `BIGINT` value that represents the number of rows copied. The signature is:
+
+```c
+dblink_ora_copy(<conn_name>, <command>, <schema_name>, <table_name>,
+<truncate>, <count>)
+```
+
+Where:
+
+-   `conn_name` specifies the name of the link.
+
+-   `command` specifies the text of the SQL `SELECT` statement invoked on the Oracle server.
+
+-   `schema_name` specifies the name of the target schema.
+
+-   `table_name` specifies the name of the target table.
+
+-   `truncate` specifies whether the server performs a `TRUNCATE` on the table prior to copying. Specify `TRUE` if you want the server to `TRUNCATE` the table. `truncate` is optional. If omitted, the value is `FALSE`.
+
+-   `count` reports status information every `n` records, where `n` is a number. While the function executes, EDB Postgres Advanced Server raises a notice of severity `INFO` with each iteration of the count. For example, if FeedbackCount is `10`, `dblink_ora_copy()` raises a notice every 10 records. `count` is optional. If omitted, the value is `0`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx
new file mode 100644
index 00000000000..6e8d23ae84a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/01_dblink_ora_functions_and_procedures/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "dblink_ora functions and procedures"
+indexCards: simple
+description: "Describes the functions and procedures supported by dblink_ora"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.124.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.354.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/01_dblink_ora_functions_and_procedures/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/working_with_oracle_data/06_dblink_ora/01_dblink_ora_functions_and_procedures/
+---
+
+<div id="dblink_ora_functions_and_procedures" class="registered_link"></div>
+
+The dblink_ora utility supports functions and procedures that enable you to issue arbitrary queries to a remote Oracle server.
+
+<div class="toctree" maxdepth="3">
+
+dblink_ora_connect dblink_ora_status dblink_ora_disconnect dblink_ora_record dblink_ora_call dblink_ora_exec dblink_ora_copy
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/01_example_partition_by_list.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/01_example_partition_by_list.mdx
new file mode 100644
index 00000000000..515dde0941e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/01_example_partition_by_list.mdx
@@ -0,0 +1,47 @@
+---
+title: "Example: PARTITION BY LIST"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/01_example_partition_by_list/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_by_list" class="registered_link"></div>
+
+This example creates a partitioned table `sales` using the `PARTITION BY LIST` clause. The `sales` table stores information in three partitions: `europe`, `asia`, and `americas`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The resulting table is partitioned by the value specified in the `country` column:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
+
+-   Rows with a value of `FRANCE` or `ITALY` in the `country` column are stored in the `europe` partition.
+-   Rows with a value of `INDIA` or `PAKISTAN` in the `country` column are stored in the `asia` partition.
+-   Rows with a value of `US` or `CANADA` in the `country` column are stored in the `americas` partition.
+
+The server evaluates the following statement against the partitioning rules and stores the row in the `europe` partition:
+
+`INSERT INTO sales VALUES (10, '9519a', 'FRANCE', '18-Aug-2012', '650000');`
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/02_example_automatic_list_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/02_example_automatic_list_partition.mdx
new file mode 100644
index 00000000000..f28b6d7517d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/02_example_automatic_list_partition.mdx
@@ -0,0 +1,60 @@
+---
+title: "Example: AUTOMATIC LIST PARTITION"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/02_example_automatic_list_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_automatic_list_partition" class="registered_link"></div>
+
+This example shows a `sales` table that uses an `AUTOMATIC` clause to create an automatic list partitioned table on the `sales_state` column. The database creates a partition and adds data to a table.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no      number,
+  part_no      varchar2,
+  sales_state  varchar2(20),
+  date         date,
+  amount       number
+)
+PARTITION BY LIST(sales_state) AUTOMATIC
+(
+  PARTITION P_CAL VALUES('CALIFORNIA'),
+  PARTITION P_FLO VALUES('FLORIDA')
+);
+```
+
+Query the `ALL_TAB_PARTITIONS` view to see an existing partition that's successfully created:
+
+```sql
+edb=# SELECT table_name, partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ table_name | partition_name |  high_value
+------------+----------------+--------------
+ SALES      | P_CAL          | 'CALIFORNIA'
+ SALES      | P_FLO          | 'FLORIDA'
+(2 rows)
+```
+
+Insert data into a `sales` table that can't fit into an existing partition. For the regular list partitioned table, you get an error. However, automatic list partitioning creates and inserts the data into a new partition.
+
+```sql
+edb=# INSERT INTO sales VALUES (1, 'IND', 'INDIANA');
+INSERT 0 1
+edb=# INSERT INTO sales VALUES (2, 'OHI', 'OHIO');
+INSERT 0 1
+```
+
+Query the `ALL_TAB_PARTITIONS` view again after the insert. The partition is created, and data is inserted to hold a new value. A system-generated name of the partition is created that varies for each session.
+
+```sql
+edb=# SELECT table_name, partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ table_name | partition_name |  high_value
+------------+----------------+--------------
+ SALES      | P_CAL          | 'CALIFORNIA'
+ SALES      | P_FLO          | 'FLORIDA'
+ SALES      | SYS106900103   | 'INDIANA'
+ SALES      | SYS106900104   | 'OHIO'
+(4 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/03_example_partition_by_range.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/03_example_partition_by_range.mdx
new file mode 100644
index 00000000000..8f949738732
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/03_example_partition_by_range.mdx
@@ -0,0 +1,54 @@
+---
+title: "Example: PARTITION BY RANGE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/03_example_partition_by_range/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_by_range" class="registered_link"></div>
+
+This example creates a partitioned table `sales` using the `PARTITION BY RANGE` clause. The `sales` table stores information in four partitions: `q1_2012`, `q2_2012`, `q3_2012` and `q4_2012`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+(
+  PARTITION q1_2012
+    VALUES LESS THAN('2012-Apr-01'),
+  PARTITION q2_2012
+    VALUES LESS THAN('2012-Jul-01'),
+  PARTITION q3_2012
+    VALUES LESS THAN('2012-Oct-01'),
+  PARTITION q4_2012
+    VALUES LESS THAN('2013-Jan-01')
+);
+```
+
+The resulting table is partitioned by the value specified in the `date` column:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ Q1_2012        | '01-APR-12 00:00:00'
+ Q2_2012        | '01-JUL-12 00:00:00'
+ Q3_2012        | '01-OCT-12 00:00:00'
+ Q4_2012        | '01-JAN-13 00:00:00'
+(4 rows)
+```
+
+-   Any row with a value in the `date` column before April 1, 2012 is stored in a partition named `q1_2012`.
+-   Any row with a value in the `date` column before July 1, 2012 is stored in a partition named `q2_2012`.
+-   Any row with a value in the `date` column before October 1, 2012 is stored in a partition named `q3_2012`.
+-   Any row with a value in the `date` column before January 1, 2013 is stored in a partition named `q4_2012`.
+
+The server evaluates the following statement against the partitioning rules and stores the row in the `q3_2012` partition:
+
+`INSERT INTO sales VALUES (10, '9519a', 'FRANCE', '18-Aug-2012', '650000');`
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/04_example_interval_range_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/04_example_interval_range_partition.mdx
new file mode 100644
index 00000000000..ec3295ac6c9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/04_example_interval_range_partition.mdx
@@ -0,0 +1,58 @@
+---
+title: "Example: INTERVAL RANGE PARTITION"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/04_example_interval_range_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_interval_range_partition" class="registered_link"></div>
+
+This example shows a `sales` table that's partitioned by interval on the `sold_month` column. The range partition is created to establish a transition point, and new partitions are created beyond that transition point. The database creates a new interval range partition and adds data to a table.
+
+```sql
+CREATE TABLE sales
+(
+  prod_id           int,
+  prod_quantity     int,
+  sold_month        date
+)
+PARTITION BY RANGE(sold_month)
+INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
+(
+  PARTITION p1
+    VALUES LESS THAN('15-JAN-2019'),
+  PARTITION p2
+    VALUES LESS THAN('15-FEB-2019')
+);
+```
+
+Query the `ALL_TAB_PARTITIONS` view before the database creates an interval range partition:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ P1             | '15-JAN-19 00:00:00'
+ P2             | '15-FEB-19 00:00:00'
+(2 rows)
+```
+
+Insert data into a `sales` table that exceeds the high value of a range partition:
+
+```sql
+edb=# INSERT INTO sales VALUES (1,200,'10-MAY-2019');
+INSERT 0 1
+```
+
+Query the `ALL_TAB_PARTITIONS` view again after the insert. The data is successfully inserted, and a system-generated name of the interval range partition is created. The name varies for each session.
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ P1             | '15-JAN-19 00:00:00'
+ P2             | '15-FEB-19 00:00:00'
+ SYS916340103   | '15-MAY-19 00:00:00'
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/05_example_partition_by_hash.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/05_example_partition_by_hash.mdx
new file mode 100644
index 00000000000..e75066bda25
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/05_example_partition_by_hash.mdx
@@ -0,0 +1,73 @@
+---
+title: "Example: PARTITION BY HASH"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/05_example_partition_by_hash/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_by_hash" class="registered_link"></div>
+
+This example creates a partitioned table `sales` using the `PARTITION BY HASH` clause. The `sales` table stores information in three partitions: `p1`, `p2`, and `p3`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no)
+(
+  PARTITION p1,
+  PARTITION p2,
+  PARTITION p3
+);
+```
+
+The table returns an empty string for the hash partition value specified in the `part_no` column:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name | high_value
+----------------+------------
+ P1             |
+ P2             |
+ P3             |
+(3 rows)
+```
+
+Use the following command to view the hash value of the `part_no` column:
+
+```sql
+edb=# \d+ sales
+__OUTPUT__
+                                       Partitioned table "public.sales"
+ Column  |            Type            |Collation|Nullable|Default|Storage  |
+---------+----------------------------+----------+--------+------+---------+-
+ dept_no | numeric                    |          |        |      | main    |
+ part_no | character varying          |          |        |      | extended|
+ country | character varying(20)      |          |        |      | extended|
+ date    | timestamp without time zone|          |        |      | plain   |
+ amount  | numeric                    |          |        |      | main    |
+Partition key: HASH (part_no)
+Partitions: sales_p1 FOR VALUES WITH (modulus 3, remainder 0),
+            sales_p2 FOR VALUES WITH (modulus 3, remainder 1),
+            sales_p3 FOR VALUES WITH (modulus 3, remainder 2)
+```
+
+The table is partitioned by the hash value of the values specified in the `part_no` column:
+
+```sql
+edb=# SELECT partition_name, partition_position from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name | partition_position
+----------------+--------------------
+ P1             |                  1
+ P2             |                  2
+ P3             |                  3
+(3 rows)
+```
+
+The server evaluates the hash value of the `part_no` column and distributes the rows into approximately equal partitions.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/06_example_partitions_number.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/06_example_partitions_number.mdx
new file mode 100644
index 00000000000..2d9e378a59f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/06_example_partitions_number.mdx
@@ -0,0 +1,444 @@
+---
+title: "Example: PARTITION BY HASH...PARTITIONS num..."
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/06_example_partitions_number/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partitions_number" class="registered_link"></div>
+
+This example creates a hash-partitioned table `sales` using the `PARTITION BY HASH` clause. The partitioning column is `part_no`. The example specifies the number of partitions to create.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) PARTITIONS 8;
+```
+
+The eight partitions are created and assigned system-generated names. The partitions are stored in the default tablespace of the table.
+
+```sql
+edb=# SELECT table_name, partition_name FROM ALL_TAB_PARTITIONS WHERE
+table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name
+------------+----------------
+ SALES      | SYS0101
+ SALES      | SYS0102
+ SALES      | SYS0103
+ SALES      | SYS0104
+ SALES      | SYS0105
+ SALES      | SYS0106
+ SALES      | SYS0107
+ SALES      | SYS0108
+(8 rows)
+```
+
+## Example: PARTITION BY HASH...PARTITIONS num...STORE IN
+
+This example creates a hash-partitioned table named `sales`. The example specifies the number of partitions to create and the tablespaces in which the partition resides.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) PARTITIONS 5 STORE IN (ts1, ts2, ts3);
+```
+
+The `STORE IN` clause evenly distributes the partitions across the tablespaces `ts1`, `ts2`, and `ts3`.
+
+```sql
+edb=# SELECT table_name, partition_name, tablespace_name FROM
+ALL_TAB_PARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | tablespace_name
+------------+----------------+-----------------
+ SALES      | SYS0101        | TS1
+ SALES      | SYS0102        | TS2
+ SALES      | SYS0103        | TS3
+ SALES      | SYS0104        | TS1
+ SALES      | SYS0105        | TS2
+(5 rows)
+```
+
+## Example: HASH/RANGE PARTITIONS num...
+
+The `HASH` partition clause allows you to define a partitioning strategy. You can extend the `PARTITION BY HASH` clause to include `SUBPARTITION BY` either `[ RANGE | LIST | HASH ]` to create subpartitions in a `HASH` partitioned table.
+
+This example creates a table `sales` that's hash partitioned by `part_no` and subpartitioned using a range by `dept_no`. The example specifies the number of partitions when creating the table `sales`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) SUBPARTITION BY RANGE (dept_no) PARTITIONS 5;
+```
+
+The five partitions are created with default subpartitions and assigned system-generated names:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | SYS0101        | SYS0102
+ SALES      | SYS0103        | SYS0104
+ SALES      | SYS0105        | SYS0106
+ SALES      | SYS0107        | SYS0108
+ SALES      | SYS0109        | SYS0110
+(5 rows)
+```
+
+## Example: LIST/HASH SUBPARTITIONS num...
+
+This example shows the table `sales` that's list-partitioned by `country`. It is subpartitioned using hash partitioning by the `dept_no` column. This example specifies the number of subpartitions when creating the table.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (dept_no) SUBPARTITIONS 3
+(
+  PARTITION p1 VALUES('FRANCE', 'ITALY'),
+  PARTITION p2 VALUES('INDIA', 'PAKISTAN'),
+  PARTITION p3 VALUES('US', 'CANADA')
+);
+```
+
+The three partitions `p1`, `p2`, and `p3` each contain three subpartitions with system-generated names:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | P1             | SYS0101
+ SALES      | P1             | SYS0102
+ SALES      | P1             | SYS0103
+ SALES      | P2             | SYS0104
+ SALES      | P2             | SYS0105
+ SALES      | P2             | SYS0106
+ SALES      | P3             | SYS0107
+ SALES      | P3             | SYS0108
+ SALES      | P3             | SYS0109
+(9 rows)
+```
+
+## Example: HASH/HASH PARTITIONS num... SUBPARTITIONS num...
+
+This example creates the `sales` table, hash partitioned by `part_no` and hash subpartitioned by `dept_no`:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) SUBPARTITION BY HASH (dept_no) SUBPARTITIONS 3
+PARTITIONS 2;
+```
+
+The two partitions are created. Each partition includes three subpartitions with the system-generated name assigned to them.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | SYS0101        | SYS0102
+ SALES      | SYS0101        | SYS0103
+ SALES      | SYS0101        | SYS0104
+ SALES      | SYS0105        | SYS0106
+ SALES      | SYS0105        | SYS0107
+ SALES      | SYS0105        | SYS0108
+(6 rows)
+```
+
+## Example: HASH/HASH SUBPARTITIONS num... STORE IN
+
+This example creates a hash-partitioned table `sales`. This example specifies the number of partitions and subpartitions to create when creating a hash partitioned table. It also specifies the tablespaces in which the subpartitions reside when creating a hash-partitioned table.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) SUBPARTITION BY HASH (dept_no) SUBPARTITIONS 3
+PARTITIONS 2 STORE IN (ts1, ts2);
+```
+
+The two partitions are created and assigned system-generated names. The partitions are stored in the default tablespace. Subpartitions are stored in tablespaces `ts1` and `ts2`.
+
+```sql
+edb=# SELECT table_name, partition_name, tablespace_name FROM
+ALL_TAB_PARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | tablespace_name
+------------+----------------+-----------------
+ SALES      | SYS0101        |
+ SALES      | SYS0105        |
+(2 rows)
+```
+
+The `STORE IN` clause assigns the hash subpartitions to the tablespaces and stores them in the two named tablespaces `ts1` and `ts2`:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | SYS0101        | SYS0102           | TS1
+ SALES      | SYS0101        | SYS0103           | TS2
+ SALES      | SYS0101        | SYS0104           | TS1
+ SALES      | SYS0105        | SYS0106           | TS1
+ SALES      | SYS0105        | SYS0107           | TS2
+ SALES      | SYS0105        | SYS0108           | TS1
+(6 rows)
+```
+
+## Example: HASH/HASH PARTITIONS num ...STORE IN SUBPARTITIONS num... STORE IN
+
+This example creates the hash-partitioned table `sales`. It specifies the number of partitions and subpartitions to create and the tablespaces in which the partitions and subpartitions reside.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY HASH (part_no) SUBPARTITION BY HASH (dept_no) SUBPARTITIONS 3
+STORE IN (ts3) PARTITIONS 2 STORE IN (ts1, ts2);
+```
+
+The two partitions are created with system-generated names and stored in the default tablespace:
+
+```sql
+edb=# SELECT table_name, partition_name, tablespace_name FROM
+ALL_TAB_PARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | tablespace_name
+------------+----------------+-----------------
+ SALES      | SYS0101        |
+ SALES      | SYS0105        |
+(2 rows)
+```
+
+Each partition includes three subpartitions. The `STORE IN` clause stores the subpartitions in tablespaces `ts1` and `ts2`:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | SYS0101        | SYS0102           | TS1
+ SALES      | SYS0101        | SYS0103           | TS2
+ SALES      | SYS0101        | SYS0104           | TS1
+ SALES      | SYS0105        | SYS0106           | TS1
+ SALES      | SYS0105        | SYS0107           | TS2
+ SALES      | SYS0105        | SYS0108           | TS1
+(6 rows)
+```
+
+!!! Note
+    If you specify the `STORE IN` clause for partitions and subpartitions, then the subpartitions are stored in the tablespaces defined in the `PARTITIONS...STORE IN` clause. The `SUBPARTITIONS...STORE IN` clause is ignored.
+
+## Example: RANGE/HASH SUBPARTITIONS num...
+
+This example creates a range-partitioned table `sales`, which is first partitioned by the transaction date. Two range partitions are created and then hash subpartitioned using the value of the `country` column.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE (date) SUBPARTITION BY HASH (country) SUBPARTITIONS 2
+(
+  PARTITION p1 VALUES LESS THAN ('2012-Apr-01') (SUBPARTITION q1_europe),
+  PARTITION p2 VALUES LESS THAN ('2012-Jul-01')
+);
+```
+
+This statement creates a table with two partitions. The subpartition explicitly named `q1_europe` is created for partition `p1`. Because subpartitions aren't named for partition `p2`, the subpartitions are created based on the subpartition number and are assigned a system-generated name.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | P1             | Q1_EUROPE
+ SALES      | P2             | SYS0101
+ SALES      | P2             | SYS0102
+(3 rows)
+```
+
+## Example: RANGE/HASH SUBPARTITIONS num... IN PARTITION DESCRIPTION
+
+This example creates a range-partitioned table `sales`. The table is first partitioned by the transaction date. Two range partitions are created and then hash subpartitioned using the value of the `country` column.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE (date) SUBPARTITION BY HASH (country) SUBPARTITIONS 2
+(
+  PARTITION p1 VALUES LESS THAN ('2012-Apr-01') SUBPARTITIONS 3,
+  PARTITION p2 VALUES LESS THAN ('2012-Jul-01')
+);
+```
+
+The partition `p1` explicitly defines the subpartition count in the partition description. By default, two subpartitions are created for partition `p2`. Since you don't name subpartitions, system-generated names are assigned.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | P1             | SYS0101
+ SALES      | P1             | SYS0102
+ SALES      | P1             | SYS0103
+ SALES      | P2             | SYS0104
+ SALES      | P2             | SYS0105
+(5 rows)
+```
+
+## Example: LIST/HASH SUBPARTITIONS num STORE IN... IN PARTITION DESCRIPTION
+
+This example creates a list-partitioned table `sales` with two list partitions. Partition `p1` consists of three subpartitions, and partition `p2` consists of two subpartitions. Since you don't name subpartitions, system-generated names are assigned.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
+STORE IN (ts1)
+(
+  PARTITION p1 VALUES ('FRANCE', 'ITALY'),
+  PARTITION p2 VALUES ('INDIA', 'PAKISTAN') SUBPARTITIONS 2 STORE IN
+  (ts2)
+);
+```
+
+The partition `p2` explicitly defines the subpartition count in the partition description. Based on the definition, two subpartitions are created and stored in the tablespace named `ts2`. The subpartitions for partition `p1` are stored in the tablespace named `ts1`.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | P1             | SYS0101           | TS1
+ SALES      | P1             | SYS0102           | TS1
+ SALES      | P1             | SYS0103           | TS1
+ SALES      | P2             | SYS0104           | TS2
+ SALES      | P2             | SYS0105           | TS2
+(5 rows)
+```
+
+## Example: LIST/HASH STORE IN...TABLESPACES
+
+This example creates a list-partitioned table `sales`. Partition `p1` consists of three subpartitions stored explicitly in the tablespace `ts2`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
+STORE IN (ts1)
+(
+  PARTITION p1 VALUES ('FRANCE', 'ITALY') TABLESPACE ts2
+);
+```
+
+The `SELECT` statement shows partition `p1`, consisting of three subpartitions stored in the tablespace `ts2`:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | P1             | SYS0101           | TS2
+ SALES      | P1             | SYS0102           | TS2
+ SALES      | P1             | SYS0103           | TS2
+(3 rows)
+```
+
+This command adds a partition `p2` to the `sales` table. Five subpartitions are created and distributed across the tablespace listed by the `STORE IN` clause.
+
+```sql
+ALTER TABLE sales ADD PARTITION p2 VALUES ('US', 'CANADA') SUBPARTITIONS 5
+STORE IN (ts1);
+```
+
+A query of the `ALL_TAB_PARTITIONS` view shows the `sales` table with a partition named `p2`. The partition has five subpartitions. The `STORE IN` clause distributes the subpartitions across a tablespace named `ts1`.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
+'P2' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | P2             | SYS0105           | TS1
+ SALES      | P2             | SYS0106           | TS1
+ SALES      | P2             | SYS0107           | TS1
+ SALES      | P2             | SYS0108           | TS1
+ SALES      | P2             | SYS0109           | TS1
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/07_example_partition_by_range_subpartition_by_list.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/07_example_partition_by_range_subpartition_by_list.mdx
new file mode 100644
index 00000000000..cc897341c92
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/07_example_partition_by_range_subpartition_by_list.mdx
@@ -0,0 +1,82 @@
+---
+title: "Example: PARTITION BY RANGE, SUBPARTITION BY LIST"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/07_example_partition_by_range_subpartition_by_list/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_by_range_subpartition_by_list" class="registered_link"></div>
+
+This example creates a partitioned table `sales` that's first partitioned by the transaction date. The range partitions `q1_2012`, `q2_2012`, `q3_2012` and `q4_2012` are then list subpartitioned using the value of the `country` column.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST(country)
+  (
+    PARTITION q1_2012
+      VALUES LESS THAN('2012-Apr-01')
+      (
+        SUBPARTITION q1_europe VALUES ('FRANCE', 'ITALY'),
+        SUBPARTITION q1_asia VALUES ('INDIA', 'PAKISTAN'),
+        SUBPARTITION q1_americas VALUES ('US', 'CANADA')
+      ),
+  PARTITION q2_2012
+    VALUES LESS THAN('2012-Jul-01')
+      (
+        SUBPARTITION q2_europe VALUES ('FRANCE', 'ITALY'),
+        SUBPARTITION q2_asia VALUES ('INDIA', 'PAKISTAN'),
+        SUBPARTITION q2_americas VALUES ('US', 'CANADA')
+      ),
+  PARTITION q3_2012
+    VALUES LESS THAN('2012-Oct-01')
+      (
+        SUBPARTITION q3_europe VALUES ('FRANCE', 'ITALY'),
+        SUBPARTITION q3_asia VALUES ('INDIA', 'PAKISTAN'),
+        SUBPARTITION q3_americas VALUES ('US', 'CANADA')
+      ),
+  PARTITION q4_2012
+    VALUES LESS THAN('2013-Jan-01')
+      (
+        SUBPARTITION q4_europe VALUES ('FRANCE', 'ITALY'),
+        SUBPARTITION q4_asia VALUES ('INDIA', 'PAKISTAN'),
+        SUBPARTITION q4_americas VALUES ('US', 'CANADA')
+      )
+);
+```
+
+This statement creates a table with four partitions. Each partition has three subpartitions.
+
+```sql
+edb=# SELECT subpartition_name, high_value, partition_name FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value      | partition_name
+-------------------+---------------------+----------------
+ Q1_EUROPE         | 'FRANCE', 'ITALY'   | Q1_2012
+ Q1_ASIA           | 'INDIA', 'PAKISTAN' | Q1_2012
+ Q1_AMERICAS       | 'US', 'CANADA'      | Q1_2012
+ Q2_EUROPE         | 'FRANCE', 'ITALY'   | Q2_2012
+ Q2_ASIA           | 'INDIA', 'PAKISTAN' | Q2_2012
+ Q2_AMERICAS       | 'US', 'CANADA'      | Q2_2012
+ Q3_EUROPE         | 'FRANCE', 'ITALY'   | Q3_2012
+ Q3_ASIA           | 'INDIA', 'PAKISTAN' | Q3_2012
+ Q3_AMERICAS       | 'US', 'CANADA'      | Q3_2012
+ Q4_EUROPE         | 'FRANCE', 'ITALY'   | Q4_2012
+ Q4_ASIA           | 'INDIA', 'PAKISTAN' | Q4_2012
+ Q4_AMERICAS       | 'US', 'CANADA'      | Q4_2012
+(12 rows)
+```
+
+When a row is added to this table, the value in the `date` column is compared to the values specified in the range-partitioning rules. The server selects the partition for the row to reside in. The value in the `country` column is then compared to the values specified in the list subpartitioning rules. When the server locates a match for the value, the row is stored in the corresponding subpartition.
+
+Any row added to the table is stored in a subpartition, so the partitions contain no data.
+
+The server evaluates the following statement against the partitioning and subpartitioning rules. It stores the row in the `q3_europe` partition.
+
+`INSERT INTO sales VALUES (10, '9519a', 'FRANCE', '18-Aug-2012', '650000');`
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/08_example_creating_unique_index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/08_example_creating_unique_index.mdx
new file mode 100644
index 00000000000..d9944f6f480
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/08_example_creating_unique_index.mdx
@@ -0,0 +1,82 @@
+---
+title: "Example: CREATING UNIQUE INDEX on PARTITION TABLE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/08_example_creating_unique_index/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_partition_by_range_subpartition_by_list" class="registered_link"></div>
+
+For unique-index partitioned tables, you can use the range, list, or hash-partitioning method. To create a unique `ROWID` for the partitioned table, you must set the parameter `default_with_rowids = true`.
+
+This example creates a partitioned table `sales` using the `PARTITION BY LIST` clause. The `sales` table stores information in three partitions: `europe`, `asia`, and `americas`.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA') 
+) 
+WITH(ROWIDS=TRUE);
+```
+
+The table is partitioned by the value specified in the `country` column:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value      
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
+
+Insert values into the `sales` table:
+
+```sql
+INSERT INTO sales VALUES (10, '9519a', 'FRANCE', '18-Aug-2012', '650000');
+INSERT INTO sales VALUES (10, '9519b', 'ITALY', '20-Aug-2012', '700000');
+```
+
+This query shows that a unique index is created for the `sales` table:
+
+```sql
+edb=# SELECT oid, relname, relhasindex from pg_class where relname='sales';
+__OUTPUT__
+  oid  | relname | relhasindex 
+-------+---------+-------------
+ 16557 | sales   | f
+(1 row)
+```
+
+Querying the contents of the `sales_europe` confirms that the unique index is created for the table:
+
+```sql
+edb=# SELECT oid, relname, relhasindex from pg_class where relname='sales_europe';
+__OUTPUT__
+  oid  |   relname    | relhasindex 
+-------+--------------+-------------
+ 16561 | sales_europe | t
+(1 row)
+```
+```sql
+edb=# SELECT * from pg_index where indrelid='16561';
+__OUTPUT__
+ indexrelid | indrelid | indnatts | indnkeyatts | indisunique | indisprimary | indisexclusion | indimmediate | indisclustered | indisvalid | indcheckxmin | indisready | indislive | indisreplident |
+ indkey | indcollation | indclass | indoption | indexprs | indpred 
+------------+----------+----------+-------------+-------------+--------------+----------------+--------------+----------------+------------+--------------+------------+-----------+----------------+
+--------+--------------+----------+-----------+----------+---------
+      16565 |    16561 |        1 |           1 | t           | f            | f              | t            | f              | t          | f            | t          | t         | f              |
+ 1      | 0            | 3124     | 0         |          | 
+(1 row)
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/09_example_subpartition_template.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/09_example_subpartition_template.mdx
new file mode 100644
index 00000000000..a574b58f6b7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/09_example_subpartition_template.mdx
@@ -0,0 +1,190 @@
+---
+title: "Example: CREATING SUBPARTITION TEMPLATE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/09_example_subpartition_template/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_subpartition_template" class="registered_link"></div>
+
+These examples show how to create subpartitions in a partitioned table using a subpartition template.
+
+This example creates a table `sales` list partitioned by `country` and subpartitioned using list by `date`. The `sales` table uses a subpartition template and displays the subpartition and tablespace name. 
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) 
+  SUBPARTITION BY LIST (date)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe VALUES('2021-Jan-01') TABLESPACE ts1,
+    SUBPARTITION asia VALUES('2021-Apr-01') TABLESPACE ts2,
+    SUBPARTITION americas VALUES('2021-Jul-01') TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES('2021-Jul-01')
+); 
+```   
+
+The `SELECT` statement shows partition `q1_2021` consisting of three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(3 rows)
+```
+
+## Example: Creating a subpartition template for LIST/RANGE partitioned table
+
+This example creates a table `sales` list partitioned by `country` and subpartitioned using range partitioning by the `date` column: 
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY RANGE(date)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe VALUES LESS THAN('2021-Jan-01') TABLESPACE ts1,
+    SUBPARTITION asia VALUES LESS THAN('2021-Apr-01') TABLESPACE ts2,
+    SUBPARTITION americas VALUES LESS THAN('2021-Jul-01') TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES ('2021-Jul-01')
+); 
+```     
+
+The `sales` table creates a partition named `q1_2021` that includes three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(3 rows)
+```
+
+## Example: Creating a subpartition template for LIST/HASH partitioned table
+
+This example creates a list-partitioned table `sales` that's first partitioned by `country` and then hash subpartitioned using the value of the `dept_no` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY HASH (dept_no)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe TABLESPACE ts1,
+    SUBPARTITION asia TABLESPACE ts2,
+    SUBPARTITION americas TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES ('2021-Jul-01')
+); 
+```  
+
+The `sales` table creates a `q1_2021` partition that includes three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`. 
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name | high_value | tablespace_name 
+----------------+-------------------+------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  |            | TS3
+ Q1_2021        | Q1_2021_ASIA      |            | TS2
+ Q1_2021        | Q1_2021_EUROPE    |            | TS1
+(3 rows)
+```
+
+## Example: Creating a subpartition template for INTERVAL/HASH partitioned table
+
+This example creates a `sales` table, interval partitioned using monthly intervals on the `date` column and hash subpartitioned using the value of the `dept_no` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date) INTERVAL(NUMTOYMINTERVAL(1, 'MONTH'))
+  SUBPARTITION BY HASH (dept_no)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe TABLESPACE ts1,
+    SUBPARTITION asia TABLESPACE ts2,
+    SUBPARTITION americas TABLESPACE ts3
+)
+( 
+    PARTITION q2_2021 VALUES LESS THAN ('2021-Jul-01')
+); 
+```  
+
+The `sales` table creates a partition `q2_2021` consisting of three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`: 
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name | high_value | tablespace_name 
+----------------+-------------------+------------+-----------------
+ Q2_2021        | Q2_2021_AMERICAS  |            | TS3
+ Q2_2021        | Q2_2021_ASIA      |            | TS2
+ Q2_2021        | Q2_2021_EUROPE    |            | TS1
+(3 rows)
+```
+
+Insert values into the `sales` table:
+
+```sql
+INSERT INTO sales VALUES (10, '9519a', 'FRANCE', '05-Jul-2021', '650000');
+```
+
+The `SELECT` statement shows a system-generated name of partitions and subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`. 
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name | high_value | tablespace_name 
+----------------+-------------------+------------+-----------------
+ Q2_2021        | Q2_2021_AMERICAS  |            | TS3
+ Q2_2021        | Q2_2021_ASIA      |            | TS2
+ Q2_2021        | Q2_2021_EUROPE    |            | TS1
+ SYS368340105   | SYS368340106      |            | TS1
+ SYS368340105   | SYS368340107      |            | TS2
+ SYS368340105   | SYS368340108      |            | TS3
+(6 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/index.mdx
new file mode 100644
index 00000000000..7ed3023a36f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/index.mdx
@@ -0,0 +1,234 @@
+---
+title: "CREATE TABLE...PARTITION BY"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_table_partition_by" class="registered_link"></div>
+
+Use the `PARTITION BY` clause of the `CREATE TABLE` command to create a partitioned table with data distributed among one or more partitions and subpartitions. The syntax can take several forms.
+
+## List partitioning syntax
+
+Use this form to create a list-partitioned table:
+
+```sql
+CREATE TABLE [ schema. ]<table_name> 
+   <table_definition>
+   PARTITION BY LIST(<column>) [ AUTOMATIC ]
+   [SUBPARTITION BY {RANGE|LIST|HASH} (<column>[, <column> ]...) 
+   [SUBPARTITION TEMPLATE (<subpartition_template_description>)]]
+   (<list_partition_definition>[, <list_partition_definition>]...)
+   [ENABLE ROW MOVEMENT];
+
+Where `list_partition_definition` is:
+
+      PARTITION [<partition_name>]
+        VALUES (<value>[, <value>]...)
+        [TABLESPACE <tablespace_name>]
+        [(<subpartition>, ...)]
+
+Where `subpartition_template_description` is:
+
+      SUBPARTITION [<subpartition_name>] 
+        VALUES (<value>[, <value>]...) 
+        [TABLESPACE <tablespace_name>], ...
+```
+
+## Range partitioning syntax
+
+Use this form to create a range-partitioned table:
+
+```sql
+CREATE TABLE [ schema. ]<table_name>
+   <table_definition>
+   PARTITION BY RANGE(<column>[, <column> ]...)
+   [INTERVAL (<constant> | <expression>)]
+   [SUBPARTITION BY {RANGE|LIST|HASH} (<column>[, <column> ]...) 
+   [SUBPARTITION TEMPLATE (<subpartition_template_description>)]]
+   (<range_partition_definition>[, <range_partition_definition>]...)
+   [ENABLE ROW MOVEMENT];
+
+Where `range_partition_definition` is:
+
+      PARTITION [<partition_name>]
+        VALUES LESS THAN (<value>[, <value>]...)
+        [TABLESPACE <tablespace_name>]
+        [(<subpartition>, ...)]
+
+Where `subpartition_template_description` is:
+
+      SUBPARTITION [<subpartition_name>] 
+        VALUES LESS THAN (<value>[, <value>]...)
+        [TABLESPACE <tablespace_name>], ...
+```
+
+## Hash partitioning syntax
+
+Use this form to create a hash-partitioned table:
+
+```sql
+CREATE TABLE [ schema. ]<table_name>
+   <table_definition>
+   PARTITION BY HASH(<column>[, <column> ]...)
+   [SUBPARTITION BY {RANGE|LIST|HASH} (<column>[, <column> ]...) 
+   [SUBPARTITION TEMPLATE (<subpartition_template_description>)]]
+   [SUBPARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ]]
+   [PARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ] |
+   (<hash_partition_definition>[, <hash_partition_definition>]...)
+   [ENABLE ROW MOVEMENT];
+
+Where `hash_partition_definition` is:
+
+      PARTITION [<partition_name>]
+        [TABLESPACE <tablespace_name>]
+        [(<subpartition>, ...)]
+
+Where `subpartition_template_description` is:
+
+      SUBPARTITION [<subpartition_name>] 
+        [TABLESPACE <tablespace_name>], ...
+```
+
+## Subpartitioning syntax
+
+`subpartition` can be one of the following:
+
+```sql
+{<list_subpartition> | <range_subpartition> | <hash_subpartition>}
+
+Where `list_subpartition` is:
+
+      SUBPARTITION [<subpartition_name>]
+        VALUES (<value>[, <value>]...)
+        [TABLESPACE <tablespace_name>]
+
+Where `range_subpartition` is:
+
+      SUBPARTITION [<subpartition_name>]
+        VALUES LESS THAN (<value>[, <value>]...)
+        [TABLESPACE <tablespace_name>]
+
+Where `hash_subpartition` is:
+
+      SUBPARTITION [<subpartition_name>]
+        [TABLESPACE <tablespace_name>] |
+      SUBPARTITIONS <num> [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ]
+```
+
+## Description
+
+The `CREATE TABLE… PARTITION BY` command creates a table with one or more partitions. Each partition can have one or more subpartitions. There's no upper limit to the number of defined partitions. However, if you include the `PARTITION BY` clause, you must specify at least one partitioning rule. The resulting table is owned by the user that creates it.
+
+### `PARTITION BY LIST` clause
+
+Use the `PARTITION BY LIST` clause to divide a table into partitions based on the values entered in a specified column. Each partitioning rule must specify at least one literal value. However, there's no upper limit placed on the number of values you can specify. Include a rule that specifies a matching value of `DEFAULT` to direct any unqualified rows to the given partition. 
+
+For more information about using the `DEFAULT` keyword, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+### `AUTOMATIC` clause
+
+Use the `AUTOMATIC` clause to specify for the table to use automatic list partitioning. By specifying the `AUTOMATIC` clause, the database creates partitions when new data is inserted into a table that doesn't correspond to any value declared for an existing partition.
+
+For more information about `AUTOMATIC LIST PARTITIONING`, see [Automatic list partitioning](../../../../application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/02_automatic_list_partitioning/#automatic_list_partitioning).
+
+### `PARTITION BY RANGE` clause
+
+Use the `PARTITION BY RANGE` clause to specify boundary rules by which to create partitions. Each partitioning rule must contain at least one column of a data type that has two operators (that is, a greater-than or equal-to operator, and a less-than operator). Range boundaries are evaluated against a `LESS THAN` clause and are non-inclusive. For example, a date boundary of January 1, 2013 includes only date values that fall on or before December 31, 2012.
+
+Specify range partition rules in ascending order. `INSERT` commands that store rows with values that exceed the top boundary of a range-partitioned table fail unless the partitioning rules include a boundary rule that specifies a value of `MAXVALUE`. If you don't include a `MAXVALUE` partitioning rule, any row that exceeds the maximum limit specified by the boundary rules results in an error.
+
+For more information about using the `MAXVALUE` keyword, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+### `INTERVAL` clause
+
+Use the `INTERVAL` clause to specify an interval range-partitioned table. With an `INTERVAL` clause, the database extends the range partitioning to create partitions of a specified interval when data is inserted into a table that exceeds an existing range partition.
+
+For more information about `INTERVAL RANGE PARTITION`, see [Interval range partitioning](../../../../application_programming/epas_compat_table_partitioning/02_selecting_a_partition_type/01_interval_range_partitioning/#interval_range_partitioning).
+
+### `PARTITION BY HASH` clause
+
+Use the `PARTITION BY HASH` clause to create a hash-partitioned table. In a `HASH` partitioned table, data is divided among equal-sized partitions based on the hash value of the column specified in the partitioning syntax. When specifying a `HASH` partition, choose a column or combination of columns that's as close to unique as possible. This technique helps to ensure that data is evenly distributed among the partitions. When selecting a partitioning column (or combination of columns), for best performance, select columns that you frequently search for exact matches.
+
+### `STORE IN` clause
+
+Use the `STORE IN` clause to specify the tablespace list across which the autogenerated partitions or subpartitions are stored.
+
+!!! Note
+    If you're upgrading EDB Postgres Advanced Server, you must rebuild the hash-partitioned table on the upgraded version server.
+
+### `TABLESPACE` keyword
+
+Use the `TABLESPACE` keyword to specify the name of a tablespace on which a partition or subpartition resides. if you don't specify a tablespace, the partition or subpartition resides in the default tablespace.
+
+### `SUBPARTITION BY` clause
+
+If a table definition includes the `SUBPARTITION BY` clause, each partition in that table must have at least one subpartition. You can explicitly define each subpartition, or it can be system defined.
+
+If the subpartition is system defined, the server-generated subpartition resides in the default tablespace, and the name of the subpartition is assigned by the server. The server creates:
+
+-   A `DEFAULT` subpartition if the `SUBPARTITION BY` clause specifies `LIST`.
+-   A `MAXVALUE` subpartition if the `SUBPARTITION BY` clause specifies `RANGE`.
+
+The server generates a subpartition name that's a combination of the partition table name and a unique identifier. You can query the `ALL_TAB_SUBPARTITIONS` table to review a complete list of subpartition names.
+
+### `SUBPARTITION TEMPLATE`
+
+Use `ENABLE ROW MOVEMENT` with a list, range, or hash partition table to support migrating tables with similar syntax from Oracle databases. However, it doesn't enable the actual row movement. This syntax isn't supported with the `ALTER TABLE` command.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the table to create.
+
+`table_definition`
+
+ The column names, data types, and constraint information as described in the PostgreSQL core documentation for the [`CREATE TABLE` statement](https://www.postgresql.org/docs/current/static/sql-createtable.html).
+
+`partition_name`
+
+ The name of the partition to create. Partition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+`subpartition_name`
+
+ The name of the subpartition to create. Subpartition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+`num`
+
+ You can use the `PARTITIONS num` clause to specify the number of `HASH` partitions to create. Alternatively, you can use the partition definition to specify individual partitions and their tablespaces.
+
+ !!! Note
+  You can use either `PARTITIONS` or `PARTITION DEFINITION` when creating a table.
+
+ The `SUBPARTITIONS num` clause is supported only for `HASH` partitions. You can use it to specify the number of hash subpartitions to create. Alternatively, you can use the subpartition definition to specify individual subpartitions and their tablespaces. If you don't specify `SUBPARTITIONS` or `SUBPARTITION DEFINITION`, then the partition creates a subpartition based on the `SUBPARTITION TEMPLATE`.
+
+`subpartition_template_description`
+
+ The list of subpartition details with subpartition name, subpartition bound, and tablespace name.
+
+`column`
+
+ The name of a column on which the partitioning rules are based. Each row is stored in a partition that corresponds to the `value` of the specified columns.
+
+`constant | expression`
+
+ The `constant` and `expression` specifies a `NUMERIC`, `DATE`, or `TIME` value.
+
+`(value[, value]...)`
+
+ Use `value` to specify a quoted literal value or comma-delimited list of literal values by which table entries are grouped into partitions. Each partitioning rule must specify at least one value. However, there's no limit on the number of values specified in a rule. `value` can be `NULL`, `DEFAULT` if specifying a `LIST` partition, or `MAXVALUE` if specifying a `RANGE` partition.
+
+When specifying rules for a list-partitioned table, include the `DEFAULT` keyword in the last partition rule to direct any unmatched rows to the given partition. If you don't include a rule that includes a value of `DEFAULT`, any `INSERT` statement that attempts to add a row that doesn't match the specified rules of at least one partition fails and returns an error.
+
+When specifying rules for a list-partitioned table, include the `MAXVALUE` keyword in the last partition rule to direct any uncategorized rows to the given partition. If you don't include a `MAXVALUE` partition, any `INSERT` statement that attempts to add a row where the partitioning key is greater than the highest value specified fails and returns an error.
+
+`tablespace_name`
+
+ The name of the tablespace in which the partition or subpartition resides.
+
+<div class="toctree" maxdepth="3">
+
+example_partition_by_list example_automatic_list_partition example_partition_by_range example_interval_range_partition example_partition_by_hash example_partitions_number example_partition_by_range_subpartition_by_list example_creating_unique_index example_subpartition_template
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/01_example_adding_a_partition_to_a_list_partitioned_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/01_example_adding_a_partition_to_a_list_partitioned_table.mdx
new file mode 100644
index 00000000000..83fbd933eae
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/01_example_adding_a_partition_to_a_list_partitioned_table.mdx
@@ -0,0 +1,60 @@
+---
+title: "Example: Adding a partition to a LIST partitioned table"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/01_example_adding_a_partition_to_a_list_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_adding_a_partition_to_a_list_partitioned_table" class="registered_link"></div>
+
+This example adds a partition to the list-partitioned `sales` table. The table was created using the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The table contains the three partitions `americas`, `asia`, and `europe`:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
+
+This command adds a partition named `east_asia` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION east_asia
+  VALUES ('CHINA', 'KOREA');
+```
+
+After the command is invoked, the table includes the `east_asia` partition:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+ EAST_ASIA      | 'CHINA', 'KOREA'
+(4 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/02_example_adding_a_partition_to_a_range_partitioned_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/02_example_adding_a_partition_to_a_range_partitioned_table.mdx
new file mode 100644
index 00000000000..1440977077f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/02_example_adding_a_partition_to_a_range_partitioned_table.mdx
@@ -0,0 +1,67 @@
+---
+title: "Example - Adding a partition to a RANGE partitioned table"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/02_example_adding_a_partition_to_a_range_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_adding_a_partition_to_a_range_partitioned_table" class="registered_link"></div>
+
+This example adds a partition to a range-partitioned table named `sales`:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+(
+  PARTITION q1_2012
+    VALUES LESS THAN('2012-Apr-01'),
+  PARTITION q2_2012
+    VALUES LESS THAN('2012-Jul-01'),
+  PARTITION q3_2012
+    VALUES LESS THAN('2012-Oct-01'),
+  PARTITION q4_2012
+    VALUES LESS THAN('2013-Jan-01')
+);
+```
+
+The table contains the four partitions `q1_2012`, `q2_2012`, `q3_2012`, and `q4_2012`:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ Q1_2012        | '01-APR-12 00:00:00'
+ Q2_2012        | '01-JUL-12 00:00:00'
+ Q3_2012        | '01-OCT-12 00:00:00'
+ Q4_2012        | '01-JAN-13 00:00:00'
+(4 rows)
+```
+
+This command adds a partition named `q1_2013` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q1_2013
+  VALUES LESS THAN('01-APR-2013');
+```
+
+After the command is invoked, the table includes the `q1_2013` partition:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ Q1_2012        | '01-APR-12 00:00:00'
+ Q2_2012        | '01-JUL-12 00:00:00'
+ Q3_2012        | '01-OCT-12 00:00:00'
+ Q4_2012        | '01-JAN-13 00:00:00'
+ Q1_2013        | '01-APR-13 00:00:00'
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/03_example_adding_a_partition_with_subpartitions_number.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/03_example_adding_a_partition_with_subpartitions_number.mdx
new file mode 100644
index 00000000000..d0a84327565
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/03_example_adding_a_partition_with_subpartitions_number.mdx
@@ -0,0 +1,190 @@
+---
+title: "Example: Adding a partition with SUBPARTITIONS num...IN PARTITION DESCRIPTION"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/03_example_adding_a_partition_with_subpartitions_number/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_adding_a_partition_with_subpartitions_number" class="registered_link"></div>
+
+This example adds a partition to a list-partitioned `sales` table. You can specify a `SUBPARTITIONS` clause to add a specified number of subpartitions. The `sales` table was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 2
+(
+  PARTITION europe VALUES ('FRANCE', 'ITALY'),
+  PARTITION asia  VALUES ('INDIA', 'PAKISTAN')
+);
+```
+
+The table contains two partitions: `europe` and `asia`. Each contains two subpartitions. Because the subpartitions aren't named, system-generated names are assigned to them.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | ASIA           | SYS0103
+ SALES      | ASIA           | SYS0104
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0102
+(4 rows)
+```
+
+This command adds a partition `americas` to the `sales` table and creates a number of subpartitions as specified in the partition description:
+
+```sql
+ALTER TABLE sales ADD PARTITION americas
+  VALUES ('US', 'CANADA');
+```
+
+After invoking the command, the table includes the partition `americas` and two newly added subpartitions:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0107
+ SALES      | AMERICAS       | SYS0108
+ SALES      | ASIA           | SYS0103
+ SALES      | ASIA           | SYS0104
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0102
+(6 rows)
+```
+
+## Example - Adding a Partition with SUBPARTITIONS num...
+
+This example adds a partition a list-partitioned table `sales` consisting of three subpartitions. The `sales` table was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
+(
+  PARTITION europe VALUES ('FRANCE', 'ITALY'),
+  PARTITION asia  VALUES ('INDIA', 'PAKISTAN')
+);
+```
+
+The table contains partitions `europe` and `asia`, each containing three subpartitions:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | ASIA           | SYS0104
+ SALES      | ASIA           | SYS0105
+ SALES      | ASIA           | SYS0106
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0102
+ SALES      | EUROPE         | SYS0103
+(6 rows)
+```
+
+This command adds a partition `americas` and five subpartitions, as specified in the `ADD PARTITION` clause:
+
+```sql
+ALTER TABLE sales ADD PARTITION americas
+  VALUES ('US', 'CANADA') SUBPARTITIONS 5;
+```
+
+After the command is invoked, the `sales` table includes the partition `americas` and five newly added subpartitions:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
+'AMERICAS' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0109
+ SALES      | AMERICAS       | SYS0110
+ SALES      | AMERICAS       | SYS0111
+ SALES      | AMERICAS       | SYS0112
+ SALES      | AMERICAS       | SYS0113
+(5 rows)
+```
+
+## Example: Adding a partition with SUBPARTITIONS num... STORE IN
+
+This example adds a partition to a list-partitioned table `sales` consisting of three subpartitions. The table was created using the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The table contains the three partitions `americas`, `asia`, and `europe`. Each contains three subpartitions with system-generated names:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0109
+ SALES      | AMERICAS       | SYS0107
+ SALES      | AMERICAS       | SYS0108
+ SALES      | ASIA           | SYS0105
+ SALES      | ASIA           | SYS0104
+ SALES      | ASIA           | SYS0106
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0103
+ SALES      | EUROPE         | SYS0102
+(9 rows)
+```
+
+This command adds a partition `east_asia` with five subpartitions as specified in the `ADD PARTITION` clause. It stores them in the tablespace named `ts1`.
+
+```sql
+ALTER TABLE sales ADD PARTITION east_asia
+  VALUES ('CHINA', 'KOREA') SUBPARTITIONS 5 STORE IN (ts1);
+```
+
+After the command is invoked, the table includes the partition `east_asia` and five newly added subpartitions stored in tablespace `ts1`:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
+'EAST_ASIA' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | EAST_ASIA      | SYS0113           | TS1
+ SALES      | EAST_ASIA      | SYS0114           | TS1
+ SALES      | EAST_ASIA      | SYS0115           | TS1
+ SALES      | EAST_ASIA      | SYS0116           | TS1
+ SALES      | EAST_ASIA      | SYS0117           | TS1
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/index.mdx
new file mode 100644
index 00000000000..b5444c4099f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/index.mdx
@@ -0,0 +1,114 @@
+---
+title: "ALTER TABLE...ADD PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.105.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.330.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.054.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/02_alter_table_add_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_add_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… ADD PARTITION` command to add a partition to an existing partitioned table. The syntax is:
+
+```sql
+ALTER TABLE <table_name> ADD PARTITION <partition_definition>;
+
+Where partition_definition is:
+
+        {<list_partition> | <range_partition>}
+
+and list_partition is:
+
+        PARTITION [<partition_name>]
+          VALUES (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+          [(<subpartition>, ...)]
+
+and range_partition is:
+
+        PARTITION [<partition_name>]
+          VALUES LESS THAN (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+          [(<subpartition>, ...)]
+
+Where subpartition is:
+
+        {<list_subpartition> | <range_subpartition> | <hash_subpartition>}
+
+and list_subpartition is:
+
+        SUBPARTITION [<subpartition_name>]
+          VALUES (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+
+and range_subpartition is:
+
+        SUBPARTITION [<subpartition_name>]
+          VALUES LESS THAN (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+
+and hash_subpartition is:
+
+        SUBPARTITION [<subpartition_name>]
+          [TABLESPACE <tablespace_name>] |
+        SUBPARTITIONS <num> [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ]
+```
+
+## Description
+
+The `ALTER TABLE… ADD PARTITION` command adds a partition to an existing partitioned table. There's no upper limit to the number of defined partitions in a partitioned table.
+
+New partitions must be of the same type (`LIST`, `RANGE`, or `HASH`) as existing partitions. The new partition rules must reference the same column specified in the partitioning rules that define the existing partitions.
+
+You can use the `ALTER TABLE… ADD PARTITION` statement to add a partition to a table with a `DEFAULT` rule. However, there can't be conflicting values between existing rows in the table and the values of the partition to add.
+
+You can't use the `ALTER TABLE… ADD PARTITION` statement to add a partition to a table with a `MAXVALUE` rule.
+
+You can alternatively use the `ALTER TABLE… SPLIT PARTITION` statement to split an existing partition, effectively increasing the number of partitions in a table.
+
+Specify `RANGE` partitions in ascending order. You can't add a new partition that precedes existing partitions in a `RANGE` partitioned table.
+
+Include the `TABLESPACE` clause to specify the tablespace in which the new partition resides. If you don't specify a tablespace, the partition resides in the default tablespace.
+
+Use the `STORE IN` clause to specify the tablespace list across which the autogenerated subpartitions are stored.
+
+If the table is indexed, the index is created on the new partition.
+
+To use the `ALTER TABLE... ADD PARTITION` command, you must be the table owner or have superuser or administrative privileges.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`partition_name`
+
+ The name of the partition to create. Partition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+`subpartition_name`
+
+ The name of the subpartition to create. Subpartition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+`(value[, value]...)`
+
+ Use `value` to specify a quoted literal value or comma-delimited list of literal values by which rows are distributed into partitions. Each partitioning rule must specify at least one `value`. There's no limit on the number of values specified in a rule. `value` can also be `NULL`, `DEFAULT` if specifying a `LIST` partition, or `MAXVALUE` if specifying a `RANGE` partition.
+
+ For information about creating a `DEFAULT` or `MAXVALUE` partition, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+`num`
+
+ The `SUBPARTITIONS num` clause is supported only for `HASH` and can be used to specify the number of hash subpartitions. Alternatively, you can use the subpartition definition to specify individual subpartitions and their tablespaces. If you don't specify `SUBPARTITIONS` or `SUBPARTITION DEFINITION`, then the partition creates a subpartition based on the `SUBPARTITION TEMPLATE`.
+
+`tablespace_name`
+
+ The name of the tablespace in which a partition or subpartition resides.
+
+<div class="toctree" maxdepth="3">
+
+example_adding_a_partition_to_a_list_partitioned_table example_adding_a_partition_to_a_range_partitioned_table example_adding_a_partition_with_subpartitions_number
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/01_example_adding_a_subpartition_to_a_list_range_partitioned_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/01_example_adding_a_subpartition_to_a_list_range_partitioned_table.mdx
new file mode 100644
index 00000000000..ce24231b504
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/01_example_adding_a_subpartition_to_a_list_range_partitioned_table.mdx
@@ -0,0 +1,89 @@
+---
+title: "Example: Adding a subpartition to a LIST/RANGE partitioned table"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/01_example_adding_a_subpartition_to_a_list_range_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_adding_a_subpartition_to_a_list_range_partitioned_table" class="registered_link"></div>
+
+This example adds a `RANGE` subpartition to the list-partitioned `sales` table. The `sales` table was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY RANGE(date)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY')
+    (
+      SUBPARTITION europe_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION europe_2012
+        VALUES LESS THAN('2013-Jan-01')
+    ),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN')
+    (
+      SUBPARTITION asia_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION asia_2012
+        VALUES LESS THAN('2013-Jan-01')
+    ),
+  PARTITION americas VALUES('US', 'CANADA')
+    (
+      SUBPARTITION americas_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION americas_2012
+        VALUES LESS THAN('2013-Jan-01')
+    )
+);
+```
+
+The `sales` table has three partitions named `europe`, `asia`, and `americas`. Each partition has two range-defined subpartitions.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value
+----------------+-------------------+----------------------
+ EUROPE         | EUROPE_2011       | '01-JAN-12 00:00:00'
+ EUROPE         | EUROPE_2012       | '01-JAN-13 00:00:00'
+ ASIA           | ASIA_2011         | '01-JAN-12 00:00:00'
+ ASIA           | ASIA_2012         | '01-JAN-13 00:00:00'
+ AMERICAS       | AMERICAS_2011     | '01-JAN-12 00:00:00'
+ AMERICAS       | AMERICAS_2012     | '01-JAN-13 00:00:00'
+(6 rows)
+```
+
+This command adds a subpartition named `europe_2013`:
+
+```sql
+ALTER TABLE sales MODIFY PARTITION europe
+  ADD SUBPARTITION europe_2013
+  VALUES LESS THAN('2015-Jan-01');
+```
+
+After the command is invoked, the table includes a subpartition named `europe_2013`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value
+----------------+-------------------+----------------------
+ EUROPE         | EUROPE_2011       | '01-JAN-12 00:00:00'
+ EUROPE         | EUROPE_2012       | '01-JAN-13 00:00:00'
+ EUROPE         | EUROPE_2013       | '01-JAN-15 00:00:00'
+ ASIA           | ASIA_2011         | '01-JAN-12 00:00:00'
+ ASIA           | ASIA_2012         | '01-JAN-13 00:00:00'
+ AMERICAS       | AMERICAS_2011     | '01-JAN-12 00:00:00'
+ AMERICAS       | AMERICAS_2012     | '01-JAN-13 00:00:00'
+(7 rows)
+```
+
+!!! Note
+    When adding a range subpartition, the subpartitioning rules must specify a range that falls after any existing subpartitions.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/02_example_adding_a_subpartition_to_a_range_list_partitioned_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/02_example_adding_a_subpartition_to_a_range_list_partitioned_table.mdx
new file mode 100644
index 00000000000..4961d291353
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/02_example_adding_a_subpartition_to_a_range_list_partitioned_table.mdx
@@ -0,0 +1,67 @@
+---
+title: "Example: Adding a subpartition to a RANGE/LIST partitioned table"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/02_example_adding_a_subpartition_to_a_range_list_partitioned_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_adding_a_subpartition_to_a_range_list_partitioned_table" class="registered_link"></div>
+
+This example adds a `LIST` subpartition to the `RANGE` partitioned `sales` table. The `sales` table was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST (country)
+  (
+    PARTITION first_half_2012 VALUES LESS THAN('01-JUL-2012')
+    (
+      SUBPARTITION europe VALUES ('ITALY', 'FRANCE'),
+      SUBPARTITION americas VALUES ('US', 'CANADA')
+    ),
+    PARTITION second_half_2012 VALUES LESS THAN('01-JAN-2013')
+    (
+      SUBPARTITION asia VALUES ('INDIA', 'PAKISTAN')
+    )
+);
+```
+
+After the command is invoked, the `sales` table has two partitions, named `first_half_2012` and `second_half_2012`. The `first_half_2012 partition` has two subpartitions, named `europe` and `americas`. The `second_half_2012` partition has one partition, named `asia`.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+  partition_name  | subpartition_name |     high_value
+------------------+-------------------+---------------------
+ SECOND_HALF_2012 | ASIA              | 'INDIA', 'PAKISTAN'
+ FIRST_HALF_2012  | AMERICAS          | 'US', 'CANADA'
+ FIRST_HALF_2012  | EUROPE            | 'ITALY', 'FRANCE'
+(3 rows)
+```
+
+This command adds a subpartition named `east_asia` to the `second_half_2012` partition:
+
+```sql
+ALTER TABLE sales MODIFY PARTITION second_half_2012
+  ADD SUBPARTITION east_asia VALUES ('CHINA');
+```
+
+After the command is invoked, the table includes a subpartition named `east_asia`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+  partition_name  | subpartition_name |     high_value
+------------------+-------------------+---------------------
+ SECOND_HALF_2012 | ASIA              | 'INDIA', 'PAKISTAN'
+ SECOND_HALF_2012 | EAST_ASIA         | 'CHINA'
+ FIRST_HALF_2012  | AMERICAS          | 'US', 'CANADA'
+ FIRST_HALF_2012  | EUROPE            | 'ITALY', 'FRANCE'
+(4 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/index.mdx
new file mode 100644
index 00000000000..bafd9325133
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/index.mdx
@@ -0,0 +1,85 @@
+---
+title: "ALTER TABLE...ADD SUBPARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.106.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.331.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.055.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/03_alter_table_add_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_add_subpartition" class="registered_link"></div>
+
+The `ALTER TABLE… ADD SUBPARTITION` command adds a subpartition to an existing subpartitioned partition. The syntax is:
+
+```sql
+ALTER TABLE <table_name> MODIFY PARTITION <partition_name>
+      ADD SUBPARTITION <subpartition_definition>;
+
+Where subpartition_definition is:
+
+{<list_subpartition> | <range_subpartition>}
+
+and list_subpartition is:
+
+        SUBPARTITION [<subpartition_name>]
+          VALUES (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+
+and range_subpartition is:
+
+        SUBPARTITION [<subpartition_name>]
+          VALUES LESS THAN (<value>[, <value>]...)
+          [TABLESPACE <tablespace_name>]
+```
+
+## Description
+
+The `ALTER TABLE… ADD SUBPARTITION` command adds a subpartition to an existing partition. The partition must already be subpartitioned. There's no upper limit to the number of defined subpartitions.
+
+New subpartitions must be of the same type (`LIST`, `RANGE` or `HASH`) as existing subpartitions. The new subpartition rules must reference the same column specified in the subpartitioning rules that define the existing subpartitions.
+
+You can use the `ALTER TABLE… ADD SUBPARTITION` statement to add a subpartition to a table with a `DEFAULT` rule. However, there must not be conflicting values between existing rows in the table and the values of the subpartition to add.
+
+You can't use the `ALTER TABLE… ADD SUBPARTITION` statement to add a subpartition to a table with a `MAXVALUE` rule.
+
+You can split an existing subpartition with the `ALTER TABLE… SPLIT SUBPARTITION` statement, effectively adding a subpartition to a table.
+
+You can't add a subpartition that precedes existing subpartitions in a range-subpartitioned table. You must specify range subpartitions in ascending order.
+
+Include the `TABLESPACE` clause to specify the tablespace in which the subpartition resides. If you don't specify a tablespace, the subpartition is created in the default tablespace.
+
+If the table is indexed, the index is created on the new subpartition.
+
+To use the `ALTER TABLE... ADD SUBPARTITION` command, you must be the table owner or have superuser or administrative privileges.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table in which the subpartition resides.
+
+`partition_name`
+
+ The name of the partition in which the new subpartition resides.
+
+`subpartition_name`
+
+ The name of the subpartition to create. Subpartition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+`(value[, value]...)`
+
+ Use `value` to specify a quoted literal value or comma-delimited list of literal values by which table entries are grouped into partitions. Each partitioning rule must specify at least one value. However, there's no limit on the number of values specified in a rule. `value` can also be `NULL`, `DEFAULT` if specifying a `LIST` partition, or `MAXVALUE` if specifying a `RANGE` partition.
+
+ For information about creating a `DEFAULT` or `MAXVALUE` partition, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+`tablespace_name`
+
+ The name of the tablespace in which the subpartition resides.
+
+<div class="toctree" maxdepth="3">
+
+example_adding_a_subpartition_to_a_list_range_partitioned_table example_adding_a_subpartition_to_a_range_list_partitioned_table
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/01_example_splitting_a_list_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/01_example_splitting_a_list_partition.mdx
new file mode 100644
index 00000000000..61615503cb8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/01_example_splitting_a_list_partition.mdx
@@ -0,0 +1,111 @@
+---
+title: "Example: Splitting a LIST partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/01_example_splitting_a_list_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_splitting_a_list_partition" class="registered_link"></div>
+
+This example divides one of the partitions in the list-partitioned `sales` table into two new partitions and redistributes the contents of the partition between them. The `sales` table is created with the statement:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The table definition creates three partitions: `europe`, `asia`, and `americas`. This command adds rows to each partition:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+The rows are distributed among the partitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_americas |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_americas |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_americas |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_americas |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_americas |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_americas |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_americas |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+This command splits the `americas` partition into partitions named `us` and `canada`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION americas
+  VALUES ('US')
+  INTO (PARTITION us, PARTITION canada);
+```
+
+A `SELECT` statement confirms that the rows were redistributed:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid   | dept_no | part_no | country  |        date        | amount
+--------------+---------+---------+----------+--------------------+--------
+ sales_canada |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_canada |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_canada |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_europe |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia   |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia   |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia   |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia   |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia   |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+ sales_us     |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_us     |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_us     |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_us     |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_us     |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+(17 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/02_example_splitting_a_range_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/02_example_splitting_a_range_partition.mdx
new file mode 100644
index 00000000000..591b238cad1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/02_example_splitting_a_range_partition.mdx
@@ -0,0 +1,120 @@
+---
+title: "Example: Splitting a RANGE partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/02_example_splitting_a_range_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_splitting_a_range_partition" class="registered_link"></div>
+
+This example divides the `q4_2012` partition of the range-partitioned `sales` table into two partitions and redistributes the partition's contents. Use this command to create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+(
+  PARTITION q1_2012
+    VALUES LESS THAN('2012-Apr-01'),
+  PARTITION q2_2012
+    VALUES LESS THAN('2012-Jul-01'),
+  PARTITION q3_2012
+    VALUES LESS THAN('2012-Oct-01'),
+  PARTITION q4_2012
+    VALUES LESS THAN('2013-Jan-01')
+);
+```
+
+The table definition creates four partitions: `q1_2012`, `q2_2012`, `q3_2012`, and `q4_2012`). This command adds rows to each partition:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+A `SELECT` statement confirms that the rows are distributed among the partitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid    | dept_no | part_no | country  |        date        | amount
+---------------+---------+---------+----------+--------------------+--------
+ sales_q1_2012 |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_q1_2012 |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_q1_2012 |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_q2_2012 |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_q2_2012 |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_q2_2012 |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_q2_2012 |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_q3_2012 |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_q3_2012 |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_q3_2012 |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_q3_2012 |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_q3_2012 |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_q4_2012 |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_q4_2012 |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_q4_2012 |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |   15000
+ sales_q4_2012 |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_q4_2012 |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+This command splits the `q4_2012` partition into two partitions named `q4_2012_p1` and `q4_2012_p2`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION q4_2012
+  AT ('15-Nov-2012')
+  INTO
+  (
+    PARTITION q4_2012_p1,
+    PARTITION q4_2012_p2
+  );
+```
+
+A `SELECT` statement confirms that the rows were redistributed across the new partitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid      | dept_no | part_no | country  |        date        |amount
+-----------------+---------+---------+----------+--------------------+------
+ sales_q1_2012   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 | 45000
+ sales_q1_2012   |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 | 75000
+ sales_q1_2012   |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 | 75000
+ sales_q2_2012   |      40 | 9519b   | US       | 12-APR-12 00:00:00 |145000
+ sales_q2_2012   |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 | 37500
+ sales_q2_2012   |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 |120000
+ sales_q2_2012   |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |  4950
+ sales_q3_2012   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 | 15000
+ sales_q3_2012   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 |650000
+ sales_q3_2012   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 |650000
+ sales_q3_2012   |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |  5090
+ sales_q3_2012   |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |  4950
+ sales_q4_2012_p1|      40 | 4577b   | US       | 11-NOV-12 00:00:00 | 25000
+ sales_q4_2012_p1|      40 | 4788b   | US       | 09-OCT-12 00:00:00 | 15000
+ sales_q4_2012_p1|      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 |650000
+ sales_q4_2012_p2|      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 | 50000
+ sales_q4_2012_p2|      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |  5090
+(17 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/03_example_splitting_a_range_list_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/03_example_splitting_a_range_list_partition.mdx
new file mode 100644
index 00000000000..b94e097a479
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/03_example_splitting_a_range_list_partition.mdx
@@ -0,0 +1,228 @@
+---
+title: "Example: Splitting a RANGE/LIST partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/03_example_splitting_a_range_list_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_splitting_a_range_list_partition" class="registered_link"></div>
+
+This example divides one of the partitions in the range-partitioned `sales` table into new partitions. This approach maintains the partitioning of the original table in the newly created partitions and redistributes the contents of the partition between them.
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST (country)
+  (
+    PARTITION q1_2012 VALUES LESS THAN('2012-Apr-01')
+    (
+      SUBPARTITION europe VALUES('FRANCE', 'ITALY'),
+      SUBPARTITION americas VALUES('US', 'CANADA'),
+      SUBPARTITION asia VALUES('INDIA', 'PAKISTAN')
+    )
+  );
+```
+
+The `sales` table contains partition `q1_2012` and the three subpartitions `europe`, `americas`, and `asia`:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, high_value FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name |     high_value
+------------+----------------+-------------------+---------------------
+ SALES      | Q1_2012        | EUROPE            | 'FRANCE', 'ITALY'
+ SALES      | Q1_2012        | AMERICAS          | 'US', 'CANADA'
+ SALES      | Q1_2012        | ASIA              | 'INDIA', 'PAKISTAN'
+(3 rows)
+```
+
+This command splits the `q1_2012` partition into partitions named `q1_2012_p1` and `q1_2012_p2`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION q1_2012
+  AT ('01-Mar-2012')
+  INTO
+  (
+    PARTITION q1_2012_p1,
+    PARTITION q1_2012_p2
+  );
+```
+
+A `SELECT` statement confirms that the same number of subpartitions is created in the newly created partitions `q1_2012_p1` and `q1_2012_p2` with system-generated names:
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, high_value FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2,3;
+__OUTPUT__
+ table_name | partition_name | subpartition_name |     high_value
+------------+----------------+-------------------+---------------------
+ SALES      | Q1_2012_P1     | SYS0105           | 'US', 'CANADA'
+ SALES      | Q1_2012_P1     | SYS0106           | 'FRANCE', 'ITALY'
+ SALES      | Q1_2012_P1     | SYS0107           | 'INDIA', 'PAKISTAN'
+ SALES      | Q1_2012_P2     | SYS0108           | 'US', 'CANADA'
+ SALES      | Q1_2012_P2     | SYS0109           | 'FRANCE', 'ITALY'
+ SALES      | Q1_2012_P2     | SYS0110           | 'INDIA', 'PAKISTAN'
+(6 rows)
+```
+
+## Example: Splitting a partition with SUBPARTITIONS num...
+
+This example divides one of the partitions in the list-partitioned `sales` table into new partitions. It maintains the partitioning of the original table in the newly created partitions and redistributes the contents of the partition between them. The `SUBPARTITIONS` clause lets you add a specified number of subpartitions. Without the `SUBPARTITIONS` clause, the new partitions inherit the default number of subpartitions. 
+
+This statement creates the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 2
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The table definition creates the three partitions `europe`, `asia`, and `americas`. Each contains two subpartitions.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0105
+ SALES      | AMERICAS       | SYS0106
+ SALES      | ASIA           | SYS0103
+ SALES      | ASIA           | SYS0104
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0102
+(6 rows)
+```
+
+This command splits the `americas` partition into partitions named `partition_us` and `partition_canada`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION americas VALUES ('US') INTO (PARTITION
+partition_us SUBPARTITIONS 5, PARTITION partition_canada);
+```
+
+A `SELECT` statement confirms that the `americas` partition is split into `partition_us` and `partition_canada`. The `partition_us` contains five subpartitions. `partition_canada` contains two default subpartitions with system-generated names.
+
+```sql
+edb=#  SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2,3;
+__OUTPUT__
+ table_name |  partition_name  | subpartition_name
+------------+------------------+-------------------
+ SALES      | ASIA             | SYS0103
+ SALES      | ASIA             | SYS0104
+ SALES      | EUROPE           | SYS0101
+ SALES      | EUROPE           | SYS0102
+ SALES      | PARTITION_CANADA | SYS0115
+ SALES      | PARTITION_CANADA | SYS0116
+ SALES      | PARTITION_US     | SYS0110
+ SALES      | PARTITION_US     | SYS0111
+ SALES      | PARTITION_US     | SYS0112
+ SALES      | PARTITION_US     | SYS0113
+ SALES      | PARTITION_US     | SYS0114
+(11 rows)
+```
+
+## Example: Splitting a partition with SUBPARTITIONS num...STORE IN
+
+This example divides the `europe` partition of the list-partitioned `sales` table into two partitions. It maintains the partitioning of the original table in the newly created partitions and redistributes the partition's contents. The `SUBPARTITIONS` clause lets you add a specified number of subpartitions. 
+
+Use the following command to create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 4
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The `sales` table contains the partitions `europe`, `asia`, and `americas`. Each contains four subpartitions with system-generated names.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0112
+ SALES      | AMERICAS       | SYS0111
+ SALES      | AMERICAS       | SYS0109
+ SALES      | AMERICAS       | SYS0110
+ SALES      | ASIA           | SYS0107
+ SALES      | ASIA           | SYS0105
+ SALES      | ASIA           | SYS0106
+ SALES      | ASIA           | SYS0108
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0104
+ SALES      | EUROPE         | SYS0103
+ SALES      | EUROPE         | SYS0102
+(12 rows)
+```
+
+This command splits the `europe` partition into the partitions `france` and `italy`:
+
+```sql
+ALTER TABLE sales SPLIT PARTITION europe VALUES ('FRANCE') INTO (PARTITION
+france SUBPARTITIONS 10 STORE IN (ts1), PARTITION italy);
+```
+
+A `SELECT` statement confirms that the `europe` partition is split into two partitions. The partition `france` contains 10 subpartitions that are stored in the tablespace `ts1`. Partition `italy` contains four subpartitions as in the original partition `europe`.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name, tablespace_name
+FROM ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2,3;
+__OUTPUT__
+ table_name | partition_name | subpartition_name | tablespace_name
+------------+----------------+-------------------+-----------------
+ SALES      | AMERICAS       | SYS0109           |
+ SALES      | AMERICAS       | SYS0110           |
+ SALES      | AMERICAS       | SYS0111           |
+ SALES      | AMERICAS       | SYS0112           |
+ SALES      | ASIA           | SYS0105           |
+ SALES      | ASIA           | SYS0106           |
+ SALES      | ASIA           | SYS0107           |
+ SALES      | ASIA           | SYS0108           |
+ SALES      | FRANCE         | SYS0116           | TS1
+ SALES      | FRANCE         | SYS0117           | TS1
+ SALES      | FRANCE         | SYS0118           | TS1
+ SALES      | FRANCE         | SYS0119           | TS1
+ SALES      | FRANCE         | SYS0120           | TS1
+ SALES      | FRANCE         | SYS0121           | TS1
+ SALES      | FRANCE         | SYS0122           | TS1
+ SALES      | FRANCE         | SYS0123           | TS1
+ SALES      | FRANCE         | SYS0124           | TS1
+ SALES      | FRANCE         | SYS0125           | TS1
+ SALES      | ITALY          | SYS0126           |
+ SALES      | ITALY          | SYS0127           |
+ SALES      | ITALY          | SYS0128           |
+ SALES      | ITALY          | SYS0129           |
+(22 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/index.mdx
new file mode 100644
index 00000000000..aeb93fb494d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/index.mdx
@@ -0,0 +1,110 @@
+---
+title: "ALTER TABLE...SPLIT PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.107.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.332.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.056.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/04_alter_table_split_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_split_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… SPLIT PARTITION` command to divide a single partition into two partitions. This command maintains the partitioning of the original table in the newly created partitions and redistributes the partition's contents between the new partitions. The command syntax comes in two forms.
+
+The first form splits a `RANGE` partition into two partitions:
+
+```sql
+ALTER TABLE <table_name> SPLIT PARTITION <partition_name>
+  AT (<range_part_value>)
+  INTO
+  (
+    PARTITION <new_part1>
+     [TABLESPACE <tablespace_name>]
+     [SUBPARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ],
+    PARTITION <new_part2>
+     [TABLESPACE <tablespace_name>]
+     [SUBPARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ]
+  );
+```
+
+The second form splits a `LIST` partition into two partitions:
+
+```sql
+ALTER TABLE <table_name> SPLIT PARTITION <partition_name>
+  VALUES (<value>[, <value>]...)
+  INTO
+  (
+    PARTITION <new_part1>
+     [TABLESPACE <tablespace_name>]
+     [SUBPARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ],
+    PARTITION <new_part2>
+     [TABLESPACE <tablespace_name>]
+     [SUBPARTITIONS <num>] [STORE IN ( <tablespace_name> [, <tablespace_name>]... ) ]
+  );
+```
+
+## Description
+
+The `ALTER TABLE...SPLIT PARTITION` command adds a partition to an existing `LIST` or `RANGE` partitioned table. The `ALTER TABLE… SPLIT PARTITION` command can't add a partition to a `HASH` partitioned table. There's no upper limit to the number of partitions.
+
+When you execute an `ALTER TABLE...SPLIT PARTITION` command, EDB Postgres Advanced Server:
+
+-  Creates two new partitions
+-  Maintains the partitioning of the original table in the newly created partitions
+-  Redistributes the content of the old partition between them, as constrained by the partitioning rules
+
+Include the `TABLESPACE` clause to specify the tablespace in which a partition resides. If you don't specify a tablespace, the partition resides in the tablespace of the original partitioned table.
+
+Use the `STORE IN` clause to specify the tablespace list across which the autogenerated subpartitions are stored.
+
+If the table is indexed, the index is created on the new partition.
+
+To use the `ALTER TABLE... SPLIT PARTITION` command, you must be the table owner or have superuser or administrative privileges.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`partition_name`
+
+ The name of the partition that's being split.
+
+`new_part1`
+
+ The name of the first partition to create. Partition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+ `new_part1` receives the rows that meet the partitioning constraints specified in the `ALTER TABLE… SPLIT PARTITION` command.
+
+`new_part2`
+
+ The name of the second partition to create. Partition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+ `new_part2` receives the rows aren't directed to `new_part1` by the partitioning constraints specified in the `ALTER TABLE… SPLIT PARTITION` command.
+
+`range_part_value`
+
+ Use `range_part_value` to specify the boundary rules by which to create the new partition. The partitioning rule must contain at least one column of a data type that has two operators, that is, a greater-than-or-equal-to operator and a less-than operator. Range boundaries are evaluated against a `LESS THAN` clause and are non-inclusive. A date boundary of January 1, 2010 includes only those date values that fall on or before December 31, 2009.
+
+`(value[, value]...)`
+
+ Use `value` to specify a quoted literal value or comma-delimited list of literal values by which to distribute rows into partitions. Each partitioning rule must specify at least one value. There's no limit on the number of values specified in a rule.
+
+ For information about creating a `DEFAULT` or `MAXVALUE` partition, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+`num`
+
+ The `SUBPARTITIONS num` clause is supported only for `HASH` subpartitions. Use the clause to specify the number of hash subpartitions. Alternatively, you can use the subpartition definition to specify individual subpartitions and their tablespaces. If you don't specify `SUBPARTITIONS` or `SUBPARTITION DEFINITION`, then the partition creates a subpartition based on the `SUBPARTITION TEMPLATE`.
+
+`tablespace_name`
+
+ The name of the tablespace in which the partition or subpartition resides.
+
+<div class="toctree" maxdepth="3">
+
+example_splitting_a_list_partition example_splitting_a_range_partition example_splitting_a_range_list_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/01_example_splitting_a_list_subpartition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/01_example_splitting_a_list_subpartition.mdx
new file mode 100644
index 00000000000..70bcd852b4f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/01_example_splitting_a_list_subpartition.mdx
@@ -0,0 +1,139 @@
+---
+title: "Example: Splitting a lIST subpartition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/01_example_splitting_a_list_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_splitting_a_list_subpartition" class="registered_link"></div>
+
+This example splits a list subpartition, redistributing the subpartition's contents between two new subpartitions.
+
+The sample table `sales` was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST (country)
+  (
+    PARTITION first_half_2012 VALUES LESS THAN('01-JUL-2012')
+    (
+      SUBPARTITION p1_europe VALUES ('ITALY', 'FRANCE'),
+      SUBPARTITION p1_americas VALUES ('US', 'CANADA')
+    ),
+    PARTITION second_half_2012 VALUES LESS THAN('01-JAN-2013')
+    (
+      SUBPARTITION p2_europe VALUES ('ITALY', 'FRANCE'),
+      SUBPARTITION p2_americas VALUES ('US', 'CANADA')
+    )
+  );
+```
+
+The `sales` table has partitions named `first_half_2012` and `second_half_2012`. Each partition has two range-defined subpartitions that distribute the partition's contents into subpartitions based on the value of the `country` column.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+  partition_name  | subpartition_name |    high_value
+------------------+-------------------+-------------------
+ SECOND_HALF_2012 | P2_AMERICAS       | 'US', 'CANADA'
+ SECOND_HALF_2012 | P2_EUROPE         | 'ITALY', 'FRANCE'
+ FIRST_HALF_2012  | P1_AMERICAS       | 'US', 'CANADA'
+ FIRST_HALF_2012  | P1_EUROPE         | 'ITALY', 'FRANCE'
+(4 rows)
+```
+
+This command adds rows to each subpartition:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000');
+```
+
+A `SELECT` statement confirms that the rows are correctly distributed among the subpartitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid      | dept_no | part_no | country |        date        | amount
+-----------------+---------+---------+---------+--------------------+--------
+sales_p1_americas|      40 | 9519b   | US      | 12-APR-12 00:00:00 | 145000
+sales_p1_americas|      30 | 9519b   | CANADA  | 01-FEB-12 00:00:00 |  75000
+sales_p1_americas|      30 | 4519b   | CANADA  | 08-APR-12 00:00:00 | 120000
+sales_p1_americas|      40 | 3788a   | US      | 12-MAY-12 00:00:00 |   4950
+sales_p1_europe  |      10 | 4519b   | FRANCE  | 17-JAN-12 00:00:00 |  45000
+sales_p2_americas|      40 | 4577b   | US      | 11-NOV-12 00:00:00 |  25000
+sales_p2_americas|      30 | 7588b   | CANADA  | 14-DEC-12 00:00:00 |  50000
+sales_p2_americas|      40 | 4788a   | US      | 23-SEP-12 00:00:00 |   4950
+sales_p2_americas|      40 | 4788b   | US      | 09-OCT-12 00:00:00 |  15000
+sales_p2_europe  |      10 | 9519b   | ITALY   | 07-JUL-12 00:00:00 |  15000
+sales_p2_europe  |      10 | 9519a   | FRANCE  | 18-AUG-12 00:00:00 | 650000
+sales_p2_europe  |      10 | 9519b   | FRANCE  | 18-AUG-12 00:00:00 | 650000
+(12 rows)
+```
+
+This command splits the `p2_americas` subpartition into two new subpartitions and redistributes the contents.
+
+```sql
+ALTER TABLE sales SPLIT SUBPARTITION p2_americas
+  VALUES ('US')
+  INTO
+  (
+    SUBPARTITION p2_us,
+    SUBPARTITION p2_canada
+  );
+```
+
+After the command is invoked, the `p2_americas` subpartition is deleted. In its place, the server creates the subpartitions `p2_us` and `p2_canada`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+  partition_name  | subpartition_name |    high_value
+------------------+-------------------+-------------------
+ FIRST_HALF_2012  | P1_EUROPE         | 'ITALY', 'FRANCE'
+ FIRST_HALF_2012  | P1_AMERICAS       | 'US', 'CANADA'
+ SECOND_HALF_2012 | P2_EUROPE         | 'ITALY', 'FRANCE'
+ SECOND_HALF_2012 | P2_US             | 'US'
+ SECOND_HALF_2012 | P2_CANADA         | 'CANADA'
+(5 rows)
+```
+
+Querying the `sales` table shows that the content of the `p2_americas` subpartition was redistributed:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid       | dept_no | part_no | country |        date        |amount
+------------------+---------+---------+---------+--------------------+------
+ sales_p1_americas|      40 | 9519b   | US      | 12-APR-12 00:00:00 |145000
+ sales_p1_americas|      30 | 9519b   | CANADA  | 01-FEB-12 00:00:00 | 75000
+ sales_p1_americas|      30 | 4519b   | CANADA  | 08-APR-12 00:00:00 |120000
+ sales_p1_americas|      40 | 3788a   | US      | 12-MAY-12 00:00:00 |  4950
+ sales_p1_europe  |      10 | 4519b   | FRANCE  | 17-JAN-12 00:00:00 | 45000
+ sales_p2_canada  |      30 | 7588b   | CANADA  | 14-DEC-12 00:00:00 | 50000
+ sales_p2_europ   |      10 | 9519b   | ITALY   | 07-JUL-12 00:00:00 | 15000
+ sales_p2_europe  |      10 | 9519a   | FRANCE  | 18-AUG-12 00:00:00 |650000
+ sales_p2_europe  |      10 | 9519b   | FRANCE  | 18-AUG-12 00:00:00 |650000
+ sales_p2_us      |      40 | 4577b   | US      | 11-NOV-12 00:00:00 | 25000
+ sales_p2_us      |      40 | 4788a   | US      | 23-SEP-12 00:00:00 |  4950
+ sales_p2_us      |      40 | 4788b   | US      | 09-OCT-12 00:00:00 | 15000
+(12 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/02_example_splitting_a_range_subpartition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/02_example_splitting_a_range_subpartition.mdx
new file mode 100644
index 00000000000..7d9a995b1fe
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/02_example_splitting_a_range_subpartition.mdx
@@ -0,0 +1,170 @@
+---
+title: "Example: Splitting a RANGE subpartition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/02_example_splitting_a_range_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_splitting_a_range_subpartition" class="registered_link"></div>
+
+This example splits a range subpartition, redistributing the subpartition's contents between two new subpartitions.
+
+The sample table `sales` was created with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY RANGE(date)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY')
+    (
+      SUBPARTITION europe_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION europe_2012
+        VALUES LESS THAN('2013-Jan-01')
+    ),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN')
+    (
+      SUBPARTITION asia_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION asia_2012
+        VALUES LESS THAN('2013-Jan-01')
+    ),
+  PARTITION americas VALUES('US', 'CANADA')
+    (
+      SUBPARTITION americas_2011
+        VALUES LESS THAN('2012-Jan-01'),
+      SUBPARTITION americas_2012
+        VALUES LESS THAN('2013-Jan-01')
+    )
+);
+```
+
+The `sales` table has the partitions `europe`, `asia`, and `americas`. Each partition has two range-defined subpartitions that sort the partitions contents into subpartitions by the value of the `date` column:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value
+----------------+-------------------+----------------------
+ EUROPE         | EUROPE_2011       | '01-JAN-12 00:00:00'
+ EUROPE         | EUROPE_2012       | '01-JAN-13 00:00:00'
+ ASIA           | ASIA_2011         | '01-JAN-12 00:00:00'
+ ASIA           | ASIA_2012         | '01-JAN-13 00:00:00'
+ AMERICAS       | AMERICAS_2011     | '01-JAN-12 00:00:00'
+ AMERICAS       | AMERICAS_2012     | '01-JAN-13 00:00:00'
+(6 rows)
+```
+
+This command adds rows to each subpartition:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+A `SELECT` statement confirms that the rows are distributed among the subpartitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid           |dept_no|part_no| country |       date         | amount
+--------------------+-------+-------+---------+--------------------+---------
+ sales_americas_2012|  40   | 9519b | US      | 12-APR-12 00:00:00 | 145000
+ sales_americas_2012|  40   | 4577b | US      | 11-NOV-12 00:00:00 |  25000
+ sales_americas_2012|  30   | 7588b | CANADA  | 14-DEC-12 00:00:00 |  50000
+ sales_americas_2012|  30   | 9519b | CANADA  | 01-FEB-12 00:00:00 |  75000
+ sales_americas_2012|  30   | 4519b | CANADA  | 08-APR-12 00:00:00 | 120000
+ sales_americas_2012|  40   | 3788a | US      | 12-MAY-12 00:00:00 |   4950
+ sales_americas_2012|  40   | 4788a | US      | 23-SEP-12 00:00:00 |   4950
+ sales_americas_2012|  40   | 4788b | US      | 09-OCT-12 00:00:00 |  15000
+ sales_europe_2012  |  10   | 4519b | FRANCE  | 17-JAN-12 00:00:00 |  45000
+ sales_europe_2012  |  10   | 9519b | ITALY   | 07-JUL-12 00:00:00 |  15000
+ sales_europe_2012  |  10   | 9519a | FRANCE  | 18-AUG-12 00:00:00 | 650000
+ sales_europe_2012  |  10   | 9519b | FRANCE  | 18-AUG-12 00:00:00 | 650000
+ sales_asia_2012    |  20   | 3788a | INDIA   | 01-MAR-12 00:00:00 |  75000
+ sales_asia_2012    |  20   | 3788a | PAKISTAN| 04-JUN-12 00:00:00 |  37500
+ sales_asia_2012    |  20   | 3788b | INDIA   | 21-SEP-12 00:00:00 |   5090
+ sales_asia_2012    |  20   | 4519a | INDIA   | 18-OCT-12 00:00:00 | 650000
+ sales_asia_2012    |  20   | 4519b | INDIA   | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+This command splits the `americas_2012` subpartition into two new subpartitions and redistributes the contents:
+
+```sql
+ALTER TABLE sales
+  SPLIT SUBPARTITION americas_2012
+  AT('2012-Jun-01')
+  INTO
+   (
+     SUBPARTITION americas_p1_2012,
+     SUBPARTITION americas_p2_2012
+   );
+```
+
+After the command is invoked, the `americas_2012` subpartition is deleted. In its place, the server creates the subpartitions `americas_p1_2012` and `americas_p2_2012`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value
+----------------+-------------------+----------------------
+ EUROPE         | EUROPE_2011       | '01-JAN-12 00:00:00'
+ EUROPE         | EUROPE_2012       | '01-JAN-13 00:00:00'
+ ASIA           | ASIA_2011         | '01-JAN-12 00:00:00'
+ ASIA           | ASIA_2012         | '01-JAN-13 00:00:00'
+ AMERICAS       | AMERICAS_2011     | '01-JAN-12 00:00:00'
+ AMERICAS       | AMERICAS_P1_2012  | '01-JUN-12 00:00:00'
+ AMERICAS       | AMERICAS_P2_2012  | '01-JAN-13 00:00:00'
+(7 rows)
+```
+
+Querying the `sales` table shows that the subpartition's contents are redistributed:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid              |dept_no|part_no|country  |      date         | amount
+-----------------------+-------+-------+---------+-------------------+-------
+ sales_americas_p1_2012|  40   | 9519b | US      | 12-APR-12 00:00:00|145000
+ sales_americas_p1_2012|  30   | 9519b | CANADA  | 01-FEB-12 00:00:00|75000
+ sales_americas_p1_2012|  30   | 4519b | CANADA  | 08-APR-12 00:00:00|120000
+ sales_americas_p1_2012|  40   | 3788a | US      | 12-MAY-12 00:00:00| 4950
+ sales_americas_p2_2012|  40   | 4577b | US      | 11-NOV-12 00:00:00|25000
+ sales_americas_p2_2012|  30   | 7588b | CANADA  | 14-DEC-12 00:00:00|50000
+ sales_americas_p2_2012|  40   | 4788a | US      | 23-SEP-12 00:00:00| 4950
+ sales_americas_p2_2012|  40   | 4788b | US      | 09-OCT-12 00:00:00|15000
+ sales_europe_2012     |  10   | 4519b | FRANCE  | 17-JAN-12 00:00:00|45000
+ sales_europe_2012     |  10   | 9519b | ITALY   | 07-JUL-12 00:00:00|15000
+ sales_europe_2012     |  10   | 9519a | FRANCE  | 18-AUG-12 00:00:00|650000
+ sales_europe_2012     |  10   | 9519b | FRANCE  | 18-AUG-12 00:00:00|650000
+ sales_asia_2012       |  20   | 3788a | INDIA   | 01-MAR-12 00:00:00|75000
+ sales_asia_2012       |  20   | 3788a | PAKISTAN| 04-JUN-12 00:00:00|37500
+ sales_asia_2012       |  20   | 3788b | INDIA   | 21-SEP-12 00:00:00|5090
+ sales_asia_2012       |  20   | 4519a | INDIA   | 18-OCT-12 00:00:00|650000
+ sales_asia_2012       |  20   | 4519b | INDIA   | 02-DEC-12 00:00:00| 5090
+(17 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/index.mdx
new file mode 100644
index 00000000000..87a76234325
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/index.mdx
@@ -0,0 +1,92 @@
+---
+title: "ALTER TABLE...SPLIT SUBPARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.108.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.333.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.057.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/05_alter_table_split_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_split_subpartition" class="registered_link"></div>
+
+Use the `ALTER TABLE… SPLIT SUBPARTITION` command to divide a single subpartition into two subpartition and redistribute the subpartition's contents. The command comes in two variations.
+
+The first variation splits a range subpartition into two subpartitions:
+
+```sql
+ALTER TABLE <table_name> SPLIT SUBPARTITION <subpartition_name>
+  AT (range_part_value)
+  INTO
+  (
+    SUBPARTITION <new_subpart1>
+      [TABLESPACE <tablespace_name>],
+    SUBPARTITION <new_subpart2>
+      [TABLESPACE <tablespace_name>]
+  );
+```
+
+The second variation splits a list subpartition into two subpartitions:
+
+```sql
+ALTER TABLE <table_name> SPLIT SUBPARTITION <subpartition_name>
+  VALUES (<value>[, <value>]...)
+  INTO
+  (
+    SUBPARTITION <new_subpart1>
+      [TABLESPACE <tablespace_name>],
+    SUBPARTITION <new_subpart2>
+      [TABLESPACE <tablespace_name>]
+  );
+```
+
+## Description
+
+The `ALTER TABLE...SPLIT SUBPARTITION` command adds a subpartition to an existing subpartitioned table. There's no upper limit to the number of defined subpartitions. When you execute an `ALTER TABLE...SPLIT SUBPARTITION` command, EDB Postgres Advanced Server creates two subpartitions. It moves any rows that contain values that are constrained by the specified subpartition rules into `new_subpart1` and any remaining rows into `new_subpart2`.
+
+The new subpartition rules must reference the column specified in the rules that define the existing subpartitions.
+
+Include the `TABLESPACE` clause to specify a tablespace in which a new subpartition resides. If you don't specify a tablespace, the subpartition is created in the default tablespace.
+
+If the table is indexed, the index is created on the new subpartition.
+
+To use the `ALTER TABLE... SPLIT SUBPARTITION` command, you must be the table owner or have superuser or administrative privileges.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`subpartition_name`
+
+ The name of the subpartition that's being split.
+
+`new_subpart1`
+
+ The name of the first subpartition to create. Subpartition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+ `new_subpart1` receives the rows that meet the subpartitioning constraints specified in the `ALTER TABLE… SPLIT SUBPARTITION` command.
+
+`new_subpart2`
+
+ The name of the second subpartition to create. Subpartition names must be unique among all partitions and subpartitions and must follow the naming conventions for object identifiers.
+
+ `new_subpart2` receives the rows that aren't directed to `new_subpart1` by the subpartitioning constraints specified in the `ALTER TABLE… SPLIT SUBPARTITION` command.
+
+`(value[, value]...)`
+
+ Use `value` to specify a quoted literal value or comma-delimited list of literal values by which table entries are grouped into partitions. Each partitioning rule must specify at least one value. There's no limit on the number of values specified in a rule. `value` can also be `NULL`, `DEFAULT` if specifying a `LIST` subpartition, or `MAXVALUE` if specifying a `RANGE` subpartition.
+
+ For information about creating a `DEFAULT` or `MAXVALUE` partition, see [Handling stray values in a LIST or RANGE partitioned table](../../../../application_programming/epas_compat_table_partitioning/05_handling_stray_values_in_a_list_or_range_partitioned_table/#handling_stray_values_in_a_list_or_range_partitioned_table).
+
+`tablespace_name`
+
+ The name of the tablespace in which the partition or subpartition resides.
+
+<div class="toctree" maxdepth="3">
+
+example_splitting_a_list_subpartition example_splitting_a_range_subpartition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/01_example_exchanging_a_table_for_a_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/01_example_exchanging_a_table_for_a_partition.mdx
new file mode 100644
index 00000000000..f79a413dc13
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/01_example_exchanging_a_table_for_a_partition.mdx
@@ -0,0 +1,135 @@
+---
+title: "Example: Exchanging a table for a partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/01_example_exchanging_a_table_for_a_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_exchanging_a_table_for_a_partition" class="registered_link"></div>
+
+This example swaps a table for the partition `americas` of the `sales` table. You can create the `sales` table with this command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Use this command to add sample data to the `sales` table:
+
+```sql
+INSERT INTO sales VALUES
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+Querying the `sales` table shows that only one row resides in the `americas` partition:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(10 rows)
+```
+
+This command creates a table `n_america` that matches the definition of the `sales` table:
+
+```sql
+CREATE TABLE n_america
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+);
+```
+
+This command adds data to the `n_america` table. The data conforms to the partitioning rules of the `americas` partition.
+
+```sql
+INSERT INTO n_america VALUES
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000');
+```
+
+This command swaps the table into the partitioned table:
+
+```sql
+ALTER TABLE sales
+  EXCHANGE PARTITION americas
+  WITH TABLE n_america;
+```
+
+Querying the `sales` table shows that the contents of the `n_america` table were exchanged for the contents of the `americas` partition:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_americas |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_americas |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_americas |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_americas |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_americas |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_americas |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_americas |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+Querying the `n_america` table shows that the row that was previously stored in the `americas` partition was moved to the `n_america` table:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM n_america;
+__OUTPUT__
+ tableoid  | dept_no | part_no | country |        date        | amount
+-----------+---------+---------+---------+--------------------+--------
+ n_america |      40 | 9519b   | US      | 12-APR-12 00:00:00 | 145000
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/index.mdx
new file mode 100644
index 00000000000..71517b027c3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/index.mdx
@@ -0,0 +1,76 @@
+---
+title: "ALTER TABLE...EXCHANGE PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.109.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.334.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.058.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/06_alter_table_exchange_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_exchange_partition" class="registered_link"></div>
+
+The `ALTER TABLE…EXCHANGE PARTITION` command swaps an existing table with a partition. If you plan to add a large quantity of data to a partitioned table, you can use the `ALTER TABLE… EXCHANGE PARTITION` command to implement a bulk load. You can also use the `ALTER TABLE… EXCHANGE PARTITION` command to remove old or unneeded data for storage.
+
+The command syntax is available in two forms. The first form swaps a table for a partition:
+
+```sql
+ALTER TABLE <target_table>
+  EXCHANGE PARTITION <target_partition>
+  WITH TABLE <source_table>
+  [(INCLUDING | EXCLUDING) INDEXES]
+  [(WITH | WITHOUT) VALIDATION];
+```
+
+The second form swaps a table for a subpartition:
+
+```sql
+ALTER TABLE <target_table>
+  EXCHANGE SUBPARTITION <target_subpartition>
+  WITH TABLE <source_table>
+  [(INCLUDING | EXCLUDING) INDEXES]
+  [(WITH | WITHOUT) VALIDATION];
+```
+
+## Description
+
+When the `ALTER TABLE… EXCHANGE PARTITION` command completes, the data originally located in the `target_partition` is located in the `source_table`. The data originally located in the `source_table` is located in the `target_partition`.
+
+The `ALTER TABLE… EXCHANGE PARTITION` command can exchange partitions in a `LIST`, `RANGE` or `HASH` partitioned table. The structure of the `source_table` must match the structure of the `target_table` in that both tables must have matching columns and data types. The data in the table must adhere to the partitioning constraints.
+
+If the `INCLUDING INDEXES` clause is specified with `EXCHANGE PARTITION`, then matching indexes in the `target_partition` and `source_table` are swapped. Indexes in the `target_partition` with no match in the `source_table` are rebuilt and vice versa. That is, indexes in the `source_table` with no match in the `target_partition` are also rebuilt.
+
+If the `EXCLUDING INDEXES` clause is specified with `EXCHANGE PARTITION`, then matching indexes in the `target_partition` and `source_table` are swapped. However the `target_partition` indexes with no match in the `source_table` are marked as invalid and vice versa. That is, indexes in the `source_table` with no match in the `target_partition` are also marked as invalid.
+
+The term *matching index* refers to indexes that have the same attributes. Attribute examples include the collation order, ascending or descending direction, ordering of nulls first or nulls last, and so forth as determined by the `CREATE INDEX` command.
+
+If you omit both `INCLUDING INDEXES` and `EXCLUDING INDEXES`, then the default action is the `EXCLUDING INDEXES` behavior.
+
+The same behavior described applies for the `target_subpartition` used with the `EXCHANGE SUBPARTITION` clause.
+
+You must own a table to invoke `ALTER TABLE… EXCHANGE PARTITION` or `ALTER TABLE… EXCHANGE SUBPARTITION` against that table.
+
+## Parameters
+
+`target_table`
+
+ The name (optionally schema-qualified) of the table in which the partition or subpartition resides.
+
+`target_partition`
+
+ The name of the partition to replace.
+
+`target_subpartition`
+
+ The name of the subpartition to replace.
+
+`source_table`
+
+ The name of the table that replaces the `target_partition` or `target_subpartition`.
+
+<div class="toctree" maxdepth="3">
+
+example_exchanging_a_table_for_a_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/01_example_moving_a_partition_to_a_different_tablespace.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/01_example_moving_a_partition_to_a_different_tablespace.mdx
new file mode 100644
index 00000000000..7c09fe424ef
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/01_example_moving_a_partition_to_a_different_tablespace.mdx
@@ -0,0 +1,66 @@
+---
+title: "Example: Moving a partition to a different tablespace"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/01_example_moving_a_partition_to_a_different_tablespace/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_moving_a_partition_to_a_different_tablespace" class="registered_link"></div>
+
+This following example moves a partition of the `sales` table from one tablespace to another. 
+
+Create the `sales` table with the command:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+(
+  PARTITION q1_2012 VALUES LESS THAN ('2012-Apr-01'),
+  PARTITION q2_2012 VALUES LESS THAN ('2012-Jul-01'),
+  PARTITION q3_2012 VALUES LESS THAN ('2012-Oct-01'),
+  PARTITION q4_2012 VALUES LESS THAN ('2013-Jan-01') TABLESPACE ts_1,
+  PARTITION q1_2013 VALUES LESS THAN ('2013-Mar-01') TABLESPACE ts_2
+);
+```
+
+Querying the `ALL_TAB_PARTITIONS` view confirms that the partitions reside on the expected servers and tablespaces:
+
+```sql
+edb=# SELECT partition_name, tablespace_name FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name | tablespace_name
+----------------+-----------------
+ Q1_2012        |
+ Q2_2012        |
+ Q3_2012        |
+ Q4_2012        | TS_1
+ Q1_2013        | TS_2
+(5 rows)
+```
+
+After preparing the target tablespace, invoke the `ALTER TABLE… MOVE PARTITION` command to move the `q1_2013` partition from a tablespace named `ts_2` to a tablespace named `ts_3`:
+
+```sql
+ALTER TABLE sales MOVE PARTITION q1_2013 TABLESPACE ts_3;
+```
+
+Querying the `ALL_TAB_PARTITIONS` view shows that the move was successful:
+
+```sql
+edb=# SELECT partition_name, tablespace_name FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name | tablespace_name
+----------------+-----------------
+ Q1_2012        |
+ Q2_2012        |
+ Q3_2012        |
+ Q4_2012        | TS_1
+ Q1_2013        | TS_3
+(5 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/index.mdx
new file mode 100644
index 00000000000..5cf0f9c0e52
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/index.mdx
@@ -0,0 +1,62 @@
+---
+title: "ALTER TABLE...MOVE PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.110.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.335.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.059.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/07_alter_table_move_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_move_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… MOVE PARTITION` command to move a partition to a different tablespace. The command takes two forms.
+
+The first form moves a partition to a new tablespace:
+
+```sql
+ALTER TABLE <table_name>
+  MOVE PARTITION <partition_name>
+   TABLESPACE <tablespace_name>;
+```
+
+The second form moves a subpartition to a new tablespace:
+
+```sql
+ALTER TABLE <table_name>
+  MOVE SUBPARTITION <subpartition_name>
+   TABLESPACE <tablespace_name>;
+```
+
+## Description
+
+The `ALTER TABLE…MOVE PARTITION` command moves a partition from its current tablespace to a different tablespace. The `ALTER TABLE… MOVE PARTITION` command can move partitions of a `LIST`, `RANGE` or `HASH` partitioned table.
+
+The same behavior applies for the `subpartition_name` used with the `MOVE SUBPARTITION` clause.
+
+You must own the table to invoke `ALTER TABLE… MOVE PARTITION` or `ALTER TABLE… MOVE SUBPARTITION`.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the table in which the partition or subpartition resides.
+
+`partition_name`
+
+ The name of the partition to move.
+
+`subpartition_name`
+
+ The name of the subpartition to move.
+
+`tablespace_name`
+
+ The name of the tablespace to which the partition or subpartition is moved.
+
+<div class="toctree" maxdepth="3">
+
+example_moving_a_partition_to_a_different_tablespace
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/01_example_renaming_a_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/01_example_renaming_a_partition.mdx
new file mode 100644
index 00000000000..4213369d13f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/01_example_renaming_a_partition.mdx
@@ -0,0 +1,59 @@
+---
+title: "Example: Renaming a partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/01_example_renaming_a_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_renaming_a_partition" class="registered_link"></div>
+
+This command creates a list-partitioned table named `sales`:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Query the `ALL_TAB_PARTITIONS` view to display the partition names:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
+
+This command renames the `americas` partition to `n_america`:
+
+```sql
+ALTER TABLE sales
+ RENAME PARTITION americas TO n_america;
+```
+
+Query the `ALL_TAB_PARTITIONS` view to show that the partition was successfully renamed:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ N_AMERICA      | 'US', 'CANADA'
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/index.mdx
new file mode 100644
index 00000000000..985a07c0904
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/index.mdx
@@ -0,0 +1,62 @@
+---
+title: "ALTER TABLE...RENAME PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.111.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.336.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.060.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/08_alter_table_rename_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_rename_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… RENAME PARTITION` command to rename a table partition. The syntax takes two forms.
+
+The first form renames a partition:
+
+```sql
+ALTER TABLE <table_name>
+ RENAME PARTITION <partition_name>
+ TO <new_name>;
+```
+
+The second form renames a subpartition:
+
+```sql
+ALTER TABLE <table_name>
+ RENAME SUBPARTITION <subpartition_name>
+ TO <new_name>;
+```
+
+## Description
+
+The `ALTER TABLE… RENAME PARTITION` command renames a partition.
+
+The behavior for `subpartition_name` is the same as for the same variable used with the `RENAME SUBPARTITION` clause.
+
+You must own the specified table to invoke `ALTER TABLE… RENAME PARTITION` or `ALTER TABLE… RENAME SUBPARTITION`.
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the table in which the partition or subpartition resides.
+
+`partition_name`
+
+ The name of the partition to rename.
+
+`subpartition_name`
+
+ The name of the subpartition to rename.
+
+`new_name`
+
+ The new name of the partition or subpartition.
+
+<div class="toctree" maxdepth="3">
+
+example_renaming_a_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/01_example_setting_an_interval_range_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/01_example_setting_an_interval_range_partition.mdx
new file mode 100644
index 00000000000..c8cdca9f582
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/01_example_setting_an_interval_range_partition.mdx
@@ -0,0 +1,65 @@
+---
+title: "Example: Setting an interval range partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/01_example_setting_an_interval_range_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_setting_an_interval_range_partition" class="registered_link"></div>
+
+This example sets an interval range partition of the `sales` table. It converts the table from range partitioning to start using monthly interval range partitioning. 
+
+This command creates the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  prod_id           int,
+  prod_quantity     int,
+  sold_month        date
+)
+PARTITION BY RANGE(sold_month)
+(
+  PARTITION p1
+    VALUES LESS THAN('15-JAN-2019'),
+  PARTITION p2
+    VALUES LESS THAN('15-FEB-2019')
+);
+```
+
+Set the interval range partitioning from the `sales` table:
+
+```sql
+ALTER TABLE sales SET INTERVAL (NUMTOYMINTERVAL(1, 'MONTH'));
+```
+
+Query the `ALL_TAB_PARTITIONS` view before a database creates an interval range partition:
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ P1             | '15-JAN-19 00:00:00'
+ P2             | '15-FEB-19 00:00:00'
+(2 rows)
+```
+
+Add data to the `sales` table that exceeds the high value of a range partition:
+
+```sql
+edb=# INSERT INTO sales VALUES (1,100,'05-APR-2019');
+INSERT 0 1
+```
+
+Query the `ALL_TAB_PARTITIONS` view again after the `INSERT` statement. The interval range partition is successfully created and data is inserted. A system-generated name of the interval range partition is created that varies for each session.
+
+```sql
+edb=# SELECT partition_name, high_value from ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |      high_value
+----------------+----------------------
+ P1             | '15-JAN-19 00:00:00'
+ P2             | '15-FEB-19 00:00:00'
+ SYS916340103   | '15-APR-19 00:00:00'
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/index.mdx
new file mode 100644
index 00000000000..66911e6e20f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/index.mdx
@@ -0,0 +1,41 @@
+---
+title: "ALTER TABLE...SET INTERVAL"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/09_alter_table_set_interval/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_set_interval" class="registered_link"></div>
+
+Use the `ALTER TABLE… SET INTERVAL` command to convert an existing range-partitioned table to an interval range-partitioned table. The database creates a partition of a specified range or interval for the partitioned table when you set `INTERVAL`. The syntax is:
+
+```sql
+ALTER TABLE <table_name> SET INTERVAL (<constant> | <expression>);
+```
+
+To disable an interval range partitioned table and convert it to a range-partitioned table, the syntax is:
+
+```sql
+ALTER TABLE <table_name> SET INTERVAL ();
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the range-partitioned table.
+
+`constant | expression`
+
+ Specifies a `NUMERIC`, `DATE`, or `TIME` value.
+
+## Description
+
+You can use the `ALTER TABLE… SET INTERVAL` command to convert the range-partitioned table to use interval range partitioning. The command creates a new partition of a specified interval. You can then insert data into the new partition.
+
+You can use the `SET INTERVAL ()` command to disable interval range partitioning. The database converts an interval range-partitioned table to range partitioned and sets the boundaries of the interval range partitions to the boundaries for the range partitions.
+
+<div class="toctree" maxdepth="3">
+
+example_setting_an_interval_range_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/01_example_setting_an_automatic_list_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/01_example_setting_an_automatic_list_partition.mdx
new file mode 100644
index 00000000000..b71f6b6ef10
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/01_example_setting_an_automatic_list_partition.mdx
@@ -0,0 +1,65 @@
+---
+title: "Example: Setting an AUTOMATIC list partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/01_example_setting_an_automatic_list_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_setting_an_automatic_list_partition" class="registered_link"></div>
+
+This example modifies a table `sales` to use automatic list partitioning instead of regular list partitioning. 
+
+This command creates a `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no      number,
+  part_no      varchar2,
+  sales_state  varchar2(20),
+  date         date,
+  amount       number
+)
+PARTITION BY LIST(sales_state)
+(
+  PARTITION P_KAN VALUES('KANSAS'),
+  PARTITION P_TEX VALUES('TEXAS')
+);
+```
+
+Implement automatic list partitioning on the `sales` table:
+
+```sql
+ALTER TABLE sales SET AUTOMATIC;
+```
+
+Query the `ALL_TAB_PARTITIONS` view to show that an existing partition is successfully created:
+
+```sql
+edb=# SELECT table_name, partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ table_name | partition_name | high_value
+------------+----------------+------------
+ SALES      | P_KAN          | 'KANSAS'
+ SALES      | P_TEX          | 'TEXAS'
+(2 rows)
+```
+
+Insert data into the `sales` table to create a partition and add the value:
+
+```sql
+edb=# INSERT INTO sales VALUES (1, 'VIR', 'VIRGINIA');
+INSERT 0 1
+```
+
+Query the `ALL_TAB_PARTITIONS` view again after the insert. The automatic list partition is successfully created and data is inserted. A system-generated name of the partition is created that varies for each session.
+
+```sql
+edb=# SELECT table_name, partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ table_name | partition_name | high_value
+------------+----------------+------------
+ SALES      | P_KAN          | 'KANSAS'
+ SALES      | P_TEX          | 'TEXAS'
+ SALES      | SYS106900103   | 'VIRGINIA'
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/index.mdx
new file mode 100644
index 00000000000..fd7f8049ce3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/index.mdx
@@ -0,0 +1,37 @@
+---
+title: "ALTER TABLE...SET [ PARTITIONING ] AUTOMATIC"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/10_alter_table_set_partitioning_automatic/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_set_partitioning_automatic" class="registered_link"></div>
+
+Use the `ALTER TABLE… SET [ PARTITIONING ] AUTOMATIC` command to convert an existing list-partitioned table to automatic list partitioning. The database automatically creates a partition based on a new value inserted into a table when `AUTOMATIC` is set. The syntax is:
+
+```sql
+ALTER TABLE <table_name> SET [ PARTITIONING ] AUTOMATIC;
+```
+
+To disable `AUTOMATIC LIST PARTITIONING` and convert to regular `LIST` partition, the syntax is:
+
+```sql
+ALTER TABLE <table_name> SET [ PARTITIONING ] MANUAL;
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the list-partitioned table.
+
+## Description
+
+You can use the `ALTER TABLE… SET [ PARTITIONING ] AUTOMATIC` command to convert the regular list-partitioned table to use automatic partitioning. A partition is created, and you can insert data into the new partition.
+
+You can use the `ALTER TABLE… SET [ PARTITIONING ] MANUAL` command to disable the automatic list partitioning. The database converts an automatic list-partitioned table to a regular list-partitioned table.
+
+<div class="toctree" maxdepth="3">
+
+example_setting_an_automatic_list_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx
new file mode 100644
index 00000000000..4e500f6159e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template.mdx
@@ -0,0 +1,469 @@
+---
+title: "Example: Setting a SUBPARTITION TEMPLATE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/01_example_setting_a_subpartition_template/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_setting_a_subpartition_template" class="registered_link"></div>
+
+This example creates a table `sales` that's range partitioned by `date` and hash-subpartitioned by `country`. 
+
+This command creates the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE (date) SUBPARTITION BY HASH (country) SUBPARTITIONS 2
+(
+  PARTITION q1_2012
+    VALUES LESS THAN('2012-Apr-01'),
+  PARTITION q2_2012
+    VALUES LESS THAN('2012-Jul-01'),
+  PARTITION q3_2012
+    VALUES LESS THAN('2012-Oct-01'),
+  PARTITION q4_2012
+    VALUES LESS THAN('2013-Jan-01')
+);
+```
+
+The table definition creates four partitions: `q1_2012`, `q2_2012`, `q3_2012`, and `q4_2012`. Each partition consists of two subpartitions with system-generated names.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | Q1_2012        | SYS0101
+ SALES      | Q1_2012        | SYS0102
+ SALES      | Q2_2012        | SYS0103
+ SALES      | Q2_2012        | SYS0104
+ SALES      | Q3_2012        | SYS0105
+ SALES      | Q3_2012        | SYS0106
+ SALES      | Q4_2012        | SYS0107
+ SALES      | Q4_2012        | SYS0108
+(8 rows)
+```
+
+Set the subpartition template on the `sales` table:
+
+```sql
+ALTER TABLE sales SET SUBPARTITION TEMPLATE 8;
+```
+
+The `sales` table is modified, with the subpartition template set to eight. If you try to add a partition `q1_2013`, a new partition is created and consists of eight subpartitions.
+
+```sql
+ALTER TABLE sales ADD PARTITION q1_2013 VALUES LESS THAN ('2013-Apr-01');
+```
+
+Query the `ALL_TAB_PARTITIONS` view. The `q1_2013` partition is successfully added. It has eight subpartitions that have system-generated names.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
+'Q1_2013' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | Q1_2013        | SYS0113
+ SALES      | Q1_2013        | SYS0114
+ SALES      | Q1_2013        | SYS0115
+ SALES      | Q1_2013        | SYS0116
+ SALES      | Q1_2013        | SYS0117
+ SALES      | Q1_2013        | SYS0118
+ SALES      | Q1_2013        | SYS0119
+ SALES      | Q1_2013        | SYS0120
+(8 rows)
+```
+
+## Example: Adding a subpartition template for LIST/LIST partitioned table 
+
+This example creates a table `sales` that's list-partitioned by country. It is subpartitioned using the list by the `date` column.  
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) 
+  SUBPARTITION BY LIST (date)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe VALUES('2021-Jan-01') TABLESPACE ts1,
+    SUBPARTITION asia VALUES('2021-Apr-01') TABLESPACE ts2,
+    SUBPARTITION americas VALUES('2021-Jul-01') TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES('2021-Jul-01')
+); 
+```   
+
+The `SELECT` statement shows partition `q1_2021` consisting of three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(3 rows)
+```
+
+This command adds a partition named `q2_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q2_2021 VALUES('US', 'CANADA');
+```
+
+This command shows that the `sales` table includes the `q2_2021` partition:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q2_2021        | Q2_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q2_2021        | Q2_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q2_2021        | Q2_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(6 rows)
+```
+
+## Example: Adding a subpartition template for LIST/RANGE partitioned table
+
+This example creates a table `sales` list-partitioned by country and subpartitioned using range partitioning by the `date` column: 
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY RANGE(date)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe VALUES LESS THAN('2021-Jan-01') TABLESPACE ts1,
+    SUBPARTITION asia VALUES LESS THAN('2021-Apr-01') TABLESPACE ts2,
+    SUBPARTITION americas VALUES LESS THAN('2021-Jul-01') TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES ('2021-Jul-01')
+); 
+```     
+
+The `sales` table creates a partition named `q1_2021` that includes three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(3 rows)
+```
+
+This command adds a partition named `q2_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q2_2021 VALUES('INDIA', 'PAKISTAN');
+```
+
+This command shows that the `sales` table includes the `q2_2021` partition:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q2_2021        | Q2_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q2_2021        | Q2_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q2_2021        | Q2_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(6 rows)
+```
+
+## Example: Adding a subpartition template for LIST/HASH partitioned table
+
+This example creates a list-partitioned table `sales` that's first partitioned by country and then hash-subpartitioned using the value of the `dept_no` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY HASH (dept_no)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe TABLESPACE ts1,
+    SUBPARTITION asia TABLESPACE ts2,
+    SUBPARTITION americas TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES ('2021-Jul-01')
+); 
+```  
+
+The `sales` table creates a `q1_2021` partition that includes three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name | high_value | tablespace_name 
+----------------+-------------------+------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  |            | TS3
+ Q1_2021        | Q1_2021_ASIA      |            | TS2
+ Q1_2021        | Q1_2021_EUROPE    |            | TS1
+(3 rows)
+```
+
+This command adds a partition named `q2_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q2_2021 VALUES('FRANCE', 'ITALY');
+```
+
+This command shows that the `sales` table includes the `q2_2021` partition:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name | high_value | tablespace_name 
+----------------+-------------------+------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  |            | TS3
+ Q1_2021        | Q1_2021_ASIA      |            | TS2
+ Q1_2021        | Q1_2021_EUROPE    |            | TS1
+ Q2_2021        | Q2_2021_AMERICAS  |            | TS3
+ Q2_2021        | Q2_2021_ASIA      |            | TS2
+ Q2_2021        | Q2_2021_EUROPE    |            | TS1
+(6 rows)
+```
+
+## Examples: Resetting a SUBPARTITION TEMPLATE
+
+This example creates a list-partitioned table `sales` that's list partitioned by `country` and hash subpartitioned by `part_no`. 
+
+This command creates the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST (country) SUBPARTITION BY HASH (part_no) SUBPARTITIONS 3
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+The table contains three partitions: `americas`, `asia`, and `europe`. Each partition consists of three subpartitions with system-generated names.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | AMERICAS       | SYS0109
+ SALES      | AMERICAS       | SYS0107
+ SALES      | AMERICAS       | SYS0108
+ SALES      | ASIA           | SYS0105
+ SALES      | ASIA           | SYS0104
+ SALES      | ASIA           | SYS0106
+ SALES      | EUROPE         | SYS0101
+ SALES      | EUROPE         | SYS0103
+ SALES      | EUROPE         | SYS0102
+(9 rows)
+```
+
+This command resets the subpartition template on the `sales` table:
+
+```sql
+ALTER TABLE sales SET SUBPARTITION TEMPLATE ();
+```
+
+The `sales` table is modified with the subpartition template reset to default `1`. Try to add a new partition `east_asia` using this command:
+
+```sql
+ALTER TABLE sales ADD PARTITION east_asia VALUES ('CHINA', 'KOREA');
+```
+
+Query the `ALL_TAB_PARTITIONS` view. A new partition `east_asia` is created consisting of one subpartition with a system-generated name.
+
+```sql
+edb=# SELECT table_name, partition_name, subpartition_name FROM
+ALL_TAB_SUBPARTITIONS WHERE table_name = 'SALES' and partition_name =
+'EAST_ASIA' ORDER BY 1,2;
+__OUTPUT__
+ table_name | partition_name | subpartition_name
+------------+----------------+-------------------
+ SALES      | EAST_ASIA      | SYS0113
+(1 row)
+```
+
+This example creates a table `sales` list-partitioned by country and subpartitioned using range partitioning by the `date` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+  SUBPARTITION BY RANGE(date)
+  SUBPARTITION TEMPLATE
+(
+    SUBPARTITION europe VALUES LESS THAN('2021-Jan-01') TABLESPACE ts1,
+    SUBPARTITION asia VALUES LESS THAN('2021-Apr-01') TABLESPACE ts2,
+    SUBPARTITION americas VALUES LESS THAN('2021-Jul-01') TABLESPACE ts3
+)
+( 
+    PARTITION q1_2021 VALUES ('2021-Jul-01')
+); 
+```    
+
+The `sales` table contains a partition named `q1_2021` that includes three subpartitions stored in tablespaces `ts1`, `ts2`, and `ts3`.
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name 
+FROM DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(3 rows)
+```
+
+This command adds a partition named `q2_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q2_2021 VALUES('INDIA', 'PAKISTAN');
+```
+
+This command shows that the `sales` table includes the `q2_2021` partition:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q2_2021        | Q2_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q2_2021        | Q2_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q2_2021        | Q2_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+(6 rows)
+```
+
+Use the `ALTER TABLE... SET SUBPARTITION TEMPLATE` command to specify a new subpartition template:
+
+```sql
+ALTER TABLE sales SET SUBPARTITION TEMPLATE 
+(
+   SUBPARTITION europe VALUES LESS THAN('2021-Jan-01'),
+   SUBPARTITION asia VALUES LESS THAN('2021-Apr-01') TABLESPACE ts2
+);
+```
+
+This command adds a partition named `q3_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q3_2021 VALUES('US', 'CANADA');
+```
+
+This command shows that the `sales` table includes the `q3_2021` partition:
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q2_2021        | Q2_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q2_2021        | Q2_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q2_2021        | Q2_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q3_2021        | Q3_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q3_2021        | Q3_2021_EUROPE    | '01-JAN-21 00:00:00' | PG_DEFAULT
+(8 rows)
+```
+
+This command resets or drops the subpartition template on the `sales` table:
+
+```sql
+ALTER TABLE sales SET SUBPARTITION TEMPLATE ();
+```
+
+This command adds a partition named `q4_2021` to the `sales` table:
+
+```sql
+ALTER TABLE sales ADD PARTITION q4_2021 VALUES('FRANCE', 'ITALY');
+```
+
+The `SELECT` statement shows partition `q4_2021` consists of a subpartition with a system-generated name: 
+
+```sql
+edb=# SELECT partition_name, subpartition_name, high_value, tablespace_name FROM 
+DBA_TAB_SUBPARTITIONS WHERE table_name = 'SALES' ORDER BY 1,2;
+__OUTPUT__
+ partition_name | subpartition_name |      high_value      | tablespace_name 
+----------------+-------------------+----------------------+-----------------
+ Q1_2021        | Q1_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q1_2021        | Q1_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q1_2021        | Q1_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q2_2021        | Q2_2021_AMERICAS  | '01-JUL-21 00:00:00' | TS3
+ Q2_2021        | Q2_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q2_2021        | Q2_2021_EUROPE    | '01-JAN-21 00:00:00' | TS1
+ Q3_2021        | Q3_2021_ASIA      | '01-APR-21 00:00:00' | TS2
+ Q3_2021        | Q3_2021_EUROPE    | '01-JAN-21 00:00:00' | PG_DEFAULT
+ Q4_2021        | SYS0112           | MAXVALUE             | PG_DEFAULT
+(9 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx
new file mode 100644
index 00000000000..ea18d15e874
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/index.mdx
@@ -0,0 +1,59 @@
+---
+title: "ALTER TABLE...SET SUBPARTITION TEMPLATE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/11_alter_table_set_subpartition_template/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_set_subpartition_template" class="registered_link"></div>
+
+Use the `ALTER TABLE… SET SUBPARTITION TEMPLATE` command to update the subpartition template for a table. The command syntax comes in several forms.
+
+To set the subpartition number for `HASH` subpartitions only:
+
+```sql
+ALTER TABLE <table_name> SET SUBPARTITION TEMPLATE <num>;
+```
+
+To set a subpartition description for an existing partitioned table:
+
+```sql
+ALTER TABLE <table_name>
+[SET SUBPARTITION TEMPLATE (<subpartition_template_description>)]
+```
+
+To reset the subpartitions number to default using the subpartition template:
+
+```sql
+ALTER TABLE <table_name> SET SUBPARTITION TEMPLATE ();
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`num`
+
+ The number of subpartitions to add for a partition.
+
+`subpartition_template_description`
+
+ The list of subpartition details with subpartition name, subpartition bound, and tablespace name.
+
+## Description
+
+You can use the `ALTER TABLE… SET SUBPARTITION TEMPLATE` command to update the subpartition template for range, list, or hash-partitioned table. If you're specifying a subpartition descriptor for a partition, use a subpartition descriptor instead of a subpartition template. You can use the subpartition template whenever a subpartition descriptor isn't specified for a partition. If you don't specify either the subpartition descriptor or subpartition template, then by default a single subpartition is created. 
+
+For more information about creating a subpartition template, see [CREATE TABLE...PARTITION BY](../../04_partitioning_commands_compatible_with_oracle_databases/01_create_table_partition_by/).
+
+!!! Note
+    The partitions added to a table after invoking `ALTER TABLE… SET SUBPARTITION TEMPLATE` command use the new `SUBPARTITION TEMPLATE`.
+
+You can use the `ALTER TABLE… SET SUBPARTITION TEMPLATE ()` command to reset the subpartitions number to default `1`.
+
+<div class="toctree" maxdepth="3">
+
+example_setting_a_subpartition_template 
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/12_drop_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/12_drop_table.mdx
new file mode 100644
index 00000000000..662f3306116
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/12_drop_table.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP TABLE"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/12_drop_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_table" class="registered_link"></div>
+
+Use the PostgreSQL `DROP TABLE` command to remove a partitioned table definition, its partitions and subpartitions, and the table contents. The syntax is:
+
+```sql
+DROP TABLE <table_name>
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+## Description
+
+The `DROP TABLE` command removes an entire table and the data that resides in that table. Deleting a table deletes any partitions or subpartitions of that table.
+
+To use the `DROP TABLE` command, you must be the owner of the partitioning root, a member of a group that owns the table, the schema owner, or a database superuser.
+
+## Example
+
+To delete a table, connect to the controller node (the host of the partitioning root), and invoke the `DROP TABLE` command. For example, delete the `sales` table:
+
+```sql
+DROP TABLE sales;
+```
+
+The server confirms that the table was dropped:
+
+```sql
+edb=# drop table sales;
+DROP TABLE
+edb=#
+```
+
+For more information about the `DROP TABLE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-droptable.html).
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/01_example_deleting_a_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/01_example_deleting_a_partition.mdx
new file mode 100644
index 00000000000..70bec10d5b9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/01_example_deleting_a_partition.mdx
@@ -0,0 +1,59 @@
+---
+title: "Example: Deleting a partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/01_example_deleting_a_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_deleting_a_partition" class="registered_link"></div>
+
+This example deletes a partition of the `sales` table. 
+
+Create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Query the `ALL_TAB_PARTITIONS` view to display the partition names:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
+
+Delete the `americas` partition from the `sales` table:
+
+```sql
+ALTER TABLE sales DROP PARTITION americas;
+```
+
+Query the `ALL_TAB_PARTITIONS` view to show that the partition was successfully deleted:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+(2 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/index.mdx
new file mode 100644
index 00000000000..fe55ec7a235
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/index.mdx
@@ -0,0 +1,40 @@
+---
+title: "ALTER TABLE...DROP PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.113.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.338.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.062.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/13_alter_table_drop_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_drop_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… DROP PARTITION` command to delete a partition definition and the data stored in that partition. The syntax is:
+
+```sql
+ALTER TABLE <table_name> DROP PARTITION <partition_name>;
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`partition_name`
+
+ The name of the partition to delete.
+
+## Description
+
+The `ALTER TABLE… DROP PARTITION` command deletes a partition and any data stored on that partition. The `ALTER TABLE… DROP PARTITION` command can drop partitions of a `LIST` or `RANGE` partitioned table. This command doesn't work on a `HASH` partitioned table. Deleting a partition deletes its subpartitions.
+
+To use the `DROP PARTITION` clause, you must be the owner of the partitioning root, a member of a group that owns the table, or have database superuser or administrative privileges.
+
+<div class="toctree" maxdepth="3">
+
+example_deleting_a_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/01_example_deleting_a_subpartition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/01_example_deleting_a_subpartition.mdx
new file mode 100644
index 00000000000..19026f0403e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/01_example_deleting_a_subpartition.mdx
@@ -0,0 +1,66 @@
+---
+title: "Example: Deleting a subpartition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/01_example_deleting_a_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_deleting_a_subpartition" class="registered_link"></div>
+
+This example deletes a subpartition of the `sales` table. 
+
+Create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST (country)
+  (
+    PARTITION first_half_2012 VALUES LESS THAN('01-JUL-2012')
+    (
+      SUBPARTITION europe VALUES ('ITALY', 'FRANCE'),
+      SUBPARTITION americas VALUES ('CANADA', 'US'),
+      SUBPARTITION asia VALUES ('PAKISTAN', 'INDIA')
+    ),
+    PARTITION second_half_2012 VALUES LESS THAN('01-JAN-2013')
+);
+```
+
+Query the `ALL_TAB_SUBPARTITIONS` view to display the subpartition names:
+
+```sql
+edb=# SELECT subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value
+-------------------+---------------------
+ EUROPE            | 'ITALY', 'FRANCE'
+ AMERICAS          | 'CANADA', 'US'
+ ASIA              | 'PAKISTAN', 'INDIA'
+ SYS0101           | DEFAULT
+(4 rows)
+```
+
+Delete the `americas` subpartition from the `sales` table:
+
+```sql
+ALTER TABLE sales DROP SUBPARTITION americas;
+```
+
+Query the `ALL_TAB_SUBPARTITIONS` view to show that the subpartition was successfully deleted:
+
+```sql
+edb=# SELECT subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value
+-------------------+---------------------
+ EUROPE            | 'ITALY', 'FRANCE'
+ ASIA              | 'PAKISTAN', 'INDIA'
+ SYS0101           | DEFAULT
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/index.mdx
new file mode 100644
index 00000000000..29419025709
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/index.mdx
@@ -0,0 +1,38 @@
+---
+title: "ALTER TABLE...DROP SUBPARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.114.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.339.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.063.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/14_alter_table_drop_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_drop_subpartition" class="registered_link"></div>
+
+Use the `ALTER TABLE… DROP SUBPARTITION` command to drop a subpartition definition and the data stored in that subpartition. The syntax is:
+
+```sql
+ALTER TABLE <table_name> DROP SUBPARTITION <subpartition_name>;
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`subpartition_name`
+
+ The name of the subpartition to delete.
+
+## Description
+
+The `ALTER TABLE… DROP SUBPARTITION` command deletes a subpartition and the data stored in that subpartition. To use the `DROP SUBPARTITION` clause, you must be the owner of the partitioning root, a member of a group that owns the table, or have superuser or administrative privileges.
+
+<div class="toctree" maxdepth="3">
+
+example_deleting_a_subpartition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/01_example_emptying_a_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/01_example_emptying_a_table.mdx
new file mode 100644
index 00000000000..9b6176495ec
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/01_example_emptying_a_table.mdx
@@ -0,0 +1,96 @@
+---
+title: "Example: Emptying a table"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/01_example_emptying_a_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_emptying_a_table" class="registered_link"></div>
+
+This example removes the data from the `sales` table. 
+
+Create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Populate the `sales` table:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+Query the `sales` table to show that the partitions have data:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_americas |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_americas |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_americas |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_americas |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_americas |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_americas |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_americas |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+Delete the contents of the `sales` table:
+
+```sql
+TRUNCATE TABLE sales;
+```
+
+Query the `sales` table to show that the data was removed but the structure is intact:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid | dept_no | part_no | country | date | amount
+----------+---------+---------+---------+------+--------
+(0 rows)
+```
+
+For more information about the `TRUNCATE TABLE` command, see the [PostgreSQL documentation](https://www.postgresql.org/docs/current/static/sql-truncate.html).
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/index.mdx
new file mode 100644
index 00000000000..d7b2af45f07
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/index.mdx
@@ -0,0 +1,36 @@
+---
+title: "TRUNCATE TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.115.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.340.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.064.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/15_truncate_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="truncate_table" class="registered_link"></div>
+
+Use the `TRUNCATE TABLE` command to remove the contents of a table while preserving the table definition. Truncating a table also truncates the table's partitions or subpartitions. The syntax is:
+
+```sql
+TRUNCATE TABLE <table_name>
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+## Description
+
+The `TRUNCATE TABLE` command removes an entire table and the data that resides in that table. Deleting a table deletes any partitions or subpartitions of that table.
+
+To use the `TRUNCATE TABLE` command, you must be the owner of the partitioning root, a member of a group that owns the table, the schema owner, or a database superuser.
+
+<div class="toctree" maxdepth="3">
+
+example_emptying_a_table
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/01_example_emptying_a_partition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/01_example_emptying_a_partition.mdx
new file mode 100644
index 00000000000..65e551a01ee
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/01_example_emptying_a_partition.mdx
@@ -0,0 +1,116 @@
+---
+title: "Example: Emptying a partition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/01_example_emptying_a_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_emptying_a_partition" class="registered_link"></div>
+
+This example removes the data from a partition of the `sales` table. 
+
+Create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY LIST(country)
+(
+  PARTITION europe VALUES('FRANCE', 'ITALY'),
+  PARTITION asia VALUES('INDIA', 'PAKISTAN'),
+  PARTITION americas VALUES('US', 'CANADA')
+);
+```
+
+Populate the `sales` table:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2012', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2012', '50000'),
+  (30, '9519b', 'CANADA', '01-Feb-2012', '75000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2012', '4950'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (10, '9519a', 'FRANCE', '18-Aug-2012', '650000'),
+  (10, '9519b', 'FRANCE', '18-Aug-2012', '650000'),
+  (20, '3788b', 'INDIA', '21-Sept-2012', '5090'),
+  (40, '4788a', 'US', '23-Sept-2012', '4950'),
+  (40, '4788b', 'US', '09-Oct-2012', '15000'),
+  (20, '4519a', 'INDIA', '18-Oct-2012', '650000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+Query the `sales` table to show that the partitions are populated with data:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid    | dept_no | part_no | country  |        date        | amount
+----------------+---------+---------+----------+--------------------+--------
+ sales_americas |      40 | 9519b   | US       | 12-APR-12 00:00:00 | 145000
+ sales_americas |      40 | 4577b   | US       | 11-NOV-12 00:00:00 |  25000
+ sales_americas |      30 | 7588b   | CANADA   | 14-DEC-12 00:00:00 |  50000
+ sales_americas |      30 | 9519b   | CANADA   | 01-FEB-12 00:00:00 |  75000
+ sales_americas |      30 | 4519b   | CANADA   | 08-APR-12 00:00:00 | 120000
+ sales_americas |      40 | 3788a   | US       | 12-MAY-12 00:00:00 |   4950
+ sales_americas |      40 | 4788a   | US       | 23-SEP-12 00:00:00 |   4950
+ sales_americas |      40 | 4788b   | US       | 09-OCT-12 00:00:00 |  15000
+ sales_europe   |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe   |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe   |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe   |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia     |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia     |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia     |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia     |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia     |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(17 rows)
+```
+
+Delete the contents of the `americas` partition:
+
+```sql
+ALTER TABLE sales TRUNCATE PARTITION americas;
+```
+
+Query the `sales` table to show that the contents of the `americas` partition were removed:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+   tableoid   | dept_no | part_no | country  |        date        | amount
+--------------+---------+---------+----------+--------------------+--------
+ sales_europe |      10 | 4519b   | FRANCE   | 17-JAN-12 00:00:00 |  45000
+ sales_europe |      10 | 9519b   | ITALY    | 07-JUL-12 00:00:00 |  15000
+ sales_europe |      10 | 9519a   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_europe |      10 | 9519b   | FRANCE   | 18-AUG-12 00:00:00 | 650000
+ sales_asia   |      20 | 3788a   | INDIA    | 01-MAR-12 00:00:00 |  75000
+ sales_asia   |      20 | 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |  37500
+ sales_asia   |      20 | 3788b   | INDIA    | 21-SEP-12 00:00:00 |   5090
+ sales_asia   |      20 | 4519a   | INDIA    | 18-OCT-12 00:00:00 | 650000
+ sales_asia   |      20 | 4519b   | INDIA    | 02-DEC-12 00:00:00 |   5090
+(9 rows)
+```
+
+The rows were removed, but the structure of the `americas` partition is intact:
+
+```sql
+edb=# SELECT partition_name, high_value FROM ALL_TAB_PARTITIONS;
+__OUTPUT__
+ partition_name |     high_value
+----------------+---------------------
+ EUROPE         | 'FRANCE', 'ITALY'
+ ASIA           | 'INDIA', 'PAKISTAN'
+ AMERICAS       | 'US', 'CANADA'
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/index.mdx
new file mode 100644
index 00000000000..aa2e3a683a1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/index.mdx
@@ -0,0 +1,45 @@
+---
+title: "ALTER TABLE...TRUNCATE PARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.116.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.341.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.065.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/16_alter_table_truncate_partition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_truncate_partition" class="registered_link"></div>
+
+Use the `ALTER TABLE… TRUNCATE PARTITION` command to remove the data from the specified partition and leave the partition structure intact. The syntax is:
+
+```sql
+ALTER TABLE <table_name> TRUNCATE PARTITION <partition_name>
+  [{DROP|REUSE} STORAGE]
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`partition_name`
+
+ The name of the partition to delete.
+
+## Description
+
+Use the `ALTER TABLE… TRUNCATE PARTITION` command to remove the data from the specified partition and leave the partition structure intact. Truncating a partition also truncates its subpartitions.
+
+`ALTER TABLE… TRUNCATE PARTITION` doesn't cause `ON DELETE` triggers for the table to fire, but it fires `ON TRUNCATE` triggers. If an `ON TRUNCATE` trigger is defined for the partition, all `BEFORE TRUNCATE` triggers are fired before any truncation happens. All `AFTER TRUNCATE` triggers are fired after the last truncation occurs.
+
+You must have the `TRUNCATE` privilege on a table to invoke `ALTER TABLE… TRUNCATE PARTITION`.
+
+`DROP STORAGE` and `REUSE STORAGE` are included only for compatibility. The clauses are parsed and ignored.
+
+<div class="toctree" maxdepth="3">
+
+example_emptying_a_partition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/01_example_emptying_a_subpartition.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/01_example_emptying_a_subpartition.mdx
new file mode 100644
index 00000000000..cebded0a6bf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/01_example_emptying_a_subpartition.mdx
@@ -0,0 +1,126 @@
+---
+title: "Example: Emptying a subpartition"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/01_example_emptying_a_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="example_emptying_a_subpartition" class="registered_link"></div>
+
+This example removes the data from a subpartition of the `sales` table. 
+
+Create the `sales` table:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date) SUBPARTITION BY LIST (country)
+(
+  PARTITION "2011" VALUES LESS THAN('01-JAN-2012')
+  (
+    SUBPARTITION europe_2011 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2011 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2011 VALUES ('US', 'CANADA')
+  ),
+  PARTITION "2012" VALUES LESS THAN('01-JAN-2013')
+  (
+    SUBPARTITION europe_2012 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2012 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2012 VALUES ('US', 'CANADA')
+  ),
+  PARTITION "2013" VALUES LESS THAN('01-JAN-2015')
+  (
+    SUBPARTITION europe_2013 VALUES ('ITALY', 'FRANCE'),
+    SUBPARTITION asia_2013 VALUES ('PAKISTAN', 'INDIA'),
+    SUBPARTITION americas_2013 VALUES ('US', 'CANADA')
+  )
+);
+```
+
+Populate the `sales` table:
+
+```sql
+INSERT INTO sales VALUES
+  (10, '4519b', 'FRANCE', '17-Jan-2011', '45000'),
+  (20, '3788a', 'INDIA', '01-Mar-2012', '75000'),
+  (40, '9519b', 'US', '12-Apr-2012', '145000'),
+  (20, '3788a', 'PAKISTAN', '04-Jun-2012', '37500'),
+  (40, '4577b', 'US', '11-Nov-2012', '25000'),
+  (30, '7588b', 'CANADA', '14-Dec-2011', '50000'),
+  (30, '4519b', 'CANADA', '08-Apr-2012', '120000'),
+  (40, '3788a', 'US', '12-May-2011', '4950'),
+  (20, '3788a', 'US', '04-Apr-2012', '37500'),
+  (40, '4577b', 'INDIA', '11-Jun-2011', '25000'),
+  (10, '9519b', 'ITALY', '07-Jul-2012', '15000'),
+  (20, '4519b', 'INDIA', '2-Dec-2012', '5090');
+```
+
+Query the `sales` table to show that the rows were distributed among the subpartitions:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+    tableoid       | dept_no| part_no | country|        date        | amount
+-------------------+--------+---------+--------+--------------------+--------
+sales_americas_2011|      30| 7588b   | CANADA | 14-DEC-11 00:00:00 | 50000
+sales_americas_2011|      40| 3788a   | US     | 12-MAY-11 00:00:00 | 4950
+sales_europe_2011  |      10| 4519b   | FRANCE | 17-JAN-11 00:00:00 | 45000
+sales_asia_2011    |      40| 4577b   | INDIA  | 11-JUN-11 00:00:00 | 25000
+sales_americas_2012|      40| 9519b   | US     | 12-APR-12 00:00:00 |145000
+sales_americas_2012|      40| 4577b   | US     | 11-NOV-12 00:00:00 | 25000
+sales_americas_2012|      30| 4519b   | CANADA | 08-APR-12 00:00:00 |120000
+sales_americas_2012|      20| 3788a   | US     | 04-APR-12 00:00:00 | 37500
+sales_europe_2012  |      10| 9519b   | ITALY  | 07-JUL-12 00:00:00 | 15000
+sales_asia_2012    |      20| 3788a   | INDIA  | 01-MAR-12 00:00:00 | 75000
+sales_asia_2012    |      20| 3788a   |PAKISTAN| 04-JUN-12 00:00:00 | 37500
+sales_asia_2012    |      20| 4519b   | INDIA  | 02-DEC-12 00:00:00 | 5090
+(12 rows)
+```
+
+Delete the contents of the `2012_americas` partition:
+
+```sql
+ALTER TABLE sales TRUNCATE SUBPARTITION "americas_2012";
+```
+
+Query the `sales` table to show that the contents of the `americas_2012` partition were removed:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales;
+__OUTPUT__
+ tableoid          | dept_no| part_no | country  |        date        |amount
+-------------------+--------+---------+----------+--------------------+------
+sales_americas_2011|      30| 7588b   | CANADA   | 14-DEC-11 00:00:00 |50000
+sales_americas_2011|      40| 3788a   | US       | 12-MAY-11 00:00:00 | 4950
+sales_europe_2011  |      10| 4519b   | FRANCE   | 17-JAN-11 00:00:00 |45000
+sales_asia_2011    |      40| 4577b   | INDIA    | 11-JUN-11 00:00:00 |25000
+sales_europe_2012  |      10| 9519b   | ITALY    | 07-JUL-12 00:00:00 |15000
+sales_asia_2012    |      20| 3788a   | INDIA    | 01-MAR-12 00:00:00 |75000
+sales_asia_2012    |      20| 3788a   | PAKISTAN | 04-JUN-12 00:00:00 |37500
+sales_asia_2012    |      20| 4519b   | INDIA    | 02-DEC-12 00:00:00 | 5090
+(8 rows)
+```
+
+The rows were removed, but the structure of the `2012_americas` partition is intact:
+
+```sql
+edb=# SELECT subpartition_name, high_value FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value
+-------------------+---------------------
+ EUROPE_2011       | 'ITALY', 'FRANCE'
+ ASIA_2011         | 'PAKISTAN', 'INDIA'
+ AMERICAS_2011     | 'US', 'CANADA'
+ EUROPE_2012       | 'ITALY', 'FRANCE'
+ ASIA_2012         | 'PAKISTAN', 'INDIA'
+ AMERICAS_2012     | 'US', 'CANADA'
+ EUROPE_2013       | 'ITALY', 'FRANCE'
+ ASIA_2013         | 'PAKISTAN', 'INDIA'
+ AMERICAS_2013     | 'US', 'CANADA'
+(9 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/index.mdx
new file mode 100644
index 00000000000..5c41a290c06
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/index.mdx
@@ -0,0 +1,46 @@
+---
+title: "ALTER TABLE...TRUNCATE SUBPARTITION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.117.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.342.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.066.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/17_alter_table_truncate_subpartition/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table_truncate_subpartition" class="registered_link"></div>
+
+Use the `ALTER TABLE… TRUNCATE SUBPARTITION` command to remove all of the data from the specified subpartition and leave the subpartition structure intact. The syntax is:
+
+```sql
+ALTER TABLE <table_name>
+  TRUNCATE SUBPARTITION <subpartition_name>
+  [{DROP|REUSE} STORAGE]
+```
+
+## Parameters
+
+`table_name`
+
+ The name (optionally schema-qualified) of the partitioned table.
+
+`subpartition_name`
+
+ The name of the subpartition to truncate.
+
+## Description
+
+The `ALTER TABLE… TRUNCATE SUBPARTITION` command removes all data from a specified subpartition, leaving the subpartition structure intact.
+
+`ALTER TABLE… TRUNCATE SUBPARTITION` doesn't cause `ON DELETE` triggers for the table to fire, but it fires `ON TRUNCATE` triggers. If an `ON TRUNCATE` trigger is defined for the subpartition, all `BEFORE TRUNCATE` triggers are fired before any truncation happens. All `AFTER TRUNCATE` triggers are fired after the last truncation occurs.
+
+You must have the `TRUNCATE` privilege on a table to invoke `ALTER TABLE… TRUNCATE SUBPARTITION`.
+
+The `DROP STORAGE` and `REUSE STORAGE` clauses are included only for compatibility. The clauses are parsed and ignored.
+
+<div class="toctree" maxdepth="3">
+
+example_emptying_a_subpartition
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/18_accessing_partition_table/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/18_accessing_partition_table/index.mdx
new file mode 100644
index 00000000000..eb8ccf27b8f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/18_accessing_partition_table/index.mdx
@@ -0,0 +1,257 @@
+---
+title: "Accessing a PARTITION or SUBPARTITION"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/18_accessing_partition_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="accessing_partition_table" class="registered_link"></div>
+
+For a partitioned table, you can access the partition or subpartition using `PARTITION part_name` or `SUBPARTITION subpart_name`. This example creates a partitioned table `sales` that's range partitioned by `date` and subpartitioned using list partitioning by the `country` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST(country)
+(
+  PARTITION q1_2020 
+    VALUES LESS THAN('2020-Apr-01')
+    (
+      SUBPARTITION q1_europe VALUES ('FRANCE', 'ITALY'),
+      SUBPARTITION q1_asia VALUES ('INDIA', 'PAKISTAN'),
+      SUBPARTITION q1_americas VALUES ('US', 'CANADA')
+    ), 
+  PARTITION q2_2020 
+    VALUES LESS THAN('2020-Jul-01')
+    (
+      SUBPARTITION q2_europe VALUES ('FRANCE', 'ITALY'),
+      SUBPARTITION q2_asia VALUES ('INDIA', 'PAKISTAN'),
+      SUBPARTITION q2_americas VALUES ('US', 'CANADA')
+    )
+);
+``` 
+
+The `SELECT` statement shows two partitions. Each partition has three subpartitions.
+
+```sql
+edb=# SELECT subpartition_name, high_value, partition_name FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value      | partition_name 
+-------------------+---------------------+----------------
+ Q1_EUROPE         | 'FRANCE', 'ITALY'   | Q1_2020
+ Q1_ASIA           | 'INDIA', 'PAKISTAN' | Q1_2020
+ Q1_AMERICAS       | 'US', 'CANADA'      | Q1_2020
+ Q2_EUROPE         | 'FRANCE', 'ITALY'   | Q2_2020
+ Q2_ASIA           | 'INDIA', 'PAKISTAN' | Q2_2020
+ Q2_AMERICAS       | 'US', 'CANADA'      | Q2_2020
+(6 rows)
+```
+
+This `INSERT` statement inserts rows into the `sales` table using specific `PARTITION part_name` or `SUBPARTITION subpart_name` values:
+
+```sql
+INSERT INTO sales PARTITION (q1_2020) VALUES (10, 'q1_2020', 'FRANCE', '2020-Feb-01', '500000');
+INSERT INTO sales PARTITION (q2_2020) VALUES (10, 'q2_2020', 'ITALY', '2020-Apr-01', '550000');
+INSERT INTO sales SUBPARTITION (q1_europe) VALUES (10, 'q1_europe', 'FRANCE', '2020-Feb-01', '600000');
+INSERT INTO sales SUBPARTITION (q2_asia) VALUES (10, 'q2_asia', 'INDIA', '2020-Apr-01', '650000');
+
+edb=# SELECT tableoid::regclass, * FROM sales ORDER BY date;
+__OUTPUT__
+    tableoid     | dept_no |  part_no  | country |        date        | amount 
+-----------------+---------+-----------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_2020   | FRANCE  | 01-FEB-20 00:00:00 | 500000
+ sales_q1_europe |      10 | q1_europe | FRANCE  | 01-FEB-20 00:00:00 | 600000
+ sales_q2_europe |      10 | q2_2020   | ITALY   | 01-APR-20 00:00:00 | 550000
+ sales_q2_asia   |      10 | q2_asia   | INDIA   | 01-APR-20 00:00:00 | 650000
+(4 rows)
+```
+
+Use this query to fetch the values from a specific partition `q1_2020` or subpartition `q1_europe`:
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales PARTITION (q1_2020) ORDER BY date;
+    tableoid     | dept_no |  part_no  | country |        date        | amount 
+-----------------+---------+-----------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_2020   | FRANCE  | 01-FEB-20 00:00:00 | 500000
+ sales_q1_europe |      10 | q1_europe | FRANCE  | 01-FEB-20 00:00:00 | 600000
+(2 rows)
+
+edb=# SELECT tableoid::regclass, country FROM sales SUBPARTITION (q1_europe) ORDER BY date;
+    tableoid     | country 
+-----------------+---------
+ sales_q1_europe | FRANCE
+ sales_q1_europe | FRANCE
+(2 rows)
+```
+
+This `SELECT` statement selects rows from a specific partition or subpartition of a partitioned table by specifying the keyword `PARTITION` or `SUBPARTITION`: 
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales PARTITION (q2_2020) ORDER BY country;
+__OUTPUT__
+    tableoid     | dept_no | part_no | country |        date        | amount 
+-----------------+---------+---------+---------+--------------------+--------
+ sales_q2_asia   |      10 | q2_asia | INDIA   | 01-APR-20 00:00:00 | 650000
+ sales_q2_europe |      10 | q2_2020 | ITALY   | 01-APR-20 00:00:00 | 550000
+(2 rows)
+```
+```sql
+edb=# SELECT tableoid::regclass, date FROM sales SUBPARTITION (q2_asia) ORDER BY country;
+__OUTPUT__
+   tableoid    |        date        
+---------------+--------------------
+ sales_q2_asia | 01-APR-20 00:00:00
+(1 row)
+```
+
+This `UPDATE` statement updates values in a partition or subpartition of the `sales` table:
+
+```sql
+edb=# UPDATE sales PARTITION (q1_2020) SET amount = 10000 WHERE amount = 500000 RETURNING tableoid::regclass, *;
+__OUTPUT__
+    tableoid     | dept_no | part_no | country |        date        | amount 
+-----------------+---------+---------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_2020 | FRANCE  | 01-FEB-20 00:00:00 |  10000
+(1 row)
+
+UPDATE 1
+```
+```sql
+edb=# UPDATE sales SUBPARTITION (q1_europe) SET amount = 5000 WHERE amount = 600000 RETURNING tableoid::regclass, *;
+__OUTPUT__
+    tableoid     | dept_no |  part_no  | country |        date        | amount 
+-----------------+---------+-----------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_europe | FRANCE  | 01-FEB-20 00:00:00 |   5000
+(1 row)
+
+UPDATE 1
+```
+
+This `DELETE` statement removes rows from the partition `q2_2020` or subpartition `q2_asia` of the `sales` table:
+
+```sql
+edb=# DELETE FROM sales PARTITION (q2_2020) WHERE amount = 550000 RETURNING tableoid::regclass, *;
+__OUTPUT__
+    tableoid     | dept_no | part_no | country |        date        | amount 
+-----------------+---------+---------+---------+--------------------+--------
+ sales_q2_europe |      10 | q2_2020 | ITALY   | 01-APR-20 00:00:00 | 550000
+(1 row)
+
+DELETE 1
+```
+```sql
+edb=# DELETE FROM sales SUBPARTITION (q2_asia) RETURNING tableoid::regclass, *;
+__OUTPUT__
+   tableoid    | dept_no | part_no | country |        date        | amount 
+---------------+---------+---------+---------+--------------------+--------
+ sales_q2_asia |      10 | q2_asia | INDIA   | 01-APR-20 00:00:00 | 650000
+(1 row)
+
+DELETE 1
+```
+
+## Using alias for accessing PARTITION or SUBPARTITION
+
+You can use aliases with `SELECT`, `INSERT`, `UPDATE`, or `DELETE` statements to access a partition or subpartition. This example creates a partitioned table `sales` that's range partitioned by date and subpartitioned using list partitioning by the `country` column:
+
+```sql
+CREATE TABLE sales
+(
+  dept_no     number,
+  part_no     varchar2,
+  country     varchar2(20),
+  date        date,
+  amount      number
+)
+PARTITION BY RANGE(date)
+  SUBPARTITION BY LIST(country)
+(
+  PARTITION q1_2020 
+    VALUES LESS THAN('2020-Apr-01')
+    (
+      SUBPARTITION q1_europe VALUES ('FRANCE', 'ITALY'),
+      SUBPARTITION q1_asia VALUES ('INDIA', 'PAKISTAN'),
+      SUBPARTITION q1_americas VALUES ('US', 'CANADA')
+    ), 
+  PARTITION q2_2020 
+    VALUES LESS THAN('2020-Jul-01')
+    (
+      SUBPARTITION q2_europe VALUES ('FRANCE', 'ITALY'),
+      SUBPARTITION q2_asia VALUES ('INDIA', 'PAKISTAN'),
+      SUBPARTITION q2_americas VALUES ('US', 'CANADA')
+    )
+);
+```
+
+The `SELECT` statement shows two partitions. Each partition has three subpartitions.
+
+```sql
+edb=# SELECT subpartition_name, high_value, partition_name FROM ALL_TAB_SUBPARTITIONS;
+__OUTPUT__
+ subpartition_name |     high_value      | partition_name 
+-------------------+---------------------+----------------
+ Q1_EUROPE         | 'FRANCE', 'ITALY'   | Q1_2020
+ Q1_ASIA           | 'INDIA', 'PAKISTAN' | Q1_2020
+ Q1_AMERICAS       | 'US', 'CANADA'      | Q1_2020
+ Q2_EUROPE         | 'FRANCE', 'ITALY'   | Q2_2020
+ Q2_ASIA           | 'INDIA', 'PAKISTAN' | Q2_2020
+ Q2_AMERICAS       | 'US', 'CANADA'      | Q2_2020
+(6 rows)
+```
+
+This `INSERT` statement creates an alias of the `sales` table and inserts rows into partition `q1_2020` and `q2_2020` or subpartition `q1_europe` and `q1_asia`:
+
+```sql
+INSERT INTO sales PARTITION (q1_2020) AS q1_sales VALUES (10, 'q1_2020', 'FRANCE', '2020-Feb-01', '500000');
+INSERT INTO sales PARTITION (q2_2020) q2_sales (q2_sales.dept_no, q2_sales.part_no, q2_sales.country, q2_sales.date, q2_sales.amount) VALUES (20, 'q2_2020', 'ITALY', '2020-Apr-01', '550000');
+INSERT INTO sales SUBPARTITION (q1_europe) AS sales_q1_europe VALUES (10, 'q1_europe', 'FRANCE', '2020-Feb-01', '600000');
+INSERT INTO sales SUBPARTITION (q1_asia) sales_q1_asia (sales_q1_asia.dept_no, sales_q1_asia.part_no, sales_q1_asia.country, sales_q1_asia.date, sales_q1_asia.amount) VALUES (20, 'q1_asia', 'INDIA', '2020-Mar-01', '650000');
+```
+
+This `SELECT` statement selects rows from a specific partition or subpartition of a `sales` table: 
+
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales PARTITION (q1_2020) AS q1_sales ORDER BY country;
+__OUTPUT__
+    tableoid     | dept_no |  part_no  | country |        date        | amount 
+-----------------+---------+-----------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_2020   | FRANCE  | 01-FEB-20 00:00:00 | 500000
+ sales_q1_europe |      10 | q1_europe | FRANCE  | 01-FEB-20 00:00:00 | 600000
+ sales_q1_asia   |      20 | q1_asia   | INDIA   | 01-MAR-20 00:00:00 | 650000
+(3 rows)
+```
+```sql
+edb=# SELECT tableoid::regclass, * FROM sales SUBPARTITION (q1_europe) sales_q1_europe ORDER BY country;
+__OUTPUT__
+    tableoid     | dept_no |  part_no  | country |        date        | amount 
+-----------------+---------+-----------+---------+--------------------+--------
+ sales_q1_europe |      10 | q1_2020   | FRANCE  | 01-FEB-20 00:00:00 | 500000
+ sales_q1_europe |      10 | q1_europe | FRANCE  | 01-FEB-20 00:00:00 | 600000
+(2 rows)
+```
+
+This `UPDATE` statement updates values in a partition or subpartition of the `sales` table:
+
+```sql
+edb=# UPDATE sales PARTITION (q1_2020) AS q1_sales SET q1_sales.amount = 10000 WHERE q1_sales.amount = 500000;
+UPDATE 1
+
+edb=# UPDATE sales SUBPARTITION (q1_europe) sales_q1_europe SET sales_q1_europe.amount = 5000 WHERE sales_q1_europe.amount = 600000;
+UPDATE 1
+```
+
+This `DELETE` statement removes rows from the partition `q1_2020` or subpartition `q1_europe` of the `sales` table:
+
+```sql
+edb=# DELETE FROM sales PARTITION (q1_2020) q1_sales WHERE q1_sales.amount = 10000;
+DELETE 1
+
+edb=# DELETE FROM sales SUBPARTITION (q1_europe) AS sales_q1_europe WHERE sales_q1_europe.amount = 5000;
+DELETE 1
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/index.mdx
new file mode 100644
index 00000000000..0c2bd6bb9be
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/index.mdx
@@ -0,0 +1,21 @@
+---
+title: "Partitioning commands compatible with Oracle Databases"
+indexCards: simple
+description: "Listing of table partitioning syntaxes that are compatible with Oracle databases"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.104.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.329.html"
+redirects:
+  - /epas/latest/epas_compat_table_partitioning/04_partitioning_commands_compatible_with_oracle_databases/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="partitioning_commands_compatible_with_oracle_databases" class="registered_link"></div>
+
+EDB Postgres Advanced Server supports using table partitioning syntaxes that are compatible with Oracle databases. 
+
+<div class="toctree" maxdepth="4">
+
+create_table_partition_by alter_table_add_partition alter_table_add_subpartition alter_table_split_partition alter_table_split_subpartition alter_table_exchange_partition alter_table_move_partition alter_table_rename_partition alter_table_set_interval alter_table_set_partitioning_automatic alter_table_set_subpartition_template drop_table alter_table_drop_partition alter_table_drop_subpartition truncate_table alter_table_truncate_partition alter_table_truncate_subpartition accessing_partition_table
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/limitations.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/limitations.mdx
new file mode 100644
index 00000000000..9c7eaf63abd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/04_partitioning_commands_compatible_with_oracle_databases/limitations.mdx
@@ -0,0 +1,39 @@
+---
+title: "Limitations for partitioning commands compatible with Oracle databases"
+indexCards: simple
+navTitle: Limitations
+---
+
+## Limitations for primary or unique keys
+
+For Oracle compatibility, EDB Postgres Advanced Server allows you to use a `CREATE TABLE` statement to create a unique or primary key constraint on a partitioned table that includes a non-partitioned key column. This capability differs from PostgreSQL, and it has the following limitations:
+
+- The primary or unique key is created only on a child table. The key isn't created on a parent or root table.
+
+- When using an `ALTER` statement to create a new partition, the primary or unique key isn't created automatically. You must create it manually.
+
+- The uniqueness of the key is limited to the child partition. The unique key doesn't apply across the partitioning hierarchy. 
+
+## Interval partitioning limitations
+
+Interval range partitioning is a useful capability, but it has the following limitations: 
+
+- Interval partitioning is restricted to a single partition key. If you try to create or alter an existing partitioned table having a multi-column partitioned key, it fails.
+
+- The supported key must be a numerical or date range type.
+
+- You can't define `DEFAULT` and `MAXVALUE` for an interval-partitioned table.
+
+- Data to insert can't have `NULL`, `Not-a-Number`, or `Infinity` values specified in the partitioning key column.
+
+- The interval-partitioning expression must yield a constant value and can't be a negative value.
+
+- For the interval-partitioned table, define at least one partition first.
+
+## Automatic partitioning limitations
+
+Automatic list partitioning has the following limitations:
+
+- Like interval partitioning, automatic partitioning is restricted to a single partition key.
+
+- An automatic partitioned table can't have a `DEFAULT` partition.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx
new file mode 100644
index 00000000000..434aa533aab
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert.mdx
@@ -0,0 +1,398 @@
+---
+title: "DBMS_ALERT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.12.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.190.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.148.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/01_dbms_alert/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_ALERT` package lets you register for, send, and receive alerts. The following table lists the supported procedures:
+
+| Function/procedure                                    | Return type | Description                                         |
+| ----------------------------------------------------- | ----------- | --------------------------------------------------- |
+| `REGISTER(name)`                                      | n/a         | Register to be able to receive alerts named `name`. |
+| `REMOVE(name)`                                        | n/a         | Remove registration for the alert named `name`.     |
+| `REMOVEALL`                                           | n/a         | Remove registration for all alerts.                 |
+| `SIGNAL(name, message)`                               | n/a         | Signal the alert named `name` with `message`.     |
+| `WAITANY(name OUT, message OUT, status OUT, timeout)` | n/a         | Wait for any registered alert to occur.             |
+| `WAITONE(name, message OUT, status OUT, timeout)`     | n/a         | Wait for the specified alert, `name`, to occur.     |
+
+EDB Postgres Advanced Server's implementation of `DBMS_ALERT` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+EDB Postgres Advanced Server allows a maximum of 500 concurrent alerts. You can use the `dbms_alert.max_alerts` GUC variable, located in the `postgresql.conf` file, to specify the maximum number of concurrent alerts allowed on a system.
+
+To set a value for the `dbms_alert.max_alerts` variable, open the `postgresql.conf` file, which is located by default in `/opt/PostgresPlus/14AS/data`, with your choice of editor. Edit the `dbms_alert.max_alerts` parameter as shown:
+
+```ini
+dbms_alert.max_alerts = alert_count
+```
+
+`alert_count`
+
+`alert_count` specifies the maximum number of concurrent alerts. By default, the value of `dbms_alert.max_alerts` is `100`. To disable this feature, set `dbms_alert.max_alerts` to `0`.
+
+For the `dbms_alert.max_alerts` GUC to function correctly, the `custom_variable_classes` parameter must contain `dbms_alerts`:
+
+```ini
+custom_variable_classes = 'dbms_alert, …'
+```
+
+After editing the `postgresql.conf` file parameters, you must restart the server for the changes to take effect.
+
+## REGISTER
+
+The `REGISTER` procedure enables the current session to be notified of the specified alert.
+
+```sql
+REGISTER(<name> VARCHAR2)
+```
+
+### Parameters
+
+`name`
+
+ Name of the alert to register.
+
+### Examples
+
+This anonymous block registers for an alert named `alert_test` and then waits for the signal.
+
+```sql
+DECLARE
+    v_name           VARCHAR2(30) := 'alert_test';
+    v_msg            VARCHAR2(80);
+    v_status         INTEGER;
+    v_timeout        NUMBER(3) := 120;
+BEGIN
+    DBMS_ALERT.REGISTER(v_name);
+    DBMS_OUTPUT.PUT_LINE('Registered for alert ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
+    DBMS_ALERT.WAITONE(v_name,v_msg,v_status,v_timeout);
+    DBMS_OUTPUT.PUT_LINE('Alert name   : ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Alert msg    : ' || v_msg);
+    DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
+    DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
+    DBMS_ALERT.REMOVE(v_name);
+END;
+
+Registered for alert alert_test
+Waiting for signal...
+```
+
+## REMOVE
+
+The `REMOVE` procedure unregisters the session for the named alert.
+
+```sql
+REMOVE(<name> VARCHAR2)
+```
+
+### Parameters
+
+`name`
+
+ Name of the alert to unregister.
+
+## REMOVEALL
+
+The `REMOVEALL` procedure unregisters the session for all alerts.
+
+```sql
+REMOVEALL
+```
+
+## SIGNAL
+
+The `SIGNAL` procedure signals the occurrence of the named alert.
+
+```sql
+SIGNAL(<name> VARCHAR2, <message> VARCHAR2)
+```
+
+### Parameters
+
+`name`
+
+ Name of the alert.
+
+`message`
+
+ Information to pass with this alert.
+
+### Examples
+
+This anonymous block signals an alert for `alert_test`.
+
+```sql
+DECLARE
+    v_name   VARCHAR2(30) := 'alert_test';
+BEGIN
+    DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
+END;
+Issued alert for alert_test
+```
+
+## WAITANY
+
+The `WAITANY` procedure waits for any of the registered alerts to occur.
+
+```sql
+WAITANY(<name> OUT VARCHAR2, <message> OUT VARCHAR2,
+  <status> OUT INTEGER, <timeout> NUMBER)
+```
+
+### Parameters
+
+`name`
+
+ Variable receiving the name of the alert.
+
+`message`
+
+ Variable receiving the message sent by the `SIGNAL` procedure.
+
+`status`
+
+ Status code returned by the operation. Possible values are: `0` – alert occurred; `1` – timeout occurred.
+
+`timeout`
+
+ Time to wait for an alert in seconds.
+
+### Examples
+
+This anonymous block uses the `WAITANY` procedure to receive an alert named `alert_test` or `any_alert`:
+
+```sql
+DECLARE
+    v_name           VARCHAR2(30);
+    v_msg            VARCHAR2(80);
+    v_status         INTEGER;
+    v_timeout        NUMBER(3) := 120;
+BEGIN
+    DBMS_ALERT.REGISTER('alert_test');
+    DBMS_ALERT.REGISTER('any_alert');
+    DBMS_OUTPUT.PUT_LINE('Registered for alert alert_test and any_alert');
+    DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
+    DBMS_ALERT.WAITANY(v_name,v_msg,v_status,v_timeout);
+    DBMS_OUTPUT.PUT_LINE('Alert name   : ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Alert msg    : ' || v_msg);
+    DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
+    DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
+    DBMS_ALERT.REMOVEALL;
+END;
+
+Registered for alert alert_test and any_alert
+Waiting for signal...
+```
+
+An anonymous block in a second session issues a signal for `any_alert`:
+
+```sql
+DECLARE
+    v_name   VARCHAR2(30) := 'any_alert';
+BEGIN
+    DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
+END;
+
+Issued alert for any_alert
+```
+
+Control returns to the first anonymous block and the remainder of the code is executed:
+
+```text
+Registered for alert alert_test and any_alert
+Waiting for signal...
+Alert name   : any_alert
+Alert msg    : This is the message from any_alert
+Alert status : 0
+Alert timeout: 120 seconds
+```
+
+## WAITONE
+
+The `WAITONE` procedure waits for the specified registered alert to occur.
+
+```sql
+WAITONE(<name> VARCHAR2, <message> OUT VARCHAR2,
+  <status> OUT INTEGER, <timeout> NUMBER)
+```
+
+### Parameters
+
+`name`
+
+ Name of the alert.
+
+`message`
+
+ Variable receiving the message sent by the `SIGNAL` procedure.
+
+`status`
+
+ Status code returned by the operation. Possible values are: `0` – alert occurred; `1` – timeout occurred.
+
+`timeout`
+
+ Time to wait for an alert in seconds.
+
+### Examples
+
+This anonymous block is similar to the one used in the `WAITANY` example except the `WAITONE` procedure is used to receive the alert named `alert_test`.
+
+```sql
+DECLARE
+    v_name           VARCHAR2(30) := 'alert_test';
+    v_msg            VARCHAR2(80);
+    v_status         INTEGER;
+    v_timeout        NUMBER(3) := 120;
+BEGIN
+    DBMS_ALERT.REGISTER(v_name);
+    DBMS_OUTPUT.PUT_LINE('Registered for alert ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
+    DBMS_ALERT.WAITONE(v_name,v_msg,v_status,v_timeout);
+    DBMS_OUTPUT.PUT_LINE('Alert name   : ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Alert msg    : ' || v_msg);
+    DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
+    DBMS_OUTPUT.PUT_LINE('Alert timeout: ' || v_timeout || ' seconds');
+    DBMS_ALERT.REMOVE(v_name);
+END; 
+
+Registered for alert alert_test
+Waiting for signal...
+```
+
+Signal sent for `alert_test` sent by an anonymous block in a second session:
+
+```sql
+DECLARE
+    v_name   VARCHAR2(30) := 'alert_test';
+BEGIN
+    DBMS_ALERT.SIGNAL(v_name,'This is the message from ' || v_name);
+    DBMS_OUTPUT.PUT_LINE('Issued alert for ' || v_name);
+END;
+
+Issued alert for alert_test
+```
+
+First session is alerted, control returns to the anonymous block, and the remainder of the code is executed:
+
+```text
+Registered for alert alert_test
+Waiting for signal...
+Alert name   : alert_test
+Alert msg    : This is the message from alert_test
+Alert status : 0
+Alert timeout: 120 seconds
+```
+
+## Comprehensive example
+
+The following example uses two triggers to send alerts when the `dept` table or the `emp` table is changed. An anonymous block listens for these alerts and displays messages when an alert is received.
+
+The following are the triggers on the `dept` and `emp` tables:
+
+```sql
+CREATE OR REPLACE TRIGGER dept_alert_trig
+    AFTER INSERT OR UPDATE OR DELETE ON dept
+DECLARE
+    v_action        VARCHAR2(25);
+BEGIN
+    IF INSERTING THEN
+        v_action := ' added department(s) ';
+    ELSIF UPDATING THEN
+        v_action := ' updated department(s) ';
+    ELSIF DELETING THEN
+        v_action := ' deleted department(s) ';
+    END IF;
+    DBMS_ALERT.SIGNAL('dept_alert',USER || v_action || 'on ' ||
+        SYSDATE);
+END;
+
+CREATE OR REPLACE TRIGGER emp_alert_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+DECLARE
+    v_action        VARCHAR2(25);
+BEGIN
+    IF INSERTING THEN
+        v_action := ' added employee(s) ';
+    ELSIF UPDATING THEN
+        v_action := ' updated employee(s) ';
+    ELSIF DELETING THEN
+        v_action := ' deleted employee(s) ';
+    END IF;
+    DBMS_ALERT.SIGNAL('emp_alert',USER || v_action || 'on ' ||
+        SYSDATE);
+END;
+```
+
+This anonymous block is executed in a session while updates to the `dept` and `emp` tables occur in other sessions:
+
+```sql
+DECLARE
+    v_dept_alert     VARCHAR2(30) := 'dept_alert';
+    v_emp_alert      VARCHAR2(30) := 'emp_alert';
+    v_name           VARCHAR2(30);
+    v_msg            VARCHAR2(80);
+    v_status         INTEGER;
+    v_timeout        NUMBER(3) := 60;
+BEGIN
+    DBMS_ALERT.REGISTER(v_dept_alert);
+    DBMS_ALERT.REGISTER(v_emp_alert);
+    DBMS_OUTPUT.PUT_LINE('Registered for alerts dept_alert and emp_alert');
+    DBMS_OUTPUT.PUT_LINE('Waiting for signal...');
+    LOOP
+        DBMS_ALERT.WAITANY(v_name,v_msg,v_status,v_timeout);
+        EXIT WHEN v_status != 0;
+        DBMS_OUTPUT.PUT_LINE('Alert name   : ' || v_name);
+        DBMS_OUTPUT.PUT_LINE('Alert msg    : ' || v_msg);
+        DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
+        DBMS_OUTPUT.PUT_LINE('------------------------------------' ||
+            '-------------------------');
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Alert status : ' || v_status);
+    DBMS_ALERT.REMOVEALL;
+END;
+
+Registered for alerts dept_alert and emp_alert
+Waiting for signal...
+```
+
+The following changes are made by user, mary:
+
+```sql
+INSERT INTO dept VALUES (50,'FINANCE','CHICAGO');
+INSERT INTO emp (empno,ename,deptno) VALUES (9001,'JONES',50);
+INSERT INTO emp (empno,ename,deptno) VALUES (9002,'ALICE',50);
+```
+
+The following change is made by user, john:
+
+```sql
+INSERT INTO dept VALUES (60,'HR','LOS ANGELES');
+```
+
+The following is the output displayed by the anonymous block receiving the signals from the triggers:
+
+```text
+Registered for alerts dept_alert and emp_alert
+Waiting for signal...
+Alert name   : dept_alert
+Alert msg    : mary added department(s) on 25-OCT-07 16:41:01
+Alert status : 0
+-------------------------------------------------------------
+Alert name   : emp_alert
+Alert msg    : mary added employee(s) on 25-OCT-07 16:41:02
+Alert status : 0
+-------------------------------------------------------------
+Alert name   : dept_alert
+Alert msg    : john added department(s) on 25-OCT-07 16:41:22
+Alert status : 0
+-------------------------------------------------------------
+Alert status : 1
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx
new file mode 100644
index 00000000000..044c5c764de
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue.mdx
@@ -0,0 +1,118 @@
+---
+title: "ENQUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/01_enqueue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `ENQUEUE` procedure adds an entry to a queue. The signature is:
+
+```sql
+ENQUEUE(
+  <queue_name> IN VARCHAR2,
+  <enqueue_options> IN DBMS_AQ.ENQUEUE_OPTIONS_T,
+  <message_properties> IN DBMS_AQ.MESSAGE_PROPERTIES_T,
+  <payload> IN <type_name>,
+  <msgid> OUT RAW)
+```
+
+## Parameters
+
+`queue_name`
+
+ The name (optionally schema qualified) of an existing queue. If you omit the schema name, the server uses the schema specified in the `SEARCH_PATH`. Unlike Oracle, unquoted identifiers are converted to lower case before storing. To include special characters or use a case-sensitive name, enclose the name in double quotes.
+
+ For detailed information about creating a queue, see [DBMS_AQADM.CREATE_QUEUE](../03_dbms_aqadm/03_create_queue).
+
+`enqueue_options`
+
+  `enqueue_options` is a value of the type `enqueue_options_t`:
+
+```sql
+DBMS_AQ.ENQUEUE_OPTIONS_T IS RECORD(
+ visibility BINARY_INTEGER DEFAULT ON_COMMIT,
+ relative_msgid RAW(16) DEFAULT NULL,
+ sequence_deviation BINARY INTEGER DEFAULT NULL,
+ transformation VARCHAR2(61) DEFAULT NULL,
+ delivery_mode PLS_INTEGER NOT NULL DEFAULT PERSISTENT);
+```
+
+Currently, the only supported parameter values for `enqueue_options_t` are:
+
+| `visibility`         | `ON_COMMIT`. |
+| -------------------- | ------------ |
+| `delivery_mode`      | `PERSISTENT` |
+| `sequence_deviation` | `NULL`       |
+| `transformation`     | `NULL`       |
+| `relative_msgid`     | `NULL`       |
+
+`message_properties`
+
+ `message_properties` is a value of the type `message_properties_t`:
+
+```sql
+message_properties_t IS RECORD(
+  priority INTEGER,
+  delay INTEGER,
+  expiration INTEGER,
+  correlation CHARACTER VARYING(128) COLLATE pg_catalog.”C”,
+  attempts INTEGER,
+  recipient_list “AQ$_RECIPIENT_LIST_T”,
+  exception_queue CHARACTER VARYING(61) COLLATE pg_catalog.”C”,
+  enqueue_time TIMESTAMP WITHOUT TIME ZONE,
+  state INTEGER,
+  original_msgid BYTEA,
+  transaction_group CHARACTER VARYING(30) COLLATE pg_catalog.”C”,
+  delivery_mode INTEGER
+DBMS_AQ.PERSISTENT);
+```
+
+The supported values for `message_properties_t` are:
+
+|                     |                                                                                                                                                                                                                                                                                                                                                        |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `priority`          | If the queue table definition includes a `sort_list` that references `priority`, this parameter affects the order that messages are dequeued. A lower value indicates a higher dequeue priority.                                                                                                                                                       |
+| `delay`             | Specify the number of seconds to pass before a message is available for dequeueing or `NO_DELAY`.                                                                                                                                                                                                                                               |
+| `expiration`        | Use the expiration parameter to specify the number of seconds until a message expires.                                                                                                                                                                                                                                                                 |
+| `correlation`       | Use correlation to specify a message to associate with the entry. The default is `NULL`.                                                                                                                                                                                                                                                    |
+| `attempts`          | This is a system-maintained value that specifies the number of attempts to dequeue the message.                                                                                                                                                                                                                                                        |
+| `recipient_list`    | This parameter is not supported.                                                                                                                                                                                                                                                                                                                       |
+| `exception_queue`   | Use the `exception_queue` parameter to specify the name of an exception queue to which to move a message if it expires or is dequeued by a transaction that rolls back too many times.                                                                                                                                                           |
+| `enqueue_time`      | `enqueue_time` is the time the record was added to the queue. This value is provided by the system.                                                                                                                                                                                                                                                    |
+| `state`             | This parameter is maintained by DBMS_AQ. The state can be:<br /><br />`DBMS_AQ.WAITING` – The delay wasn't reached.<br /><br />`DBMS_AQ.READY` – The queue entry is ready for processing.<br /><br />`DBMS_AQ.PROCESSED` – The queue entry was processed.<br /><br />`DBMS_AQ.EXPIRED` – The queue entry was moved to the exception queue. |
+| `original_msgid`    | This parameter is accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                              |
+| `transaction_group` | This parameter is accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                              |
+| `delivery_mode`     | This parameter isn't supported. Specify a value of `DBMS_AQ.PERSISTENT`.                                                                                                                                                                                                                                                                              |
+
+`payload`
+
+ Use the `payload` parameter to provide the data to associate with the queue entry. The payload type must match the type specified when creating the corresponding queue table (see [DBMS_AQADM.CREATE_QUEUE_TABLE](../03_dbms_aqadm/04_create_queue_table)).
+
+`msgid`
+
+ Use the `msgid` parameter to retrieve a unique (system-generated) message identifier.
+
+## Example
+
+The following anonymous block calls `DBMS_AQ.ENQUEUE`, adding a message to a queue named `work_order`:
+
+```sql
+DECLARE
+
+  enqueue_options    DBMS_AQ.ENQUEUE_OPTIONS_T;
+  message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
+  message_handle     raw(16);
+  payload            work_order;
+
+BEGIN
+
+  payload := work_order('Smith', 'system upgrade');
+
+DBMS_AQ.ENQUEUE(
+  queue_name         => 'work_order',
+  enqueue_options    => enqueue_options,
+  message_properties => message_properties,
+  payload            => payload,
+  msgid              => message_handle
+    );
+ END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx
new file mode 100644
index 00000000000..1673daa1a2e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue.mdx
@@ -0,0 +1,130 @@
+---
+title: "DEQUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/02_dequeue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DEQUEUE` procedure dequeues a message. The signature is:
+
+```sql
+DEQUEUE(
+  <queue_name> IN VARCHAR2,
+  <dequeue_options> IN DBMS_AQ.DEQUEUE_OPTIONS_T,
+  <message_properties> OUT DBMS_AQ.MESSAGE_PROPERTIES_T,
+  <payload> OUT <type_name>,
+  <msgid> OUT RAW)
+```
+
+## Parameters
+
+`queue_name`
+
+ The name (optionally schema-qualified) of an existing queue. If you omit the schema name, the server uses the schema specified in the `SEARCH_PATH`. Unlike Oracle, unquoted identifiers are converted to lower case before storing. To include special characters or use a case-sensitive name, enclose the name in double quotes.
+
+ For detailed information about creating a queue, see [DBMS_AQADM.CREATE_QUEUE](../03_dbms_aqadm/03_create_queue).
+
+`dequeue_options` is a value of the type, `dequeue_options_t`:
+
+```sql
+DEQUEUE_OPTIONS_T IS RECORD(
+  consumer_name CHARACTER VARYING(30),
+  dequeue_mode INTEGER,
+  navigation INTEGER,
+  visibility INTEGER,
+  wait INTEGER,
+  msgid BYTEA,
+  correlation CHARACTER VARYING(128),
+  deq_condition CHARACTER VARYING(4000),
+  transformation CHARACTER VARYING(61),
+  delivery_mode INTEGER);
+```
+
+Currently, the supported parameter values for `dequeue_options_t` are:
+
+|                  |                                                                                                                                                                                                                                                                                                                                                                                  |
+| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `consumer_name`  | Must be `NULL`.                                                                                                                                                                                                                                                                                                                                                                  |
+| `dequeue_mode`   | The locking behavior of the dequeue operation. Must be either:<br /><br />`DBMS_AQ.BROWSE` – Read the message without obtaining a lock.<br /><br />`DBMS_AQ.LOCKED` – Read the message after acquiring a lock.<br /><br />`DBMS_AQ.REMOVE` – Read the message before deleting the message.<br /><br />`DBMS_AQ.REMOVE_NODATA` – Read the message, but don't delete the message. |
+| `navigation`     | Identifies the message to retrieve. Must be either:<br /><br />`FIRST_MESSAGE` – The first message in the queue that matches the search term.<br /><br />`NEXT_MESSAGE` – The next message that's available that matches the first term.                                                                                                                         |
+| `visibility`     | Must be `ON_COMMIT`. If you roll back the current transaction, the dequeued item remains in the queue.                                                                                                                                                                                                                                                                       |
+| `wait`           | Must be a number larger than 0, or:<br /><br />`DBMS_AQ.FOREVER` – Wait indefinitely.<br /><br />`DBMS_AQ.NO_WAIT` – Don't wait.                                                                                                                                                                                                                                                |
+| `msgid`          | The message ID of the message that to dequeue.                                                                                                                                                                                                                                                                                                                             |
+| `correlation`    | Accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                                                                         |
+| `deq_condition`  | A `VARCHAR2` expression that evaluates to a `BOOLEAN` value indicating whether to deqeueue the message.                                                                                                                                                                                                                                                                         |
+| `transformation` | Accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                                                                         |
+| `delivery_mode`  | Must be `PERSISTENT`. Buffered messages aren't supported.                                                                                                                                                                                                                                                                                                          |
+
+`message_properties` is a value of the type `message_properties_t`:
+
+```sql
+message_properties_t IS RECORD(
+  priority INTEGER,
+  delay INTEGER,
+  expiration INTEGER,
+  correlation CHARACTER VARYING(128) COLLATE pg_catalog.”C”,
+  attempts INTEGER,
+  recipient_list “AQ$_RECIPIENT_LIST_T”,
+  exception_queue CHARACTER VARYING(61) COLLATE pg_catalog.”C”,
+  enqueue_time TIMESTAMP WITHOUT TIME ZONE,
+  state INTEGER,
+  original_msgid BYTEA,
+  transaction_group CHARACTER VARYING(30) COLLATE pg_catalog.”C”,
+  delivery_mode INTEGER
+DBMS_AQ.PERSISTENT);
+```
+
+The supported values for `message_properties_t` are:
+
+|                     |                                                                                                                                                                                                                                                                                                                                                        |
+| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `priority`          | If the queue table definition includes a `sort_list` that references `priority`, this parameter affects the order that messages are dequeued. A lower value indicates a higher dequeue priority.                                                                                                                                                       |
+| `delay`             | Specify the number of seconds that pass before a message is available for dequeueing or `NO_DELAY`.                                                                                                                                                                                                                                               |
+| `expiration`        | Use the expiration parameter to specify the number of seconds until a message expires.                                                                                                                                                                                                                                                                 |
+| `correlation`       | Use correlation to specify a message to associate with the entry. The default is `NULL`.                                                                                                                                                                                                                                                    |
+| `attempts`          | This is a system-maintained value that specifies the number of attempts to dequeue the message.                                                                                                                                                                                                                                                        |
+| `recipient_list`    | This parameter isn't supported.                                                                                                                                                                                                                                                                                                                       |
+| `exception_queue`   | Use the `exception_queue` parameter to specify the name of an exception queue to which to move a message if it expires or is dequeued by a transaction that rolls back too many times.                                                                                                                                                           |
+| `enqueue_time`      | `enqueue_time` is the time the record was added to the queue. This value is provided by the system.                                                                                                                                                                                                                                                    |
+| `state`             | This parameter is maintained by DBMS_AQ; state can be:<br /><br />`DBMS_AQ.WAITING` – the delay has not been reached.<br /><br />`DBMS_AQ.READY` – the queue entry is ready for processing.<br /><br />`DBMS_AQ.PROCESSED` – the queue entry has been processed.<br /><br />`DBMS_AQ.EXPIRED` – the queue entry has been moved to the exception queue. |
+| `original_msgid`    | This parameter is accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                              |
+| `transaction_group` | This parameter is accepted for compatibility and ignored.                                                                                                                                                                                                                                                                                              |
+| `delivery_mode`     | This parameter isn't supported. Specify a value of `DBMS_AQ.PERSISTENT`.                                                                                                                                                                                                                                                                              |
+
+`payload`
+
+ Use the `payload` parameter to retrieve the payload of a message with a dequeue operation. The payload type must match the type specified when creating the queue table.
+
+`msgid`
+
+ Use the `msgid` parameter to retrieve a unique message identifier.
+
+## Example
+
+The following anonymous block calls `DBMS_AQ.DEQUEUE`, retrieving a message from the queue and a payload:
+
+```sql
+DECLARE
+
+  dequeue_options    DBMS_AQ.DEQUEUE_OPTIONS_T;
+  message_properties DBMS_AQ.MESSAGE_PROPERTIES_T;
+  message_handle     raw(16);
+  payload            work_order;
+
+BEGIN
+  dequeue_options.dequeue_mode := DBMS_AQ.BROWSE;
+
+  DBMS_AQ.DEQUEUE(
+    queue_name         => 'work_queue',
+    dequeue_options    => dequeue_options,
+    message_properties => message_properties,
+    payload            => payload,
+    msgid              => message_handle
+  );
+
+  DBMS_OUTPUT.PUT_LINE(
+  'The next work order is [' || payload.subject || '].'
+  );
+END;
+```
+
+The payload is displayed by `DBMS_OUTPUT.PUT_LINE`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx
new file mode 100644
index 00000000000..a8449dd1612
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register.mdx
@@ -0,0 +1,61 @@
+---
+title: "REGISTER"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/03_register/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `REGISTER` procedure to register an email address, procedure, or URL to notify when an item is enqueued or dequeued. The signature is:
+
+```sql
+REGISTER(
+  <reg_list> IN SYS.AQ$_REG_INFO_LIST,
+  <count> IN NUMBER)
+```
+
+## Parameters
+
+`reg_list` is a list of type `AQ$_REG_INFO_LIST` that provides information about each subscription that you want to register. Each entry in the list is of the type `AQ$_REG_INFO` and can contain:
+
+<div class="tabularcolumns">
+
+</div>
+
+| Attribute   | Type            | Description                                                                                                                                                                                                                                                                                                                                                                 |
+| ----------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `name`      | VARCHAR2 (128)  | The (optionally schema-qualified) name of the subscription.                                                                                                                                                                                                                                                                                                                 |
+| `namespace` | NUMERIC         | The only supported value is `DBMS_AQ.NAMESPACE_AQ (0)`.                                                                                                                                                                                                                                                                                                                      |
+| `callback`  | VARCHAR2 (4000) | Describes the action to perform on notification. Currently, only calls to PL/SQL procedures are supported. The call takes the form:<br /><br />`plsql://schema.procedure`<br /><br />Where:<br /><br />schema specifies the schema in which the procedure resides.<br /><br />procedure specifies the name of the procedure to notify.      |
+| `context`   | RAW (16)        | Any user-defined value required by the procedure.                                                                                                                                                                                                                                                                                                                           |
+
+`count`
+
+ `count` is the number of entries in `reg_list`.
+
+## Example
+
+The following anonymous block calls `DBMS_AQ.REGISTER`, registering procedures to notify when an item is added to or removed from a queue. A set of attributes (of `sys.aq$_reg_info` type) is provided for each subscription identified in the `DECLARE` section:
+
+```sql
+DECLARE
+   subscription1 sys.aq$_reg_info;
+   subscription2 sys.aq$_reg_info;
+   subscription3 sys.aq$_reg_info;
+   subscriptionlist sys.aq$_reg_info_list;
+BEGIN
+   subscription1 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://assign_worker?PR=0',HEXTORAW('FFFF'));
+   subscription2 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://add_to_history?PR=1',HEXTORAW('FFFF'));
+   subscription3 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://reserve_parts?PR=2',HEXTORAW('FFFF'));
+
+   subscriptionlist := sys.aq$_reg_info_list(subscription1,
+subscription2, subscription3);
+   dbms_aq.register(subscriptionlist, 3);
+   commit;
+
+  END;
+   /
+```
+
+The `subscriptionlist` is of type `sys.aq$_reg_info_list` and contains the previously described `sys.aq$_reg_info` objects. The list name and an object count are passed to `dbms_aq.register`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx
new file mode 100644
index 00000000000..ce893dc3364
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister.mdx
@@ -0,0 +1,62 @@
+---
+title: "UNREGISTER"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/04_unregister/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `UNREGISTER` procedure to turn off notifications related to enqueueing and dequeueing. The signature is:
+
+```sql
+UNREGISTER(
+  <reg_list> IN SYS.AQ$_REG_INFO_LIST,
+  <count> IN NUMBER)
+```
+
+## Parameter
+
+`reg_list`
+
+   `reg_list` is a list of type `AQ$_REG_INFO_LIST` that provides information about each subscription that you want to register. Each entry in the list is of the type `AQ$_REG_INFO` and can contain:
+
+<div class="tabularcolumns">
+
+</div>
+
+| Attribute   | Type            | Description                                                                                                                                                                                                                                                                                                                                                                 |
+| ----------- | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `name`      | VARCHAR2 (128)  | The (optionally schema-qualified) name of the subscription.                                                                                                                                                                                                                                                                                                                 |
+| `namespace` | NUMERIC         | The only supported value is `DBMS_AQ.NAMESPACE_AQ (0)`.                                                                                                                                                                                                                                                                                                                      |
+| `callback`  | VARCHAR2 (4000) | Describes the action to perform on notification. Currently, only calls to PL/SQL procedures are supported. The call taked the form:<br /><br />`plsql://schema.procedure` <br /><br />Where:<br /><br />schema specifies the schema in which the procedure resides.<br /><br />procedure specifies the name of the procedure to notify.     |
+| `context`   | RAW (16)        | Any user-defined value required by the procedure.                                                                                                                                                                                                                                                                                                                           |
+
+`count`
+
+ `count` is the number of entries in `reg_list`.
+
+## Example
+
+The following anonymous block calls `DBMS_AQ.UNREGISTER`, disabling the notifications specified in the example for `DBMS_AQ.REGISTER`:
+
+```sql
+DECLARE
+   subscription1 sys.aq$_reg_info;
+   subscription2 sys.aq$_reg_info;
+   subscription3 sys.aq$_reg_info;
+   subscriptionlist sys.aq$_reg_info_list;
+BEGIN
+   subscription1 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://assign_worker?PR=0',HEXTORAW('FFFF'));
+   subscription2 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://add_to_history?PR=1',HEXTORAW('FFFF'));
+   subscription3 := sys.aq$_reg_info('q', DBMS_AQ.NAMESPACE_AQ,
+'plsql://reserve_parts?PR=2',HEXTORAW('FFFF'));
+
+   subscriptionlist := sys.aq$_reg_info_list(subscription1,
+subscription2, subscription3);
+   dbms_aq.unregister(subscriptionlist, 3);
+   commit;
+  END;
+   /
+```
+
+The `subscriptionlist` is of type `sys.aq$_reg_info_list` and contains `sys.aq$_reg_info` objects. The list name and an object count are passed to `dbms_aq.unregister`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/index.mdx
new file mode 100644
index 00000000000..d9f350defe3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/index.mdx
@@ -0,0 +1,74 @@
+---
+title: "DBMS_AQ"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.13.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/02_dbms_aq/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server Advanced Queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue, and a collection of queues is stored in a queue table. Procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove them from a queue or to register or unregister a PL/SQL callback procedure.
+
+EDB Postgres Advanced Server also provides extended (noncompatible) functionality for the `DBMS_AQ` package with SQL commands. See [SQL reference](../../../epas_compat_sql) for detailed information about the following SQL commands:
+
+-   `ALTER QUEUE`
+-   `ALTER QUEUE TABLE`
+-   `CREATE QUEUE`
+-   `CREATE QUEUE TABLE`
+-   `DROP QUEUE`
+-   `DROP QUEUE TABLE`
+
+The `DBMS_AQ` package provides procedures that allow you to enqueue a message, dequeue a message, and manage callback procedures. The supported procedures are:
+
+| Function/procedure | Return type | Description                                                        |
+| ------------------ | ----------- | ------------------------------------------------------------------ |
+| `ENQUEUE`          | n/a         | Post a message to a queue.                                         |
+| `DEQUEUE`          | n/a         | Retrieve a message from a queue if or when a message is available. |
+| `REGISTER`         | n/a         | Register a callback procedure.                                     |
+| `UNREGISTER`       | n/a         | Unregister a callback procedure.                                   |
+
+EDB Postgres Advanced Server's implementation of `DBMS_AQ` is a partial implementation when compared to Oracle's version. Only those procedures listed in the table above are supported.
+
+EDB Postgres Advanced Server supports use of these constants:
+
+| Constant                          | Description                                                                       | For parameters                                               |
+| --------------------------------- | --------------------------------------------------------------------------------- | ------------------------------------------------------------ |
+| `DBMS_AQ.BROWSE (0)`              | Read the message without locking.                                                 | `dequeue_options_t.dequeue_mode`                             |
+| `DBMS_AQ.LOCKED (1)`              | This constant is defined but returns an error if used.                            | `dequeue_options_t.dequeue_mode`                             |
+| `DBMS_AQ.REMOVE (2)`              | Delete the message after reading (the default).                                    | `dequeue_options_t.dequeue_mode`                             |
+| `DBMS_AQ.REMOVE_NODATA (3)`       | This constant is defined but returns an error if used.                            | `dequeue_options_t.dequeue_mode`                             |
+| `DBMS_AQ.FIRST_MESSAGE (0)`       | Return the first available message that matches the search terms.                 | `dequeue_options_t.navigation`                               |
+| `DBMS_AQ.NEXT_MESSAGE (1)`        | Return the next available message that matches the search terms.                  | `dequeue_options_t.navigation`                               |
+| `DBMS_AQ.NEXT_TRANSACTION (2)`    | This constant is defined but returns an error if used.                            | `dequeue_options_t.navigation`                               |
+| `DBMS_AQ.FOREVER (-1)`            | Wait forever if a message that matches the search term isn't found (the default). | `dequeue_options_t.wait`                                     |
+| `DBMS_AQ.NO_WAIT (0)`             | Don't wait if a message that matches the search term isn't found.               | `dequeue_options_t.wait`                                     |
+| `DBMS_AQ.ON_COMMIT (0)`           | The dequeue is part of the current transaction.                                   | `enqueue_options_t.visibility, dequeue_options_t.visibility` |
+| `DBMS_AQ.IMMEDIATE (1)`           | This constant is defined but returns an error if used.                            | `enqueue_options_t.visibility, dequeue_options_t.visibility` |
+| `DBMS_AQ.PERSISTENT (0)`          | Store the message in a table.                                          | `enqueue_options_t.delivery_mode`                            |
+| `DBMS_AQ.BUFFERED (1)`            | This constant is defined but returns an error if used.                            | `enqueue_options_t.delivery_mode`                            |
+| `DBMS_AQ.READY (0)`               | Specifies that the message is ready to process.                                   | `message_properties_t.state`                                 |
+| `DBMS_AQ.WAITING (1)`             | Specifies that the message is waiting to be processed.                            | `message_properties_t.state`                                 |
+| `DBMS_AQ.PROCESSED (2)`           | Specifies that the message was processed.                                    | `message_properties_t.state`                                 |
+| `DBMS_AQ.EXPIRED (3)`             | Specifies that the message is in the exception queue.                             | `message_properties_t.state`                                 |
+| `DBMS_AQ.NO_DELAY (0)`            | This constant is defined but returns an error if used.                            | `message_properties_t.delay`                                 |
+| `DBMS_AQ.NEVER (NULL)`            | This constant is defined but returns an error if used.                            | `message_properties_t.expiration`                            |
+| `DBMS_AQ.NAMESPACE_AQ (0)`        | Accept notifications from `DBMS_AQ` queues.                                       | `sys.aq$_reg_info.namespace`                                 |
+| `DBMS_AQ.NAMESPACE_ANONYMOUS (1)` | This constant is defined but returns an error if used.                            | `sys.aq$_reg_info.namespace`                                 |
+
+The `DBMS_AQ` configuration parameters listed in the following table can be defined in the `postgresql.conf` file. After the configuration parameters are defined, you can invoke the `DBMS_AQ` package to use and manage messages held in queues and queue tables.
+
+| Parameter                     | Description                                                                                      |
+| ----------------------------- | ------------------------------------------------------------------------------------------------ |
+| `dbms_aq.max_workers`         | The maximum number of workers to run.                                                            |
+| `dbms_aq.max_idle_time`       | The idle time a worker must wait before exiting.                                                 |
+| `dbms_aq.min_work_time`       | The minimum time a worker can run before exiting.                                                |
+| `dbms_aq.launch_delay`        | The minimum time between creating workers.                                                       |
+| `dbms_aq.batch_size`          | The maximum number of messages to process in a single transaction. The default batch size is 10. |
+| `dbms_aq.max_databases`       | The size of the `DBMS_AQ` hash table of databases. The default value is 1024.                      |
+| `dbms_aq.max_pending_retries` | The size of the `DBMS_AQ` hash table of pending retries. The default value is 1024.                |
+
+<div class="toctree" maxdepth="5">
+
+enqueue dequeue register unregister
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/01_alter_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/01_alter_queue.mdx
new file mode 100644
index 00000000000..eaff7c527a4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/01_alter_queue.mdx
@@ -0,0 +1,50 @@
+---
+title: "ALTER_QUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/01_alter_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `ALTER_QUEUE` procedure to modify an existing queue. The signature is:
+
+```sql
+ALTER_QUEUE(
+  <max_retries> IN NUMBER DEFAULT NULL,
+  <retry_delay> IN NUMBER DEFAULT 0
+  <retention_time> IN NUMBER DEFAULT 0,
+  <auto_commit> IN BOOLEAN DEFAULT TRUE)
+  <comment> IN VARCHAR2 DEFAULT NULL,
+```
+
+## Parameters
+
+`queue_name`
+
+ The name of the new queue.
+
+`max_retries`
+
+ `max_retries` specifies the maximum number of attempts to remove a message with a dequeue statement. The value of `max_retries` is incremented with each `ROLLBACK` statement. When the number of failed attempts reaches the value specified by `max_retries`, the message is moved to the exception queue. Specify `0` to indicate that no retries are allowed.
+
+`retry_delay`
+
+ `retry_delay` specifies the number of seconds until a message is scheduled for reprocessing after a `ROLLBACK`. Specify `0` to retry the message immediately (the default).
+
+`retention_time`
+
+ `retention_time` specifies the length of time in seconds that a message is stored after being dequeued. You can also specify `0` (the default) to indicate not to retain the message after dequeueing or `INFINITE` to retain the message forever.
+
+`auto_commit`
+
+ This parameter is accepted for compatibility and ignored.
+
+`comment`
+
+ `comment` specifies a comment associated with the queue.
+
+## Example
+
+The following command alters a queue named `work_order`, setting the `retry_delay` parameter to 5 seconds:
+
+```sql
+EXEC DBMS_AQADM.ALTER_QUEUE(queue_name => 'work_order', retry_delay => 5);
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/02_alter_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/02_alter_queue_table.mdx
new file mode 100644
index 00000000000..fcd4f6f67a9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/02_alter_queue_table.mdx
@@ -0,0 +1,45 @@
+---
+title: "ALTER_QUEUE_TABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/02_alter_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `ALTER_QUEUE_TABLE` procedure to modify an existing queue table. The signature is:
+
+```sql
+ALTER_QUEUE_TABLE (
+  <queue_table> IN VARCHAR2,
+  <comment> IN VARCHAR2 DEFAULT NULL,
+  <primary_instance> IN BINARY_INTEGER DEFAULT 0,
+  <secondary_instance> IN BINARY_INTEGER DEFAULT 0,
+```
+
+## Parameters
+
+`queue_table`
+
+ The (optionally schema-qualified) name of the queue table.
+
+`comment`
+
+ Use the `comment` parameter to provide a comment about the queue table.
+
+`primary_instance`
+
+ `primary_instance` is accepted for compatibility and stored but is ignored.
+
+`secondary_instance`
+
+ `secondary_instance` is accepted for compatibility but is ignored.
+
+## Example
+
+The following command modifies a queue table named `work_order_table`:
+
+```sql
+EXEC DBMS_AQADM.ALTER_QUEUE_TABLE
+      (queue_table => 'work_order_table', comment => 'This queue table
+contains work orders for the shipping department.');
+```
+
+The queue table is named `work_order_table`. The command adds a comment to the definition of the queue table.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/03_create_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/03_create_queue.mdx
new file mode 100644
index 00000000000..5540c645fe6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/03_create_queue.mdx
@@ -0,0 +1,73 @@
+---
+title: "CREATE_QUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/03_create_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `CREATE_QUEUE` procedure to create a queue in an existing queue table. The signature is:
+
+```sql
+CREATE_QUEUE(
+  <queue_name> IN VARCHAR2
+  <queue_table> IN VARCHAR2,
+  <queue_type> IN BINARY_INTEGER DEFAULT NORMAL_QUEUE,
+  <max_retries> IN NUMBER DEFAULT 5,
+  <retry_delay> IN NUMBER DEFAULT 0
+  <retention_time> IN NUMBER DEFAULT 0,
+  <dependency_tracking> IN BOOLEAN DEFAULT FALSE,
+  <comment> IN VARCHAR2 DEFAULT NULL,
+  <auto_commit> IN BOOLEAN DEFAULT TRUE)
+```
+
+## Parameters
+
+`queue_name`
+
+ The name of the new queue.
+
+`queue_table`
+
+ The name of the table in which the new queue resides.
+
+`queue_type`
+
+ The type of the new queue. The valid values for `queue_type` are:
+
+ `DBMS_AQADM.NORMAL_QUEUE` &mdash; This value specifies a normal queue (the default).
+
+ `DBMS_AQADM.EXCEPTION_QUEUE` &mdash; This value specifies that the new queue is an exception queue. An exception queue supports only dequeue operations.
+
+`max_retries`
+
+ `max_retries` specifies the maximum number of attempts to remove a message with a dequeue statement. The value of `max_retries` is incremented with each `ROLLBACK` statement. When the number of failed attempts reaches the value specified by `max_retries`, the message is moved to the exception queue. The default value for a system table is `0`. The default value for a user-created table is `5`.
+
+`retry_delay`
+
+ `retry_delay` specifies the number of seconds until a message is scheduled for reprocessing after a `ROLLBACK`. Specify `0` to retry the message immediately (the default).
+
+`retention_time`
+
+ `retention_time` specifies the length of time (in seconds) that a message is stored after being dequeued. You can also specify `0` (the default) to indicate not to retain the message after dequeueing or `INFINITE` to retain the message forever.
+
+`dependency_tracking`
+
+ This parameter is accepted for compatibility and ignored.
+
+`comment`
+
+ `comment` specifies a comment associated with the queue.
+
+`auto_commit`
+
+ This parameter is accepted for compatibility and ignored.
+
+## Example
+
+The following anonymous block creates a queue named `work_order` in the `work_order_table` table:
+
+```sql
+BEGIN
+DBMS_AQADM.CREATE_QUEUE ( queue_name => 'work_order', queue_table =>
+'work_order_table', comment => 'This queue contains pending work orders.');
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/04_create_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/04_create_queue_table.mdx
new file mode 100644
index 00000000000..f6e38aab891
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/04_create_queue_table.mdx
@@ -0,0 +1,115 @@
+---
+title: "CREATE_QUEUE_TABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/04_create_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `CREATE_QUEUE_TABLE` procedure to create a queue table. The signature is:
+
+```sql
+CREATE_QUEUE_TABLE (
+  <queue_table> IN VARCHAR2,
+  <queue_payload_type> IN VARCHAR2,
+  <storage_clause> IN VARCHAR2 DEFAULT NULL,
+  <sort_list> IN VARCHAR2 DEFAULT NULL,
+  <multiple_consumers> IN BOOLEAN DEFAULT FALSE,
+  <message_grouping> IN BINARY_INTEGER DEFAULT NONE,
+  <comment> IN VARCHAR2 DEFAULT NULL,
+  <auto_commit> IN BOOLEAN DEFAULT TRUE,
+  <primary_instance> IN BINARY_INTEGER DEFAULT 0,
+  <secondary_instance> IN BINARY_INTEGER DEFAULT 0,
+  <compatible> IN VARCHAR2 DEFAULT NULL,
+  <secure> IN BOOLEAN DEFAULT FALSE)
+```
+
+## Parameters
+
+`queue_table`
+
+ The (optionally schema-qualified) name of the queue table.
+
+`queue_payload_type`
+
+ The user-defined type of the data that's stored in the queue table. To specify a `RAW` data type, you must create a user-defined type that identifies a `RAW` type.
+
+`storage_clause`
+
+Use the `storage_clause` parameter to specify attributes for the queue table. Only the `TABLESPACE` option is enforced. All others are accepted for compatibility and ignored. Use the `TABLESPACE` clause to specify the name of a tablespace in which to create the table.
+
+ `storage_clause` can be one or more of the following:
+
+```sql
+TABLESPACE tablespace_name, PCTFREE integer, PCTUSED integer,
+INITRANS integer, MAXTRANS integer or STORAGE storage_option.
+```
+
+`storage_option` can be one or more of the following:
+
+```sql
+MINEXTENTS integer, MAXEXTENTS integer, PCTINCREASE integer, INITIAL
+size_clause, NEXT, FREELISTS integer, OPTIMAL size_clause, BUFFER_
+POOL {KEEP|RECYCLE|DEFAULT}.
+```
+
+`sort_list`
+
+ `sort_list` controls the dequeueing order of the queue. Specify the names of the columns to use to sort the queue in ascending order. The currently accepted values are the following combinations of `enq_time` and `priority`:
+
+-   `enq_time, priority`
+
+-   `priority, enq_time`
+
+-   `priority`
+
+-   `enq_time`
+
+`multiple_consumers`
+
+ `multiple_consumers` queue tables isn't supported.
+
+`message_grouping`
+
+ If specified, `message_grouping` must be `NONE`.
+
+`comment`
+
+ Use the `comment` parameter to provide a comment about the queue table.
+
+`auto_commit`
+
+ `auto_commit` is accepted for compatibility but is ignored.
+
+`primary_instance`
+
+ `primary_instance` is accepted for compatibility and stored but is ignored.
+
+`secondary_instance`
+
+ `secondary_instance` is accepted for compatibility but is ignored.
+
+`compatible`
+
+ `compatible` is accepted for compatibility but is ignored.
+
+`secure`
+
+ `secure` is accepted for compatibility but is ignored.
+
+## Example
+
+The following anonymous block first creates a type (`work_order`) with attributes that hold a name (a `VARCHAR2`), and a project description (a `TEXT`). The block then uses that type to create a queue table:
+
+```sql
+BEGIN
+
+CREATE TYPE work_order AS (name VARCHAR2, project TEXT, completed BOOLEAN);
+
+EXEC DBMS_AQADM.CREATE_QUEUE_TABLE
+      (queue_table => 'work_order_table',
+       queue_payload_type => 'work_order',
+       comment => 'Work order message queue table');
+
+END;
+```
+
+The queue table is named `work_order_table` and contains a payload of a type `work_order`. A comment notes that this is the `Work order message queue table`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/05_drop_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/05_drop_queue.mdx
new file mode 100644
index 00000000000..46b6a37582a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/05_drop_queue.mdx
@@ -0,0 +1,33 @@
+---
+title: "DROP_QUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/05_drop_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DROP_QUEUE` procedure to delete a queue. The signature is:
+
+```sql
+DROP_QUEUE(
+  <queue_name>  IN VARCHAR2,
+  <auto_commit> IN BOOLEAN DEFAULT TRUE)
+```
+
+## Parameters
+
+`queue_name`
+
+ The name of the queue that you want to drop.
+
+`auto_commit`
+
+ `auto_commit` is accepted for compatibility but is ignored.
+
+## Example
+
+The following anonymous block drops the queue named `work_order`:
+
+```sql
+BEGIN
+DBMS_AQADM.DROP_QUEUE(queue_name => 'work_order');
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/06_drop_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/06_drop_queue_table.mdx
new file mode 100644
index 00000000000..38398f2e24c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/06_drop_queue_table.mdx
@@ -0,0 +1,41 @@
+---
+title: "DROP_QUEUE_TABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/06_drop_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DROP_QUEUE_TABLE` procedure to delete a queue table. The signature is:
+
+```sql
+DROP_QUEUE_TABLE(
+  <queue_table> IN VARCHAR2,
+  <force> IN BOOLEAN default FALSE,
+  <auto_commit> IN BOOLEAN default TRUE)
+```
+
+## Parameters
+
+`queue_table`
+
+ The (optionally schema-qualified) name of the queue table.
+
+`force`
+
+ The `force` keyword determines the behavior of the `DROP_QUEUE_TABLE` command when dropping a table that contain entries:
+
+-   If the target table contains entries and `force` is `FALSE`, the command fails, and the server issues an error.
+-   If the target table contains entries and `force` is `TRUE`, the command drops the table and any dependent objects.
+
+`auto_commit`
+
+ `auto_commit` is accepted for compatibility but is ignored.
+
+## Example
+
+The following anonymous block drops a table named `work_order_table`:
+
+```sql
+BEGIN
+   DBMS_AQADM.DROP_QUEUE_TABLE ('work_order_table', force => TRUE);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/07_purge_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/07_purge_queue_table.mdx
new file mode 100644
index 00000000000..60cbea3e5ce
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/07_purge_queue_table.mdx
@@ -0,0 +1,46 @@
+---
+title: "PURGE_QUEUE_TABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/07_purge_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `PURGE_QUEUE_TABLE` procedure to delete messages from a queue table. The signature is:
+
+```sql
+PURGE_QUEUE_TABLE(
+  <queue_table> IN VARCHAR2,
+  <purge_condition> IN VARCHAR2,
+  <purge_options> IN aq$_purge_options_t)
+```
+
+## Parameters
+
+`queue_table`
+
+ `queue_table` specifies the name of the queue table from which you're deleting a message.
+
+`purge_condition`
+
+ Use `purge_condition` to specify a condition (a SQL `WHERE` clause) that the server evaluates when deciding which messages to purge.
+
+`purge_options`
+
+ `purge_options` is an object of the type `aq$_purge_options_t`. An `aq$_purge_options_t` object contains:
+
+| Attribute       | Type    | Description                                                                                                         |
+| --------------- | ------- | ------------------------------------------------------------------------------------------------------------------- |
+| `block`         | Boolean | Specify `TRUE` to hold an exclusive lock on all queues in the table. The default is `FALSE`.          |
+| `delivery_mode` | INTEGER | `delivery_mode` specifies the type of message to purge. The only accepted value is `DBMS_AQ.PERSISTENT`. |
+
+## Example
+
+The following anonymous block removes any messages from the `work_order_table` with a value in the `completed` column of `YES`:
+
+```sql
+DECLARE
+   purge_options dbms_aqadm.aq$_purge_options_t;
+BEGIN
+   dbms_aqadm.purge_queue_table('work_order_table', 'completed = YES',
+purge_options);
+  END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/08_start_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/08_start_queue.mdx
new file mode 100644
index 00000000000..3dce6deb146
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/08_start_queue.mdx
@@ -0,0 +1,39 @@
+---
+title: "START_QUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/08_start_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `START_QUEUE` procedure to make a queue available for enqueuing and dequeueing. The signature is:
+
+```sql
+START_QUEUE(
+  <queue_name> IN VARCHAR2,
+  <enqueue> IN BOOLEAN DEFAULT TRUE,
+  <dequeue> IN BOOLEAN DEFAULT TRUE)
+```
+
+## Parameters
+
+`queue_name`
+
+ `queue_name` specifies the name of the queue that you're starting.
+
+`enqueue`
+
+ Specify `TRUE` to enable enqueueing (the default) or `FALSE` to leave the current setting unchanged.
+
+`dequeue`
+
+ Specify `TRUE` to enable dequeueing (the default) or `FALSE` to leave the current setting unchanged.
+
+## Example
+
+The following anonymous block makes a queue named `work_order` available for enqueueing:
+
+```sql
+BEGIN
+DBMS_AQADM.START_QUEUE
+(queue_name => 'work_order);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/09_stop_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/09_stop_queue.mdx
new file mode 100644
index 00000000000..a63d2aeb9d5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/09_stop_queue.mdx
@@ -0,0 +1,46 @@
+---
+title: "STOP_QUEUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/09_stop_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `STOP_QUEUE` procedure to disable enqueuing or dequeueing on a specified queue. The signature is:
+
+```sql
+STOP_QUEUE(
+  <queue_name> IN VARCHAR2,
+  <enqueue> IN BOOLEAN DEFAULT TRUE,
+  <dequeue> IN BOOLEAN DEFAULT TRUE,
+  <wait> IN BOOLEAN DEFAULT TRUE)
+```
+
+## Parameters
+
+`queue_name`
+
+ `queue_name` specifies the name of the queue that you're stopping.
+
+`enqueue`
+
+ Specify `TRUE` to disable enqueueing (the default) or `FALSE` to leave the current setting unchanged.
+
+`dequeue`
+
+ Specify `TRUE` to disable dequeueing (the default) or `FALSE` to leave the current setting unchanged.
+
+`wait`
+
+ Specify `TRUE` to instruct the server to wait for any uncompleted transactions to complete before applying the specified changes. While waiting to stop the queue, no transactions are allowed to enqueue or dequeue from the specified queue. Specify `FALSE` to stop the queue immediately.
+
+## Example
+
+The following anonymous block disables enqueueing and dequeueing from the queue named `work_order`:
+
+```sql
+BEGIN
+DBMS_AQADM.STOP_QUEUE(queue_name =>'work_order', enqueue=>TRUE,
+dequeue=>TRUE, wait=>TRUE);
+END;
+```
+
+Enqueueing and dequeueing stops after any outstanding transactions complete.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/index.mdx
new file mode 100644
index 00000000000..53d7f7ad940
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/index.mdx
@@ -0,0 +1,52 @@
+---
+title: "DBMS_AQADM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.14.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/03_dbms_aqadm/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server advanced queueing provides message queueing and message processing for the EDB Postgres Advanced Server database. User-defined messages are stored in a queue, and a collection of queues is stored in a queue table. Procedures in the `DBMS_AQADM` package create and manage message queues and queue tables. Use the `DBMS_AQ` package to add messages to or remove messages from a queue or to register or unregister a PL/SQL callback procedure.
+
+EDB Postgres Advanced Server also provides extended (non-compatible) functionality for the `DBMS_AQ` package with SQL commands. See [SQL reference](../../../epas_compat_sql/) for detailed information about the following SQL commands:
+
+-   `ALTER QUEUE`
+-   `ALTER QUEUE TABLE`
+-   `CREATE QUEUE`
+-   `CREATE QUEUE TABLE`
+-   `DROP QUEUE`
+-   `DROP QUEUE TABLE`
+
+The `DBMS_AQADM` package provides procedures that allow you to create and manage queues and queue tables. EDB Postgres Advanced Server's implementation of `DBMS_AQADM` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+| Function/procedure   | Return type | Description                                                       |
+| -------------------- | ----------- | ----------------------------------------------------------------- |
+| `ALTER_QUEUE`        | n/a         | Modify an existing queue.                                         |
+| `ALTER_QUEUE_TABLE`  | n/a         | Modify an existing queue table.                                   |
+| `CREATE_QUEUE`       | n/a         | Create a queue.                                                   |
+| `CREATE_QUEUE_TABLE` | n/a         | Create a queue table.                                             |
+| `DROP_QUEUE`         | n/a         | Drop an existing queue.                                           |
+| `DROP_QUEUE_TABLE`   | n/a         | Drop an existing queue table.                                     |
+| `PURGE_QUEUE_TABLE`  | n/a         | Remove one or more messages from a queue table.                   |
+| `START_QUEUE`        | n/a         | Make a queue available for enqueueing and dequeueing procedures.  |
+| `STOP_QUEUE`         | n/a         | Make a queue unavailable for enqueueing and dequeueing procedures. |
+
+EDB Postgres Advanced Server supports use of the arguments listed in the table:
+
+| Constant                                | Description                                                 | For parameters                    |
+| --------------------------------------- | ----------------------------------------------------------- | --------------------------------- |
+| `DBMS_AQADM.TRANSACTIONAL(1)`           | This constant is defined but returns an error if used.      | `message_grouping`                |
+| `DBMS_AQADM.NONE(0)`                    | Use to specify message grouping for a queue table.          | `message_grouping`                |
+| `DBMS_AQADM.NORMAL_QUEUE(0)`            | Use with `create_queue` to specify `queue_type`.            | `queue_type`                      |
+| `DBMS_AQADM.EXCEPTION_QUEUE (1)`        | Use with `create_queue` to specify `queue_type`.            | `queue_type`                      |
+| `DBMS_AQADM.INFINITE(-1)`               | Use with `create_queue` to specify `retention_time`.        | `retention_time`                  |
+| `DBMS_AQADM.PERSISTENT (0)`             | Store the message in a table.                    | `enqueue_options_t.delivery_mode` |
+| `DBMS_AQADM.BUFFERED (1)`               | This constant is defined but returns an error if used.      | `enqueue_options_t.delivery_mode` |
+| `DBMS_AQADM.PERSISTENT_OR_BUFFERED (2)` | This constant is defined but returns an error if used.      | `enqueue_options_t.delivery_mode` |
+
+<div class="toctree" maxdepth="5">
+
+alter_queue alter_queue_table create_queue create_queue_table drop_queue drop_queue_table purge_queue_table start_queue stop_queue
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx
new file mode 100644
index 00000000000..4abbf1cbfa3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt.mdx
@@ -0,0 +1,98 @@
+---
+title: "DECRYPT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/01_decrypt/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DECRYPT` function or procedure decrypts data using a user-specified cipher algorithm, key, and optional initialization vector. The signature of the `DECRYPT` function is:
+
+```sql
+DECRYPT
+  (<src> IN RAW, <typ> IN INTEGER, <key> IN RAW, <iv> IN RAW
+   DEFAULT NULL) RETURN RAW
+```
+
+The signature of the `DECRYPT` procedure is:
+
+```sql
+DECRYPT
+  (<dst> INOUT BLOB, <src> IN BLOB, <typ> IN INTEGER, <key> IN RAW,
+   <iv> IN RAW DEFAULT NULL)
+```
+
+or
+
+```sql
+DECRYPT
+  (<dst> INOUT CLOB, <src> IN CLOB, <typ> IN INTEGER, <key> IN RAW,
+   <iv> IN RAW DEFAULT NULL)
+```
+
+When invoked as a procedure, `DECRYPT` returns `BLOB` or `CLOB` data to a user-specified `BLOB`.
+
+## Parameters
+
+`dst`
+
+ `dst` specifies the name of a `BLOB` to which the output of the `DECRYPT` procedure is written. The `DECRYPT` procedure overwrites any existing data currently in `dst`.
+
+`src`
+
+ `src` specifies the source data to decrypt. If you're invoking `DECRYPT` as a function, specify `RAW` data. If invoking `DECRYPT` as a procedure, specify `BLOB` or `CLOB` data.
+
+`typ`
+
+ `typ` specifies the block cipher type and any modifiers. Match the type specified when the `src` was encrypted. EDB Postgres Advanced Server supports the following block cipher algorithms, modifiers, and cipher suites:
+
+| Block cipher algorithms            |                                                             |
+| ---------------------------------- | ----------------------------------------------------------- |
+| `ENCRYPT_DES`                      | `CONSTANT INTEGER := 1;`                                    |
+| `ENCRYPT_3DES`                     | `CONSTANT INTEGER := 3;`                                    |
+| `ENCRYPT_AES`                      | `CONSTANT INTEGER := 4;`                                    |
+| `ENCRYPT_AES128`                   | `CONSTANT INTEGER := 6;`                                    |
+| `ENCRYPT_AES192`                   | `CONSTANT INTEGER := 192;`                                  |
+| `ENCRYPT_AES256`                   | `CONSTANT INTEGER := 256;`                                  |
+| **Block cipher modifiers**         |                                                             |
+| `CHAIN_CBC`                        | `CONSTANT INTEGER := 256;`                                  |
+| `CHAIN_ECB`                        | `CONSTANT INTEGER := 768;`                                  |
+| **Block cipher padding modifiers** |                                                             |
+| `PAD_PKCS5`                        | `CONSTANT INTEGER := 4096;`                                 |
+| `PAD_NONE`                         | `CONSTANT INTEGER := 8192;`                                 |
+| **Block cipher suites**            |                                                             |
+| `DES_CBC_PKCS5`                    | `CONSTANT INTEGER := ENCRYPT_DES + CHAIN_CBC + PAD_PKCS5;`  |
+| `DES3_CBC_PKCS5`                   | `CONSTANT INTEGER := ENCRYPT_3DES + CHAIN_CBC + PAD_PKCS5;` |
+| `AES_CBC_PKCS5`                    | `CONSTANT INTEGER := ENCRYPT_AES + CHAIN_CBC + PAD_PKCS5;`  |
+
+`key`
+
+ `key` specifies the user-defined decryption key. Match the key specified when the `src` was encrypted.
+
+`iv`
+
+ `iv` (optional) specifies an initialization vector. If an initialization vector was specified when the `src` was encrypted, you must specify an initialization vector when decrypting the `src`. The default is `NULL`.
+
+## Examples
+
+This example uses the `DBMS_CRYPTO.DECRYPT` function to decrypt an encrypted password retrieved from the `passwords` table:
+
+```sql
+CREATE TABLE passwords
+(
+  principal VARCHAR2(90) PRIMARY KEY, -- username
+  ciphertext RAW(9) -- encrypted password
+);
+
+CREATE FUNCTION get_password(username VARCHAR2) RETURN RAW AS
+ typ       INTEGER := DBMS_CRYPTO.DES_CBC_PKCS5;
+ key       RAW(128) := 'my secret key';
+ iv        RAW(100) := 'my initialization vector';
+ password  RAW(2048);
+BEGIN
+
+  SELECT ciphertext INTO password FROM passwords WHERE principal = username;
+
+  RETURN dbms_crypto.decrypt(password, typ, key, iv);
+END;
+```
+
+When calling `DECRYPT`, you must pass the same cipher type, key value, and initialization vector that was used when encrypting the target.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx
new file mode 100644
index 00000000000..82fe2f9c32e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt.mdx
@@ -0,0 +1,95 @@
+---
+title: "ENCRYPT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/02_encrypt/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `ENCRYPT` function or procedure uses a user-specified algorithm, key, and optional initialization vector to encrypt `RAW`, `BLOB`, or `CLOB` data. The signature of the `ENCRYPT` function is:
+
+```sql
+ENCRYPT
+  (<src> IN RAW, <typ> IN INTEGER, <key> IN RAW,
+   <iv> IN RAW DEFAULT NULL) RETURN RAW
+```
+
+The signature of the `ENCRYPT` procedure is:
+
+```sql
+ENCRYPT
+  (<dst> INOUT BLOB, <src> IN BLOB, <typ> IN INTEGER, <key> IN RAW,
+   <iv> IN RAW DEFAULT NULL)
+```
+
+or
+
+```sql
+ENCRYPT
+  (<dst> INOUT BLOB, <src> IN CLOB, <typ> IN INTEGER, <key> IN RAW,
+   <iv> IN RAW DEFAULT NULL)
+```
+
+When invoked as a procedure, `ENCRYPT` returns `BLOB` or `CLOB` data to a user-specified `BLOB`.
+
+## Parameters
+
+`dst`
+
+ `dst` specifies the name of a `BLOB` to which to write the output of the `ENCRYPT` procedure. The `ENCRYPT` procedure overwrites any existing data currently in `dst`.
+
+`src`
+
+ `src` specifies the source data to encrypt. If you're invoking `ENCRYPT` as a function, specify `RAW` data. If invoking `ENCRYPT` as a procedure, specify `BLOB` or `CLOB` data.
+
+`typ`
+
+ `typ` specifies the block cipher type used by `ENCRYPT` and any modifiers. EDB Postgres Advanced Server supports the block cipher algorithms, modifiers, and cipher suites shown in the table.
+
+| Block cipher algorithms            |                                                             |
+| ---------------------------------- | ----------------------------------------------------------- |
+| `ENCRYPT_DES`                      | `CONSTANT INTEGER := 1;`                                    |
+| `ENCRYPT_3DES`                     | `CONSTANT INTEGER := 3;`                                    |
+| `ENCRYPT_AES`                      | `CONSTANT INTEGER := 4;`                                    |
+| `ENCRYPT_AES128`                   | `CONSTANT INTEGER := 6;`                                    |
+| `ENCRYPT_AES192`                   | `CONSTANT INTEGER := 192;`                                  |
+| `ENCRYPT_AES256`                   | `CONSTANT INTEGER := 256;`                                  |
+| **Block cipher modifiers**         |                                                             |
+| `CHAIN_CBC`                        | `CONSTANT INTEGER := 256;`                                  |
+| `CHAIN_ECB`                        | `CONSTANT INTEGER := 768;`                                  |
+| **Block cipher padding modifiers** |                                                             |
+| `PAD_PKCS5`                        | `CONSTANT INTEGER := 4096;`                                 |
+| `PAD_NONE`                         | `CONSTANT INTEGER := 8192;`                                 |
+| **Block cipher suites**            |                                                             |
+| `DES_CBC_PKCS5`                    | `CONSTANT INTEGER := ENCRYPT_DES + CHAIN_CBC + PAD_PKCS5;`  |
+| `DES3_CBC_PKCS5`                   | `CONSTANT INTEGER := ENCRYPT_3DES + CHAIN_CBC + PAD_PKCS5;` |
+| `AES_CBC_PKCS5`                    | `CONSTANT INTEGER := ENCRYPT_AES + CHAIN_CBC + PAD_PKCS5;`  |
+
+`key`
+
+ `key` specifies the encryption key.
+
+`iv`
+
+ `iv` (optional) specifies an initialization vector. By default, `iv` is `NULL`.
+
+## Examples
+
+This example uses the `DBMS_CRYPTO.DES_CBC_PKCS5` Block Cipher Suite (a predefined set of algorithms and modifiers) to encrypt a value retrieved from the `passwords` table:
+
+```sql
+CREATE TABLE passwords
+(
+  principal   VARCHAR2(90) PRIMARY KEY, -- username
+  ciphertext  RAW(9) -- encrypted password
+);
+CREATE PROCEDURE set_password(username VARCHAR2, cleartext RAW) AS
+ typ         INTEGER := DBMS_CRYPTO.DES_CBC_PKCS5;
+ key         RAW(128) := 'my secret key';
+ iv          RAW(100) := 'my initialization vector';
+ encrypted   RAW(2048);
+BEGIN
+  encrypted := dbms_crypto.encrypt(cleartext, typ, key, iv);
+  UPDATE passwords SET ciphertext = encrypted WHERE principal = username;
+END;
+```
+
+`ENCRYPT` uses a key value of `my secret key` and an initialization vector of `my initialization vector` when encrypting the password. Specify the same key and initialization vector when decrypting the password.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/03_hash.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/03_hash.mdx
new file mode 100644
index 00000000000..0da0b2c2490
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/03_hash.mdx
@@ -0,0 +1,46 @@
+---
+title: "HASH"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/03_hash/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `HASH` function uses a user-specified algorithm to return the hash value of a `RAW` or `CLOB` value. The `HASH` function is available in three forms:
+
+```sql
+HASH
+  (<src> IN RAW, <typ> IN INTEGER) RETURN RAW
+
+HASH
+  (<src> IN CLOB, <typ> IN INTEGER) RETURN RAW
+```
+
+## Parameters
+
+`src`
+
+ `src` specifies the value for which the hash value is generated. You can specify a `RAW`, `BLOB`, or `CLOB` value.
+
+`typ`
+
+ `typ` specifies the `HASH` function type. EDB Postgres Advanced Server supports the `HASH` function types shown in the table.
+
+| HASH functions     |                          |
+| ------------------ | ------------------------ |
+| `HASH_MD4`         | `CONSTANT INTEGER := 1;` |
+| `HASH_MD5`         | `CONSTANT INTEGER := 2;` |
+| `HASH_SH1`         | `CONSTANT INTEGER := 3;` |
+
+## Examples
+
+This example uses `DBMS_CRYPTO.HASH` to find the `md5` hash value of the string, `cleartext source`:
+
+```sql
+DECLARE
+  typ INTEGER := DBMS_CRYPTO.HASH_MD5;
+  hash_value RAW(100);
+BEGIN
+
+  hash_value := DBMS_CRYPTO.HASH('cleartext source', typ);
+
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/04_mac.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/04_mac.mdx
new file mode 100644
index 00000000000..e966a76446a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/04_mac.mdx
@@ -0,0 +1,52 @@
+---
+title: "MAC"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/04_mac/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `MAC` function uses a user-specified `MAC` function to return the hashed `MAC` value of a `RAW` or `CLOB` value. The `MAC` function is available in three forms:
+
+```sql
+MAC
+  (<src> IN RAW, <typ> IN INTEGER, <key> IN RAW) RETURN RAW
+
+MAC
+  (<src> IN CLOB, <typ> IN INTEGER, <key> IN RAW) RETURN RAW
+```
+
+## Parameters
+
+`src`
+
+ `src` specifies the value for which the `MAC` value is generated. Specify a `RAW`, `BLOB`, or `CLOB` value.
+
+`typ`
+
+ `typ` specifies the `MAC` function used. EDB Postgres Advanced Server supports the `MAC` functions shown in the table.
+
+| MAC functions     |                          |
+| ----------------- | ------------------------ |
+| `HMAC_MD5`        | `CONSTANT INTEGER := 1;` |
+| `HMAC_SH1`        | `CONSTANT INTEGER := 2;` |
+
+`key`
+
+ `key` specifies the key used to calculate the hashed `MAC` value.
+
+## Examples
+
+This example finds the hashed `MAC` value of the string `cleartext source`:
+
+```sql
+DECLARE
+  typ INTEGER := DBMS_CRYPTO.HMAC_MD5;
+  key RAW(100) := 'my secret key';
+  mac_value RAW(100);
+BEGIN
+
+  mac_value := DBMS_CRYPTO.MAC('cleartext source', typ, key);
+
+END;
+```
+
+`DBMS_CRYPTO.MAC` uses a key value of `my secret` key when calculating the `MAC` value of `cleartext source`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/05_randombytes.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/05_randombytes.mdx
new file mode 100644
index 00000000000..f1dbf8052eb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/05_randombytes.mdx
@@ -0,0 +1,30 @@
+---
+title: "RANDOMBYTES"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/05_randombytes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RANDOMBYTES` function returns a `RAW` value of the specified length, containing cryptographically random bytes. The signature is:
+
+```sql
+RANDOMBYTES
+  (<number_bytes> IN INTEGER) RETURNS RAW
+```
+
+## Parameter
+
+`number_bytes`
+
+ `number_bytes` specifies the number of random bytes to return.
+
+## Examples
+
+This example uses `RANDOMBYTES` to return a value that is 1024 bytes long:
+
+```sql
+DECLARE
+  result RAW(1024);
+BEGIN
+  result := DBMS_CRYPTO.RANDOMBYTES(1024);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/06_randominteger.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/06_randominteger.mdx
new file mode 100644
index 00000000000..f376ec5dd87
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/06_randominteger.mdx
@@ -0,0 +1,24 @@
+---
+title: "RANDOMINTEGER"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/06_randominteger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RANDOMINTEGER()` function returns a random integer between `0` and `268,435,455`. The signature is:
+
+```sql
+RANDOMINTEGER() RETURNS INTEGER
+```
+
+## Examples
+
+This example uses the `RANDOMINTEGER` function to return a cryptographically strong random `INTEGER` value:
+
+```sql
+DECLARE
+  result INTEGER;
+BEGIN
+  result := DBMS_CRYPTO.RANDOMINTEGER();
+  DBMS_OUTPUT.PUT_LINE(result);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/07_randomnumber.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/07_randomnumber.mdx
new file mode 100644
index 00000000000..1e340deb3ec
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/07_randomnumber.mdx
@@ -0,0 +1,24 @@
+---
+title: "RANDOMNUMBER"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/07_randomnumber/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RANDOMNUMBER()` function returns a random number between 0 and 268,435,455. The signature is:
+
+```sql
+RANDOMNUMBER() RETURNS NUMBER
+```
+
+## Examples
+
+This example uses the `RANDOMNUMBER` function to return a cryptographically strong random number:
+
+```sql
+DECLARE
+  result NUMBER;
+BEGIN
+  result := DBMS_CRYPTO.RANDOMNUMBER();
+  DBMS_OUTPUT.PUT_LINE(result);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/index.mdx
new file mode 100644
index 00000000000..fe577fd11ff
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/index.mdx
@@ -0,0 +1,47 @@
+---
+title: "DBMS_CRYPTO"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.15.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.191.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.149.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/04_dbms_crypto/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_CRYPTO` package provides functions and procedures that allow you to encrypt or decrypt `RAW, BLOB`, or `CLOB` data. You can also use `DBMS_CRYPTO` functions to generate cryptographically strong random values.
+
+The table lists the `DBMS_CRYPTO` functions and procedures.
+
+| Function/procedure                      | Return type | Description                                                                                         |
+| --------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------- |
+| `DECRYPT(src, typ, key, iv)`            | `RAW`       | Decrypts `RAW` data.                                                                                |
+| `DECRYPT(dst INOUT, src, typ, key, iv)` | N/A         | Decrypts `BLOB` data.                                                                               |
+| `DECRYPT(dst INOUT, src, typ, key, iv)` | N/A         | Decrypts `CLOB` data.                                                                               |
+| `ENCRYPT(src, typ, key, iv)`            | `RAW`       | Encrypts `RAW` data.                                                                                |
+| `ENCRYPT(dst INOUT, src, typ, key, iv)` | N/A         | Encrypts `BLOB` data.                                                                               |
+| `ENCRYPT(dst INOUT, src, typ, key, iv)` | N/A         | Encrypts `CLOB` data.                                                                               |
+| `HASH(src, typ)`                        | `RAW`       | Applies a hash algorithm to `RAW` data.                                                             |
+| `MAC(src, typ, key)`                    | `RAW`       | Returns the hashed `MAC` value of the given `RAW` data using the specified hash algorithm and key.  |
+| `MAC(src, typ, key)`                    | `RAW`       | Returns the hashed `MAC` value of the given `CLOB` data using the specified hash algorithm and key. |
+| `RANDOMBYTES(number_bytes)`             | `RAW`       | Returns a specified number of cryptographically strong random bytes.                                |
+| `RANDOMINTEGER()`                       | `INTEGER`   | Returns a random integer.                                                                         |
+| `RANDOMNUMBER()`                        | `NUMBER`    | Returns a random number.                                                                          |
+
+`DBMS_CRYPTO` functions and procedures support the following error messages:
+
+`ORA-28239 - DBMS_CRYPTO.KeyNull`
+
+`ORA-28829 - DBMS_CRYPTO.CipherSuiteNull`
+
+`ORA-28827 - DBMS_CRYPTO.CipherSuiteInvalid`
+
+Unlike Oracle, EDB Postgres Advanced Server doesn't return error `ORA-28233` if you reencrypt previously encrypted information.
+
+`RAW` and `BLOB` are synonyms for the PostgreSQL `BYTEA` data type. `CLOB` is a synonym for `TEXT`.
+
+<div class="toctree" maxdepth="5">
+
+decrypt encrypt hash mac randombytes randominteger randomnumber
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/01_broken.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/01_broken.mdx
new file mode 100644
index 00000000000..33b46933d8d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/01_broken.mdx
@@ -0,0 +1,43 @@
+---
+title: "BROKEN"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/01_broken/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `BROKEN` procedure sets the state of a job to either broken or not broken. You can execute a broken job only by using the `RUN` procedure.
+
+```sql
+BROKEN(<job> BINARY_INTEGER, <broken> BOOLEAN [, <next_date> DATE ])
+```
+
+## Parameters
+
+`job`
+
+ Identifier of the job to set as broken or not broken.
+
+`broken`
+
+ If set to `TRUE`, the job’s state is set to broken. If set to `FALSE`, the job’s state is set to not broken. You can run broken jobs only by using the `RUN` procedure.
+
+`next_date`
+
+ Date/time when the job is to be run. The default is `SYSDATE`.
+
+## Examples
+
+Set the state of a job with job identifier 104 to broken:
+
+```sql
+BEGIN
+    DBMS_JOB.BROKEN(104,true);
+END;
+```
+
+Change the state back to not broken:
+
+```sql
+BEGIN
+    DBMS_JOB.BROKEN(104,false);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/02_change.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/02_change.mdx
new file mode 100644
index 00000000000..e82b51c39de
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/02_change.mdx
@@ -0,0 +1,49 @@
+---
+title: "CHANGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/02_change/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CHANGE` procedure modifies certain job attributes including the stored procedure to run, the next date/time the job runs, and how often it runs.
+
+```sql
+CHANGE(<job> BINARY_INTEGER <what> VARCHAR2, <next_date> DATE,
+  <interval> VARCHAR2, <instance> BINARY_INTEGER, <force> BOOLEAN)
+```
+
+## Parameters
+
+`job`
+
+ Identifier of the job to modify.
+
+`what`
+
+ Stored procedure name. Set this parameter to null if you want the existing value to remain unchanged.
+
+`next_date`
+
+ Date/time to run the job next. Set this parameter to null if you want the existing value to remain unchanged.
+
+`interval`
+
+ Date function that, when evaluated, provides the next date/time to run the job. Set this parameter to null if you want the existing value to remain unchanged.
+
+`instance`
+
+ This argument is ignored but is included for compatibility.
+
+`force`
+
+ This argument is ignored but is included for compatibility.
+
+## Examples
+
+Change the job to run next on December 13, 2007. Leave other parameters unchanged.
+
+```sql
+BEGIN
+    DBMS_JOB.CHANGE(104,NULL,TO_DATE('13-DEC-07','DD-MON-YY'),NULL, NULL,
+    NULL);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/03_interval.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/03_interval.mdx
new file mode 100644
index 00000000000..3ac87dc466f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/03_interval.mdx
@@ -0,0 +1,31 @@
+---
+title: "INTERVAL"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/03_interval/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `INTERVAL` procedure sets how often to run a job.
+
+```sql
+INTERVAL(<job> BINARY_INTEGER, <interval> VARCHAR2)
+```
+
+## Parameters
+
+`job`
+
+ Identifier of the job to modify.
+
+`interval`
+
+ Date function that, when evaluated, provides the next date/time to run the job. If `interval` is `NULL` and the job is complete, the job is removed from the queue.
+
+## Examples
+
+Change the job to run once a week:
+
+```sql
+BEGIN
+    DBMS_JOB.INTERVAL(104,'SYSDATE + 7');
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/04_next_date.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/04_next_date.mdx
new file mode 100644
index 00000000000..e1663fa22ab
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/04_next_date.mdx
@@ -0,0 +1,31 @@
+---
+title: "NEXT_DATE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/04_next_date/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `NEXT_DATE` procedure sets the date/time to run the job next.
+
+```sql
+NEXT_DATE(<job> BINARY_INTEGER, <next_date> DATE)
+```
+
+## Parameters
+
+`job`
+
+ Identifier of the job whose next run date you want to set.
+
+`next_date`
+
+ Date/time when you want the job run next.
+
+## Examples
+
+Change the job to run next on December 14, 2007:
+
+```sql
+BEGIN
+    DBMS_JOB.NEXT_DATE(104, TO_DATE('14-DEC-07','DD-MON-YY'));
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/05_remove.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/05_remove.mdx
new file mode 100644
index 00000000000..4fdb05afc12
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/05_remove.mdx
@@ -0,0 +1,27 @@
+---
+title: "REMOVE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/05_remove/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `REMOVE` proceduzre deletes the specified job from the database. You must resubmit the job using the `SUBMIT` procedure to execute it again. The stored procedure that was associated with the job isn't deleted.
+
+```sql
+REMOVE(<job> BINARY_INTEGER)
+```
+
+## Parameter
+
+`job`
+
+ Identifier of the job to remove from the database.
+
+## Examples
+
+Remove a job from the database:
+
+```sql
+BEGIN
+    DBMS_JOB.REMOVE(104);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/06_run.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/06_run.mdx
new file mode 100644
index 00000000000..38b26690d86
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/06_run.mdx
@@ -0,0 +1,27 @@
+---
+title: "RUN"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/06_run/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RUN` procedure forces the job to run even if its state is broken.
+
+```sql
+RUN(<job> BINARY_INTEGER)
+```
+
+## Parameter
+
+`job`
+
+ Identifier of the job to run.
+
+## Examples
+
+Force a job to run.
+
+```sql
+BEGIN
+    DBMS_JOB.RUN(104);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/07_submit.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/07_submit.mdx
new file mode 100644
index 00000000000..10d67c62db2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/07_submit.mdx
@@ -0,0 +1,68 @@
+---
+title: "SUBMIT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/07_submit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `SUBMIT` procedure creates a job definition and stores it in the database. A job consists of:
+-  A job identifier
+-  The stored procedure to execute
+-  When to first run the job
+-  A date function that calculates the next date/time for the job to run
+
+```sql
+SUBMIT(<job> OUT BINARY_INTEGER, <what> VARCHAR2
+  [, <next_date> DATE [, <interval> VARCHAR2 [, <no_parse> BOOLEAN ]]])
+```
+
+## Parameters
+
+`job`
+
+ Identifier assigned to the job.
+
+`what`
+
+ Name of the stored procedure for the job to execute.
+
+`next_date`
+
+ Date/time to run the job next. The default is `SYSDATE`.
+
+`interval`
+
+ Date function that, when evaluated, provides the next date/time for the job to run. If `interval` is set to null, then the job runs only once. Null is the default.
+
+`no_parse`
+
+ If set to `TRUE`, don't syntax-check the stored procedure upon job creation. Check only when the job first executes. If set to `FALSE`, check the procedure upon job creation. The default is `FALSE`.
+
+!!! Note 
+    The `no_parse` option isn't supported in this implementation of `SUBMIT()`. It's included only for compatibility.
+
+## Examples
+
+This example creates a job using the stored procedure `job_proc`. The job executes immediately and runs once a day after that, as set by the `interval` parameter, `SYSDATE + 1`.
+
+```sql
+DECLARE
+    jobid INTEGER;
+BEGIN
+    DBMS_JOB.SUBMIT(jobid,'job_proc;',SYSDATE,
+        'SYSDATE + 1');
+    DBMS_OUTPUT.PUT_LINE('jobid: ' || jobid);
+END;
+
+jobid: 104
+```
+
+The job immediately executes the procedure `job_proc`, populating the table `jobrun` with a row:
+
+```sql
+SELECT * FROM jobrun;
+__OUTPUT__
+            runtime
+-------------------------------------
+ job_proc run at 2007-12-11 11:43:25
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/08_what.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/08_what.mdx
new file mode 100644
index 00000000000..7c97118533d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/08_what.mdx
@@ -0,0 +1,31 @@
+---
+title: "WHAT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/08_what/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `WHAT` procedure changes the stored procedure that the job executes.
+
+```sql
+WHAT(<job> BINARY_INTEGER, <what> VARCHAR2)
+```
+
+## Parameters
+
+`job`
+
+ Identifier of the job whose stored procedure you want to change.
+
+`what`
+
+ Name of the stored procedure to execute.
+
+## Examples
+
+Change the job to run the `list_emp` procedure:
+
+```sql
+BEGIN
+    DBMS_JOB.WHAT(104,'list_emp;');
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
new file mode 100644
index 00000000000..0a9169e4950
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/index.mdx
@@ -0,0 +1,53 @@
+---
+title: "DBMS_JOB"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.16.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.192.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.150.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/05_dbms_job/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_JOB` package's jobs are scheduled and run in the background by the `edb_job_scheduler` extension. For more information, see [EDB Job Scheduler extension](/pg_extensions/edb_job_scheduler).
+
+The `DBMS_JOB` package lets you create, schedule, and manage jobs. A job runs a stored procedure that was previously stored in the database. The `SUBMIT` procedure creates and stores a job definition. A job identifier is assigned to a job with a stored procedure and the attributes describing when and how often to run the job.
+ 
+EDB Postgres Advanced Server's implementation of `DBMS_JOB` is a partial implementation when compared to Oracle's version. The following table lists the supported `DBMS_JOB` procedures.
+
+| Function/procedure                                               | Return type | Description                                                                                                                                                 |
+| ---------------------------------------------------------------- | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `BROKEN(job, broken [, next_date ])`                             | n/a         | Specify that a given job is either broken or not broken.                                                                                                    |
+| `CHANGE(job, what, next_date, interval, instance, force)`        | n/a         | Change the job’s parameters.                                                                                                                                |
+| `INTERVAL(job, interval)`                                        | n/a         | Set the execution frequency by means of a date function that is recalculated each time the job is run. This value becomes the next date/time for execution. |
+| `NEXT_DATE(job, next_date)`                                      | n/a         | Set the next date/time to run the job.                                                                                                                |
+| `REMOVE(job)`                                                    | n/a         | Delete the job definition from the database.                                                                                                                |
+| `RUN(job)`                                                       | n/a         | Force execution of a job even if it's marked broken.                                                                                                      |
+| `SUBMIT(job OUT, what [, next_date [, interval [, no_parse ]]])` | n/a         | Create a job and store its definition in the database.                                                                                                    |
+| `WHAT(job, what)`                                                | n/a         | Change the stored procedure run by a job.                                                                                                                   |
+
+When and how often a job runs depends on two interacting parameters: `next_date` and `interval`. The `next_date` parameter is a date/time value that specifies the next date/time to execute the job. The `interval` parameter is a string that contains a date function that evaluates to a date/time value.
+
+Before the job executes, the expression in the `interval` parameter is evaluated. The resulting value replaces the `next_date` value stored with the job. The job is then executed. The expression in `interval` is repeatedly reevaluated before each job executes, supplying the `next_date` date/time for the next execution.
+
+These examples use the stored procedure `job_proc`. The procedure inserts a timestamp into the table `jobrun`, which contains a single column, `VARCHAR2`.
+
+```sql
+CREATE TABLE jobrun (
+    runtime VARCHAR2(40)
+);
+
+CREATE OR REPLACE PROCEDURE job_proc
+IS
+BEGIN
+    INSERT INTO jobrun VALUES ('job_proc run at ' || TO_CHAR(SYSDATE,
+        'yyyy-mm-dd hh24:mi:ss'));
+END;
+```
+
+
+<div class="toctree" maxdepth="5">
+
+broken change interval next_date remove run submit what
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/01_append.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/01_append.mdx
new file mode 100644
index 00000000000..1870084ea94
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/01_append.mdx
@@ -0,0 +1,21 @@
+---
+title: "APPEND"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/01_append/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `APPEND` procedure appends one large object to another. Both large objects must be the same type.
+
+```sql
+APPEND(<dest_lob> IN OUT { BLOB | CLOB }, <src_lob> { BLOB | CLOB })
+```
+
+## Parameters
+
+`dest_lob`
+
+ Large object locator for the destination object. Must be the same data type as `src_lob`.
+
+`src_lob`
+
+ Large object locator for the source object. Must be the same data type as `dest_lob`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/02_compare.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/02_compare.mdx
new file mode 100644
index 00000000000..5ff9b57db4f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/02_compare.mdx
@@ -0,0 +1,39 @@
+---
+title: "COMPARE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/02_compare/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `COMPARE` procedure performs an exact byte-by-byte comparison of two large objects for a given length at given offsets. The large objects being compared must be the same data type.
+
+```sql
+<status> INTEGER COMPARE(<lob_1> { BLOB | CLOB },
+   <lob_2> { BLOB | CLOB }
+   [, <amount> INTEGER [, <offset_1> INTEGER [, <offset_2> INTEGER ]]])
+```
+
+## Parameters
+
+`lob_1`
+
+ Large object locator of the first large object to compare. Must be the same data type as `lob_2`.
+
+`lob_2`
+
+ Large object locator of the second large object to compare. Must be the same data type as `lob_1`.
+
+`amount`
+
+ If the data type of the large objects is `BLOB`, then the comparison is made for `amount` bytes. If the data type of the large objects is `CLOB`, then the comparison is made for `amount` characters. The default is the maximum size of a large object.
+
+`offset_1`
+
+ Position in the first large object to begin the comparison. The first byte/character is offset 1. The default is 1.
+
+`offset_2`
+
+ Position in the second large object to begin the comparison. The first byte/character is offset 1. The default is 1.
+
+`status`
+
+ Zero if both large objects are exactly the same for the specified length for the specified offsets. Nonzero if the objects aren't the same. `NULL` if `amount`, `offset_1`, or `offset_2` are less than zero.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/03_converttoblob.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/03_converttoblob.mdx
new file mode 100644
index 00000000000..83bcb97339d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/03_converttoblob.mdx
@@ -0,0 +1,60 @@
+---
+title: "CONVERTTOBLOB"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/03_converttoblob/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CONVERTTOBLOB` procedure converts character data to binary.
+
+```sql
+CONVERTTOBLOB(<dest_lob> IN OUT BLOB, <src_clob> CLOB,
+  <amount> INTEGER, <dest_offset> IN OUT INTEGER,
+  <src_offset> IN OUT INTEGER, <blob_csid> NUMBER,
+  <lang_context> IN OUT INTEGER, <warning> OUT INTEGER)
+```
+
+## Parameters
+
+`dest_lob`
+
+ `BLOB` large object locator to which to convert the character data.
+
+`src_clob`
+
+ `CLOB` large object locator of the character data to convert.
+
+`amount`
+
+ Number of characters of `src_clob` to convert.
+
+`dest_offset IN`
+
+ Position in bytes in the destination `BLOB` where you want to begin writing the source `CLOB`. The first byte is offset 1.
+
+`dest_offset OUT`
+
+ Position in bytes in the destination `BLOB` after the write operation completes. The first byte is offset 1.
+
+`src_offset IN`
+
+ Position in characters in the source `CLOB` where you want to begin conversion to the destination `BLOB`. The first character is offset 1.
+
+`src_offset OUT`
+
+ Position in characters in the source `CLOB` after the conversion operation completes. The first character is offset 1.
+
+`blob_csid`
+
+ Character set ID of the converted destination `BLOB`.
+
+`lang_context IN`
+
+ Language context for the conversion. The default value of `0` is typically used for this setting.
+
+`lang_context OUT`
+
+ Language context after the conversion completes.
+
+`warning`
+
+ `0` if the conversion was successful, `1` if a character can't be converted.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/04_converttoclob.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/04_converttoclob.mdx
new file mode 100644
index 00000000000..2ab1e88345a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/04_converttoclob.mdx
@@ -0,0 +1,60 @@
+---
+title: "CONVERTTOCLOB"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/04_converttoclob/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CONVERTTOCLOB` procedure converts binary data to character.
+
+```sql
+CONVERTTOCLOB(<dest_lob> IN OUT CLOB, <src_blob> BLOB,
+  <amount> INTEGER, <dest_offset> IN OUT INTEGER,
+  <src_offset> IN OUT INTEGER, <blob_csid> NUMBER,
+  <lang_context> IN OUT INTEGER, <warning> OUT INTEGER)
+```
+
+## Parameters
+
+`dest_lob`
+
+ `CLOB` large object locator to which to convert the binary data.
+
+`src_blob`
+
+ `BLOB` large object locator of the binary data to convert.
+
+`amount`
+
+ Number of bytes of `src_blob` to convert.
+
+`dest_offset IN`
+
+ Position in characters in the destination `CLOB` where you want to begin writing the source `BLOB`. The first character is offset 1.
+
+`dest_offset OUT`
+
+ Position in characters in the destination `CLOB` after the write operation completes. The first character is offset 1.
+
+`src_offset IN`
+
+ Position in bytes in the source `BLOB` where you want the conversion to the destination `CLOB` to begin. The first byte is offset 1.
+
+`src_offset OUT`
+
+ Position in bytes in the source `BLOB` after the conversion operation completes. The first byte is offset 1.
+
+`blob_csid`
+
+ Character set ID of the converted destination `CLOB`.
+
+`lang_context IN`
+
+ Language context for the conversion. The default value of `0` is typically used for this setting.
+
+`lang_context OUT`
+
+ Language context after the conversion completes.
+
+`warning`
+
+ `0` if the conversion was successful, `1` if a character can't be converted.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/05_copy.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/05_copy.mdx
new file mode 100644
index 00000000000..34856bb91e4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/05_copy.mdx
@@ -0,0 +1,36 @@
+---
+title: "COPY"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/05_copy/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `COPY` procedure copies one large object to another. The source and destination large objects must be the same data type.
+
+```sql
+COPY(<dest_lob> IN OUT { BLOB | CLOB }, <src_lob>
+{ BLOB | CLOB },
+  <amount> INTEGER
+  [, <dest_offset> INTEGER [, <src_offset> INTEGER ]])
+```
+
+## Parameters
+
+`dest_lob`
+
+ Large object locator of the large object to which you want to copy `src_lob`. Must be the same data type as `src_lob`.
+
+`src_lob`
+
+ Large object locator of the large object to copy to `dest_lob`. Must be the same data type as `dest_lob`.
+
+`amount`
+
+ Number of bytes/characters of `src_lob` to copy.
+
+`dest_offset`
+
+ Position in the destination large object where you want writing of the source large object to begin. The first position is offset 1. The default is 1.
+
+`src_offset`
+
+ Position in the source large object where you want copying to the destination large object to begin. The first position is offset 1. The default is 1.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/06_erase.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/06_erase.mdx
new file mode 100644
index 00000000000..de09d11d94d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/06_erase.mdx
@@ -0,0 +1,30 @@
+---
+title: "ERASE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/06_erase/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `ERASE` procedure erases a portion of a large object. To erase a large object means to replace the specified portion with zero-byte fillers for `BLOB` or with spaces for `CLOB`. The actual size of the large object isn't altered.
+
+```sql
+ERASE(<lob_loc> IN OUT { BLOB | CLOB }, <amount> IN OUT INTEGER
+  [, <offset> INTEGER ])
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to erase.
+
+`amount IN`
+
+ Number of bytes/characters to erase.
+
+`amount OUT`
+
+ Number of bytes/characters erased. This value can be smaller than the input value if the end of the large object is reached before `amount` bytes/characters are erased.
+
+`offset`
+
+ Position in the large object where erasing begins. The first byte/character is position 1. The default is 1.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/07_get_storage_limit.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/07_get_storage_limit.mdx
new file mode 100644
index 00000000000..1bdd40ee60a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/07_get_storage_limit.mdx
@@ -0,0 +1,23 @@
+---
+title: "GET_STORAGE_LIMIT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/07_get_storage_limit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `GET_STORAGE_LIMIT` function returns the limit on the largest allowable large object.
+
+```sql
+<size> INTEGER GET_STORAGE_LIMIT(<lob_loc> BLOB)
+
+<size> INTEGER GET_STORAGE_LIMIT(<lob_loc> CLOB)
+```
+
+## Parameters
+
+`size`
+
+ Maximum allowable size of a large object in this database.
+
+`lob_loc`
+
+ This parameter is ignored but is included for compatibility.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/08_getlength.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/08_getlength.mdx
new file mode 100644
index 00000000000..2233e75bd5e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/08_getlength.mdx
@@ -0,0 +1,23 @@
+---
+title: "GETLENGTH"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/08_getlength/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `GETLENGTH` function returns the length of a large object.
+
+```sql
+<amount> INTEGER GETLENGTH(<lob_loc> BLOB)
+
+<amount> INTEGER GETLENGTH(<lob_loc> CLOB)
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object whose length to obtain.
+
+`amount`
+
+ Length of the large object for `BLOB` or characters for `CLOB`, in bytes.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/09_instr.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/09_instr.mdx
new file mode 100644
index 00000000000..e0a303365e2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/09_instr.mdx
@@ -0,0 +1,34 @@
+---
+title: "INSTR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/09_instr/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `INSTR` function returns the location of the nth occurrence of a given pattern in a large object.
+
+```sql
+<position> INTEGER INSTR(<lob_loc> { BLOB | CLOB },
+   <pattern> { RAW | VARCHAR2 } [, <offset> INTEGER [, <nth> INTEGER ]])
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object in which to search for `pattern`.
+
+`pattern`
+
+ Pattern of bytes or characters to match against the large object, `lob`. `pattern` must be `RAW` if `lob_loc` is a `BLOB`. `pattern` must be `VARCHAR2` if `lob_loc` is a `CLOB`.
+
+`offset`
+
+ Position in `lob_loc` to start search for `pattern`. The first byte/character is position 1. The default is 1.
+
+`nth`
+
+ Search for `pattern`, `nth` number of times starting at the position given by `offset`. The default is 1.
+
+`position`
+
+ Position in the large object where `pattern` appears the `nth` time, starting from the position given by `offset`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/10_read.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/10_read.mdx
new file mode 100644
index 00000000000..9c1ff519c36
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/10_read.mdx
@@ -0,0 +1,34 @@
+---
+title: "READ"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/10_read/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `READ` procedure reads a portion of a large object into a buffer.
+
+```sql
+READ(<lob_loc> { BLOB | CLOB }, <amount> IN OUT BINARY_INTEGER,
+  <offset> INTEGER, <buffer> OUT { RAW | VARCHAR2 })
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to read.
+
+`amount IN`
+
+ Number of bytes/characters to read.
+
+`amount OUT`
+
+ Number of bytes/characters read. If there's no more data to read, then `amount` returns `0` and a `DATA_NOT_FOUND` exception is thrown.
+
+`offset`
+
+ Position to begin reading. The first byte/character is position 1.
+
+`buffer`
+
+ Variable to receive the large object. If `lob_loc` is a `BLOB`, then `buffer` must be `RAW`. If `lob_loc` is a `CLOB`, then `buffer` must be `VARCHAR2`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx
new file mode 100644
index 00000000000..9d0a6785d56
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/11_substr.mdx
@@ -0,0 +1,30 @@
+---
+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
+---
+
+The `SUBSTR` function returns a portion of a large object.
+
+```sql
+<data> { RAW | VARCHAR2 } SUBSTR(<lob_loc> { BLOB | CLOB }
+   [, <amount> INTEGER [, <offset> INTEGER ]])
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to read.
+
+`amount`
+
+ Number of bytes/characters to return. Default is 32,767.
+
+`offset`
+
+ Position in the large object to begin returning data. The first byte/character is position 1. The default is 1.
+
+`data`
+
+ Returned portion of the large object to read. If `lob_loc` is a `BLOB`, the return data type is `RAW`. If `lob_loc` is a `CLOB`, the return data type is `VARCHAR2`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/12_trim.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/12_trim.mdx
new file mode 100644
index 00000000000..593eebc10f6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/12_trim.mdx
@@ -0,0 +1,21 @@
+---
+title: "TRIM"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/12_trim/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `TRIM` procedure truncates a large object to the specified length.
+
+```sql
+TRIM(<lob_loc> IN OUT { BLOB | CLOB }, <newlen> INTEGER)
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to trim.
+
+`newlen`
+
+ Number of bytes/characters to which you want to trim the large object.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/13_write.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/13_write.mdx
new file mode 100644
index 00000000000..4d1fef2b0bb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/13_write.mdx
@@ -0,0 +1,31 @@
+---
+title: "WRITE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/13_write/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `WRITE` procedure writes data into a large object. Any existing data in the large object at the specified offset for the given length is overwritten by data given in the buffer.
+
+```sql
+WRITE(<lob_loc> IN OUT { BLOB | CLOB },
+  <amount> BINARY_INTEGER,
+  <offset> INTEGER, <buffer> { RAW | VARCHAR2 })
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to write.
+
+`amount`
+
+ The number of bytes/characters in `buffer` to write to the large object.
+
+`offset`
+
+ The offset in bytes/characters from the beginning of the large object (origin is 1) for the write operation to begin.
+
+`buffer`
+
+ Contains data to write to the large object. If `lob_loc` is a `BLOB`, then `buffer` must be `RAW`. If `lob_loc` is a `CLOB`, then `buffer` must be `VARCHAR2`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/14_writeappend.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/14_writeappend.mdx
new file mode 100644
index 00000000000..40e49df26df
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/14_writeappend.mdx
@@ -0,0 +1,26 @@
+---
+title: "WRITEAPPEND"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/14_writeappend/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `WRITEAPPEND` procedure adds data to the end of a large object.
+
+```sql
+WRITEAPPEND(<lob_loc> IN OUT { BLOB | CLOB },
+  <amount> BINARY_INTEGER, <buffer> { RAW | VARCHAR2 })
+```
+
+## Parameters
+
+`lob_loc`
+
+ Large object locator of the large object to which you want to append the data.
+
+`amount`
+
+ Number of bytes/characters from `buffer` to append to the large object.
+
+`buffer`
+
+ Data to append to the large object. If `lob_loc` is a `BLOB`, then `buffer` must be `RAW`. If `lob_loc` is a `CLOB`, then `buffer` must be `VARCHAR2`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/index.mdx
new file mode 100644
index 00000000000..2194ec12356
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/index.mdx
@@ -0,0 +1,60 @@
+---
+title: "DBMS_LOB"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.17.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.193.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.151.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/06_dbms_lob/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_LOB` package lets you operate on large objects. The following table lists the supported functions and procedures. EDB Postgres Advanced Server's implementation of `DBMS_LOB` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in this table are supported.
+
+| Function/procedure                                                                                                                     | Return type     | Description                                                                                  |
+| -------------------------------------------------------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------- |
+| `APPEND(dest_lob IN OUT, src_lob)`                                                                                                     | n/a             | Appends one large object to another.                                                         |
+| `COMPARE(lob_1, lob_2 [, amount [, offset_1 [, offset_2 ]]])`                                                                          | `INTEGER`       | Compares two large objects.                                                                  |
+| `CONVERTOBLOB(dest_lob IN OUT, src_clob, amount, dest_offset IN OUT, src_offset IN OUT, blob_csid, lang_context IN OUT, warning OUT)`  | n/a             | Converts character data to binary.                                                           |
+| `CONVERTTOCLOB(dest_lob IN OUT, src_blob, amount, dest_offset IN OUT, src_offset IN OUT, blob_csid, lang_context IN OUT, warning OUT)` | n/a             | Converts binary data to character.                                                           |
+| `COPY(dest_lob IN OUT, src_lob, amount [, dest_offset [, src_offset ]])`                                                               | n/a             | Copies one large object to another.                                                          |
+| `ERASE(lob_loc IN OUT, amount IN OUT [, offset ])`                                                                                     | n/a             | Erases a large object.                                                                        |
+| `GET_STORAGE_LIMIT(lob_loc)`                                                                                                           | `INTEGER`       | Gets the storage limit for large objects.                                                     |
+| `GETLENGTH(lob_loc)`                                                                                                                   | `INTEGER`       | Gets the length of the large object.                                                          |
+| `INSTR(lob_loc, pattern [, offset [, nth ]])`                                                                                          | `INTEGER`       | Gets the position of the nth occurrence of a pattern in the large object starting at `offset` |
+| `READ(lob_loc, amount IN OUT, offset, buffer OUT)`                                                                                     | n/a             | Reads a large object.                                                                         |
+| `SUBSTR(lob_loc [, amount [, offset ]])`                                                                                               | `RAW, VARCHAR2` | Gets part of a large object.                                                                  |
+| `TRIM(lob_loc IN OUT, newlen)`                                                                                                         | n/a             | Trims a large object to the specified length.                                                 |
+| `WRITE(lob_loc IN OUT, amount, offset, buffer)`                                                                                        | n/a             | Writes data to a large object.                                                                |
+| `WRITEAPPEND(lob_loc IN OUT, amount, buffer)`                                                                                          | n/a             | Writes data from the buffer to the end of a large object.                                     |
+
+
+The following table lists the public variables available in the package.
+
+| Public variables          | Data type     | Value        |
+| ------------------------- | ------------- | ------------ |
+| `compress off`            | `INTEGER`     | `0`          |
+| `compress_on`             | `INTEGER`     | `1`          |
+| `deduplicate_off`         | `INTEGER`     | `0`          |
+| `deduplicate_on`          | `INTEGER`     | `4`          |
+| `default_csid`            | `INTEGER`     | `0`          |
+| `default_lang_ctx`        | `INTEGER`     | `0`          |
+| `encrypt_off`             | `INTEGER`     | `0`          |
+| `encrypt_on`              | `INTEGER`     | `1`          |
+| `file_readonly`           | `INTEGER`     | `0`          |
+| `lobmaxsize`              | `INTEGER`     | `1073741823` |
+| `lob_readonly`            | `INTEGER`     | `0`          |
+| `lob_readwrite`           | `INTEGER`     | `1`          |
+| `no_warning`              | `INTEGER`     | `0`          |
+| `opt_compress`            | `INTEGER`     | `1`          |
+| `opt_deduplicate`         | `INTEGER`     | `4`          |
+| `opt_encrypt`             | `INTEGER`     | `2`          |
+| `warn_inconvertible_char` | `INTEGER`     | `1`          |
+
+Lengths and offsets are measured in bytes if the large objects are `BLOB`. Lengths and offsets are measured in characters if the large objects are `CLOB`.
+
+<div class="toctree" maxdepth="5">
+
+append compare converttoblob converttoclob copy erase get_storage_limit getlength instr read substr trim write writeappend
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/07_dbms_lock.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/07_dbms_lock.mdx
new file mode 100644
index 00000000000..6544d0cb45b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/07_dbms_lock.mdx
@@ -0,0 +1,32 @@
+---
+title: "DBMS_LOCK"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.18.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.194.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.152.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/07_dbms_lock/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server provides support for the `DBMS_LOCK.SLEEP` procedure.
+
+| Function/procedure | Return type | Description                                               |
+| ------------------ | ----------- | --------------------------------------------------------- |
+| `SLEEP(seconds)`   | n/a         | Suspends a session for the specified number of `seconds`. |
+
+EDB Postgres Advanced Server's implementation of `DBMS_LOCK` is a partial implementation when compared to Oracle's version. Only `DBMS_LOCK.SLEEP` is supported.
+
+## SLEEP
+
+The `SLEEP` procedure suspends the current session for the specified number of seconds.
+
+```sql
+SLEEP(<seconds> NUMBER)
+```
+
+### Parameters
+
+`seconds`
+
+ `seconds` specifies the number of seconds for which you want to suspend the session. `seconds` can be a fractional value. For example, enter `1.75` to specify one and three-fourths of a second.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/01_get_mv_dependencies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/01_get_mv_dependencies.mdx
new file mode 100644
index 00000000000..4558fe0860d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/01_get_mv_dependencies.mdx
@@ -0,0 +1,36 @@
+---
+title: "GET_MV_DEPENDENCIES"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/01_get_mv_dependencies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+When given the name of a materialized view, `GET_MV_DEPENDENCIES` returns a list of items that depend on the specified view. The signature is:
+
+```sql
+GET_MV_DEPENDENCIES(
+  <list> IN VARCHAR2,
+  <deplist> OUT VARCHAR2);
+```
+
+## Parameters
+
+`list`
+
+ `list` specifies the name of a materialized view or a comma-separated list of materialized view names.
+
+`deplist`
+
+ `deplist` is a comma-separated list of schema-qualified dependencies. `deplist` is a `VARCHAR2` value.
+
+## Examples
+
+This example displays a list of the dependencies on a materialized view named `public.emp_view`.
+
+```sql
+DECLARE
+  deplist VARCHAR2(1000);
+BEGIN
+  DBMS_MVIEW.GET_MV_DEPENDENCIES('public.emp_view', deplist);
+  DBMS_OUTPUT.PUT_LINE('deplist: ' || deplist);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/02_refresh.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/02_refresh.mdx
new file mode 100644
index 00000000000..91355d680b2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/02_refresh.mdx
@@ -0,0 +1,91 @@
+---
+title: "REFRESH"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/02_refresh/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `REFRESH` procedure to refresh all views specified in either a comma-separated list of view names or a table of `DBMS_UTILITY.UNCL_ARRAY` values. The procedure has two signatures. Use the first form when specifying a comma-separated list of view names:
+
+```sql
+REFRESH(
+  <list> IN VARCHAR2,
+  <method> IN VARCHAR2 DEFAULT NULL,
+  <rollback_seg> IN VARCHAR2 DEFAULT NULL,
+  <push_deferred_rpc> IN BOOLEAN DEFAULT TRUE,
+  <refresh_after_errors> IN BOOLEAN DEFAULT FALSE,
+  <purge_option> IN NUMBER DEFAULT 1,
+  <parallelism> IN NUMBER DEFAULT 0,
+  <heap_size> IN NUMBER DEFAULT 0,
+  <atomic_refresh> IN BOOLEAN DEFAULT TRUE,
+  <nested> IN BOOLEAN DEFAULT FALSE);
+```
+
+Use the second form to specify view names in a table of `DBMS_UTILITY.UNCL_ARRAY` values:
+
+```sql
+REFRESH(
+  <tab> IN OUT DBMS_UTILITY.UNCL_ARRAY,
+  <method> IN VARCHAR2 DEFAULT NULL,
+  <rollback_seg> IN VARCHAR2 DEFAULT NULL,
+  <push_deferred_rpc> IN BOOLEAN DEFAULT TRUE,
+  <refresh_after_errors> IN BOOLEAN DEFAULT FALSE,
+  <purge_option> IN NUMBER DEFAULT 1,
+  <parallelism> IN NUMBER DEFAULT 0,
+  <heap_size> IN NUMBER DEFAULT 0,
+  <atomic_refresh> IN BOOLEAN DEFAULT TRUE,
+  <nested> IN BOOLEAN DEFAULT FALSE);
+```
+
+## Parameters
+
+`list`
+
+ `list` is a `VARCHAR2` value that specifies the name of a materialized view or a comma-separated list of materialized view names. The names can be schema-qualified.
+
+`tab`
+
+ `tab` is a table of `DBMS_UTILITY.UNCL_ARRAY` values that specify names of a materialized view.
+
+`method`
+
+ `method` is a `VARCHAR2` value that specifies the refresh method to apply to the specified views. The only supported method is `C`, which performs a complete refresh of the view.
+
+`rollback_seg`
+
+ `rollback_seg` is accepted for compatibility and ignored. The default is `NULL`.
+
+`push_deferred_rpc`
+
+ `push_deferred_rpc` is accepted for compatibility and ignored. The default is `TRUE`.
+
+`refresh_after_errors`
+
+ `refresh_after_errors` is accepted for compatibility and ignored. The default is `FALSE`.
+
+`purge_option`
+
+ `purge_option` is accepted for compatibility and ignored. The default is `1`.
+
+`parallelism`
+
+ `parallelism` is accepted for compatibility and ignored. The default is `0`.
+
+`heap_size IN NUMBER DEFAULT 0`,
+
+ `heap_size` is accepted for compatibility and ignored. The default is `0`.
+
+`atomic_refresh`
+
+ `atomic_refresh` is accepted for compatibility and ignored. The default is `TRUE`.
+
+`nested`
+
+ `nested` is accepted for compatibility and ignored. The default is `FALSE`.
+
+## Examples
+
+This example uses `DBMS_MVIEW.REFRESH` to perform a complete refresh on the `public.emp_view` materialized view:
+
+```sql
+EXEC DBMS_MVIEW.REFRESH(list => 'public.emp_view', method => 'C');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/03_refresh_all_mviews.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/03_refresh_all_mviews.mdx
new file mode 100644
index 00000000000..e144a2f4053
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/03_refresh_all_mviews.mdx
@@ -0,0 +1,52 @@
+---
+title: "REFRESH_ALL_MVIEWS"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/03_refresh_all_mviews/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `REFRESH_ALL_MVIEWS` procedure to refresh any materialized views that weren't refreshed since the table or view on which the view depends was modified. The signature is:
+
+```sql
+REFRESH_ALL_MVIEWS(
+  <number_of_failures> OUT BINARY_INTEGER,
+  <method> IN VARCHAR2 DEFAULT NULL,
+  <rollback_seg> IN VARCHAR2 DEFAULT NULL,
+  <refresh_after_errors> IN BOOLEAN DEFAULT FALSE,
+  <atomic_refresh> IN BOOLEAN DEFAULT TRUE);
+```
+
+## Parameters
+
+`number_of_failures`
+
+ `number_of_failures` is a `BINARY_INTEGER` that specifies the number of failures that occurred during the refresh.
+
+`method`
+
+ `method` is a `VARCHAR2` value that specifies the refresh method to apply to the specified views. The only supported method is `C`, which performs a complete refresh of the view.
+
+`rollback_seg`
+
+ `rollback_seg` is accepted for compatibility and ignored. The default is `NULL`.
+
+`refresh_after_errors`
+
+ `refresh_after_errors` is accepted for compatibility and ignored. The default is `FALSE`.
+
+`atomic_refresh`
+
+ `atomic_refresh` is accepted for compatibility and ignored. The default is `TRUE`.
+
+## Examples
+
+This example performs a complete refresh on all materialized views:
+
+```sql
+DECLARE
+  errors INTEGER;
+BEGIN
+  DBMS_MVIEW.REFRESH_ALL_MVIEWS(errors, method => 'C');
+END;
+```
+
+Upon completion, `errors` contains the number of failures.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/04_refresh_dependent.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/04_refresh_dependent.mdx
new file mode 100644
index 00000000000..b7a5dbdd975
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/04_refresh_dependent.mdx
@@ -0,0 +1,82 @@
+---
+title: "REFRESH_DEPENDENT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/04_refresh_dependent/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `REFRESH_DEPENDENT` procedure to refresh all material views that depend on the views specified in the call to the procedure. You can specify a comma-separated list or provide the view names in a table of `DBMS_UTILITY.UNCL_ARRAY` values.
+
+Use the first form of the procedure to refresh all material views that depend on the views specified in a comma-separated list:
+
+```sql
+REFRESH_DEPENDENT(
+  <number_of_failures> OUT BINARY_INTEGER,
+  <list> IN VARCHAR2,
+  <method> IN VARCHAR2 DEFAULT NULL,
+  <rollback_seg> IN VARCHAR2 DEFAULT NULL
+  <refresh_after_errors> IN BOOLEAN DEFAULT FALSE,
+  <atomic_refresh> IN BOOLEAN DEFAULT TRUE,
+  <nested> IN BOOLEAN DEFAULT FALSE);
+```
+
+Use the second form of the procedure to refresh all material views that depend on the views specified in a table of `DBMS_UTILITY.UNCL_ARRAY` values:
+
+```sql
+REFRESH_DEPENDENT(
+  <number_of_failures> OUT BINARY_INTEGER,
+  <tab> IN DBMS_UTILITY.UNCL_ARRAY,
+  <method> IN VARCHAR2 DEFAULT NULL,
+  <rollback_seg> IN VARCHAR2 DEFAULT NULL,
+  <refresh_after_errors> IN BOOLEAN DEFAULT FALSE,
+  <atomic_refresh> IN BOOLEAN DEFAULT TRUE,
+  <nested> IN BOOLEAN DEFAULT FALSE);
+```
+
+## Parameters
+
+`number_of_failures`
+
+ `number_of_failures` is a `BINARY_INTEGER` that contains the number of failures that occurred during the refresh operation.
+
+`list`
+
+ `list` is a `VARCHAR2` value that specifies the name of a materialized view or a comma-separated list of materialized view names. The names can be schema-qualified.
+
+`tab`
+
+ `tab` is a table of `DBMS_UTILITY.UNCL_ARRAY` values that specify the names of a materialized view.
+
+`method`
+
+ `method` is a `VARCHAR2` value that specifies the refresh method to apply to the specified views. The only supported method is `C`, which performs a complete refresh of the view.
+
+`rollback_seg`
+
+ `rollback_seg` is accepted for compatibility and ignored. The default is `NULL`.
+
+`refresh_after_errors`
+
+ `refresh_after_errors` is accepted for compatibility and ignored. The default is `FALSE`.
+
+`atomic_refresh`
+
+ `atomic_refresh` is accepted for compatibility and ignored. The default is `TRUE`.
+
+`nested`
+
+ `nested` is accepted for compatibility and ignored. The default is `FALSE`.
+
+## Examples
+
+This example performs a complete refresh on all materialized views that depend on a materialized view named `emp_view` that resides in the `public` schema:
+
+```sql
+DECLARE
+  errors INTEGER;
+BEGIN
+  DBMS_MVIEW.REFRESH_DEPENDENT(errors, list => 'public.emp_view', method =>
+'C');
+END;
+```
+
+Upon completion, `errors` contains the number of failures.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/index.mdx
new file mode 100644
index 00000000000..32f6da47711
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/index.mdx
@@ -0,0 +1,29 @@
+---
+title: "DBMS_MVIEW"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.19.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.195.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.153.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/08_dbms_mview/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use procedures in the `DBMS_MVIEW` package to manage and refresh materialized views and their dependencies. EDB Postgres Advanced Server provides support for the following `DBMS_MVIEW` procedures:
+
+| Procedure                                                                                                                                                                                                                                   | Return type | Description                                                                                                                                                    |
+| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `GET_MV_DEPENDENCIES(list VARCHAR2, deplist VARCHAR2);`                                                                                                                                                                                     | n/a         | The `GET_MV_DEPENDENCIES` procedure returns a list of dependencies for a specified view.                                                                       |
+| `REFRESH(list VARCHAR2, method VARCHAR2, rollback_seg VARCHAR2 , push_deferred_rpc BOOLEAN, refresh_after_errors BOOLEAN , purge_option NUMBER, parallelism NUMBER, heap_size NUMBER , atomic_refresh BOOLEAN , nested BOOLEAN);`           | n/a         | This variation of the `REFRESH` procedure refreshes all views named in a comma-separated list of view names.                                                   |
+| `REFRESH(tab dbms_utility.uncl_array, method VARCHAR2, rollback_seg VARCHAR2, push_deferred_rpc BOOLEAN, refresh_after_errors BOOLEAN, purge_option NUMBER, parallelism NUMBER, heap_size NUMBER, atomic_refresh BOOLEAN, nested BOOLEAN);` | n/a         | This variation of the `REFRESH` procedure refreshes all views named in a table of `dbms_utility.uncl_array` values.                                            |
+| `REFRESH_ALL_MVIEWS(number_of_failures BINARY_INTEGER, method VARCHAR2, rollback_seg VARCHAR2, refresh_after_errors BOOLEAN, atomic_refresh BOOLEAN);`                                                                                      | n/a         | The `REFRESH_ALL_MVIEWS` procedure refreshes all materialized views.                                                                                           |
+| `REFRESH_DEPENDENT(number_of_failures BINARY_INTEGER, list VARCHAR2, method VARCHAR2, rollback_seg VARCHAR2, refresh_after_errors BOOLEAN, atomic_refresh BOOLEAN, nested BOOLEAN);`                                                        | n/a         | This variation of the `REFRESH_DEPENDENT` procedure refreshes all views that depend on the views listed in a comma-separated list.                      |
+| `REFRESH_DEPENDENT(number_of_failures BINARY_INTEGER, tab dbms_utility.uncl_array, method VARCHAR2, rollback_seg VARCHAR2, refresh_after_errors BOOLEAN, atomic_refresh BOOLEAN, nested BOOLEAN);`                                          | n/a         | This variation of the `REFRESH_DEPENDENT` procedure refreshes all views that depend on the views listed in a table of `dbms_utility.uncl_array` values. |
+
+EDB Postgres Advanced Server's implementation of `DBMS_MVIEW` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+<div class="toctree" maxdepth="5">
+
+get_mv_dependencies refresh refresh_all_mviews refresh_dependent
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx
new file mode 100644
index 00000000000..519da36c9dd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/09_dbms_output.mdx
@@ -0,0 +1,431 @@
+---
+title: "DBMS_OUTPUT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.20.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.196.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.154.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/09_dbms_output/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_OUTPUT` package sends messages (lines of text) to a message buffer or gets messages from the message buffer. A message buffer is local to a single session. Use the `DBMS_PIPE` package to send messages between sessions.
+
+The procedures and functions available in the `DBMS_OUTPUT` package are listed in the following table.
+
+| Function/procedure                      | Return type | Description                                                                                          |
+| --------------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------- |
+| `DISABLE`                               | n/a         | Disable the capability to send and receive messages.                                                 |
+| `ENABLE(buffer_size)`                   | n/a         | Enable the capability to send and receive messages.                                                  |
+| `GET_LINE(line OUT, status OUT)`        | n/a         | Get a line from the message buffer.                                                                  |
+| `GET_LINES(lines OUT, numlines IN OUT)` | n/a         | Get multiple lines from the message buffer.                                                          |
+| `NEW_LINE`                              | n/a         | Puts an end-of-line character sequence.                                                              |
+| `PUT(item)`                             | n/a         | Puts a partial line without an end-of-line character sequence.                                       |
+| `PUT_LINE(item)`                        | n/a         | Puts a complete line with an end-of-line character sequence.                                         |
+| `SERVEROUTPUT(stdout)`                  | n/a         | Direct messages from `PUT, PUT_LINE,` or `NEW_LINE` to either standard output or the message buffer. |
+
+The following table lists the public variables available in the `DBMS_OUTPUT` package.
+
+| Public variables     | Data type     | Value     | Description        |
+| -------------------- | ------------- | --------- | ------------------ |
+| `chararr`            | `TABLE`       |           | For message lines. |
+
+## CHARARR
+
+The `CHARARR` is for storing multiple message lines.
+
+```sql
+TYPE chararr IS TABLE OF VARCHAR2(32767) INDEX BY BINARY_INTEGER;
+```
+
+## DISABLE
+
+The `DISABLE` procedure clears out the message buffer. You can no longer access any messages in the buffer at the time the `DISABLE` procedure is executed. Any messages later sent with the `PUT`, `PUT_LINE,` or `NEW_LINE` procedures are discarded. No error is returned to the sender when the `PUT`, `PUT_LINE,` or `NEW_LINE` procedures are executed and messages were disabled.
+
+Use the `ENABLE or `SERVEROUTPUT(TRUE)` procedure to reenable sending and receiving messages.
+
+```sql
+DISABLE
+```
+
+### Examples
+
+This anonymous block disables sending and receiving messages in the current session.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.DISABLE;
+END;
+```
+
+## ENABLE
+
+The `ENABLE` procedure enables you to send messages to or retrieve messages from the message buffer. Running `SERVEROUTPUT(TRUE)` also implicitly performs the `ENABLE` procedure.
+
+The destination of a message sent with `PUT`, `PUT_LINE`, or `NEW_LINE` depends on the state of `SERVEROUTPUT`.
+
+-   If the last state of `SERVEROUTPUT` is `TRUE`, the message goes to standard output of the command line.
+-   If the last state of `SERVEROUTPUT` is `FALSE`, the message goes to the message buffer.
+
+```sql
+ENABLE [ (<buffer_size> INTEGER) ]
+```
+
+### Parameter
+
+`buffer_size`
+
+ Maximum length of the message buffer in bytes. If you specify a `buffer_size` of less than 2000, the buffer size is set to 2000.
+
+### Examples
+
+This anonymous block enables messages. Setting `SERVEROUTPUT(TRUE)` forces them to standard output.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.ENABLE;
+    DBMS_OUTPUT.SERVEROUTPUT(TRUE);
+    DBMS_OUTPUT.PUT_LINE('Messages enabled');
+END;
+
+Messages enabled
+```
+
+You can achieve the same effect by using `SERVEROUTPUT(TRUE)`.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.SERVEROUTPUT(TRUE);
+    DBMS_OUTPUT.PUT_LINE('Messages enabled');
+END;
+
+Messages enabled
+```
+
+This anonymous block enables messages, but setting `SERVEROUTPUT(FALSE)` directs messages to the message buffer.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.ENABLE;
+    DBMS_OUTPUT.SERVEROUTPUT(FALSE);
+    DBMS_OUTPUT.PUT_LINE('Message sent to buffer');
+END;
+```
+
+## GET_LINE
+
+The `GET_LINE` procedure retrieves a line of text from the message buffer. Only text that was terminated by an end-of-line character sequence is retrieved. That includes complete lines generated using `PUT_LINE` or by a series of `PUT` calls followed by a `NEW_LINE` call.
+
+```sql
+GET_LINE(<line> OUT VARCHAR2, <status> OUT INTEGER)
+```
+
+### Parameters
+
+`line`
+
+ Variable receiving the line of text from the message buffer.
+
+`status`
+
+ `0` if a line was returned from the message buffer, `1` if there was no line to return.
+
+### Examples
+
+This anonymous block writes the `emp` table out to the message buffer as a comma-delimited string for each row.
+
+```sql
+EXEC DBMS_OUTPUT.SERVEROUTPUT(FALSE);
+
+DECLARE
+    v_emprec        VARCHAR2(120);
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    DBMS_OUTPUT.ENABLE;
+    FOR i IN emp_cur LOOP
+        v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
+            NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
+            ',' || i.sal || ',' ||
+            NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+    END LOOP;
+END;
+```
+
+This anonymous block reads the message buffer and inserts the messages written by the prior example into a table named `messages`. The rows in `messages` are then displayed.
+
+```sql
+CREATE TABLE messages (
+    status          INTEGER,
+    msg             VARCHAR2(100)
+);
+
+DECLARE
+    v_line          VARCHAR2(100);
+    v_status        INTEGER := 0;
+BEGIN
+    DBMS_OUTPUT.GET_LINE(v_line,v_status);
+    WHILE v_status = 0 LOOP
+        INSERT INTO messages VALUES(v_status, v_line);
+        DBMS_OUTPUT.GET_LINE(v_line,v_status);
+    END LOOP;
+END;
+
+SELECT msg FROM messages;
+__OUTPUT__
+                               msg
+-----------------------------------------------------------------
+ 7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+ 7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+ 7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+ 7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+ 7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+ 7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+ 7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+ 7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+ 7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+ 7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+ 7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+ 7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+ 7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+ 7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+(14 rows)
+```
+
+## GET_LINES
+
+The `GET_LINES` procedure retrieves one or more lines of text from the message buffer into a collection. Only text that was terminated by an end-of-line character sequence is retrieved. That includes complete lines generated using `PUT_LINE` or by a series of `PUT` calls followed by a `NEW_LINE` call.
+
+```sql
+GET_LINES(<lines> OUT CHARARR, <numlines> IN OUT INTEGER)
+```
+
+### Parameters
+
+`lines`
+
+ Table receiving the lines of text from the message buffer. See `CHARARR` for a description of `lines.`
+
+`numlines IN`
+
+ Number of lines to retrieve from the message buffer.
+
+`numlines OUT`
+
+ Actual number of lines retrieved from the message buffer. If the output value of `numlines` is less than the input value, then no more lines are left in the message buffer.
+
+### Examples
+
+This example uses the `GET_LINES` procedure to store all rows from the `emp` table that were placed in the message buffer into an array.
+
+```sql
+EXEC DBMS_OUTPUT.SERVEROUTPUT(FALSE);
+
+DECLARE
+    v_emprec        VARCHAR2(120);
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    DBMS_OUTPUT.ENABLE;
+    FOR i IN emp_cur LOOP
+        v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
+            NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
+            ',' || i.sal || ',' ||
+            NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+    END LOOP;
+END;
+
+DECLARE
+    v_lines         DBMS_OUTPUT.CHARARR;
+    v_numlines      INTEGER := 14;
+    v_status        INTEGER := 0;
+BEGIN
+    DBMS_OUTPUT.GET_LINES(v_lines,v_numlines);
+    FOR i IN 1..v_numlines LOOP
+        INSERT INTO messages VALUES(v_numlines, v_lines(i));
+    END LOOP;
+END;
+
+SELECT msg FROM messages;
+__OUTPUT__
+                               msg
+-----------------------------------------------------------------
+ 7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+ 7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+ 7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+ 7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+ 7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+ 7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+ 7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+ 7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+ 7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+ 7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+ 7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+ 7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+ 7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+ 7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+(14 rows)
+```
+
+## NEW_LINE
+
+The `NEW_LINE` procedure writes an end-of-line character sequence in the message buffer.
+
+```sql
+NEW_LINE
+```
+
+### Parameter
+
+The `NEW_LINE` procedure expects no parameters.
+
+## PUT
+
+The `PUT` procedure writes a string to the message buffer. No end-of-line character sequence is written at the end of the string. Use the `NEW_LINE` procedure to add an end-of-line character sequence.
+
+```sql
+PUT(<item> VARCHAR2)
+```
+
+### Parameter
+
+`item`
+
+ Text written to the message buffer.
+
+### Examples
+
+The following example uses the `PUT` procedure to display a comma-delimited list of employees from the `emp` table.
+
+```sql
+DECLARE
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    FOR i IN emp_cur LOOP
+        DBMS_OUTPUT.PUT(i.empno);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.ename);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.job);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.mgr);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.hiredate);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.sal);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.comm);
+        DBMS_OUTPUT.PUT(',');
+        DBMS_OUTPUT.PUT(i.deptno);
+        DBMS_OUTPUT.NEW_LINE;
+    END LOOP;
+END;
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+## PUT_LINE
+
+The `PUT_LINE` procedure writes a single line to the message buffer including an end-of-line character sequence.
+
+```text
+PUT_LINE(<item> VARCHAR2)
+```
+
+### Parameter
+
+`item`
+
+ Text to write to the message buffer.
+
+### Examples
+
+This example uses the `PUT_LINE` procedure to display a comma-delimited list of employees from the `emp` table.
+
+```sql
+DECLARE
+    v_emprec        VARCHAR2(120);
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    FOR i IN emp_cur LOOP
+        v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
+            NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
+            ',' || i.sal || ',' ||
+            NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+    END LOOP;
+END;
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+## SERVEROUTPUT
+
+The `SERVEROUTPUT` procedure directs messages to standard output of the command line or to the message buffer. Setting `SERVEROUTPUT(TRUE)` also performs an implicit execution of `ENABLE`.
+
+The default setting of `SERVEROUTPUT` depends on the implementation. For example, in Oracle SQL\*Plus, `SERVEROUTPUT(FALSE)` is the default. In PSQL, `SERVEROUTPUT(TRUE)` is the default. Also, in Oracle SQL\*Plus, you control this setting using the SQL\*Plus `SET` comman, not by a stored procedure as implemented in EDB Postgres Advanced Server.
+
+```sql
+SERVEROUTPUT(<stdout> BOOLEAN)
+```
+
+To get an Oracle-style display output, you can set the `dbms_output.serveroutput` to `FALSE` in the `postgresql.conf` file, which disables the message output. The default is `TRUE`, which enables the message output.
+
+### Parameter
+
+`stdout`
+
+ Set to `TRUE` if you want subsequent `PUT`, `PUT_LINE`, or `NEW_LINE` to send text directly to standard output of the command line. Set to `FALSE` to send text to the message buffer.
+
+### Examples
+
+This anonymous block sends the first message to the command line and the second message to the message buffer.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.SERVEROUTPUT(TRUE);
+    DBMS_OUTPUT.PUT_LINE('This message goes to the command line');
+    DBMS_OUTPUT.SERVEROUTPUT(FALSE);
+    DBMS_OUTPUT.PUT_LINE('This message goes to the message buffer');
+END;
+
+This message goes to the command line
+```
+
+If, in the same session, the following anonymous block is executed, the message stored in the message buffer from the prior example is flushed. It's displayed on the command line along with the new message.
+
+```sql
+BEGIN
+    DBMS_OUTPUT.SERVEROUTPUT(TRUE);
+    DBMS_OUTPUT.PUT_LINE('Flush messages from the buffer');
+END;
+
+This message goes to the message buffer
+Flush messages from the buffer
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/01_create_pipe.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/01_create_pipe.mdx
new file mode 100644
index 00000000000..b83a954f388
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/01_create_pipe.mdx
@@ -0,0 +1,56 @@
+---
+title: "CREATE_PIPE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/01_create_pipe/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CREATE_PIPE` function creates an explicit public pipe or an explicit private pipe with a specified name.
+
+```sql
+<status> INTEGER CREATE_PIPE(<pipename> VARCHAR2
+   [, <maxpipesize> INTEGER ] [, <private> BOOLEAN ])
+```
+
+## Parameters
+
+`pipename`
+
+ Name of the pipe.
+
+`maxpipesize`
+
+ Maximum capacity of the pipe in bytes. Default is 8192 bytes.
+
+`private`
+
+ Create a public pipe if set to `FALSE`. Create a private pipe if set to `TRUE.` This is the default.
+
+`status`
+
+ Status code returned by the operation. `0` indicates successful creation.
+
+## Examples
+
+This example creates a private pipe named `messages`:
+
+```sql
+DECLARE
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.CREATE_PIPE('messages');
+    DBMS_OUTPUT.PUT_LINE('CREATE_PIPE status: ' || v_status);
+END;
+CREATE_PIPE status: 0
+```
+
+This example creates a public pipe named `mailbox`:
+
+```sql
+DECLARE
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.CREATE_PIPE('mailbox',8192,FALSE);
+    DBMS_OUTPUT.PUT_LINE('CREATE_PIPE status: ' || v_status);
+END;
+CREATE_PIPE status: 0
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/02_next_item_pipe.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/02_next_item_pipe.mdx
new file mode 100644
index 00000000000..e2c9bf0fa0a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/02_next_item_pipe.mdx
@@ -0,0 +1,116 @@
+---
+title: "NEXT_ITEM_TYPE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/02_next_item_pipe/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `NEXT_ITEM_TYPE` function returns an integer code identifying the data type of the next data item in a message that was retrieved into the session’s local message buffer. As each item is moved off of the local message buffer with the `UNPACK_MESSAGE` procedure, the `NEXT_ITEM_TYPE` function returns the data type code for the next available item. A code of `0` is returned when no more items are left in the message.
+
+```sql
+<typecode> INTEGER NEXT_ITEM_TYPE
+```
+
+## Parameters
+
+`typecode`
+
+ Code identifying the data type of the next data item is shown in the following table.
+
+| Type code | Data type          |
+| --------- | ------------------ |
+| `0`       | No more data items |
+| `9`       | `NUMBER`           |
+| `11`      | `VARCHAR2`         |
+| `13`      | `DATE`             |
+| `23`      | `RAW`              |
+
+ !!! Note
+    The type codes listed in the table aren't compatible with Oracle databases. Oracle assigns a different numbering sequence to the data types.
+
+## Examples
+
+This example shows a pipe packed with a `NUMBER` item, a `VARCHAR2` item, a `DATE` item, and a `RAW` item. A second anonymous block then uses the `NEXT_ITEM_TYPE` function to display the type code of each item.
+
+```sql
+DECLARE
+    v_number        NUMBER := 123;
+    v_varchar       VARCHAR2(20) := 'Character data';
+    v_date          DATE := SYSDATE;
+    v_raw           RAW(4) := '21222324';
+    v_status        INTEGER;
+BEGIN
+    DBMS_PIPE.PACK_MESSAGE(v_number);
+    DBMS_PIPE.PACK_MESSAGE(v_varchar);
+    DBMS_PIPE.PACK_MESSAGE(v_date);
+    DBMS_PIPE.PACK_MESSAGE(v_raw);
+    v_status := DBMS_PIPE.SEND_MESSAGE('datatypes');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+SEND_MESSAGE status: 0
+
+DECLARE
+    v_number        NUMBER;
+    v_varchar       VARCHAR2(20);
+    v_date          DATE;
+    v_timestamp     TIMESTAMP;
+    v_raw           RAW(4);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('datatypes');
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+    DBMS_OUTPUT.PUT_LINE('----------------------------------');
+
+    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+    DBMS_OUTPUT.PUT_LINE('NEXT_ITEM_TYPE: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_number);
+    DBMS_OUTPUT.PUT_LINE('NUMBER Item   : ' || v_number);
+    DBMS_OUTPUT.PUT_LINE('----------------------------------');
+
+    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+    DBMS_OUTPUT.PUT_LINE('NEXT_ITEM_TYPE: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_varchar);
+    DBMS_OUTPUT.PUT_LINE('VARCHAR2 Item : ' || v_varchar);
+    DBMS_OUTPUT.PUT_LINE('----------------------------------');
+
+    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+    DBMS_OUTPUT.PUT_LINE('NEXT_ITEM_TYPE: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_date);
+    DBMS_OUTPUT.PUT_LINE('DATE Item     : ' || v_date);
+    DBMS_OUTPUT.PUT_LINE('----------------------------------');
+
+    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+    DBMS_OUTPUT.PUT_LINE('NEXT_ITEM_TYPE: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_raw);
+    DBMS_OUTPUT.PUT_LINE('RAW Item      : ' || v_raw);
+    DBMS_OUTPUT.PUT_LINE('----------------------------------');
+
+    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+    DBMS_OUTPUT.PUT_LINE('NEXT_ITEM_TYPE: ' || v_status);
+    DBMS_OUTPUT.PUT_LINE('---------------------------------');
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+RECEIVE_MESSAGE status: 0
+----------------------------------
+NEXT_ITEM_TYPE: 9
+NUMBER Item   : 123
+----------------------------------
+NEXT_ITEM_TYPE: 11
+VARCHAR2 Item : Character data
+----------------------------------
+NEXT_ITEM_TYPE: 13
+DATE Item     : 02-OCT-07 11:11:43
+----------------------------------
+NEXT_ITEM_TYPE: 23
+RAW Item      : 21222324
+----------------------------------
+NEXT_ITEM_TYPE: 0
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/03_pack_message.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/03_pack_message.mdx
new file mode 100644
index 00000000000..6c05d934b6b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/03_pack_message.mdx
@@ -0,0 +1,19 @@
+---
+title: "PACK_MESSAGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/03_pack_message/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `PACK_MESSAGE` procedure places an item of data in the session’s local message buffer. You must execute `PACK_MESSAGE` at least once before issuing a `SEND_MESSAGE` call.
+
+```sql
+PACK_MESSAGE(<item> { DATE | NUMBER | VARCHAR2 | RAW })
+```
+
+Use the `UNPACK_MESSAGE` procedure to obtain data items once the message is retrieved using a `RECEIVE_MESSAGE` call.
+
+## Parameters
+
+`item`
+
+ An expression evaluating to any of the acceptable parameter data types. The value is added to the session’s local message buffer.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/04_purge.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/04_purge.mdx
new file mode 100644
index 00000000000..742f397a609
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/04_purge.mdx
@@ -0,0 +1,77 @@
+---
+title: "PURGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/04_purge/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `PURGE` procedure removes the unreceived messages from a specified implicit pipe.
+
+```sql
+PURGE(<pipename> VARCHAR2)
+```
+
+Use the `REMOVE_PIPE` function to delete an explicit pipe.
+
+## Parameters
+
+`pipename`
+
+ Name of the pipe.
+
+## Examples
+
+Two messages are sent on a pipe:
+
+```sql
+DECLARE
+    v_status        INTEGER;
+BEGIN
+    DBMS_PIPE.PACK_MESSAGE('Message #1');
+    v_status := DBMS_PIPE.SEND_MESSAGE('pipe');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+
+    DBMS_PIPE.PACK_MESSAGE('Message #2');
+    v_status := DBMS_PIPE.SEND_MESSAGE('pipe');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+END;
+
+SEND_MESSAGE status: 0
+SEND_MESSAGE status: 0
+```
+
+Receive the first message and unpack it:
+
+```sql
+DECLARE
+    v_item          VARCHAR2(80);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('pipe',1);
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_item);
+    DBMS_OUTPUT.PUT_LINE('Item: ' || v_item);
+END;
+
+RECEIVE_MESSAGE status: 0
+Item: Message #1
+```
+
+Purge the pipe:
+
+```sql
+EXEC DBMS_PIPE.PURGE('pipe');
+```
+
+Try to retrieve the next message. The `RECEIVE_MESSAGE` call returns status code `1` indicating it timed out because no message was available.
+
+```sql
+DECLARE
+    v_item          VARCHAR2(80);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('pipe',1);
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+END;
+
+RECEIVE_MESSAGE status: 1
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/05_receive_message.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/05_receive_message.mdx
new file mode 100644
index 00000000000..5ef1c01247b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/05_receive_message.mdx
@@ -0,0 +1,34 @@
+---
+title: "RECEIVE_MESSAGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/05_receive_message/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RECEIVE_MESSAGE` function obtains a message from a specified pipe.
+
+```sql
+<status> INTEGER RECEIVE_MESSAGE(<pipename> VARCHAR2
+   [, <timeout> INTEGER ])
+```
+
+## Parameters
+
+`pipename`
+
+ Name of the pipe.
+
+`timeout`
+
+ Wait time (seconds). Default is 86400000 (1000 days).
+
+`status`
+
+ Status code returned by the operation.
+
+ The possible status codes are:
+
+| Status code | Description                      |
+| ----------- | -------------------------------- |
+| `0`         | Success                          |
+| `1`         | Time out                         |
+| `2`         | Message too large for the buffer |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/06_remove_pipe.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/06_remove_pipe.mdx
new file mode 100644
index 00000000000..679be0c4e3a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/06_remove_pipe.mdx
@@ -0,0 +1,90 @@
+---
+title: "REMOVE_PIPE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/06_remove_pipe/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `REMOVE_PIPE` function deletes an explicit private or explicit public pipe.
+
+```sql
+<status> INTEGER REMOVE_PIPE(<pipename> VARCHAR2)
+```
+
+Use the `REMOVE_PIPE` function to delete explicitly created pipes, that is, pipes created with the `CREATE_PIPE` function.
+
+## Parameters
+
+`pipename`
+
+ Name of the pipe.
+
+`status`
+
+ Status code returned by the operation. A status code of `0` is returned even if the named pipe is nonexistent.
+
+## Examples
+
+Two messages are sent on a pipe:
+
+```sql
+DECLARE
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.CREATE_PIPE('pipe');
+    DBMS_OUTPUT.PUT_LINE('CREATE_PIPE status : ' || v_status);
+
+    DBMS_PIPE.PACK_MESSAGE('Message #1');
+    v_status := DBMS_PIPE.SEND_MESSAGE('pipe');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+
+    DBMS_PIPE.PACK_MESSAGE('Message #2');
+    v_status := DBMS_PIPE.SEND_MESSAGE('pipe');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+END;
+
+CREATE_PIPE status : 0
+SEND_MESSAGE status: 0
+SEND_MESSAGE status: 0
+```
+
+Receive the first message and unpack it:
+
+```sql
+DECLARE
+    v_item          VARCHAR2(80);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('pipe',1);
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_item);
+    DBMS_OUTPUT.PUT_LINE('Item: ' || v_item);
+END;
+
+RECEIVE_MESSAGE status: 0
+Item: Message #1
+```
+
+Remove the pipe:
+
+```sql
+SELECT DBMS_PIPE.REMOVE_PIPE('pipe') FROM DUAL;
+__OUTPUT__
+remove_pipe
+-------------
+        0
+(1 row)
+```
+
+Try to retrieve the next message. The `RECEIVE_MESSAGE` call returns status code `1` indicating it timed out because the pipe was deleted.
+
+```sql
+DECLARE
+    v_item          VARCHAR2(80);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('pipe',1);
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+END;
+
+RECEIVE_MESSAGE status: 1
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/07_reset_buffer.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/07_reset_buffer.mdx
new file mode 100644
index 00000000000..bc883c9d826
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/07_reset_buffer.mdx
@@ -0,0 +1,52 @@
+---
+title: "RESET_BUFFER"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/07_reset_buffer/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `RESET_BUFFER` procedure resets a pointer to the session’s local message buffer back to the beginning of the buffer. This causes later `PACK_MESSAGE` calls to overwrite any data items that were in the message buffer before the `RESET_BUFFER` call.
+
+```sql
+RESET_BUFFER
+```
+
+## Examples
+
+A message to John is written to the local message buffer. It is replaced by a message to Bob by calling `RESET_BUFFER`. The message is sent on the pipe.
+
+```sql
+DECLARE
+    v_status        INTEGER;
+BEGIN
+    DBMS_PIPE.PACK_MESSAGE('Hi, John');
+    DBMS_PIPE.PACK_MESSAGE('Can you attend a meeting at 3:00, today?');
+    DBMS_PIPE.PACK_MESSAGE('If not, is tomorrow at 8:30 ok with you?');
+    DBMS_PIPE.RESET_BUFFER;
+    DBMS_PIPE.PACK_MESSAGE('Hi, Bob');
+    DBMS_PIPE.PACK_MESSAGE('Can you attend a meeting at 9:30, tomorrow?');
+    v_status := DBMS_PIPE.SEND_MESSAGE('pipe');
+    DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE status: ' || v_status);
+END;
+
+SEND_MESSAGE status: 0
+```
+
+The message to Bob is in the received message:
+
+```sql
+DECLARE
+    v_item          VARCHAR2(80);
+    v_status        INTEGER;
+BEGIN
+    v_status := DBMS_PIPE.RECEIVE_MESSAGE('pipe',1);
+    DBMS_OUTPUT.PUT_LINE('RECEIVE_MESSAGE status: ' || v_status);
+    DBMS_PIPE.UNPACK_MESSAGE(v_item);
+    DBMS_OUTPUT.PUT_LINE('Item: ' || v_item);
+    DBMS_PIPE.UNPACK_MESSAGE(v_item);
+    DBMS_OUTPUT.PUT_LINE('Item: ' || v_item);
+END;
+
+RECEIVE_MESSAGE status: 0
+Item: Hi, Bob
+Item: Can you attend a meeting at 9:30, tomorrow?
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/08_send_message.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/08_send_message.mdx
new file mode 100644
index 00000000000..f820ef919b9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/08_send_message.mdx
@@ -0,0 +1,38 @@
+---
+title: "SEND_MESSAGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/08_send_message/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `SEND_MESSAGE` function sends a message from the session’s local message buffer to the specified pipe.
+
+```sql
+<status> SEND_MESSAGE(<pipename> VARCHAR2 [, <timeout> INTEGER ]
+   [, <maxpipesize> INTEGER ])
+```
+
+## Parameters
+
+`pipename`
+
+ Name of the pipe.
+
+`timeout`
+
+ Wait time (seconds). Default is 86400000 (1000 days).
+
+`maxpipesize`
+
+ Maximum capacity of the pipe in bytes. Default is 8192 bytes.
+
+`status`
+
+ Status code returned by the operation.
+
+ The possible status codes are:
+
+| Status code | Description          |
+| ----------- | -------------------- |
+| `0`         | Success              |
+| `1`         | Time out             |
+| `3`         | Function interrupted |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/09_unique_session_name.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/09_unique_session_name.mdx
new file mode 100644
index 00000000000..2deb54b9b80
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/09_unique_session_name.mdx
@@ -0,0 +1,32 @@
+---
+title: "UNIQUE_SESSION_NAME"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/09_unique_session_name/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UNIQUE_SESSION_NAME` function returns a name that is unique to the current session.
+
+```sql
+<name> VARCHAR2 UNIQUE_SESSION_NAME
+```
+
+## Parameters
+
+`name`
+
+ Unique session name.
+
+## Examples
+
+The following anonymous block retrieves and displays a unique session name:
+
+```sql
+DECLARE
+    v_session       VARCHAR2(30);
+BEGIN
+    v_session := DBMS_PIPE.UNIQUE_SESSION_NAME;
+    DBMS_OUTPUT.PUT_LINE('Session Name: ' || v_session);
+END;
+
+Session Name: PG$PIPE$5$2752
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/10_unpack_message.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/10_unpack_message.mdx
new file mode 100644
index 00000000000..59313a90e21
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/10_unpack_message.mdx
@@ -0,0 +1,17 @@
+---
+title: "UNPACK_MESSAGE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/10_unpack_message/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UNPACK_MESSAGE` procedure copies the data items of a message from the local message buffer to a specified program variable. You must place the message in the local message buffer with the `RECEIVE_MESSAGE` function before using `UNPACK_MESSAGE`.
+
+```sql
+UNPACK_MESSAGE(<item> OUT { DATE | NUMBER | VARCHAR2 | RAW })
+```
+
+## Parameters
+
+`item`
+
+ Type-compatible variable that receives a data item from the local message buffer.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/11_comprehensive_example.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/11_comprehensive_example.mdx
new file mode 100644
index 00000000000..7f64c168deb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/11_comprehensive_example.mdx
@@ -0,0 +1,160 @@
+---
+title: "Comprehensive example"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/11_comprehensive_example/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This example uses a pipe as a “mailbox." Three procedures are enclosed in a package named `mailbox`. These procedures:
+
+1.  Create the mailbox.
+2.  Add a multi-item message to the mailbox (up to three items). 
+3.  Display the full contents of the mailbox.
+
+```sql
+CREATE OR REPLACE PACKAGE mailbox
+IS
+    PROCEDURE create_mailbox;
+    PROCEDURE add_message (
+        p_mailbox   VARCHAR2,
+        p_item_1    VARCHAR2,
+        p_item_2    VARCHAR2 DEFAULT 'END',
+        p_item_3    VARCHAR2 DEFAULT 'END'
+    );
+    PROCEDURE empty_mailbox (
+        p_mailbox   VARCHAR2,
+        p_waittime  INTEGER DEFAULT 10
+    );
+END mailbox;
+
+CREATE OR REPLACE PACKAGE BODY mailbox
+IS
+    PROCEDURE create_mailbox
+    IS
+        v_mailbox   VARCHAR2(30);
+        v_status    INTEGER;
+    BEGIN
+        v_mailbox := DBMS_PIPE.UNIQUE_SESSION_NAME;
+        v_status := DBMS_PIPE.CREATE_PIPE(v_mailbox,1000,FALSE);
+        IF v_status = 0 THEN
+            DBMS_OUTPUT.PUT_LINE('Created mailbox: ' || v_mailbox);
+        ELSE
+            DBMS_OUTPUT.PUT_LINE('CREATE_PIPE failed - status: ' ||
+                v_status);
+        END IF;
+    END create_mailbox;
+
+    PROCEDURE add_message (
+        p_mailbox   VARCHAR2,
+        p_item_1    VARCHAR2,
+        p_item_2    VARCHAR2 DEFAULT 'END',
+        p_item_3    VARCHAR2 DEFAULT 'END'
+    )
+    IS
+        v_item_cnt  INTEGER := 0;
+        v_status    INTEGER;
+    BEGIN
+        DBMS_PIPE.PACK_MESSAGE(p_item_1);
+        v_item_cnt := 1;
+        IF p_item_2 != 'END' THEN
+            DBMS_PIPE.PACK_MESSAGE(p_item_2);
+            v_item_cnt := v_item_cnt + 1;
+        END IF;
+        IF p_item_3 != 'END' THEN
+            DBMS_PIPE.PACK_MESSAGE(p_item_3);
+            v_item_cnt := v_item_cnt + 1;
+        END IF;
+        v_status := DBMS_PIPE.SEND_MESSAGE(p_mailbox);
+        IF v_status = 0 THEN
+            DBMS_OUTPUT.PUT_LINE('Added message with ' || v_item_cnt ||
+                ' item(s) to mailbox ' || p_mailbox);
+        ELSE
+            DBMS_OUTPUT.PUT_LINE('SEND_MESSAGE in add_message failed - ' ||
+                'status: ' || v_status);
+        END IF;
+    END add_message;
+
+    PROCEDURE empty_mailbox (
+        p_mailbox   VARCHAR2,
+        p_waittime  INTEGER DEFAULT 10
+    )
+    IS
+        v_msgno     INTEGER DEFAULT 0;
+        v_itemno    INTEGER DEFAULT 0;
+        v_item      VARCHAR2(100);
+        v_status    INTEGER;
+    BEGIN
+        v_status := DBMS_PIPE.RECEIVE_MESSAGE(p_mailbox,p_waittime);
+        WHILE v_status = 0 LOOP
+            v_msgno := v_msgno + 1;
+            DBMS_OUTPUT.PUT_LINE('****** Start message #' || v_msgno ||
+                ' ******');
+            BEGIN
+                LOOP
+                    v_status := DBMS_PIPE.NEXT_ITEM_TYPE;
+                    EXIT WHEN v_status = 0;
+                    DBMS_PIPE.UNPACK_MESSAGE(v_item);
+                    v_itemno := v_itemno + 1;
+                    DBMS_OUTPUT.PUT_LINE('Item #' || v_itemno || ': ' ||
+                        v_item);
+                END LOOP;
+                DBMS_OUTPUT.PUT_LINE('******* End message #' || v_msgno ||
+                    ' *******');
+                DBMS_OUTPUT.PUT_LINE('*');
+                v_itemno := 0;
+                v_status := DBMS_PIPE.RECEIVE_MESSAGE(p_mailbox,1);
+            END;
+        END LOOP;
+        DBMS_OUTPUT.PUT_LINE('Number of messages received: ' || v_msgno);
+        v_status := DBMS_PIPE.REMOVE_PIPE(p_mailbox);
+        IF v_status = 0 THEN
+            DBMS_OUTPUT.PUT_LINE('Deleted mailbox ' || p_mailbox);
+        ELSE
+            DBMS_OUTPUT.PUT_LINE('Could not delete mailbox - status: '
+                || v_status);
+        END IF;
+    END empty_mailbox;
+END mailbox;
+```
+
+The following shows executing the procedures in `mailbox`. The first procedure creates a public pipe using a name generated by the `UNIQUE_SESSION_NAME` function.
+
+```sql
+EXEC mailbox.create_mailbox;
+
+Created mailbox: PG$PIPE$13$3940
+```
+
+Using the mailbox name, any user in the same database with access to the `mailbox` package and `DBMS_PIPE` package can add messages:
+
+```sql
+EXEC mailbox.add_message('PG$PIPE$13$3940','Hi, John','Can you attend a
+meeting at 3:00, today?','-- Mary');
+
+Added message with 3 item(s) to mailbox PG$PIPE$13$3940
+
+EXEC mailbox.add_message('PG$PIPE$13$3940','Don''t forget to submit your
+report','Thanks,','-- Joe');
+
+Added message with 3 item(s) to mailbox PG$PIPE$13$3940
+```
+
+Finally, the contents of the mailbox can be emptied:
+
+```sql
+EXEC mailbox.empty_mailbox('PG$PIPE$13$3940');
+
+****** Start message #1 ******
+Item #1: Hi, John
+Item #2: Can you attend a meeting at 3:00, today?
+Item #3: -- Mary
+******* End message #1 *******
+*
+****** Start message #2 ******
+Item #1: Don't forget to submit your report
+Item #2: Thanks,
+Item #3: Joe
+******* End message #2 *******
+*
+Number of messages received: 2
+Deleted mailbox PG$PIPE$13$3940
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/index.mdx
new file mode 100644
index 00000000000..e6640c7ef1d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/index.mdx
@@ -0,0 +1,45 @@
+---
+title: "DBMS_PIPE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.21.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.197.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.155.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/10_dbms_pipe/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_PIPE` package lets you send messages through a pipe in or between sessions connected to the same database cluster.
+
+The table shows the procedures and functions available in the `DBMS_PIPE` package:
+
+| Function/procedure                                     | Return type | Description                                                                                                     |
+| ------------------------------------------------------ | ----------- | --------------------------------------------------------------------------------------------------------------- |
+| `CREATE_PIPE(pipename [, maxpipesize ] [, private ])`  | `INTEGER`   | Explicitly create a private pipe if `private` is `true` (the default) or a public pipe if `private` is `false`. |
+| `NEXT_ITEM_TYPE`                                       | `INTEGER`   | Determine the data type of the next item in a received message.                                                 |
+| `PACK_MESSAGE(item)`                                   | n/a         | Place `item` in the session’s local message buffer.                                                             |
+| `PURGE(pipename)`                                      | n/a         | Remove unreceived messages from the specified pipe.                                                             |
+| `RECEIVE_MESSAGE(pipename [, timeout ])`               | `INTEGER`   | Get a message from a specified pipe.                                                                            |
+| `REMOVE_PIPE(pipename)`                                | `INTEGER`   | Delete an explicitly created pipe.                                                                              |
+| `RESET_BUFFER`                                         | n/a         | Reset the local message buffer.                                                                                 |
+| `SEND_MESSAGE(pipename [, timeout ] [, maxpipesize ])` | `INTEGER`   | Send a message on a pipe.                                                                                       |
+| `UNIQUE_SESSION_NAME`                                  | `VARCHAR2`  | Obtain a unique session name.                                                                                   |
+| `UNPACK_MESSAGE(item OUT)`                             | n/a         | Retrieve the next data item from a message into a type-compatible variable, `item`.                             |
+
+Pipes are categorized as *implicit* or *explicit*. An implicit pipe is created if a reference is made to a pipe name that wasn't previously created by the `CREATE_PIPE` function. For example, if the `SEND_MESSAGE` function is executed using a nonexistent pipe name, a new implicit pipe is created with that name. An explicit pipe is created using the `CREATE_PIPE` function in which the first parameter specifies the pipe name for the new pipe.
+
+Pipes are also categorized as *private* or *public*. Only the user who created the pipe can access a private pipe. Even a superuser can't access a private pipe that was created by another user. Any user who has access to the `DBMS_PIPE` package can access a public pipe.
+
+You can create a public pipe only by using the `CREATE_PIPE` function with the third parameter set to `FALSE`. You can use the `CREATE_PIPE` function to create a private pipe by setting the third parameter to `TRUE` or by omitting the third parameter. All implicit pipes are private.
+
+The individual data items, or lines, of a message are first built in a *local message buffer*, unique to the current session. The `PACK_MESSAGE` procedure builds the message in the session’s local message buffer. You then use the `SEND_MESSAGE` function to send the message through the pipe.
+
+Receipt of a message involves the reverse operation. You use the `RECEIVE_MESSAGE` function to get a message from the specified pipe. The message is written to the session’s local message buffer. You then use The `UNPACK_MESSAGE` procedure to transfer the message data items from the message buffer to program variables. If a pipe contains multiple messages, `RECEIVE_MESSAGE` gets the messages in FIFO (first-in-first-out) order.
+
+Each session maintains separate message buffers for messages created with the `PACK_MESSAGE` procedure and messages retrieved by the `RECEIVE_MESSAGE` function. Thus messages can be both built and received in the same session. However, if consecutive `RECEIVE_MESSAGE` calls are made, only the message from the last `RECEIVE_MESSAGE` call is preserved in the local message buffer.
+
+<div class="toctree" maxdepth="5">
+
+create_pipe next_item_pipe pack_message purge receive_message remove_pipe reset_buffer send_message unique_session_name unpack_message comprehensive_example
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_privilege_capture.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_privilege_capture.mdx
new file mode 100644
index 00000000000..6f46f632254
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/10_dbms_privilege_capture.mdx
@@ -0,0 +1,462 @@
+---
+title: "DBMS_PRIVILEGE_CAPTURE"
+---
+
+EDB Postgres Advanced Server provides support for capturing and analyzing the privilege usage by the users. 
+
+There are two ways to capture and analyze the privilege usage:
+- Using `DBMS_PRIVILEGE_CAPTURE` package compatible to Oracle.
+- Using SQL commands.
+
+See [SQL reference](../../epas_compat_sql) for detailed information about the SQL commands:
+- [CREATE CAPTURE PRIVILEGES POLICY](../../epas_compat_sql/19a_create_capture_privilege)
+- [ALTER CAPTURE PRIVILEGES POLICY](../../epas_compat_sql/01_alter_capture_privilege)
+- [DROP CAPTURE PRIVILEGES POLICY](../../epas_compat_sql/44a_drop_capture_privilege)
+
+The `DBMS_PRIVILEGE_CAPTURE` package provides an interface for database privilege analysis. 
+
+The procedures available in the `DBMS_PRIVILEGE_CAPTURE` package are:
+
+| Function/procedure | Function or procedure | Return type |                                      Description                                      |
+| ------------------ | --------------------- | ----------- | ------------------------------------------------------------------------------------- |
+| `CREATE_CAPTURE`   | Procedure             | n/a         | Creates a policy that specifies the conditions for analyzing privilege use.           |
+| `ENABLE_CAPTURE`   | Procedure             | n/a         | Starts capturing the privilege usage for a specific privilege analysis policy.        |
+| `DISABLE_CAPTURE`  | Procedure             | n/a         | Stops capturing the privilege use for a specific privilege analysis policy.           |
+| `DROP_CAPTURE`     | Procedure             | n/a         | Removes a privilege analysis policy along with the data captured.                     |
+| `GENERATE_RESULT`  | Procedure             | n/a         | Populates the data dictionary views with the privilege analysis data                  |
+| `DELETE_RUN`       | Procedure             | n/a         | Deletes a privilege analysis capture run.                                             |
+
+
+This package enables you to create a policy that captures the use of system and object privileges granted to the users. It helps you determine that users are using the privileges or not. After analysis, you can revoke the unused privileges to help reducing the number of excess privilege grants for users.
+
+A super user or the non-super user with role `CAPTURE_ADMIN` can access the `DBMS_PRIVILEGE_CAPTURE` package. 
+
+## Configure parameters in postgresql.conf file
+
+To enable the feature, set this parameter value greater than zero in `postgresql.conf` file:
+
+`edb_max_capture_privileges_policies = 2`
+
+This parameter limits the maximum number of policies at cluster level. By default the value is 0. Set this parameter to greater than zero. Also, only one policy can be enabled per database even if `edb_max_capture_privileges_policies` value is set to more than 1. Restart the server after changing the value of this parameter.
+
+`edb_capture_privileges_hash_entries = 2000`
+
+This parameter sets the hash table size for each privilege policy. Whatever value is set, once that many records of privilege use are captured it gets flushed to DBA_USED_PRIVS and DBA_UNUSED_PRIVS system catalogs. Minimum value is 1 and the default value is 2000. Restart the server after changing the value of this parameter.
+
+## CREATE_CAPTURE
+
+The `CREATE_CAPTURE` procedure creates a privilege analysis policy that specifies the conditions for analyzing privilege use. It also, optionally specifies the roles for which privilege use is to be analyzed, and the conditions under which privilege use is to be analyzed.
+
+```sql
+DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE (
+    name        IN VARCHAR2,
+    description IN VARCHAR2 DEFAULT NULL,
+    type        IN NUMBER DEFAULT G_DATABASE,
+    roles       IN ROLE_NAME_LIST DEFAULT ROLE_NAME_LIST(),
+    condition   IN VARCHAR2 DEFAULT NULL);
+```
+
+### Parameters
+
+`name`
+
+ Name of the privilege analysis policy. A string of size up to 30 characters.
+
+`description`
+
+ Description of the policy up to 1024 characters.
+
+`type`
+
+ Type of the privilege analysis policy. Possible values are:
+ - `G_DATABASE` &mdash; Captures all privilege use in the database, except privileges used by superuser.
+ - `G_ROLE` &mdash; Captures the use of a privilege if the privilege is part of a specified role or list of roles.
+ - `G_CONTEXT` &mdash; Captures the use of a privilege if the context specified by the `condition` parameter evaluates to true.
+ - `G_ROLE_AND_CONTEXT` &mdash; Captures the use of a privilege if the privilege is part of the specified list of roles and when the condition specified by the `condition` parameter is true.
+
+`roles`
+
+ The roles whose privileges are to be analyzed. Required if the `type` is `G_ROLE` or `G_ROLE_AND_CONTEXT`.
+
+`condition`
+
+ Boolean expression containing up to 4000 characters. Required if `type` is `G_CONTEXT` or `G_ROLE_AND_CONTEXT`. 
+
+ ## ENABLE_CAPTURE
+
+`ENABLE_CAPTURE` procedure starts the recording of privilege analysis for a specified privilege analysis policy and optionally provides a capture run for this policy. After a policy is enabled, all privilege use under the policy condition is recorded.
+
+ ```sql
+ DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE (
+    name      IN VARCHAR2,
+    run_name  IN VARCHAR2 DEFAULT NULL);
+ ```
+
+### Parameters
+
+`name`
+
+ Name of the privilege analysis policy to be enabled.
+
+`run_name`
+
+ Name of the capture run to associate with this policy, less than 128 characters. Enclose exotic characters in double quotation marks.
+
+## DISABLE_CAPTURE
+
+`DISABLE_CAPTURE` procedure stops the recording of privilege use for a specified privilege analysis policy. When a policy is disabled, privilege use meeting the policy condition is no longer needed.
+
+```sql
+DBMS_PRIVILEGE_CAPTURE.DISABLE_CAPTURE (
+    name  IN VARCHAR2,
+    run_name IN VARCHAR2 DEFAULT NULL
+    );
+```
+
+### Parameters
+
+`name`
+
+Name of the privilege analysis policy to be disabled.
+
+`run_name`
+
+Name of the capture run.
+
+## DROP_CAPTURE
+
+`DROP_CAPTURE` procedure removes a privilege analysis policy together with the data recorded. When a policy is removed, all previously recorded privilege use data associated with the policy is deleted.
+
+```sql
+DBMS_PRIVILEGE_CAPTURE.DROP_CAPTURE (
+    name  IN VARCHAR2);
+```
+
+### Parameters
+
+`name`
+
+ Name of the privilege analysis policy to be removed.
+
+## GENERATE_RESULT
+
+`GENERATE_RESULT` procedure populates the data dictionary views with the privilege analysis data.
+
+```sql
+DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT (
+    name         IN VARCHAR2,
+    run_name     IN VARCHAR2 DEFAULT NULL,
+    dependency   IN BOOLEAN DEFAULT NULL /* This is just for redwood compatibility */);
+```
+
+### Parameters
+
+`name`
+
+ Name of the privilege analysis policy for which the data dictionary views are populated.
+
+`run_name`
+
+ Name of the capture run associated with the privilege analysis policy. If you skip this parameter, then the records of all the created runs are analyzed. Specify this parameter to analyze the records of specific run.
+
+ `dependency`
+
+This parameter is added for Oracle compatibility. The value is boolean Y (yes) or N (no).
+
+
+## DELETE_RUN
+
+`DELETE_RUN` procedure deletes a privilege analysis capture run.
+
+```sql
+DBMS_PRIVILEGE_CAPTURE.DELETE_RUN (
+    name      IN VARCHAR2,
+    run_name  IN VARCHAR2);
+```
+
+### Parameters
+
+`name`
+
+ Name of the privilege analysis policy with which the capture run is associated.
+
+`run_name`
+
+ Name of the capture run.
+
+## Examples
+
+To enable the privilege analysis feature, set the parameter to a value greater than zero in `postgresql.conf` file:
+
+```ini
+edb_max_capture_privileges_policies = 2
+```
+
+Login as a superuser or grant the `CAPTURE_ADMIN` role to the non-super user:
+
+```sql
+GRANT CAPTURE_ADMIN TO user1;
+```
+
+Create a table:
+
+```sql
+CREATE TABLE tab1 (a INT);
+```
+
+### Policy on database
+
+```sql
+## Create a privilege analysis policy on the database:
+BEGIN
+    DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE (
+        name         => 'policy_on_database',
+        type         => DBMS_PRIVILEGE_CAPTURE.G_DATABASE);
+
+    DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE (
+        name         => 'policy_on_database');
+END;
+
+## Insert data into the table:
+INSERT INTO tab1 VALUES(1);
+SELECT * FROM tab1;
+
+## Disable the policy:
+DBMS_PRIVILEGE_CAPTURE.DISABLE_CAPTURE(
+    name            => 'policy_on_database');
+END;
+
+## Run `GENERATE_RESULT` procedure to populate the dictionary views:
+BEGIN
+  DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT(
+    name   => 'policy_on_database');
+END;
+```
+
+Query the data dictionary views to find used privileges:
+
+```sql
+SELECT * FROM DBA_USED_PRIVS ORDER BY object_name COLLATE "C", privilege_type COLLATE "C";
+__OUTPUT__
+|    policy_name     | run_name | object_class |                                      object_name                                      | column_name | application | role_name | privilege_type 
++--------------------+----------+--------------+---------------------------------------------------------------------------------------+-------------+-------------+-----------+---------------
+| policy_on_database |          | procedure    | dbms_privilege_capture._validate_input_parameter(character varying,character varying) | -           | edb-psql    | edb       | EXECUTE
+| policy_on_database |          | procedure    | dbms_privilege_capture.disable_capture(character varying,character varying)           | -           | edb-psql    | edb       | EXECUTE
+| policy_on_database |          | table        | public.tab1                                                                           | -           | edb-psql    | edb       | INSERT
+| policy_on_database |          | table        | public.tab1                                                                           | -           | edb-psql    | edb       | SELECT
+(4 rows)
+```
+
+Query the data dictionary views to find unused privileges:
+
+```sql
+SELECT * FROM DBA_UNUSED_PRIVS ORDER BY object_name COLLATE "C", privilege_type COLLATE "C";
+__OUTPUT__
+|    policy_name     | run_name | object_class | object_name | column_name | application | role_name | privilege_type 
++--------------------+----------+--------------+-------------+-------------+-------------+-----------+----------------
+| policy_on_database |          | table        | public.tab1 | -           | edb-psql    | edb       | DELETE
+| policy_on_database |          | table        | public.tab1 | -           | edb-psql    | edb       | REFERENCES
+| policy_on_database |          | table        | public.tab1 | -           | edb-psql    | edb       | TRIGGER
+| policy_on_database |          | table        | public.tab1 | -           | edb-psql    | edb       | TRUNCATE
+| policy_on_database |          | table        | public.tab1 | -           | edb-psql    | edb       | UPDATE
+(5 rows)
+```
+
+Drop the policy:
+
+```sql
+BEGIN
+  DBMS_PRIVILEGE_CAPTURE.drop_capture(
+    name   => 'policy_on_database');
+END;
+```
+
+Query the data dictionary views to check policy and its related data is removed:
+
+```sql
+SELECT * FROM DBA_PRIV_CAPTURES;
+__OUTPUT__
+|name  | description | type | enabled | roles | context | run_name 
++------+-------------+------+---------+-------+---------+----------
+(0 rows)
+```
+
+```sql
+SELECT * FROM DBA_USED_PRIVS;
+__OUTPUT__
+| policy_name | run_name | object_class | object_name | column_name | application | role_name | privilege_type 
++-------------+----------+--------------+-------------+-------------+-------------+-----------+----------------
+(0 rows)
+```
+
+### Policy on context
+
+```sql
+## Create a function:
+CREATE OR REPLACE FUNCTION func1(i INTEGER) RETURNS INTEGER AS $$
+  BEGIN
+     RETURN i + 1;
+  END;
+$$ LANGUAGE plpgsql;
+
+## Create a policy on context:
+BEGIN
+	DBMS_PRIVILEGE_CAPTURE.CREATE_CAPTURE(
+		name			=> 'policy_on_db_context',
+		type			=> DBMS_PRIVILEGE_CAPTURE.G_CONTEXT,
+		condition		=> '1=1');
+
+	DBMS_PRIVILEGE_CAPTURE.ENABLE_CAPTURE(
+		name			=> 'policy_on_db_context');
+END;
+
+## Access objects:
+SELECT func1(1);
+DELETE FROM tab1;
+
+## Disable policy:
+BEGIN
+	DBMS_PRIVILEGE_CAPTURE.DISABLE_CAPTURE(
+		name			=> 'policy_on_db_context');
+END;
+
+## Run `GENERATE_RESULT` procedure to populate the dictionary views:
+BEGIN
+  DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT(
+    name   => 'policy_on_db_context');
+END;
+```
+
+Query the data dictionary views to find used privileges:
+
+```sql
+SELECT * FROM DBA_USED_PRIVS ORDER BY object_name COLLATE "C", privilege_type COLLATE "C";
+__OUTPUT__
+|     policy_name      | run_name | object_class |                                      object_name                                      | column_name | application | role_name | privilege_type 
++----------------------+----------+--------------+---------------------------------------------------------------------------------------+-------------+-------------+-----------+----------------
+| policy_on_db_context |          | procedure    | dbms_privilege_capture._validate_input_parameter(character varying,character varying) | -           | edb-psql    | edb       | EXECUTE
+| policy_on_db_context |          | procedure    | dbms_privilege_capture.disable_capture(character varying,character varying)           | -           | edb-psql    | edb       | EXECUTE
+| policy_on_db_context |          | function     | public.func1(integer)                                                                 | -           | edb-psql    | edb       | EXECUTE
+| policy_on_db_context |          | table        | public.tab1                                                                           | -           | edb-psql    | edb       | DELETE
+(4 rows)
+```
+
+Query the data dictionary views to find unused privileges:
+
+```sql
+SELECT * FROM DBA_UNUSED_PRIVS ORDER BY object_name COLLATE "C", privilege_type COLLATE "C";
+__OUTPUT__
+|     policy_name      | run_name | object_class | object_name | column_name | application | role_name | privilege_type |
++----------------------+----------+--------------+-------------+-------------+-------------+-----------+----------------+
+| policy_on_db_context |          | table        | public.tab1 | -           | edb-psql    | edb       | INSERT         |
+| policy_on_db_context |          | table        | public.tab1 | -           | edb-psql    | edb       | REFERENCES     |
+| policy_on_db_context |          | table        | public.tab1 | -           | edb-psql    | edb       | TRIGGER        |
+| policy_on_db_context |          | table        | public.tab1 | -           | edb-psql    | edb       | TRUNCATE       |
+| policy_on_db_context |          | table        | public.tab1 | -           | edb-psql    | edb       | UPDATE         |
+(6 rows)
+```
+
+Drop the policy:
+
+```sql
+BEGIN
+  DBMS_PRIVILEGE_CAPTURE.drop_capture(
+    name   => 'policy_on_db_context');
+END;
+```
+
+Query the data dictionary views to check policy and its related data is removed:
+
+```sql
+SELECT * FROM DBA_PRIV_CAPTURES;
+__OUTPUT__
+| name | description | type | enabled | roles | context | run_name 
++------+-------------+------+---------+-------+---------+----------
+(0 rows)
+```
+
+```sql
+SELECT * FROM DBA_USED_PRIVS;
+__OUTPUT__
+| policy_name | run_name | object_class | object_name | column_name | application | role_name | privilege_type 
++-------------+----------+--------------+-------------+-------------+-------------+-----------+----------------
+(0 rows)
+```
+
+### Policy on role
+
+```sql
+## Create a role and grant privileges to role:
+CREATE ROLE ROLE1;
+GRANT SELECT, UPDATE, DELETE on tab1 to user1;
+
+## Create a privilege analysis policy on role:
+BEGIN
+	DBMS_PRIVILEGE_CAPTURE.create_capture(
+		name			=> 'policy_on_role',
+		type			=> DBMS_PRIVILEGE_CAPTURE.G_ROLE,
+		roles			=> ROLE_NAME_LIST('role1'));
+
+	DBMS_PRIVILEGE_CAPTURE.enable_capture(
+		name			=> 'policy_on_role',
+		run_name		=> 'run1');
+END;
+
+## Set role and delete data from the table:
+SET ROLE role1;
+DELETE FROM tab1;
+SET ROLE edb;
+
+## Disable the policy:
+BEGIN
+	DBMS_PRIVILEGE_CAPTURE.disable_capture(
+		name			=> 'policy_on_role');
+END;
+
+## Run Generate_result procedure to populate the dictionary views:
+BEGIN
+  DBMS_PRIVILEGE_CAPTURE.generate_result(
+    name   => 'policy_on_role');
+END;
+```
+
+Query the data dictionary views to find captured policy information:
+
+```sql
+SELECT * FROM DBA_PRIV_CAPTURES;
+__OUTPUT__
+|      name      | description |  type  | enabled |  roles  | context | run_name |
++----------------+-------------+--------+---------+---------+---------+----------+
+| policy_on_role |             | G_ROLE | f       | {role1} |         | run1     |
+(1 row)
+```
+
+Query the data dictionary views to find used privileges:
+
+```sql
+SELECT * FROM DBA_USED_PRIVS;
+__OUTPUT__
+|  policy_name   | run_name | object_class | object_name | column_name | application | role_name | privilege_type |
++----------------+----------+--------------+-------------+-------------+-------------+-----------+----------------+
+| policy_on_role | run1     | table        | public.tab1 | -           | edb-psql    | role1     | DELETE         |
+(1 row)
+```
+
+Query the data dictionary views to find unused privileges:
+
+```sql
+SELECT * FROM DBA_UNUSED_PRIVS ORDER BY object_name COLLATE "C", role_name, privilege_type COLLATE "C";
+__OUTPUT__
+|  policy_name   | run_name | object_class |     object_name     | column_name | application | role_name | privilege_type 
++----------------+----------+--------------+---------------------+-------------+-------------+-----------+----------------
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | role1     | SELECT
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | role1     | UPDATE
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | DELETE
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | INSERT
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | REFERENCES
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | SELECT
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | TRIGGER
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | TRUNCATE
+| policy_on_role | run1     | table        | public.tab1         | -           | edb-psql    | edb       | UPDATE
+(9 rows)
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/11_dbms_profiler.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/11_dbms_profiler.mdx
new file mode 100644
index 00000000000..3d4461307f6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/11_dbms_profiler.mdx
@@ -0,0 +1,853 @@
+---
+title: "DBMS_PROFILER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.24.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.23.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.22.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.25.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.198.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.138.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.156.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.140.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.137.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/11_dbms_profiler/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_PROFILER` package collects and stores performance information about the PL/pgSQL and SPL statements that are executed during a performance profiling session. Use these functions and procedures to control the profiling tool.
+
+| Function/procedure                                              | Return type              | Description                                                                                                      |
+| --------------------------------------------------------------- | ------------------------ | ---------------------------------------------------------------------------------------------------------------- |
+| `FLUSH_DATA`                                                    | Status Code or Exception | Flushes performance data collected in the current session without terminating the session. Profiling continues. |
+| `GET_VERSION(major OUT, minor OUT)`                             | n/a                      | Returns the version number of this package.                                                                      |
+| `INTERNAL_VERSION_CHECK`                                        | Status Code              | Confirms that the current version of the profiler works with the current database.                           |
+| `PAUSE_PROFILER`                                                | Status Code or Exception | Pauses data collection.                                                                                           |
+| `RESUME_PROFILER`                                               | Status Code or Exception | Resumes data collection.                                                                                          |
+| `START_PROFILER(run_comment, run_comment1 [, run_number OUT ])` | Status Code or Exception | Starts data collection.                                                                                           |
+| `STOP_PROFILER`                                                 | Status Code or Exception | Stops data collection and flushes performance data to the `PLSQL_PROFILER_RAWDATA` table.                           |
+
+The functions in the `DBMS_PROFILER` package return a status code to indicate success or failure. The `DBMS_PROFILER` procedures raise an exception only if they encounter a failure. The table shows the status codes and messages returned by the functions and the exceptions raised by the procedures.
+
+| Status code | Message         | Exception          | Description                                             |
+| ----------- | --------------- | ------------------ | ------------------------------------------------------- |
+| `-1`        | `error version` | `version_mismatch` | The profiler version and the database are incompatible. |
+| `0`         | `success`       | n/a                | The operation completed successfully.                   |
+| `1`         | `error_param`   | `profiler_error`   | The operation received an incorrect parameter.          |
+| `2`         | `error_io`      | `profiler_error`   | The data flush operation failed.                        |
+
+## FLUSH_DATA
+
+The `FLUSH_DATA` function/procedure flushes the data collected in the current session without terminating the profiler session. The data is flushed to the tables described in the EDB Postgres Advanced Server Performance Features Guide. The function and procedure signatures are:
+
+```sql
+<status> INTEGER FLUSH_DATA
+
+FLUSH_DATA
+```
+
+### Parameters
+
+`status`
+
+ Status code returned by the operation.
+
+## GET_VERSION
+
+The `GET_VERSION` procedure returns the version of `DBMS_PROFILER`. The procedure signature is:
+
+```sql
+GET_VERSION(<major> OUT INTEGER, <minor> OUT INTEGER)
+```
+
+### Parameters
+
+`major`
+
+ The major version number of `DBMS_PROFILER`.
+
+`minor`
+
+ The minor version number of `DBMS_PROFILER`.
+
+## INTERNAL_VERSION_CHECK
+
+The `INTERNAL_VERSION_CHECK` function confirms that the current version of `DBMS_PROFILER` works with the current database. The function signature is:
+
+```sql
+<status> INTEGER INTERNAL_VERSION_CHECK
+```
+
+### Parameters
+
+`status`
+
+ Status code returned by the operation.
+
+## PAUSE_PROFILER
+
+The `PAUSE_PROFILER` function/procedure pauses a profiling session. The function and procedure signatures are:
+
+```sql
+<status> INTEGER PAUSE_PROFILER
+
+PAUSE_PROFILER
+```
+
+### Parameters
+
+`status`
+
+ Status code returned by the operation.
+
+## RESUME_PROFILER
+
+The `RESUME_PROFILER` function/procedure pauses a profiling session. The function and procedure signatures are:
+
+```sql
+<status> INTEGER RESUME_PROFILER
+
+RESUME_PROFILER
+```
+
+### Parameters
+
+`status`
+
+ Status code returned by the operation.
+
+## START_PROFILER
+
+The `START_PROFILER` function/procedure starts a data collection session. The function and procedure signatures are:
+
+```sql
+<status> INTEGER START_PROFILER(<run_comment> TEXT := SYSDATE,
+   <run_comment1> TEXT := '' [, <run_number> OUT INTEGER ])
+
+START_PROFILER(<run_comment> TEXT := SYSDATE,
+  <run_comment1> TEXT := '' [, <run_number> OUT INTEGER ])
+```
+
+### Parameters
+
+`run_comment`
+
+ A user-defined comment for the profiler session. The default value is `SYSDATE`.
+
+`run_comment1`
+
+ An additional user-defined comment for the profiler session. The default value is ''.
+
+`run_number`
+
+ The session number of the profiler session.
+
+`status`
+
+ Status code returned by the operation.
+
+## STOP_PROFILER
+
+The `STOP_PROFILER` function/procedure stops a profiling session and flushes the performance information to the `DBMS_PROFILER` tables and view. The function and procedure signatures are:
+
+```sql
+<status> INTEGER STOP_PROFILER
+
+STOP_PROFILER
+```
+
+### Parameters
+
+`status`
+
+ Status code returned by the operation.
+
+## Using DBMS_PROFILER
+
+The `DBMS_PROFILER` package collects and stores performance information about the PL/pgSQL and SPL statements that are executed during a profiling session. You can review the performance information in the tables and views provided by the profiler.
+
+`DBMS_PROFILER` works by recording a set of performance-related counters and timers for each line of PL/pgSQL or SPL statement that executes in a profiling session. The counters and timers are stored in a table named `SYS.PLSQL_PROFILER_DATA`. When you complete a profiling session, `DBMS_PROFILER` writes a row to the performance statistics table for each line of PL/pgSQL or SPL code that executed in the session. For example, suppose you execute the following function:
+
+```sql
+1 - CREATE OR REPLACE FUNCTION getBalance(acctNumber INTEGER)
+2 - RETURNS NUMERIC AS $$
+3 - DECLARE
+4 -   result NUMERIC;
+5 - BEGIN
+6 -   SELECT INTO result balance FROM acct WHERE id = acctNumber;
+7 -
+8 -   IF (result IS NULL) THEN
+9 -       RAISE INFO 'Balance is null';
+10-   END IF;
+11-
+12-   RETURN result;
+13- END;
+14- $$ LANGUAGE 'plpgsql';
+```
+
+`DBMS_PROFILER` adds one `PLSQL_PROFILER_DATA` entry for each line of code in the `getBalance()` function, including blank lines and comments. The entry corresponding to the `SELECT` statement executed exactly one time and required a very small amount of time to execute. On the other hand, the entry corresponding to the `RAISE INFO` statement executed once or not at all, depending on the value for the `balance` column.
+
+Some of the lines in this function contain no executable code so the performance statistics for those lines always contains zero values.
+
+To start a profiling session, invoke the `DBMS_PROFILER.START_PROFILER` function or procedure. Once you've invoked `START_PROFILER`, EDB Postgres Advanced Server profiles every PL/pgSQL or SPL function, procedure, trigger, or anonymous block that your session executes until you either stop or pause the profiler by calling `STOP_PROFILER` or `PAUSE_PROFILER`.
+
+!!! Note
+    When you start or resume the profiler, the profiler gathers performance statistics only for functions/procedures/triggers that start after the call to `START_PROFILER` (or `RESUME_PROFILER`).
+
+While the profiler is active, EDB Postgres Advanced Server records a large set of timers and counters in memory. When you invoke the `STOP_PROFILER` or `FLUSH_DATA` function/procedure, `DBMS_PROFILER` writes those timers and counters to a set of three tables:
+
+-   `SYS.PLSQL_PROFILER_RAWDATA`
+
+    Contains the performance counters and timers for each statement executed in the session.
+
+-   `SYS.PLSQL_PROFILER_RUNS`
+
+    Contains a summary of each run, aggregating the information found in `PLSQL_PROFILER_RAWDATA`.
+
+-   `SYS.PLSQL_PROFILER_UNITS`
+
+    Contains a summary of each code unit (function, procedure, trigger, or anonymous block) executed in a session.
+
+In addition, `DBMS_PROFILER` defines a view, `SYS.PLSQL_PROFILER_DATA`, which contains a subset of the `PLSQL_PROFILER_RAWDATA` table.
+
+A user who is not a superuser can gather profiling information but can't view that profiling information unless a superuser grants specific privileges on the profiling tables stored in the `SYS` schema. This permits a nonprivileged user to gather performance statistics without exposing information that the administrator might want to keep secret.
+
+### Querying the DBMS_PROFILER tables and view
+
+The following example uses `DBMS_PROFILER` to retrieve performance information for procedures, functions, and triggers included in the sample data distributed with EDB Postgres Advanced Server.
+
+1.  Open the EDB-PSQL command line, and establish a connection to the EDB Postgres Advanced Server database. Use an `EXEC` statement to start the profiling session:
+
+```sql
+acctg=# EXEC dbms_profiler.start_profiler('profile list_emp');
+
+EDB-SPL Procedure successfully completed
+```
+
+!!! Note
+    The call to `start_profiler()` includes a comment that `DBMS_PROFILER` associates with the profiler session.
+
+2.  Call the `list_emp` function:
+
+```sql
+acctg=# SELECT list_emp();
+__OUTPUT__
+INFO:  EMPNO    ENAME
+INFO:  -----    -------
+INFO:  7369     SMITH
+INFO:  7499     ALLEN
+INFO:  7521     WARD
+INFO:  7566     JONES
+INFO:  7654     MARTIN
+INFO:  7698     BLAKE
+INFO:  7782     CLARK
+INFO:  7788     SCOTT
+INFO:  7839     KING
+INFO:  7844     TURNER
+INFO:  7876     ADAMS
+INFO:  7900     JAMES
+INFO:  7902     FORD
+INFO:  7934     MILLER
+ list_emp
+----------
+
+(1 row)
+```
+
+3.  Stop the profiling session with a call to `dbms_profiler.stop_profiler`:
+
+```sql
+acctg=# EXEC dbms_profiler.stop_profiler;
+
+EDB-SPL Procedure successfully completed
+```
+
+4.  Start a new session with the `dbms_profiler.start_profiler` function followed by a new comment:
+
+```sql
+acctg=# EXEC dbms_profiler.start_profiler('profile get_dept_name and
+emp_sal_trig');
+
+EDB-SPL Procedure successfully completed
+```
+
+5.  Invoke the `get_dept_name` function:
+
+```sql
+acctg=# SELECT get_dept_name(10);
+__OUTPUT__
+ get_dept_name
+---------------
+ ACCOUNTING
+(1 row)
+```
+
+6.  Execute an `UPDATE` statement that causes a trigger to execute:
+
+```sql
+acctg=# UPDATE memp SET sal = 500 WHERE empno = 7902;
+INFO: Updating employee 7902
+INFO: ..Old salary: 3000.00
+INFO: ..New salary: 500.00
+INFO: ..Raise: -2500.00
+INFO: User enterprisedb updated employee(s) on 04-FEB-14
+UPDATE 1
+```
+
+7.  End the profiling session and flush the performance information to the profiling tables:
+
+```sql
+acctg=# EXEC dbms_profiler.stop_profiler;
+
+EDB-SPL Procedure successfully completed
+```
+
+8.  Query the `plsql_profiler_runs` table to view a list of the profiling sessions, arranged by `runid:`
+
+```sql
+acctg=# SELECT * FROM plsql_profiler_runs;
+__OUTPUT__
+ runid | related_run |  run_owner   |         run_date
+ |              run_comment               | run_total_time | run_system_info
+ | run_comment1 | spare1
+-------+-------------+--------------+---------------------------+-------------
+---------------------------+----------------+-----------------+--------------
++--------
+      1 |             | enterprisedb | 04-FEB-14 09:32:48.874315 | profile
+      list_emp                       |           4154 |
+      |              |
+      2 |             | enterprisedb | 04-FEB-14 09:41:30.546503 | profile
+      get_dept_name and emp_sal_trig |           2088 |
+      |              |
+(2 rows)
+```
+
+9.  Query the `plsql_profiler_units` table to view the amount of time consumed by each unit (function, procedure, or trigger):
+
+```sql
+acctg=# SELECT * FROM plsql_profiler_units;
+__OUTPUT__
+ runid | unit_number | unit_type |  unit_owner  |
+ unit_name            | unit_timestamp | total_time | spare1 | spare2
+-------+-------------+-----------+--------------+----------------------------
+-----+----------------+------------+--------+--------
+     1 |       16999 | FUNCTION  | enterprisedb |
+     list_emp()                      |                |          4 |        |
+     2 |       17002 | FUNCTION  | enterprisedb |
+     user_audit_trig()               |                |          1 |        |
+     2 |       17000 | FUNCTION  | enterprisedb | get_dept_name(p_deptno
+     numeric) |                |          1 |        |
+     2 |       17004 | FUNCTION  | enterprisedb |
+     emp_sal_trig()                  |                |          1 |        |
+(4 rows)
+```
+
+10. Query the `plsql_profiler_rawdata` table to view a list of the wait-event counters and wait-event times:
+
+```sql
+acctg=# SELECT runid, sourcecode, func_oid, line_number, exec_count,
+tuples_returned, time_total FROM plsql_profiler_rawdata;
+__OUTPUT__
+ runid |                            sourcecode                           |
+ func_oid | line_number | exec_count | tuples_returned | time_total
+-------+-----------------------------------------------------------------+---
+-------+-------------+------------+-----------------+------------
+    1 | DECLARE
+    |    16999 |           1 |          0 |               0 |          0
+    1 |     v_empno         NUMERIC(4);
+    |    16999 |           2 |          0 |               0 |          0
+    1 |     v_ename         VARCHAR(10);
+    |    16999 |           3 |          0 |               0 |          0
+    1 |     emp_cur CURSOR FOR
+    |    16999 |           4 |          0 |               0 |          0
+    1 |         SELECT empno, ename FROM memp ORDER BY empno;
+    |    16999 |           5 |          0 |               0 |          0
+    1 | BEGIN
+    |    16999 |           6 |          0 |               0 |          0
+    1 |     OPEN emp_cur;
+    |    16999 |           7 |          0 |               0 |          0
+    1 |     RAISE INFO 'EMPNO    ENAME';
+    |    16999 |           8 |          1 |               0 |   0.001621
+    1 |     RAISE INFO '-----    -------';
+    |    16999 |           9 |          1 |               0 |   0.000301
+    1 |     LOOP
+    |    16999 |          10 |          1 |               0 |    4.6e-05
+    1 |         FETCH emp_cur INTO v_empno, v_ename;
+    |    16999 |          11 |          1 |               0 |   0.001114
+    1 |         EXIT WHEN NOT FOUND;
+    |    16999 |          12 |         15 |               0 |   0.000206
+    1 |         RAISE INFO '%     %', v_empno, v_ename;
+    |    16999 |          13 |         15 |               0 |    8.3e-05
+    1 |     END LOOP;
+    |    16999 |          14 |         14 |               0 |   0.000773
+    1 |     CLOSE emp_cur;
+    |    16999 |          15 |          0 |               0 |          0
+    1 |     RETURN;
+    |    16999 |          16 |          1 |               0 |      1e-05
+    1 | END;
+    |    16999 |          17 |          1 |               0 |          0
+    1 |
+    |    16999 |          18 |          0 |               0 |          0
+    2 | DECLARE
+    |    17002 |           1 |          0 |               0 |          0
+    2 |     v_action        VARCHAR(24);
+    |    17002 |           2 |          0 |               0 |          0
+    2 |     v_text          TEXT;
+    |    17002 |           3 |          0 |               0 |          0
+    2 | BEGIN
+    |    17002 |           4 |          0 |               0 |          0
+    2 |     IF TG_OP = 'INSERT' THEN
+    |    17002 |           5 |          0 |               0 |          0
+    2 |         v_action := ' added employee(s) on ';
+    |    17002 |           6 |          1 |               0 |   0.000143
+    2 |     ELSIF TG_OP = 'UPDATE' THEN
+    |    17002 |           7 |          0 |               0 |          0
+    2 |         v_action := ' updated employee(s) on ';
+    |    17002 |           8 |          0 |               0 |          0
+    2 |     ELSIF TG_OP = 'DELETE' THEN
+    |    17002 |           9 |          1 |               0 |    3.2e-05
+    2 |         v_action := ' deleted employee(s) on ';
+    |    17002 |          10 |          0 |               0 |          0
+    2 |     END IF;
+    |    17002 |          11 |          0 |               0 |          0
+    2 |     v_text := 'User ' || USER || v_action || CURRENT_DATE;
+    |    17002 |          12 |          0 |               0 |          0
+    2 |     RAISE INFO ' %', v_text;
+    |    17002 |          13 |          1 |               0 |   0.000383
+    2 |     RETURN NULL;
+    |    17002 |          14 |          1 |               0 |    6.3e-05
+    2 | END;
+    |    17002 |          15 |          1 |               0 |    3.6e-05
+    2 |
+    |    17002 |          16 |          0 |               0 |          0
+    2 | DECLARE
+    |    17000 |           1 |          0 |               0 |          0
+    2 |     v_dname         VARCHAR(14);
+    |    17000 |           2 |          0 |               0 |          0
+    2 | BEGIN
+    |    17000 |           3 |          0 |               0 |          0
+    2 |     SELECT INTO v_dname dname FROM dept WHERE deptno = p_deptno;
+    |    17000 |           4 |          0 |               0 |          0
+    2 |     RETURN v_dname;
+    |    17000 |           5 |          1 |               0 |   0.000647
+    2 |     IF NOT FOUND THEN
+    |    17000 |           6 |          1 |               0 |    2.6e-05
+    2 |         RAISE INFO 'Invalid department number %', p_deptno;
+    |    17000 |           7 |          0 |               0 |          0
+    2 |         RETURN '';
+    |    17000 |           8 |          0 |               0 |          0
+    2 |     END IF;
+    |    17000 |           9 |          0 |               0 |          0
+    2 | END;
+    |    17000 |          10 |          0 |               0 |          0
+    2 |
+    |    17000 |          11 |          0 |               0 |          0
+    2 | DECLARE
+    |    17004 |           1 |          0 |               0 |          0
+    2 |     sal_diff       NUMERIC(7,2);
+    |    17004 |           2 |          0 |               0 |          0
+    2 | BEGIN
+    |    17004 |           3 |          0 |               0 |          0
+    2 |     IF TG_OP = 'INSERT' THEN
+    |    17004 |           4 |          0 |               0 |          0
+    2 |         RAISE INFO 'Inserting employee %', NEW.empno;
+    |    17004 |           5 |          1 |               0 |    8.4e-05
+    2 |         RAISE INFO '..New salary: %', NEW.sal;
+    |    17004 |           6 |          0 |               0 |          0
+    2 |         RETURN NEW;
+    |    17004 |           7 |          0 |               0 |          0
+    2 |     END IF;
+    |    17004 |           8 |          0 |               0 |          0
+    2 |     IF TG_OP = 'UPDATE' THEN
+    |    17004 |           9 |          0 |               0 |          0
+    2 |         sal_diff := NEW.sal - OLD.sal;
+    |    17004 |          10 |          1 |               0 |   0.000355
+    2 |         RAISE INFO 'Updating employee %', OLD.empno;
+    |    17004 |          11 |          1 |               0 |   0.000177
+    2 |         RAISE INFO '..Old salary: %', OLD.sal;
+    |    17004 |          12 |          1 |               0 |    5.5e-05
+    2 |         RAISE INFO '..New salary: %', NEW.sal;
+    |    17004 |          13 |          1 |               0 |    3.1e-05
+    2 |         RAISE INFO '..Raise     : %', sal_diff;
+    |    17004 |          14 |          1 |               0 |    2.8e-05
+    2 |         RETURN NEW;
+    |    17004 |          15 |          1 |               0 |    2.7e-05
+    2 |     END IF;
+    |    17004 |          16 |          1 |               0 |      1e-06
+    2 |     IF TG_OP = 'DELETE' THEN
+    |    17004 |          17 |          0 |               0 |          0
+    2 |         RAISE INFO 'Deleting employee %', OLD.empno;
+    |    17004 |          18 |          0 |               0 |          0
+    2 |         RAISE INFO '..Old salary: %', OLD.sal;
+    |    17004 |          19 |          0 |               0 |          0
+    2 |         RETURN OLD;
+    |    17004 |          20 |          0 |               0 |          0
+    2 |     END IF;
+    |    17004 |          21 |          0 |               0 |          0
+    2 | END;
+    |    17004 |          22 |          0 |               0 |          0
+    2 |
+    |    17004 |          23 |          0 |               0 |          0
+ (68 rows)
+                                                                                                                   
+```
+
+11. Query the `plsql_profiler_data` view to review a subset of the information found in `plsql_profiler_rawdata` table:
+
+```sql
+acctg=# SELECT * FROM plsql_profiler_data;
+__OUTPUT__
+runid | unit_number | line# | total_occur | total_time | min_time | max_time
+| spare1 | spare2 | spare3 | spare4
+-------+-------------+-------+-------------+------------+----------+---------
+-+--------+--------+--------+--------
+     1 |       16999 |     1 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     2 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     3 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     4 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     5 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     6 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     7 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |     8 |           1 |   0.001621 | 0.001621 |
+     0.001621 |        |        |        |
+     1 |       16999 |     9 |           1 |   0.000301 | 0.000301 |
+     0.000301 |        |        |        |
+     1 |       16999 |    10 |           1 |    4.6e-05 |  4.6e-05 |  4.6e-
+     05 |        |        |        |
+     1 |       16999 |    11 |           1 |   0.001114 | 0.001114 |
+     0.001114 |        |        |        |
+     1 |       16999 |    12 |          15 |   0.000206 |    5e-06 |  7.8e-
+     05 |        |        |        |
+     1 |       16999 |    13 |          15 |    8.3e-05 |    2e-06 |  4.7e-
+     05 |        |        |        |
+     1 |       16999 |    14 |          14 |   0.000773 |  4.7e-05 |
+     0.000116 |        |        |        |
+     1 |       16999 |    15 |           0 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |    16 |           1 |      1e-05 |    1e-05 |    1e-
+     05 |        |        |        |
+     1 |       16999 |    17 |           1 |          0 |        0 |
+     0 |        |        |        |
+     1 |       16999 |    18 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     1 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     2 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     3 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     4 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     5 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     6 |           1 |   0.000143 | 0.000143 |
+     0.000143 |        |        |        |
+     2 |       17002 |     7 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     8 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |     9 |           1 |    3.2e-05 |  3.2e-05 |  3.2e-
+     05 |        |        |        |
+     2 |       17002 |    10 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |    11 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |    12 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17002 |    13 |           1 |   0.000383 | 0.000383 |
+     0.000383 |        |        |        |
+     2 |       17002 |    14 |           1 |    6.3e-05 |  6.3e-05 |  6.3e-
+     05 |        |        |        |
+     2 |       17002 |    15 |           1 |    3.6e-05 |  3.6e-05 |  3.6e-
+     05 |        |        |        |
+     2 |       17002 |    16 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     1 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     2 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     3 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     4 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     5 |           1 |   0.000647 | 0.000647 |
+     0.000647 |        |        |        |
+     2 |       17000 |     6 |           1 |    2.6e-05 |  2.6e-05 |  2.6e-
+     05 |        |        |        |
+     2 |       17000 |     7 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     8 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |     9 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |    10 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17000 |    11 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     1 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     2 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     3 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     4 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     5 |           1 |    8.4e-05 |  8.4e-05 |  8.4e-
+     05 |        |        |        |
+     2 |       17004 |     6 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     7 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     8 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |     9 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    10 |           1 |   0.000355 | 0.000355 |
+     0.000355 |        |        |        |
+     2 |       17004 |    11 |           1 |   0.000177 | 0.000177 |
+     0.000177 |        |        |        |
+     2 |       17004 |    12 |           1 |    5.5e-05 |  5.5e-05 |  5.5e-
+     05 |        |        |        |
+     2 |       17004 |    13 |           1 |    3.1e-05 |  3.1e-05 |  3.1e-
+     05 |        |        |        |
+     2 |       17004 |    14 |           1 |    2.8e-05 |  2.8e-05 |  2.8e-
+     05 |        |        |        |
+     2 |       17004 |    15 |           1 |    2.7e-05 |  2.7e-05 |  2.7e-
+     05 |        |        |        |
+     2 |       17004 |    16 |           1 |      1e-06 |    1e-06 |    1e-
+     06 |        |        |        |
+     2 |       17004 |    17 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    18 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    19 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    20 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    21 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    22 |           0 |          0 |        0 |
+     0 |        |        |        |
+     2 |       17004 |    23 |           0 |          0 |        0 |
+     0 |        |        |        |
+(68 rows)
+```
+
+### DBMS_PROFILER reference
+
+The EDB Postgres Advanced Server installer creates the following tables and views that you can query to review PL/SQL performance profile information:
+
+| Table name               | Description                                                                                                          |
+| ------------------------ | -------------------------------------------------------------------------------------------------------------------- |
+| `PLSQL_PROFILER_RUNS`    | Table containing information about all profiler runs, organized by `runid`.                                          |
+| `PLSQL_PROFILER_UNITS`   | Table containing information about all profiler runs, organized by unit.                                             |
+| `PLSQL_PROFILER_DATA`    | View containing performance statistics.                                                                              |
+| `PLSQL_PROFILER_RAWDATA` | Table containing the performance statistics and the extended performance statistics for DRITA counters and timers. |
+
+#### PLSQL_PROFILER_RUNS
+
+The `PLSQL_PROFILER_RUNS` table contains the following columns:
+
+| Column            | Data type                     | Description                                    |
+| ----------------- | ----------------------------- | ---------------------------------------------- |
+| `runid`           | `INTEGER (NOT NULL)`          | Unique identifier (`plsql_profiler_runnumber`) |
+| `related_run`     | `INTEGER`                     | The `runid` of a related run                  |
+| `run_owner`       | `TEXT`                        | The role that recorded the profiling session  |
+| `run_date`        | `TIMESTAMP WITHOUT TIME ZONE` | The profiling session start time              |
+| `run_comment`     | `TEXT`                        | User comments relevant to this run             |
+| `run_total_time`  | `BIGINT`                      | Run time (in microseconds)                     |
+| `run_system_info` | `TEXT`                        | Currently unused                               |
+| `run_comment1`    | `TEXT`                        | Additional user comments                       |
+| `spare1`          | `TEXT`                        | Currently unused                               |
+
+#### PLSQL_PROFILER_UNITS
+
+The `PLSQL_PROFILER_UNITS` table contains the following columns:
+
+| Column           | Data type                     | Description                                                                      |
+| ---------------- | ----------------------------- | -------------------------------------------------------------------------------- |
+| `runid`          | `INTEGER`                     | Unique identifier (`plsql_profiler_runnumber`)                                   |
+| `unit_number`    | `OID`                         | Corresponds to the OID of the row in the pg_proc table that identifies the unit |
+| `unit_type`      | `TEXT`                        | PL/SQL function, procedure, trigger or anonymous block                           |
+| `unit_owner`     | `TEXT`                        | The identity of the role that owns the unit                                     |
+| `unit_name`      | `TEXT`                        | The complete signature of the unit                                              |
+| `unit_timestamp` | `TIMESTAMP WITHOUT TIME ZONE` | Creation date of the unit (currently NULL)                                      |
+| `total_time`     | `BIGINT`                      | Time spent within the unit (in milliseconds)                                     |
+| `spare1`         | `BIGINT`                      | Currently unused                                                                 |
+| `spare2`         | `BIGINT`                      | Currently unused                                                                 |
+
+#### PLSQL_PROFILER_DATA
+
+The `PLSQL_PROFILER_DATA` view contains the following columns:
+
+| Column        | Data type          | Description                                              |
+| ------------- | ------------------ | -------------------------------------------------------- |
+| `runid`       | `INTEGER`          | Unique identifier (`plsql_profiler_runnumber`)           |
+| `unit_number` | `OID`              | Object ID of the unit that contains the current line    |
+| `line#`       | `INTEGER`          | Current line number of the profiled workload            |
+| `total_occur` | `BIGINT`           | The number of times that the line was executed          |
+| `total_time`  | `DOUBLE PRECISION` | The amount of time spent executing the line (in seconds) |
+| `min_time`    | `DOUBLE PRECISION` | The minimum execution time for the line                 |
+| `max_time`    | `DOUBLE PRECISION` | The maximum execution time for the line                 |
+| `spare1`      | `NUMBER`           | Currently unused                                         |
+| `spare2`      | `NUMBER`           | Currently unused                                         |
+| `spare3`      | `NUMBER`           | Currently unused                                         |
+| `spare4`      | `NUMBER`           | Currently unused                                         |
+
+#### PLSQL_PROFILER_RAWDATA
+
+The `PLSQL_PROFILER_RAWDATA` table contains the statistical and wait-events information found in the `PLSQL_PROFILER_DATA` view, as well as the performance statistics returned by the DRITA counters and timers.
+
+| Column                                   | Data type          | Description                                                                                                                                                                                                                                                            |
+| ---------------------------------------- | ------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `runid`                                  | `INTEGER`          | The run identifier `(plsql_profiler_runnumber)`.                                                                                                                                                                                                                       |
+| `sourcecode`                             | `TEXT`             | The individual line of profiled code.                                                                                                                                                                                                                                  |
+| `func_oid`                               | `OID`              | Object ID of the unit that contains the current line.                                                                                                                                                                                                                 |
+| `line_number`                            | `INTEGER`          | Current line number of the profiled workload.                                                                                                                                                                                                                          |
+| `exec_count`                             | `BIGINT`           | The number of times that the line was executed.                                                                                                                                                                                                                        |
+| `tuples_returned`                        | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `time_total`                             | `DOUBLE PRECISION` | The amount of time spent executing the line, in seconds.                                                                                                                                                                                                               |
+| `time_shortest`                          | `DOUBLE PRECISION` | The minimum execution time for the line.                                                                                                                                                                                                                               |
+| `time_longest`                           | `DOUBLE PRECISION` | The maximum execution time for the line.                                                                                                                                                                                                                               |
+| `num_scans`                              | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `tuples_fetched`                         | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `tuples_inserted`                        | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `tuples_updated`                         | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `tuples_deleted`                         | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `blocks_fetched`                         | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `blocks_hit`                             | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                       |
+| `wal_write`                              | `BIGINT`           | A server has waited for a write to the write-ahead log buffer. Expect this value to be high.                                                                                                                                                                          |
+| `wal_flush`                              | `BIGINT`           | A server has waited for the write-ahead log to flush to disk.                                                                                                                                                                                                          |
+| `wal_file_sync`                          | `BIGINT`           | A server has waited for the write-ahead log to sync to disk (related to the `wal_sync_method` parameter which, by default, is 'fsync' - better performance can be gained by changing this parameter to `open_sync`).                                                   |
+| `db_file_read`                           | `BIGINT`           | A server has waited for the completion of a read (from disk).                                                                                                                                                                                                          |
+| `db_file_write`                          | `BIGINT`           | A server has waited for the completion of a write (to disk).                                                                                                                                                                                                           |
+| `db_file_sync`                           | `BIGINT`           | A server has waited for the operating system to flush all changes to disk.                                                                                                                                                                                             |
+| `db_file_extend`                         | `BIGINT`           | A server has waited for the operating system while adding a new page to the end of a file.                                                                                                                                                                             |
+| `sql_parse`                              | `BIGINT`           | Currently unused.                                                                                                                                                                                                                                                      |
+| `query_plan`                             | `BIGINT`           | A server has generated a query plan.                                                                                                                                                                                                                                   |
+| `other_lwlock_acquire`                   | `BIGINT`           | A server has waited for other light-weight lock to protect data.                                                                                                                                                                                                       |
+| `shared_plan_cache_collision`            | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_collision` event.                                                                                                                                                                                     |
+| `shared_plan_cache_insert`               | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_insert` event.                                                                                                                                                                                        |
+| `shared_plan_cache_hit`                  | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_hit` event.                                                                                                                                                                                           |
+| `shared_plan_cache_miss`                 | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_miss` event.                                                                                                                                                                                          |
+| `shared_plan_cache_lock`                 | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_lock` event.                                                                                                                                                                                          |
+| `shared_plan_cache_busy`                 | `BIGINT`           | A server has waited for the completion of the `shared_plan_cache_busy` event.                                                                                                                                                                                          |
+| `shmemindexlock`                         | `BIGINT`           | A server has waited to find or allocate space in the shared memory.                                                                                                                                                                                                    |
+| `oidgenlock`                             | `BIGINT`           | A server has waited to allocate or assign an OID.                                                                                                                                                                                                                      |
+| `xidgenlock`                             | `BIGINT`           | A server has waited to allocate or assign a transaction ID.                                                                                                                                                                                                            |
+| `procarraylock`                          | `BIGINT`           | A server has waited to get a snapshot or clearing a transaction ID at transaction end.                                                                                                                                                                                 |
+| `sinvalreadlock`                         | `BIGINT`           | A server has waited to retrieve or remove messages from shared invalidation queue.                                                                                                                                                                                     |
+| `sinvalwritelock`                        | `BIGINT`           | A server has waited to add a message to the shared invalidation queue.                                                                                                                                                                                                 |
+| `walbufmappinglock`                      | `BIGINT`           | A server has waited to replace a page in WAL buffers.                                                                                                                                                                                                                  |
+| `walwritelock`                           | `BIGINT`           | A server has waited for WAL buffers to be written to disk.                                                                                                                                                                                                             |
+| `controlfilelock`                        | `BIGINT`           | A server has waited to read or update the control file or creation of a new WAL file.                                                                                                                                                                                  |
+| `checkpointlock`                         | `BIGINT`           | A server has waited to perform a checkpoint.                                                                                                                                                                                                                           |
+| `clogcontrollock`                        | `BIGINT`           | A server has waited to read or update the transaction status.                                                                                                                                                                                                          |
+| `subtranscontrollock`                    | `BIGINT`           | A server has waited to read or update the sub-transaction information.                                                                                                                                                                                                 |
+| `multixactgenlock`                       | `BIGINT`           | A server has waited to read or update the shared multixact state.                                                                                                                                                                                                      |
+| `multixactoffsetcontrollock`             | `BIGINT`           | A server has waited to read or update multixact offset mappings.                                                                                                                                                                                                       |
+| `multixactmembercontrollock`             | `BIGINT`           | A server has waited to read or update multixact member mappings.                                                                                                                                                                                                       |
+| `relcacheinitlock`                       | `BIGINT`           | A server has waited to read or write the relation cache initialization file.                                                                                                                                                                                           |
+| `checkpointercommlock`                   | `BIGINT`           | A server has waited to manage the fsync requests.                                                                                                                                                                                                                      |
+| `twophasestatelock`                      | `BIGINT`           | A server has waited to read or update the state of prepared transactions.                                                                                                                                                                                              |
+| `tablespacecreatelock`                   | `BIGINT`           | A server has waited to create or drop the tablespace.                                                                                                                                                                                                                  |
+| `btreevacuumlock`                        | `BIGINT`           | A server has waited to read or update the vacuum related information for a B-tree index.                                                                                                                                                                               |
+| `addinshmeminitlock`                     | `BIGINT`           | A server has waited to manage space allocation in shared memory.                                                                                                                                                                                                       |
+| `autovacuumlock`                         | `BIGINT`           | The autovacuum launcher waiting to read or update the current state of autovacuum workers.                                                                                                                                                                             |
+| `autovacuumschedulelock`                 | `BIGINT`           | A server has waited to ensure that the table selected for a vacuum still needs vacuuming.                                                                                                                                                                              |
+| `syncscanlock`                           | `BIGINT`           | A server has waited to get the start location of a scan on a table for synchronized scans.                                                                                                                                                                             |
+| `relationmappinglock`                    | `BIGINT`           | A server has waited to update the relation map file used to store catalog to file node mapping.                                                                                                                                                                        |
+| `asyncctllock`                           | `BIGINT`           | A server has waited to read or update shared notification state.                                                                                                                                                                                                       |
+| `asyncqueuelock`                         | `BIGINT`           | A server has waited to read or update the notification messages.                                                                                                                                                                                                       |
+| `serializablexacthashlock`               | `BIGINT`           | A server has waited to retrieve or store information about serializable transactions.                                                                                                                                                                                  |
+| `serializablefinishedlistlock`           | `BIGINT`           | A server has waited to access the list of finished serializable transactions.                                                                                                                                                                                          |
+| `serializablepredicatelocklistlock`      | `BIGINT`           | A server has waited to perform an operation on a list of locks held by serializable transactions.                                                                                                                                                                      |
+| `oldserxidlock`                          | `BIGINT`           | A server has waited to read or record the conflicting serializable transactions.                                                                                                                                                                                       |
+| `syncreplock`                            | `BIGINT`           | A server has waited to read or update information about synchronous replicas.                                                                                                                                                                                          |
+| `backgroundworkerlock`                   | `BIGINT`           | A server has waited to read or update the background worker state.                                                                                                                                                                                                     |
+| `dynamicsharedmemorycontrollock`         | `BIGINT`           | A server has waited to read or update the dynamic shared memory state.                                                                                                                                                                                                 |
+| `autofilelock`                           | `BIGINT`           | A server has waited to update the `postgresql.auto.conf` file.                                                                                                                                                                                                         |
+| `replicationslotallocationlock`          | `BIGINT`           | A server has waited to allocate or free a replication slot.                                                                                                                                                                                                            |
+| `replicationslotcontrollock`             | `BIGINT`           | A server has waited to read or update replication slot state.                                                                                                                                                                                                          |
+| `committscontrollock`                    | `BIGINT`           | A server has waited to read or update transaction commit timestamps.                                                                                                                                                                                                   |
+| `committslock`                           | `BIGINT`           | A server has waited to read or update the last value set for the transaction timestamp.                                                                                                                                                                                |
+| `replicationoriginlock`                  | `BIGINT`           | A server has waited to set up, drop, or use replication origin.                                                                                                                                                                                                        |
+| `multixacttruncationlock`                | `BIGINT`           | A server has waited to read or truncate multixact information.                                                                                                                                                                                                         |
+| `oldsnapshottimemaplock`                 | `BIGINT`           | A server has waited to read or update old snapshot control information.                                                                                                                                                                                                |
+| `backendrandomlock`                      | `BIGINT`           | A server has waited to generate a random number.                                                                                                                                                                                                                       |
+| `logicalrepworkerlock`                   | `BIGINT`           | A server has waited for the action on logical replication worker to finish.                                                                                                                                                                                            |
+| `clogtruncationlock`                     | `BIGINT`           | A server has waited to truncate the write-ahead log or waiting for write-ahead log truncation to finish.                                                                                                                                                               |
+| `bulkloadlock`                           | `BIGINT`           | A server has waited for the `bulkloadlock` to bulk upload the data.                                                                                                                                                                                                    |
+| `edbresourcemanagerlock`                 | `BIGINT`           | The `edbresourcemanagerlock` provides detail about edb resource manager lock module.                                                                                                                                                                                   |
+| `wal_write_time`                         | `BIGINT`           | The amount of time that the server has waited for a `wal_write` wait event to write to the write-ahead log buffer (expect this value to be high).                                                                                                                      |
+| `wal_flush_time`                         | `BIGINT`           | The amount of time that the server has waited for a `wal_flush` wait event to write-ahead log to flush to disk.                                                                                                                                                        |
+| `wal_file_sync_time`                     | `BIGINT`           | The amount of time that the server has waited for a `wal_file_sync` wait event to write-ahead log to sync to disk (related to the wal_sync_method parameter which, by default, is 'fsync' - better performance can be gained by changing this parameter to open_sync). |
+| `db_file_read_time`                      | `BIGINT`           | The amount of time that the server has waited for the `db_file_read` wait event for completion of a read (from disk).                                                                                                                                                  |
+| `db_file_write_time`                     | `BIGINT`           | The amount of time that the server has waited for the `db_file_write` wait event for completion of a write (to disk).                                                                                                                                                  |
+| `db_file_sync_time`                      | `BIGINT`           | The amount of time that the server has waited for the `db_file_sync` wait event to sync all changes to disk.                                                                                                                                                           |
+| `db_file_extend_time`                    | `BIGINT`           | The amount of time that the server has waited for the `db_file_extend` wait event while adding a new page to the end of a file.                                                                                                                                        |
+| `sql_parse_time`                         | `BIGINT`           | The amount of time that the server has waited for the `sql_parse` wait event to parse a SQL statement.                                                                                                                                                                 |
+| `query_plan_time`                        | `BIGINT`           | The amount of time that the server has waited for the `query_plan` wait event to compute the execution plan for a SQL statement.                                                                                                                                       |
+| `other_lwlock_acquire_time`              | `BIGINT`           | The amount of time that the server has waited for the `other_lwlock_acquire` wait event to protect data.                                                                                                                                                               |
+| `shared_plan_cache_collision_time`       | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_collision` wait event.                                                                                                                                                                        |
+| `shared_plan_cache_insert_time`          | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_insert` wait event.                                                                                                                                                                           |
+| `shared_plan_cache_hit_time`             | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_hit` wait event.                                                                                                                                                                              |
+| `shared_plan_cache_miss_time`            | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_miss` wait event.                                                                                                                                                                             |
+| `shared_plan_cache_lock_time`            | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_lock` wait event.                                                                                                                                                                             |
+| `shared_plan_cache_busy_time`            | `BIGINT`           | The amount of time that the server has waited for the `shared_plan_cache_busy` wait event.                                                                                                                                                                             |
+| `shmemindexlock_time`                    | `BIGINT`           | The amount of time that the server has waited for the `shmemindexlock` wait event to find or allocate space in the shared memory.                                                                                                                                      |
+| `oidgenlock_time`                        | `BIGINT`           | The amount of time that the server has waited for the `oidgenlock` wait event to allocate or assign an OID.                                                                                                                                                            |
+| `xidgenlock_time`                        | `BIGINT`           | The amount of time that the server has waited for `xidgenlock` wait event to allocate or assign a transaction ID.                                                                                                                                                      |
+| `procarraylock_time`                     | `BIGINT`           | The amount of time that the server has waited for a `procarraylock` wait event to clear a transaction ID at transaction end.                                                                                                                                           |
+| `sinvalreadlock_time`                    | `BIGINT`           | The amount of time that the server has waited for a `sinvalreadlock` wait event to retrieve or remove messages from shared invalidation queue.                                                                                                                         |
+| `sinvalwritelock_time`                   | `BIGINT`           | The amount of time that the server has waited for a `sinvalwritelock` wait event to add a message to the shared invalidation queue.                                                                                                                                    |
+| `walbufmappinglock_time`                 | `BIGINT`           | The amount of time that the server has waited for a `walbufmappinglock` wait event to replace a page in WAL buffers.                                                                                                                                                   |
+| `walwritelock_time`                      | `BIGINT`           | The amount of time that the server has waited for a `walwritelock` wait event to write the WAL buffers to disk.                                                                                                                                                        |
+| `controlfilelock_time`                   | `BIGINT`           | The amount of time that the server has waited for a `controlfilelock` wait event to read or update the control file or to create a new WAL file.                                                                                                                       |
+| `checkpointlock_time`                    | `BIGINT`           | The amount of time that the server has waited for a `checkpointlock` wait event to perform a checkpoint.                                                                                                                                                               |
+| `clogcontrollock_time`                   | `BIGINT`           | The amount of time that the server has waited for a `clogcontrollock` wait event to read or update the transaction status.                                                                                                                                             |
+| `subtranscontrollock_time`               | `BIGINT`           | The amount of time that the server has waited for the `subtranscontrollock` wait event to read or update the sub-transaction information.                                                                                                                              |
+| `multixactgenlock_time`                  | `BIGINT`           | The amount of time that the server has waited for the `multixactgenlock` wait event to read or update the shared multixact state.                                                                                                                                      |
+| `multixactoffsetcontrollock_time`        | `BIGINT`           | The amount of time that the server has waited for the `multixactoffsetcontrollock` wait event to read or update multixact offset mappings.                                                                                                                             |
+| `multixactmembercontrollock_time`        | `BIGINT`           | The amount of time that the server has waited for the `multixactmembercontrollock` wait event to read or update multixact member mappings.                                                                                                                             |
+| `relcacheinitlock_time`                  | `BIGINT`           | The amount of time that the server has waited for the `relcacheinitlock` wait event to read or write the relation cache initialization file.                                                                                                                           |
+| `checkpointercommlock_time`              | `BIGINT`           | The amount of time that the server has waited for the `checkpointercommlock` wait event to manage the fsync requests.                                                                                                                                                  |
+| `twophasestatelock_time`                 | `BIGINT`           | The amount of time that the server has waited for the `twophasestatelock` wait event to read or update the state of prepared transactions.                                                                                                                             |
+| `tablespacecreatelock_time`              | `BIGINT`           | The amount of time that the server has waited for the `tablespacecreatelock` wait event to create or drop the tablespace.                                                                                                                                              |
+| `btreevacuumlock_time`                   | `BIGINT`           | The amount of time that the server has waited for the `btreevacuumlock` wait event to read or update the vacuum related information for a B-tree index.                                                                                                                |
+| `addinshmeminitlock_time`                | `BIGINT`           | The amount of time that the server has waited for the `addinshmeminitlock` wait event to manage space allocation in shared memory.                                                                                                                                     |
+| `autovacuumlock_time`                    | `BIGINT`           | The amount of time that the server has waited for the `autovacuumlock` wait event to read or update the current state of autovacuum workers.                                                                                                                           |
+| `autovacuumschedulelock_time`            | `BIGINT`           | The amount of time that the server has waited for the `autovacuumschedulelock` wait event to ensure that the table selected for a vacuum still needs vacuuming.                                                                                                        |
+| `syncscanlock_time`                      | `BIGINT`           | The amount of time that the server has waited for the `syncscanlock` wait event to get the start location of a scan on a table for synchronized scans.                                                                                                                 |
+| `relationmappinglock_time`               | `BIGINT`           | The amount of time that the server has waited for the `relationmappinglock` wait event to update the relation map file used to store catalog to file node mapping.                                                                                                     |
+| `asyncctllock_time`                      | `BIGINT`           | The amount of time that the server has waited for the `asyncctllock` wait event to read or update shared notification state.                                                                                                                                           |
+| `asyncqueuelock_time`                    | `BIGINT`           | The amount of time that the server has waited for the `asyncqueuelock` wait event to read or update the notification messages.                                                                                                                                         |
+| `serializablexacthashlock_time`          | `BIGINT`           | The amount of time that the server has waited for the `serializablexacthashlock` wait event to retrieve or store information about serializable transactions.                                                                                                          |
+| `serializablefinishedlistlock_time`      | `BIGINT`           | The amount of time that the server has waited for the `serializablefinishedlistlock` wait event to access the list of finished serializable transactions.                                                                                                              |
+| `serializablepredicatelocklistlock_time` | `BIGINT`           | The amount of time that the server has waited for the `serializablepredicatelocklistlock` wait event to perform an operation on a list of locks held by serializable transactions.                                                                                     |
+| `oldserxidlock_time`                     | `BIGINT`           | The amount of time that the server has waited for the `oldserxidlock` wait event to read or record the conflicting serializable transactions.                                                                                                                          |
+| `syncreplock_time`                       | `BIGINT`           | The amount of time that the server has waited for the `syncreplock` wait event to read or update information about synchronous replicas.                                                                                                                               |
+| `backgroundworkerlock_time`              | `BIGINT`           | The amount of time that the server has waited for the `backgroundworkerlock` wait event to read or update the background worker state.                                                                                                                                 |
+| `dynamicsharedmemorycontrollock_time`    | `BIGINT`           | The amount of time that the server has waited for the `dynamicsharedmemorycontrollock` wait event to read or update the dynamic shared memory state.                                                                                                                   |
+| `autofilelock_time`                      | `BIGINT`           | The amount of time that the server has waited for the `autofilelock` wait event to update the `postgresql.auto.conf` file.                                                                                                                                             |
+| `replicationslotallocationlock_time`     | `BIGINT`           | The amount of time that the server has waited for the `replicationslotallocationlock` wait event to allocate or free a replication slot.                                                                                                                               |
+| `replicationslotcontrollock_time`        | `BIGINT`           | The amount of time that the server has waited for the `replicationslotcontrollock` wait event to read or update replication slot state.                                                                                                                                |
+| `committscontrollock_time`               | `BIGINT`           | The amount of time that the server has waited for the `committscontrollock` wait event to read or update transaction commit timestamps.                                                                                                                                |
+| `committslock_time`                      | `BIGINT`           | The amount of time that the server has waited for the `committslock` wait event to read or update the last value set for the transaction timestamp.                                                                                                                    |
+| `replicationoriginlock_time`             | `BIGINT`           | The amount of time that the server has waited for the `replicationoriginlock` wait event to set up, drop, or use replication origin.                                                                                                                                   |
+| `multixacttruncationlock_time`           | `BIGINT`           | The amount of time that the server has waited for the `multixacttruncationlock` wait event to read or truncate multixact information.                                                                                                                                  |
+| `oldsnapshottimemaplock_time`            | `BIGINT`           | The amount of time that the server has waited for the `oldsnapshottimemaplock` wait event to read or update old snapshot control information.                                                                                                                          |
+| `backendrandomlock_time`                 | `BIGINT`           | The amount of time that the server has waited for the `backendrandomlock` wait event to generate a random number.                                                                                                                                                      |
+| `logicalrepworkerlock_time`              | `BIGINT`           | The amount of time that the server has waited for the `logicalrepworkerlock` wait event for an action on logical replication worker to finish.                                                                                                                         |
+| `clogtruncationlock_time`                | `BIGINT`           | The amount of time that the server has waited for the `clogtruncationlock` wait event to truncate the write-ahead log or waiting for write-ahead log truncation to finish.                                                                                             |
+| `bulkloadlock_time`                      | `BIGINT`           | The amount of time that the server has waited for the `bulkloadlock` wait event to bulk upload the data.                                                                                                                                                               |
+| `edbresourcemanagerlock_time`            | `BIGINT`           | The amount of time that the server has waited for the `edbresourcemanagerlock` wait event.                                                                                                                                                                             |
+| `totalwaits`                             | `BIGINT`           | The total number of event waits.                                                                                                                                                                                                                                       |
+| `totalwaittime`                          | `BIGINT`           | The total time spent waiting for an event.                                                                                                                                                                                                                             |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx
new file mode 100644
index 00000000000..fe66e687be7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/12_dbms_random.mdx
@@ -0,0 +1,238 @@
+---
+title: "DBMS_RANDOM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.26.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.199.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.157.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/12_dbms_random/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_RANDOM` package provides methods to generate random values. The procedures and functions available in the `DBMS_RANDOM` package are listed in the following table.
+
+| Function/procedure | Return type | Description                                                                                                                                      |
+| ------------------ | ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `INITIALIZE(val)`  | n/a         | Initializes the `DBMS_RANDOM` package with the specified seed `value`. Deprecated, but supported for backward compatibility.                     |
+| `NORMAL()`         | `NUMBER`    | Returns a random `NUMBER`.                                                                                                                       |
+| `RANDOM`           | `INTEGER`   | Returns a random `INTEGER` with a value greater than or equal to -2^31 and less than 2^31. Deprecated, but supported for backward compatibility. |
+| `SEED(val)`        | n/a         | Resets the seed with the specified `value`.                                                                                                      |
+| `SEED(val)`        | n/a         | Resets the seed with the specified `value`.                                                                                                      |
+| `STRING(opt, len)` | `VARCHAR2`  | Returns a random string.                                                                                                                         |
+| `TERMINATE`        | n/a         | `TERMINATE` has no effect. Deprecated, but supported for backward compatibility.                                                                 |
+| `VALUE`            | `NUMBER`    | Returns a random number with a value greater than or equal to `0` and less than `1`, with 38-digit precision.                                    |
+| `VALUE(low, high)` | `NUMBER`    | Returns a random number with a value greater than or equal to `low` and less than `high`.                                                        |
+
+## INITIALIZE
+
+The `INITIALIZE` procedure initializes the `DBMS_RANDOM` package with a seed value. The signature is:
+
+```sql
+INITIALIZE(<val> IN INTEGER)
+```
+
+This procedure is deprecated. It is included for backward compatibility.
+
+### Parameters
+
+`val`
+
+ `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
+
+### Example
+
+The following code shows a call to the `INITIALIZE` procedure that initializes the `DBMS_RANDOM` package with the seed value 6475:
+
+```sql
+DBMS_RANDOM.INITIALIZE(6475);
+```
+
+## NORMAL
+
+The `NORMAL` function returns a random number of type `NUMBER`. The signature is:
+
+```sql
+<result> NUMBER NORMAL()
+```
+
+### Parameters
+
+`result`
+
+ `result` is a random value of type `NUMBER`.
+
+### Example
+
+The following code shows a call to the `NORMAL` function:
+
+```sql
+x:= DBMS_RANDOM.NORMAL();
+```
+
+## RANDOM
+
+The `RANDOM` function returns a random `INTEGER` value that is greater than or equal to -2 ^31 and less than 2 ^31. The signature is:
+
+```sql
+<result> INTEGER RANDOM()
+```
+
+This function is deprecated. It is included for backward compatibility.
+
+### Parameters
+
+`result`
+
+ `result` is a random value of type `INTEGER`.
+
+### Example
+
+The following code shows a call to the `RANDOM` function. The call returns a random number:
+
+```sql
+x := DBMS_RANDOM.RANDOM();
+```
+
+## SEED
+
+The first form of the `SEED` procedure resets the seed value for the `DBMS_RANDOM` package with an `INTEGER` value. The `SEED` procedure is available in two forms. The signature of the first form is:
+
+```sql
+SEED(<val> IN INTEGER)
+```
+
+### Parameters
+
+`val`
+
+ `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
+
+### Example
+
+The following code shows a call to the `SEED` procedure. The call sets the seed value at 8495.
+
+```sql
+DBMS_RANDOM.SEED(8495);
+```
+
+## SEED
+
+The second form of the `SEED` procedure resets the seed value for the `DBMS_RANDOM` package with a string value. The `SEED` procedure is available in two forms. The signature of the second form is:
+
+```sql
+SEED(<val> IN VARCHAR2)
+```
+
+### Parameters
+
+`val`
+
+ `val` is the seed value used by the `DBMS_RANDOM` package algorithm.
+
+### Example
+
+The following code shows a call to the `SEED` procedure. The call sets the seed value to `abc123`.
+
+```sql
+DBMS_RANDOM.SEED('abc123');
+```
+
+## STRING
+
+The `STRING` function returns a random `VARCHAR2` string in a user-specified format. The signature of the `STRING` function is:
+
+```sql
+<result> VARCHAR2 STRING(<opt> IN CHAR, <len> IN NUMBER)
+```
+
+### Parameters
+
+`opt`
+
+ Formatting option for the returned string. `option` can be:
+
+| Option     | Specifies formatting option     |
+| ---------- | ------------------------------- |
+| `u` or `U` | Uppercase alpha string          |
+| `l` or `L` | Lowercase alpha string          |
+| `a` or `A` | Mixed-case string               |
+| `x` or `X` | Uppercase alphanumeric string  |
+| `p` or `P` | Any printable characters        |
+
+`len`
+
+ The length of the returned string.
+
+`result`
+
+ `result` is a random value of type `VARCHAR2`.
+
+### Example
+
+The following code shows a call to the `STRING` function. The call returns a random alphanumeric character string that is 10 characters long.
+
+```sql
+x := DBMS_RANDOM.STRING('X', 10);
+```
+
+## TERMINATE
+
+The `TERMINATE` procedure has no effect. The signature is:
+
+```sql
+TERMINATE
+```
+
+The `TERMINATE` procedure is deprecated. The procedure is supported for compatibility.
+
+## VALUE
+
+The `VALUE` function returns a random `NUMBER` that is greater than or equal to 0 and less than 1, with 38-digit precision. The `VALUE` function has two forms. The signature of the first form is:
+
+```sql
+<result> NUMBER VALUE()
+```
+
+### Parameters
+
+`result`
+
+ `result` is a random value of type `NUMBER`.
+
+### Example
+
+The following code shows a call to the `VALUE` function. The call returns a random `NUMBER`:
+
+```sql
+x := DBMS_RANDOM.VALUE();
+```
+
+## VALUE
+
+The `VALUE` function returns a random `NUMBER` with a value that is between boundaries that you specify. The `VALUE` function has two forms. The signature of the second form is:
+
+```sql
+<result> NUMBER VALUE(<low> IN NUMBER, <high> IN NUMBER)
+```
+
+### Parameters
+
+`low`
+
+ `low` specifies the lower boundary for the random value. The random value can be equal to `low`.
+
+`high`
+
+ `high` specifies the upper boundary for the random value. The random value is less than `high`.
+
+`result`
+
+ `result` is a random value of type `NUMBER`.
+
+### Example
+
+The following code shows a call to the `VALUE` function. The call returns a random `NUMBER` with a value that is greater than or equal to 1 and less than 100:
+
+```sql
+x := DBMS_RANDOM.VALUE(1, 100);
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/13_dbms_redact.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/13_dbms_redact.mdx
new file mode 100644
index 00000000000..a170d937876
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/13_dbms_redact.mdx
@@ -0,0 +1,711 @@
+---
+title: "DBMS_REDACT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/13_dbms_redact/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_REDACT` package enables you to redact or mask data returned by a query. The `DBMS_REDACT` package provides a procedure to create, alter, enable, disable, and drop policies. The procedures available in the `DBMS_REDACT` package are listed in the following table.
+
+| Function/procedure                                                                                                                                                                                                                                                                                 | Function or Procedure | Return Type | Description                                                           |
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ----------- | --------------------------------------------------------------------- |
+| `ADD_POLICY(object_schema, object_name, policy_name, policy_description, column_name, column_description, function_type, function_parameters, expression, enable, regexp_pattern, regexp_replace_string, regexp_position, regexp_occurence, regexp_match_parameter, custom_function_expression)`   | Procedure             | n/a         | Adds a data redaction policy.                                         |
+| `ALTER_POLICY(object_schema, object_name, policy_name, action, column_name, function_type, function_parameters, expression, regexp_pattern, regexp_replace_string, regexp_position, regexp_occurence, regexp_match_parameter, policy_description, column_description, custom_function_expression)` | Procedure             | n/a         | Alters the existing data redaction policy.                            |
+| `DISABLE_POLICY(object_schema, object_name, policy_name)`                                                                                                                                                                                                                                          | Procedure             | n/a         | Disables the existing data redaction policy.                          |
+| `ENABLE_POLICY(object_schema, object_name, policy_name)`                                                                                                                                                                                                                                           | Procedure             | n/a         | Enables a previously disabled data redaction policy.                  |
+| `DROP_POLICY(object_schema, object_name, policy_name)`                                                                                                                                                                                                                                             | Procedure             | n/a         | Drops a data redaction policy.                                        |
+| `UPDATE_FULL_REDACTION_VALUES(number_val, binfloat_val, bindouble_val, char_val, varchar_val, nchar_val, nvarchar_val, datecol_val, ts_val, tswtz_val, blob_val, clob_val, nclob_val)`                                                                                                             | Procedure             | n/a         | Updates the full redaction default values for the specified datatype. |
+
+The data redaction feature uses the `DBMS_REDACT` package to define policies or conditions to redact data in a column based on the table column type and redaction type.
+
+You must be the owner of the table to create or change the data redaction policies. The users are exempted from all the column redaction policies, which the table owner or superuser is by default.
+
+## Using DBMS_REDACT constants and function parameters
+
+The `DBMS_REDACT` package uses the constants and redacts the column data by using any one of the data redaction types. The redaction type can be decided based on the `function_type` parameter of `dbms_redact.add_policy` and `dbms_redact.alter_policy` procedure. The table highlights the values for `function_type` parameters of `dbms_redact.add_policy` and `dbms_redact.alter_policy`.
+
+| Constant  | Type      | Value | Description                                                                                               |
+| --------- | --------- | ----- | --------------------------------------------------------------------------------------------------------- |
+| `NONE`    | `INTEGER` | `0`   | No redaction, zero effect on the result of a query against table.                                         |
+| `FULL`    | `INTEGER` | `1`   | Full redaction, redacts full values of the column data.                                                   |
+| `PARTIAL` | `INTEGER` | `2`   | Partial redaction, redacts a portion of the column data.                                                  |
+| `RANDOM`  | `INTEGER` | `4`   | Random redaction, each query results in a different random value depending on the datatype of the column. |
+| `REGEXP`  | `INTEGER` | `5`   | Regular-expression-based redaction, searches for the pattern of data to redact.                           |
+| `CUSTOM`  | `INTEGER` | `99`  | Custom redaction type.                                                                                    |
+
+The following table shows the values for the `action` parameter of `dbms_redact.alter_policy`.
+
+| Constant                 | Type      | Value | Description                                                                                                                             |
+| ------------------------ | --------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------- |
+| `ADD_COLUMN`             | `INTEGER` | `1`   | Adds a column to the redaction policy.                                                                                                  |
+| `DROP_COLUMN`            | `INTEGER` | `2`   | Drops a column from the redaction policy.                                                                                               |
+| `MODIFY_EXPRESSION`      | `INTEGER` | `3`   | Modifies the expression of a redaction policy. The redaction is applied when the expression evaluates to the `BOOLEAN` value to `TRUE`. |
+| `MODIFY_COLUMN`          | `INTEGER` | `4`   | Modifies a column in the redaction policy to change the redaction function type or function parameter.                                  |
+| `SET_POLICY_DESCRIPTION` | `INTEGER` | `5`   | Sets the redaction policy description.                                                                                                  |
+| `SET_COLUMN_DESCRIPTION` | `INTEGER` | `6`   | Sets a description for the redaction performed on the column.                                                                           |
+
+The partial data redaction enables you to redact only a portion of the column data. To use partial redaction, you must set the `dbms_redact.add_policy` procedure `function_type` parameter to `dbms_redact.partial` and use the `function_parameters` parameter to specify the partial redaction behavior.
+
+The data redaction feature provides a predefined format to configure policies that use the following datatype:
+
+-   `Character`
+-   `Number`
+-   `Datetime`
+
+The following table highlights the format descriptor for partial redaction with respect to datatype. The example shows how to perform a redaction for a string datatype (in this scenario, a Social Security Number (SSN)), a `Number` datatype, and a `DATE` datatype.
+
+| Datatype  | Format descriptor              | Description                                                                                                                                                                                                                       | Examples                                                                                                                                                                                                                                                                     |
+| --------- | ------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Character | `REDACT_PARTIAL_INPUT_FORMAT`  | Specifies the input format. Enter `V` for each character from the input string to be possibly redacted. Enter `F` for each character from the input string that can be considered as a separator such as blank spaces or hyphens. | Consider `'VVVFVVFVVVV,VVV-VV-VVVV,X,1,5'` for masking first 5 digits of SSN strings such as `123-45-6789`, adding a hyphen to format it and thereby resulting in strings such as `XXX-XX-6789.` The field value `VVVFVVFVVVV` for matching SSN strings such as `123-45-6789`. |
+|           | `REDACT_PARTIAL_OUTPUT_FORMAT` | Specifies the output format. Enter `V` for each character from the input string to be possibly redacted. Replace each `F` character from the input format with a character such as a hyphen or any other separator.               | The field value `VVV-VV-VVVV` can be used to redact SSN strings into `XXX-XX-6789` where `X` comes from `REDACT_PARTIAL_MASKCHAR` field.                                                                                                                                     |
+|           | `REDACT_PARTIAL_MASKCHAR`      | Specifies the character to use for redaction.                                                                                                                                                                                 | The value `X` for redacting SSN strings into `XXX-XX-6789`.                                                                                                                                                                                                                  |
+|           | `REDACT_PARTIAL_MASKFROM`      | Specifies the `V` in the input format from which to start the redaction.                                                                                                                                                    | The value `1` for redacting SSN strings starting at the first `V` of the input format of `VVVFVVFVVVV` into strings such as `XXX-XX-6789`.                                                                                                                                   |
+|           | `REDACT_PARTIAL_MASKTO`        | Specifies the `V` in the input format at which to end the redaction.                                                                                                                                                        | The value `5` for redacting SSN strings up to and including the fifth `V` in the input format of `VVVFVVFVVVV` into strings such as `XXX-XX-6789`.                                                                                                                       |
+| Number    | `REDACT_PARTIAL_MASKCHAR`      | Specifies the character to display in the range between 0 and 9.                                                                                                                                                             | `‘9, 1, 5’` for redacting the first five digits of the Social Security Number `123456789` into `999996789`.                                                                                                                                                                  |
+|           | `REDACT_PARTIAL_MASKFROM`      | Specifies the start-digit position for redaction.                                                                                                                                                                                 |                                                                                                                                                                                                                                                                              |
+|           | `REDACT_PARTIAL_MASKTO`        | Specifies the end-digit position for redaction.                                                                                                                                                                                   |                                                                                                                                                                                                                                                                              |
+| Datetime  | `REDACT_PARTIAL_DATE_MONTH`    | `‘m’` redacts the month. To mask a specific month, specify `‘m#’`, where # indicates the month specified by its number between `1` and `12`.                                                                                       | `m3` displays as March.                                                                                                                                                                                                                                                      |
+|           | `REDACT_PARTIAL_DATE_DAY`      | `‘d’` redacts the day of the month. To mask with a day of the month, append `1-31` to a lowercase `d`.                                                                                                                            | `d3` displays as `03`.                                                                                                                                                                                                                                                       |
+|           | `REDACT_PARTIAL_DATE_YEAR`     | `‘y’` redacts the year. To mask with a year, append `1-9999` to a lowercase `y`.                                                                                                                                                  | `y1960` displays as `60`.                                                                                                                                                                                                                                                    |
+|           | `REDACT_PARTIAL_DATE_HOUR`     | `‘h’` redacts the hour. To mask with an hour, append `0-23` to a lowercase `h`.                                                                                                                                                   | `h18` displays as `18`.                                                                                                                                                                                                                                                      |
+|           | `REDACT_PARTIAL_DATE_MINUTE`   | `‘m’` redacts the minute. To mask with a minute, append `0-59` to a lowercase `m`.                                                                                                                                                | `m20` displays as `20`.                                                                                                                                                                                                                                                      |
+|           | `REDACT_PARTIAL_DATE_SECOND`   | `‘s’` redacts the second. To mask with a second, append `0-59` to a lowercase `s`.                                                                                                                                                | `s40` displays as `40`.                                                                                                                                                                                                                                                      |
+
+The following table represents `function_parameters` values that you can use in partial redaction.
+
+| Function parameter            | Data type  | Value                                              | Description                                                                                                                                                                                        |
+| ----------------------------- | ---------- | -------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `REDACT_US_SSN_F5`            | `VARCHAR2` | `'VVVFVVFVVVV,VVV-VV-VVVV,X,1,5'`                  | Redacts the first 5 numbers of SSN. **Example:** The number `123-45-6789` becomes `XXX-XX-6789`.                                                                                                   |
+| `REDACT_US_SSN_L4`            | `VARCHAR2` | `'VVVFVVFVVVV,VVV-VV-VVVV,X,6,9'`                  | Redacts the last 4 numbers of SSN. **Example:** The number `123-45-6789` becomes `123-45-XXXX`.                                                                                                    |
+| `REDACT_US_SSN_ENTIRE`        | `VARCHAR2` | `'VVVFVVFVVVV,VVV-VV-VVVV,X,1,9'`                  | Redacts the entire SSN. **Example:** The number `123-45-6789` becomes `XXX-XX-XXXX`.                                                                                                               |
+| `REDACT_NUM_US_SSN_F5`        | `VARCHAR2` | `'9,1,5'`                                          | Redacts the first 5 numbers of SSN when the column is a number datatype. **Example:** The number `123456789` becomes `999996789`.                                                                  |
+| `REDACT_NUM_US_SSN_L4`        | `VARCHAR2` | `'9,6,9'`                                          | Redacts the last 4 numbers of SSN when the column is a number datatype. **Example:** The number `123456789` becomes `123459999`.                                                                   |
+| `REDACT_NUM_US_SSN_ENTIRE`    | `VARCHAR2` | `'9,1,9'`                                          | Redacts the entire SSN when the column is a number datatype. **Example:** The number `123456789` becomes `999999999`.                                                                              |
+| `REDACT_ZIP_CODE`             | `VARCHAR2` | `'VVVVV,VVVVV,X,1,5'`                              | Redacts a 5 digit zip code. **Example:** `12345`becomes `XXXXX`.                                                                                                                                   |
+| `REDACT_NUM_ZIP_CODE`         | `VARCHAR2` | `'9,1,5'`                                          | Redacts a 5 digit zip code when the column is a number datatype. **Example:** `12345`becomes `99999`.                                                                                              |
+| `REDACT_CCN16_F12`            | `VARCHAR2` | `'VVVVFVVVVFVVVVFVVVV,VVVV-VVVV-VVVV-VVVV,*,1,12'` | Redacts a 16 digit credit card number and displays only 4 digits. **Example:** `1234 5678 9000 2358` becomes `****-****-****-2358`.                                                                |
+| `REDACT_DATE_MILLENNIUM`      | `VARCHAR2` | `'m1d1y2000'`                                      | Redacts a date that is in the `DD-MM-YY` format. **Example:** Redacts all date to `01-JAN-2000`.                                                                                                   |
+| `REDACT_DATE_EPOCH`           | `VARCHAR2` | `'m1d1y1970'`                                      | Redacts all dates to `01-JAN-70`.                                                                                                                                                                  |
+| `REDACT_AMEX_CCN_FORMATTED`   | `VARCHAR2` | `'VVVVFVVVVVVFVVVVV,VVVV-VVVVVV-VVVVV,*,1,10'`     | Redacts the Amercian Express credit card number and replaces the digit with `*` except for the last 5 digits. **Example:** The credit card number `1234 567890 34500` becomes `**** ****** 34500`. |
+| `REDACT_AMEX_CCN_NUMBER`      | `VARCHAR2` | `'0,1,10'`                                         | Redacts the Amercian Express credit card number and replaces the digit with `0` except for the last 5 digits. **Example:** The credit card number `1234 567890 34500` becomes `0000 000000 34500`. |
+| `REDACT_SIN_FORMATTED`        | `VARCHAR2` | `'VVVFVVVFVVV,VVV-VVV-VVV,*,1,6'`                  | Redacts the Social Insurance Number by replacing the first 6 digits by `*`. **Example:** `123-456-789` becomes `***-***-789`.                                                                      |
+| `REDACT_SIN_NUMBER`           | `VARCHAR2` | `'9,1,6'`                                          | Redacts the Social Insurance Number by replacing the first 6 digits by `9`. **Example:** `123456789` becomes `999999789`.                                                                          |
+| `REDACT_SIN_UNFORMATTED`      | `VARCHAR2` | `'VVVVVVVVV,VVVVVVVVV,*,1,6'`                      | Redacts the Social Insurance Number by replacing the first 6 digits by `*`. **Example:** `123456789` becomes `******789`.                                                                          |
+| `REDACT_CCN_FORMATTED`        | `VARCHAR2` | `'VVVVFVVVVFVVVVFVVVV,VVVV-VVVV-VVVV-VVVV,*,1,12'` | Redacts a credit card number by `*` and displays only 4 digits. **Example:** The credit card number `1234-5678-9000-4671` becomes `****-****-****-4671`.                                           |
+| `REDACT_CCN_NUMBER`           | `VARCHAR2` | `'9,1,12'`                                         | Redacts a credit card number by `0` except the last 4 digits. **Example:** The credit card number `1234567890004671` becomes `0000000000004671`.                                                   |
+| `REDACT_NA_PHONE_FORMATTED`   | `VARCHAR2` | `‘VVVFVVVFVVVV,VVV-VVV-VVVV,X,4,10'`               | Redacts the North American phone number by `X` leaving the area code. **Example:** `123-456-7890` becomes `123-XXX-XXXX`.                                                                          |
+| `REDACT_NA_PHONE_NUMBER`      | `VARCHAR2` | `'0,4,10'`                                         | Redacts the North American phone number by `0` leaving the area code. **Example:** `1234567890` becomes `1230000000`.                                                                              |
+| `REDACT_NA_PHONE_UNFORMATTED` | `VARCHAR2` | `'VVVVVVVVVV,VVVVVVVVVV,X,4,10'`                   | Redacts the North American phone number by `X` leaving the area code. **Example:** `1234567890` becomes `123XXXXXXX`.                                                                              |
+| `REDACT_UK_NIN_FORMATTED`     | `VARCHAR2` | `'VVFVVFVVFVVFV,VV VV VV VV V,X,3,8'`              | Redacts the UK National Insurance Number by `X` but leaving the alphabetic characters. **Example:** `NY 22 01 34 D` becomes `NY XX XX XX D`.                                                       |
+| `REDACT_UK_NIN_UNFORMATTED`   | `VARCHAR2` | `'VVVVVVVVV,VVVVVVVVV,X,3,8'`                      | Redacts the UK National Insurance Number by `X` but leaving the alphabetic characters. **Example:** `NY220134D` becomes `NYXXXXXXD`.                                                               |
+
+A regular expression-based redaction searches for patterns of data to redact. The `regexp_pattern` search the values for the `regexp_replace_string` to change the value. The following table shows the `regexp_pattern` values that you can use during `REGEXP` based redaction.
+
+| Function parameter and description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |  Data type |                          Value                          |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------: | :-----------------------------------------------------: |
+| `RE_PATTERN_CC_L6_T4`: Searches for the middle digits of a credit card number that includes 6 leading digits and 4 trailing digits.<br />The `regexp_replace_string` setting to use with the format is `RE_REDACT_CC_MIDDLE_DIGITS` that replaces the identified pattern with the characters specified by the `RE_REDACT_CC_MIDDLE_DIGITS` parameter.                                                                                                                                                                                                                 | `VARCHAR2` |          `'(\d\d\d\d\d\d)(\d\d\d*)(\d\d\d\d)'`          |
+| `RE_PATTERN_ANY_DIGIT`: Searches for any digit and replaces the identified pattern with the characters specified by the following values of the `regexp_replace_string` parameter.<br />`regexp_replace_string=> RE_REDACT_WITH_SINGLE_X`<br /> (replaces any matched digit with the `X` character).<br /> `regexp_replace_string=> RE_REDACT_WITH_SINGLE_1` <br /> (replaces any matched digit with the `1` character).                                                                                                                                              | `VARCHAR2` |                         `'\d'`                          |
+| `RE_PATTERN_US_PHONE`: Searches for the U.S. phone number and replaces the identified pattern with the characters specified by the `regexp_replace_string` parameter.<br /> `regexp_replace_string=> RE_REDACT_US_PHONE_L7`<br /> (searches the phone number and then replaces the last 7 digits).                                                                                                                                                                                                                                                                     | `VARCHAR2` |      `'(\(\d\d\d\)\|\d\d\d)-(\d\d\d)-(\d\d\d\d)'`       |
+| `RE_PATTERN_EMAIL_ADDRESS`: Searches for the email address and replaces the identified pattern with the characters specified by the following values of the `regexp_replace_string` parameter.<br /> `regexp_replace_string=> RE_REDACT_EMAIL_NAME`<br /> (finds the email address and redacts the email username).<br /> `regexp_replace_string=> RE_REDACT_EMAIL_DOMAIN`<br /> (finds the email address and redacts the email domain).<br /> `regexp_replace_string=> RE_REDACT_EMAIL_ENTIRE`<br /> (finds the email address and redacts the entire email address). | `VARCHAR2` | `'([A-Za-z0-9._%+-]+)@([A-Za-z0-9.-]+\.[A-Za-z]{2,4})'` |
+| `RE_PATTERN_IP_ADDRESS`: Searches for an IP address and replaces the identified pattern with the characters specified by the `regexp_replace_string` parameter. The `regexp_replace_string` parameter to be used is `RE_REDACT_IP_L3` that replaces the last section of an IP address with `999` and indicates it is redacted.                                                                                                                                                                                                                                        | `VARCHAR2` |        `'(\d{1,3}\.\d{1,3}\.\d{1,3})\.\d{1,3}'`         |
+| `RE_PATTERN_AMEX_CCN`: Searches for the American Express credit card number. The `regexp_replace_string` parameter to be used is `RE_REDACT_AMEX_CCN` that redacts all of the digits except the last 5.                                                                                                                                                                                                                                                                                                                                                               | `VARCHAR2` |                   `'.*(\d\d\d\d\d)$'`                   |
+| `RE_PATTERN_CCN`: Searches for the credit card number other than American Express credit cards. The `regexp_replace_string` parameter to be used is `RE_REDACT_CCN` that redacts all of the digits except the last 4.                                                                                                                                                                                                                                                                                                                                                 | `VARCHAR2` |                    `'.*(\d\d\d\d)$'`                    |
+| `RE_PATTERN_US_SSN`: Searches the SSN number and replaces the identified pattern with the characters specified by the `regexp_replace_string` parameter.<br /> `'\1-XXX-XXXX'` or `'XXX-XXX-\3'` return `123-XXX-XXXX` or `XXX-XXX-6789` for the value `'123-45-6789'` respectively.                                                                                                                                                                                                                                                                             | `VARCHAR2` |             `'(\d\d\d)-(\d\d)-(\d\d\d\d)'`              |
+|                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |            |                                                         |
+
+This table shows the `regexp_replace_string` values that you can use during `REGEXP` based redaction.
+
+| Function parameter           | Data type  | Value              | Description                                                                                                                                                                                                                                                                                |
+| ---------------------------- | ---------- | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `RE_REDACT_CC_MIDDLE_DIGITS` | `VARCHAR2` | `'\1XXXXXX\3'`     | Redacts the middle digits of a credit card number according to the `regexp_pattern` parameter with the `RE_PATTERN_CC_L6_T4` format and replaces each redacted character with an `X`.<br /><br /> **Example:** The credit card number `1234 5678 9000 2490` becomes `1234 56XX XXXX 2490`. |
+| `RE_REDACT_WITH_SINGLE_X`    | `VARCHAR2` | `'X'`              | Replaces the data with a single `X` character for each matching pattern as specified by setting the `regexp_pattern` parameter with the `RE_PATTERN_ANY_DIGIT` format.<br /><br /> **Example:** The credit card number `1234 5678 9000 2490` becomes `XXXX XXXX XXXX XXXX`.                |
+| `RE_REDACT_WITH_SINGLE_1`    | `VARCHAR2` | `'1'`              | Replaces the data with a single `1` digit for each of the data digits as specified by setting the `regexp_pattern` parameter with the `RE_PATTERN_ANY_DIGIT` format.<br /><br /> **Example:** The credit card number `1234 5678 9000 2490` becomes `1111 1111 1111 1111`.                  |
+| `RE_REDACT_US_PHONE_L7`      | `VARCHAR2` | `'\1-XXX-XXXX'`    | Redacts the last 7 digits of U.S phone number according to the `regexp_pattern` parameter with the `RE_PATTERN_US_PHONE` format and replaces each redacted character with an `X`.<br /><br /> **Example:** The phone number `123-444-5900` becomes `123-XXX-XXXX`.                         |
+| `RE_REDACT_EMAIL_NAME`       | `VARCHAR2` | `'xxxx@\2'`        | Redacts the email name according to the `regexp_pattern` parameter with the `RE_PATTERN_EMAIL_ADDRESS` format and replaces the email username with the four `x` characters.<br /><br /> **Example:** The email address `sjohn@example.com` becomes `xxxx@example.com`.                     |
+| `RE_REDACT_EMAIL_DOMAIN`     | `VARCHAR2` | `'\1@xxxxx.com'`   | Redacts the email domain name according to the `regexp_pattern` parameter with the `RE_PATTERN_EMAIL_ADDRESS` format and replaces the domain with the five `x` characters.<br /><br /> **Example:** The email address `sjohn@example.com` becomes `sjohn@xxxxx.com`.                       |
+| `RE_REDACT_EMAIL_ENTIRE`     | `VARCHAR2` | `'xxxx@xxxxx.com'` | Redacts the entire email address according to the `regexp_pattern` parameter with the `RE_PATTERN_EMAIL_ADDRESS` format and replaces the email address with the `x` characters.<br /><br /> **Example:** The email address `sjohn@example.com` becomes `xxxx@xxxxx.com`.                   |
+| `RE_REDACT_IP_L3`            | `VARCHAR2` | `'\1.999'`         | Redacts the last 3 digits of an IP address according to the `regexp_pattern` parameter with the `RE_PATTERN_IP_ADDRESS` format.<br /><br /> **Example:** The IP address `172.0.1.258` becomes `172.0.1.999`, which is an invalid IP address.                                               |
+| `RE_REDACT_AMEX_CCN`         | `VARCHAR2` | `'**********\1'`   | Redacts the first 10 digits of an American Express credit card number according to the `regexp_pattern` parameter with the `RE_PATTERN_AMEX_CCN` format.<br /><br /> **Example:** `123456789062816` becomes `**********62816`.                                                             |
+| `RE_REDACT_CCN`              | `VARCHAR2` | `'************\1'` | Redacts the first 12 digits of a credit card number as specified by the `regexp_pattern` parameter with the `RE_PATTERN_CCN` format.<br /><br /> **Example:** `8749012678345671` becomes `************5671`.                                                                               |
+
+The following tables show the `regexp_position` value and `regexp_occurence` values that you can use during `REGEXP` based redaction.
+
+| Function parameter | Data type | Value | Description                                                                                                                                                           |
+| ------------------ | --------- | ----- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `RE_BEGINNING`     | `INTEGER` | `1`   | Specifies the position of a character where search must begin. By default, the value is `1` that indicates the search begins at the first character of `source_char`. |
+
+| Function parameter | Data type | Value | Description                                                                                                                            |
+| ------------------ | --------- | ----- | -------------------------------------------------------------------------------------------------------------------------------------- |
+| `RE_ALL`           | `INTEGER` | `0`   | Specifies the replacement occurrence of a substring. If the value is `0`, then the replacement of each matching substring occurs.      |
+| `RE_FIRST`         | `INTEGER` | `1`   | Specifies the replacement occurrence of a substring. If the value is `1`, then the replacement of the first matching substring occurs. |
+
+The following table shows the `regexp_match_parameter` values that you can use during `REGEXP` based redaction which lets you change the default matching behavior of a function.
+
+| Function parameter     | Data type  | Value | Description                                                                                                     |
+| ---------------------- | ---------- | ----- | --------------------------------------------------------------------------------------------------------------- |
+| `RE_CASE_SENSITIVE`    | `VARCHAR2` | `'c'` | Specifies the case-sensitive matching.                                                                          |
+| `RE_CASE_INSENSITIVE`  | `VARCHAR2` | `'i'` | Specifies the case-insensitive matching.                                                                        |
+| `RE_MULTIPLE_LINES`    | `VARCHAR2` | `'m'` | Treats the source string as multiple lines but if you omit this parameter, then it indicates as a single line.  |
+| `RE_NEWLINE_WILDCARD`  | `VARCHAR2` | `'n'` | Specifies the period (.), but if you omit this parameter, then the period does not match the newline character. |
+| `RE_IGNORE_WHITESPACE` | `VARCHAR2` | `'x'` | Ignores the whitespace characters.                                                                              |
+
+!!! Note
+    If you create a redaction policy based on a numeric-type column, then make sure that the result after redaction is a number and set the replacement string accordingly to avoid runtime errors.
+
+!!! Note
+    If you create a redaction policy based on a character-type column, then make sure that a length of the result after redaction is compatible with the column type and set the replacement string accordingly to avoid runtime errors.
+
+## ADD_POLICY
+
+The `add_policy` procedure creates a new data redaction policy for a table.
+
+```sql
+PROCEDURE add_policy (
+  <object_schema>                IN VARCHAR2 DEFAULT NULL,
+  <object_name>                  IN VARCHAR2,
+  <policy_name>                  IN VARCHAR2,
+  <policy_description>           IN VARCHAR2 DEFAULT NULL,
+  <column_name>                  IN VARCHAR2 DEFAULT NULL,
+  <column_description>           IN VARCHAR2 DEFAULT NULL,
+  <function_type>                IN INTEGER DEFAULT DBMS_REDACT.FULL,
+  <function_parameters>          IN VARCHAR2 DEFAULT NULL,
+  <expression>                   IN VARCHAR2,
+  <enable>                       IN BOOLEAN DEFAULT TRUE,
+  <regexp_pattern>               IN VARCHAR2 DEFAULT NULL,
+  <regexp_replace_string>        IN VARCHAR2 DEFAULT NULL,
+  <regexp_position>              IN INTEGER DEFAULT DBMS_REDACT.RE_BEGINNING,
+  <regexp_occurrence>            IN INTEGER DEFAULT DBMS_REDACT.RE_ALL,
+  <regexp_match_parameter>       IN VARCHAR2 DEFAULT NULL,
+  <custom_function_expression>   IN VARCHAR2 DEFAULT NULL
+  )
+```
+
+### Parameters
+
+`object_schema`
+
+ Specifies the name of the schema in which the object resides and on which the data redaction policy is applied. If you specify `NULL`, then the given object is searched by the order specified by `search_path` setting.
+
+`object_name`
+
+ Name of the table on which the data redaction policy is created.
+
+`policy_name`
+
+ Name of the policy to add. Ensure that the `policy_name` is unique for the table on which the policy is created.
+
+`policy_description`
+
+ Specify the description of a redaction policy.
+
+`column_name`
+
+ Name of the column to which the redaction policy applies. To redact more than one column, use the `alter_policy` procedure to add more columns.
+
+`column_description`
+
+ Description of the column to redact. The `column_description` isn't supported, but if you specify the description for a column, a warning message appears.
+
+`function_type`
+
+ The type of redaction function to use. The possible values are `NONE`, `FULL`, `PARTIAL`, `RANDOM`, `REGEXP`, and `CUSTOM`.
+
+`function_parameters`
+
+ Specifies the function parameters for the partition redaction and is applicable only for partial redaction.
+
+`expression`
+
+ Specifies the Boolean expression for the table and determines how to apply the policy. The redaction occurs if this policy expression evaluates to `TRUE`.
+
+`enable`
+
+ When set to `TRUE`, the policy is enabled upon creation. The default is `TRUE`. When set to `FALSE`, the policy is disabled, but you can enable the policy cby calling the `enable_policy` procedure.
+
+`regexp_pattern`
+
+ Specifies the regular expression pattern to redact data. If the `regexp_pattern` doesn't match, then the `NULL` value is returned.
+
+`regexp_replace_string`
+
+ Specifies the replacement string value.
+
+`regexp_position`
+
+ Specifies the position of a character where search must begin. By default, the function parameter is `RE_BEGINNING`.
+
+`regexp_occurrence`
+
+ Specifies the replacement occurrence of a substring. If the constant is `RE_ALL`, then the replacement of each matching substring occurs. If the constant is `RE_FIRST`, then the replacement of the first matching substring occurs.
+
+`regexp_match_parameter`
+
+ Changes the default matching behavior of a function. The possible `regexp_match_parameter` constants can be `‘RE_CASE_SENSITIVE’`, `‘RE_CASE_INSENSITIVE’`, `‘RE_MULTIPLE_LINES’`, `‘RE_NEWLINE_WILDCARD’`, and `‘RE_IGNORE_WHITESPACE’`.
+
+ !!!Note
+   For more information on `constants`, `function_parameters`, or `regexp`, see [Using DBMS_REDACT Constants and Function Parameters](#using-dbms_redact-constants-and-function-parameters).
+
+`custom_function_expression`
+
+ The `custom_function_expression` applies only for the `CUSTOM` redaction type. The `custom_function_expression` is a function expression, that is, a schema-qualified function with a parameter such as `schema_name.function_name (argument1, …)` that allows a user to use their redaction logic to redact the column data.
+
+### Example
+
+This example shows how to create a policy and use full redaction for values in the `payment_details_tab` table `customer id` column.
+
+```sql
+edb=# CREATE TABLE payment_details_tab (
+customer_id NUMBER       NOT NULL,
+card_string VARCHAR2(19) NOT NULL);
+CREATE TABLE
+
+edb=# BEGIN
+  INSERT INTO payment_details_tab VALUES (4000, '1234-1234-1234-1234');
+  INSERT INTO payment_details_tab VALUES (4001, '2345-2345-2345-2345');
+END;
+
+EDB-SPL Procedure successfully completed
+
+edb=# CREATE USER redact_user;
+CREATE ROLE
+edb=# GRANT SELECT ON payment_details_tab TO redact_user;
+GRANT
+
+\c edb base_user
+
+BEGIN
+  DBMS_REDACT.add_policy(
+     object_schema              => 'public',
+     object_name                => 'payment_details_tab',
+     policy_name                => 'redactPolicy_001',
+     policy_description         => 'redactPolicy_001 for payment_details_tab table',
+     column_name                => 'customer_id',
+     function_type              => DBMS_REDACT.full,
+     expression                 => '1=1',
+     enable                     => TRUE);
+END;
+```
+
+Redacted Result:
+
+```sql
+edb=# \c edb redact_user
+You are now connected to database "edb" as user "redact_user".
+
+edb=> select customer_id from payment_details_tab order by 1;
+__OUTPUT__
+ customer_id
+-------------
+           0
+           0
+(2 rows)
+```
+
+## ALTER_POLICY
+
+The `alter_policy` procedure alters or modifies an existing data redaction policy for a table.
+
+```sql
+PROCEDURE alter_policy (
+  <object_schema>                IN VARCHAR2 DEFAULT NULL,
+  <object_name>                  IN VARCHAR2,
+  <policy_name>                  IN VARCHAR2,
+  <action>                       IN INTEGER DEFAULT DBMS_REDACT.ADD_COLUMN,
+  <column_name>                  IN VARCHAR2 DEFAULT NULL,
+  <function_type>                IN INTEGER DEFAULT DBMS_REDACT.FULL,
+  <function_parameters>          IN VARCHAR2 DEFAULT NULL,
+  <expression>                   IN VARCHAR2 DEFAULT NULL,
+  <regexp_pattern>               IN VARCHAR2 DEFAULT NULL,
+  <regexp_replace_string>        IN VARCHAR2 DEFAULT NULL,
+  <regexp_position>              IN INTEGER DEFAULT DBMS_REDACT.RE_BEGINNING,
+  <regexp_occurrence>            IN INTEGER DEFAULT DBMS_REDACT.RE_ALL,
+  <regexp_match_parameter>       IN VARCHAR2 DEFAULT NULL,
+  <policy_description>           IN VARCHAR2 DEFAULT NULL,
+  <column_description>           IN VARCHAR2 DEFAULT NULL,
+  <custom_function_expression>   IN VARCHAR2 DEFAULT NULL
+  )
+```
+
+### Parameters
+
+`object_schema`
+
+ Specifies the name of the schema in which the object resides and on which to alter the data redaction policy. If you specify `NULL`, then the given object is searched by the order specified by `search_path` setting.
+
+`object_name`
+
+ Name of the table to which to alter a data redaction policy.
+
+`policy_name`
+
+ Name of the policy to alter.
+
+`action`
+
+ The action to perform. For more information about action parameters see, [Using DBMS_REDACT Constants and Function Parameters](#using-dbms_redact-constants-and-function-parameters)
+
+`column_name`
+
+ Name of the column to which the redaction policy applies.
+
+`function_type`
+
+ The type of redaction function to use. The possible values are `NONE`, `FULL`, `PARTIAL`, `RANDOM`, `REGEXP`, and `CUSTOM`.
+
+`function_parameters`
+
+ Specifies the function parameters for the redaction function.
+
+`expression`
+
+ Specifies the Boolean expression for the table and determines how to apply the policy. The redaction occurs if this policy expression evaluates to `TRUE`.
+
+`regexp_pattern`
+
+ Enables the use of regular expressions to redact data. If the `regexp_pattern` doesn't match the data, then the `NULL` value is returned.
+
+`regexp_replace_string`
+
+ Specifies the replacement string value.
+
+`regexp_position`
+
+ Specifies the position of a character where search must begin. By default, the function parameter is `RE_BEGINNING`.
+
+`regexp_occurence`
+
+ Specifies the replacement occurrence of a substring. If the constant is `RE_ALL`, then the replacement of each matching substring occurs. If the constant is `RE_FIRST`, then the replacement of the first matching substring occurs.
+
+`regexp_match_parameter`
+
+ Changes the default matching behavior of a function. The possible `regexp_match_parameter` constants can be `‘RE_CASE_SENSITIVE’`, `‘RE_CASE_INSENSITIVE’`, `‘RE_MULTIPLE_LINES’`, `‘RE_NEWLINE_WILDCARD’`, and `‘RE_IGNORE_WHITESPACE’`.
+
+ !!!Note 
+  For more information on `constants`, `function_parameters`, or `regexp`, see [Using DBMS_REDACT Constants and Function Parameters](#using-dbms_redact-constants-and-function-parameters).
+
+`policy_description`
+
+ Specify the description of a redaction policy.
+
+`column_description`
+
+ Description of the column to redact. The `column_description` isn't supported, but if you specify the description for a column, a warning message appears.
+
+`custom_function_expression`
+
+ The `custom_function_expression` applies only for the `CUSTOM` redaction type. The `custom_function_expression` is a function expression, that is, a schema-qualified function with a parameter such as `schema_name.function_name (argument1, …)` that allows a user to use their redaction logic to redact the column data.
+
+### Example
+
+This example shows how to alter a policy using partial redaction for values in the `payment_details_tab` table `card_string` (usually a credit card number) column.
+
+```sql
+\c edb base _user
+
+BEGIN
+  DBMS_REDACT.alter_policy (
+     object_schema               => 'public',
+     object_name                 => 'payment_details_tab',
+     policy_name                 => 'redactPolicy_001',
+     action                      => DBMS_REDACT.ADD_COLUMN,
+     column_name                 => 'card_string',
+     function_type               => DBMS_REDACT.partial,
+     function_parameters         => DBMS_REDACT.REDACT_CCN16_F12);
+END;
+```
+
+Redacted Result:
+
+```sql
+edb=# \c - redact_user
+You are now connected to database "edb" as user "redact_user".
+edb=> SELECT * FROM payment_details_tab;
+__OUTPUT__
+ customer_id |     card_string
+-------------+---------------------
+           0 | ****-****-****-1234
+           0 | ****-****-****-2345
+(2 rows)
+```
+
+## DISABLE_POLICY
+
+The `disable_policy` procedure disables an existing data redaction policy.
+
+```sql
+PROCEDURE disable_policy (
+  <object_schema>       IN VARCHAR2 DEFAULT NULL,
+  <object_name>         IN VARCHAR2,
+  <policy_name>         IN VARCHAR2
+  )
+```
+
+### Parameters
+
+`object_schema`
+
+ Specifies the name of the schema in which the object resides and on which to apply the data redaction policy. If you specify `NULL`, then the given object is searched by the order specified by `search_path` setting.
+
+`object_name`
+
+ Name of the table for which to disable a data redaction policy.
+
+`policy_name`
+
+ Name of the policy to disable.
+
+### Example
+
+This example shows how to disable a policy.
+
+```sql
+\c edb base_user
+
+BEGIN
+  DBMS_REDACT.disable_policy(
+     object_schema => 'public',
+     object_name => 'payment_details_tab',
+     policy_name => 'redactPolicy_001');
+END;
+```
+
+Redacted Result: Data is no longer redacted after disabling a policy.
+
+## ENABLE_POLICY
+
+The `enable_policy` procedure enables the previously disabled data redaction policy.
+
+```sql
+PROCEDURE enable_policy (
+  <object_schema>          IN VARCHAR2 DEFAULT NULL,
+  <object_name>            IN VARCHAR2,
+  <policy_name>            IN VARCHAR2
+  )
+```
+
+### Parameters
+
+`object_schema`
+
+ Specifies the name of the schema in which the object resides and on which to apply the data redaction policy. If you specify `NULL`, then the given object is searched by the order specified by `search_path` setting.
+
+`object_name`
+
+ Name of the table to which to enable a data redaction policy.
+
+`policy_name`
+
+ Name of the policy to enable.
+
+### Example
+
+This example shows how to enable a policy.
+
+```sql
+\c edb base_user
+
+BEGIN
+  DBMS_REDACT.enable_policy(
+     object_schema => 'public',
+     object_name => 'payment_details_tab',
+     policy_name => 'redactPolicy_001');
+END;
+```
+
+Redacted Result: Data is redacted after enabling a policy.
+
+## DROP_POLICY
+
+The `drop_policy` procedure drops a data redaction policy by removing the masking policy from a table.
+
+```sql
+PROCEDURE drop_policy (
+  <object_schema>       IN VARCHAR2 DEFAULT NULL,
+  <object_name>         IN VARCHAR2,
+  <policy_name>         IN VARCHAR2
+  )
+```
+
+### Parameters
+
+`object_schema`
+
+ Specifies the name of the schema in which the object resides and on which to apply the data redaction policy. If you specify `NULL`, then the given object is searched by the order specified by `search_path` setting.
+
+`object_name`
+
+ Name of the table from which to drop a data redaction policy.
+
+`policy_name`
+
+ Name of the policy to drop.
+
+### Example
+
+This example shows how to drop a policy.
+
+```sql
+\c edb base_user
+
+BEGIN
+  DBMS_REDACT.drop_policy(
+     object_schema => 'public',
+     object_name => 'payment_details_tab',
+     policy_name => 'redactPolicy_001');
+END;
+```
+
+Redacted Result: The server drops the specified policy.
+
+## UPDATE_FULL_REDACTION_VALUES
+
+The `update_full_redaction_values` procedure updates the default displayed values for a data redaction policy. You can view these default values using the `redaction_values_for_type_full` view that uses the full redaction type.
+
+```sql
+PROCEDURE update_full_redaction_values (
+  <number_val>        IN NUMBER            DEFAULT NULL,
+  <binfloat_val>      IN FLOAT4            DEFAULT NULL,
+  <bindouble_val>     IN FLOAT8            DEFAULT NULL,
+  <char_val>          IN CHAR              DEFAULT NULL,
+  <varchar_val>       IN VARCHAR2          DEFAULT NULL,
+  <nchar_val>         IN NCHAR             DEFAULT NULL,
+  <nvarchar_val>      IN NVARCHAR2         DEFAULT NULL,
+  <datecol_val>       IN DATE              DEFAULT NULL,
+  <ts_val>            IN TIMESTAMP         DEFAULT NULL,
+  <tswtz_val>         IN TIMESTAMPTZ       DEFAULT NULL,
+  <blob_val>          IN BLOB              DEFAULT NULL,
+  <clob_val>          IN CLOB              DEFAULT NULL,
+  <nclob_val>         IN CLOB              DEFAULT NULL
+  )
+```
+
+### Parameters
+
+`number_val`
+
+ Updates the default value for columns of the `NUMBER` datatype.
+
+`binfloat_val`
+
+ The `FLOAT4` datatype is a random value. The binary float datatype isn't supported.
+
+`bindouble_val`
+
+ The `FLOAT8` datatype is a random value. The binary double datatype isn;t supported.
+
+`char_val`
+
+ Updates the default value for columns of the `CHAR` datatype.
+
+`varchar_val`
+
+ Updates the default value for columns of the `VARCHAR2` datatype.
+
+`nchar_val`
+
+ The `nchar_val` is mapped to `CHAR` datatype and returns the `CHAR` value.
+
+`nvarchar_val`
+
+ The `nvarchar_val` is mapped to `VARCHAR2` datatype and returns the `VARCHAR` value.
+
+`datecol_val`
+
+ Updates the default value for columns of the `DATE` datatype.
+
+`ts_val`
+
+ Updates the default value for columns of the `TIMESTAMP` datatype.
+
+`tswtz_val`
+
+ Updates the default value for columns of the `TIMESTAMPTZ` datatype.
+
+`blob_val`
+
+ Updates the default value for columns of the `BLOB` datatype.
+
+`clob_val`
+
+ Updates the default value for columns of the `CLOB` datatype.
+
+`nclob_val`
+
+ The `nclob_val` is mapped to `CLOB` datatype and returns the `CLOB` value.
+
+### Example
+
+This example shows how to update the full redaction values. Before updating the values, you can view the default values using the `redaction_values_for_type_full` view.
+
+```sql
+edb=# \x
+Expanded display is on.
+edb=# SELECT number_value, char_value, varchar_value, date_value,
+       timestamp_value, timestamp_with_time_zone_value, blob_value,
+clob_value
+FROM redaction_values_for_type_full;
+__OUTPUT__
+-[ RECORD 1 ]------------------+--------------------------
+number_value                   | 0
+char_value                     |
+varchar_value                  |
+date_value                     | 01-JAN-01 00:00:00
+timestamp_value                | 01-JAN-01 01:00:00
+timestamp_with_time_zone_value | 31-DEC-00 20:00:00 -05:00
+blob_value                     | \x5b72656461637465645d
+clob_value                     | [redacted]
+(1 row)
+```
+
+Update the default values for full redaction type. The `NULL` values are ignored.
+
+```sql
+\c edb base_user
+
+edb=# BEGIN
+    DBMS_REDACT.update_full_redaction_values (
+    number_val => 9999999,
+    char_val => 'Z',
+    varchar_val => 'V',
+    datecol_val => to_date('17/10/2018', 'DD/MM/YYYY'),
+    ts_val => to_timestamp('17/10/2018 11:12:13', 'DD/MM/YYYY HH24:MI:SS'),
+    tswtz_val => NULL,
+    blob_val => 'NEW REDACTED VALUE',
+    clob_val => 'NEW REDACTED VALUE');
+END;
+```
+
+You can now see the updated values using the `redaction_values_for_type_full` view.
+
+```sql
+EDB-SPL Procedure successfully completed
+edb=# SELECT number_value, char_value, varchar_value, date_value,
+       timestamp_value, timestamp_with_time_zone_value, blob_value,
+clob_value
+FROM redaction_values_for_type_full;
+__OUTPUT__
+-[ RECORD 1 ]------------------+---------------------------------------
+number_value                   | 9999999
+char_value                     | Z
+varchar_value                  | V
+date_value                     | 17-OCT-18 00:00:00
+timestamp_value                | 17-OCT-18 11:12:13
+timestamp_with_time_zone_value | 31-DEC-00 20:00:00 -05:00
+blob_value                     | \x4e45572052454441435445442056414c5545
+clob_value                     | NEW REDACTED VALUE
+(1 row)
+```
+
+Redacted Result:
+
+```sql
+edb=# \c edb redact_user
+You are now connected to database "edb" as user "redact_user".
+
+edb=> select * from payment_details_tab order by 1;
+__OUTPUT__
+ customer_id | card_string
+-------------+-------------
+     9999999 | V
+     9999999 | V
+(2 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx
new file mode 100644
index 00000000000..ac5708484c3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls.mdx
@@ -0,0 +1,509 @@
+---
+title: "DBMS_RLS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.27.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.200.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.158.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/14_dbms_rls/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_RLS` package enables you to implement Virtual Private Database on certain EDB Postgres Advanced Server database objects.
+
+EDB Postgres Advanced Server's implementation of `DBMS_RLS` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+| Function/procedure                                                                                                                                                                                                                            | Function or procedure | Return type | Description                                      |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ----------- | ------------------------------------------------ |
+| `ADD_POLICY(object_schema, object_name, policy_name, function_schema, policy_function [, statement_types [, update_check [, enable [, static_policy [, policy_type [, long_predicate [, sec_relevant_cols [, sec_relevant_cols_opt ]]]]]]]])` | Procedure             | n/a         | Add a security policy to a database object.      |
+| `DROP_POLICY(object_schema, object_name, policy_name)`                                                                                                                                                                                        | Procedure             | n/a         | Remove a security policy from a database object. |
+| `ENABLE_POLICY(object_schema, object_name, policy_name, enable)`                                                                                                                                                                              | Procedure             | n/a         | Enable or disable a security policy.             |
+
+*Virtual Private Database* is a type of fine-grained access control using security policies. *Fine-grained access control* in Virtual Private Database means that you can control access to data down to specific rows as defined by the security policy.
+
+The rules that encode a security policy are defined in a *policy function*, which is an SPL function with certain input parameters and return values. The *security policy* is the named association of the policy function to a particular database object, typically a table.
+
+!!! Note
+    In EDB Postgres Advanced Server, you can write the policy function in any language supported by EDB Postgres Advanced Server, such as SQL, PL/pgSQL, and SPL.
+
+!!! Note
+    The database objects currently supported by EDB Postgres Advanced Server Virtual Private Database are tables. You can't apply policies to views or synonyms.
+
+Virtual Private Database has these advantages:
+
+-   It provides a fine-grained level of security. Database object-level privileges given by the `GRANT` command determine access privileges to the entire instance of a database object, while Virtual Private Database provides access control for the individual rows of a database object instance.
+-   You can apply a different security policy depending on the type of SQL command (`INSERT`, `UPDATE`, `DELETE`, or `SELECT`).
+-   The security policy can vary dynamically for each applicable SQL command affecting the database object, depending on factors such as the session user of the application accessing the database object.
+-   Invoking the security policy is transparent to all applications that access the database object. Thus, you don't have to modify individual applications to apply the security policy.
+-   Once a security policy is enabled, applications (including new applications) can't circumvent the security policy except by the system privilege described in the note that follows.
+-   Even superusers can't circumvent the security policy except by the system privilege described in the note that follows.
+
+!!! Note
+    The only way to circumvent security policies is if the `EXEMPT ACCESS POLICY` system privilege is granted to a user. Grant the `EXEMPT ACCESS POLICY` privilege with extreme care as a user with this privilege is exempted from all policies in the database.
+
+The `DBMS_RLS` package provides procedures to create policies, remove policies, enable policies, and disable policies.
+
+The process for implementing Virtual Private Database is as follows:
+
+1.  Create a policy function. The function must have two input parameters of type `VARCHAR2`. The first input parameter is for the schema containing the database object to which the policy applies. The second input parameter is for the name of that database object. The function must have a `VARCHAR2` return type and return a string in the form of a `WHERE` clause predicate. This predicate is dynamically appended as an `AND` condition to the SQL command that acts on the database object. Thus, rows that don't satisfy the policy function predicate are filtered out from the SQL command result set.
+1.  Use the `ADD_POLICY` procedure to define a new policy, which is the association of a policy function with a database object. With the `ADD_POLICY` procedure, you can also specify:
+    -  The types of SQL commands (`INSERT`, `UPDATE`, `DELETE`, or `SELECT`) to which the policy applies
+    -  Whether to enable the policy at the time of its creation
+    -  Whether the policy applies to newly inserted rows or the modified image of updated rows
+1.  Use the `ENABLE_POLICY` procedure to disable or enable an existing policy.
+1.  Use the `DROP_POLICY` procedure to remove an existing policy. The `DROP_POLICY` procedure doesn't drop the policy function or the associated database object.
+
+Once you create policies, you can view them in the catalog views compatible with Oracle databases: `ALL_POLICIES`, `DBA_POLICIES`, or `USER_POLICIES`. The supported compatible views are listed in [Catalog views](../../epas_compat_cat_views/).
+
+The `SYS_CONTEXT` function is often used with `DBMS_RLS`. The signature is:
+
+```sql
+SYS_CONTEXT(<namespace>, <attribute>)
+```
+
+Where:
+
+ `namespace` is a `VARCHAR2`. The only accepted value is `USERENV`. Any other value returns `NULL`.
+
+ `attribute` is a `VARCHAR2`. Possible values are:
+
+| attribute Value  | Equivalent value              |
+| ---------------- | ----------------------------- |
+| `SESSION_USER`   | `pg_catalog.session_user`     |
+| `CURRENT_USER`   | `pg_catalog.current_user`     |
+| `CURRENT_SCHEMA` | `pg_catalog.current_schema`   |
+| `HOST`           | `pg_catalog.inet_host`        |
+| `IP_ADDRESS`     | `pg_catalog.inet_client_addr` |
+| `SERVER_HOST`    | `pg_catalog.inet_server_addr` |
+
+
+The examples used to illustrate the `DBMS_RLS` package are based on a modified copy of the sample `emp` table provided with EDB Postgres Advanced Server along with a role named `salesmgr` that is granted all privileges on the table. You can create the modified copy of the `emp` table named `vpemp` and the `salesmgr` role as follows:
+
+```sql
+CREATE TABLE public.vpemp AS SELECT empno, ename, job, sal, comm, deptno
+FROM emp;
+ALTER TABLE vpemp ADD authid VARCHAR2(12);
+UPDATE vpemp SET authid = 'researchmgr' WHERE deptno = 20;
+UPDATE vpemp SET authid = 'salesmgr' WHERE deptno = 30;
+SELECT * FROM vpemp;
+__OUTPUT__
+empno  | ename  |    job    |   sal   |  comm   | deptno |   authid
+-------+--------+-----------+---------+---------+--------+-------------
+  7782 | CLARK  | MANAGER   | 2450.00 |         |     10 |
+  7839 | KING   | PRESIDENT | 5000.00 |         |     10 |
+  7934 | MILLER | CLERK     | 1300.00 |         |     10 |
+  7369 | SMITH  | CLERK     |  800.00 |         |     20 | researchmgr
+  7566 | JONES  | MANAGER   | 2975.00 |         |     20 | researchmgr
+  7788 | SCOTT  | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7876 | ADAMS  | CLERK     | 1100.00 |         |     20 | researchmgr
+  7902 | FORD   | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7499 | ALLEN  | SALESMAN  | 1600.00 |  300.00 |     30 | salesmgr
+  7521 | WARD   | SALESMAN  | 1250.00 |  500.00 |     30 | salesmgr
+  7654 | MARTIN | SALESMAN  | 1250.00 | 1400.00 |     30 | salesmgr
+  7698 | BLAKE  | MANAGER   | 2850.00 |         |     30 | salesmgr
+  7844 | TURNER | SALESMAN  | 1500.00 |    0.00 |     30 | salesmgr
+  7900 | JAMES  | CLERK     |  950.00 |         |     30 | salesmgr
+(14 rows)
+
+CREATE ROLE salesmgr WITH LOGIN PASSWORD 'password';
+GRANT ALL ON vpemp TO salesmgr;
+```
+
+## ADD_POLICY
+
+The `ADD_POLICY` procedure creates a new policy by associating a policy function with a database object.
+
+You must be a superuser to execute this procedure.
+
+```sql
+ADD_POLICY(<object_schema> VARCHAR2, <object_name> VARCHAR2,
+  <policy_name> VARCHAR2, <function_schema> VARCHAR2,
+  <policy_function> VARCHAR2
+  [, <statement_types> VARCHAR2
+  [, <update_check> BOOLEAN
+  [, <enable> BOOLEAN
+  [, <static_policy> BOOLEAN
+  [, <policy_type> INTEGER
+  [, <long_predicate> BOOLEAN
+  [, <sec_relevant_cols> VARCHAR2
+  [, <sec_relevant_cols_opt> INTEGER ]]]]]]]])
+```
+
+### Parameters
+
+`object_schema`
+
+ Name of the schema containing the database object to which to apply the policy.
+
+`object_name`
+
+ Name of the database object to which to apply the policy. A given database object can have more than one policy applied to it.
+
+`policy_name`
+
+ Name assigned to the policy. The combination of database object (identified by `object_schema` and `object_name`) and policy name must be unique in the database.
+
+`function_schema`
+
+ Name of the schema containing the policy function.
+
+ !!! Note
+     The policy function might belong to a package. In this case `function_schema` must contain the name of the schema in which the package is defined.
+
+`policy_function`
+
+ Name of the SPL function that defines the rules of the security policy. You can specify the same function in more than one policy.
+
+ !!! Note
+     The policy function might belong to a package. In this case `policy_function` must also contain the package name in dot notation (that is, `package_name.function_name`).
+
+`statement_types`
+
+ Comma-separated list of SQL commands to which the policy applies. Valid SQL commands are `INSERT`, `UPDATE`, `DELETE`, and `SELECT`. The default is `INSERT,UPDATE,DELETE,SELECT`.
+
+ !!! Note
+    EDB Postgres Advanced Server accepts `INDEX` as a statement type but it is ignored. Policies aren't applied to index operations in EDB Postgres Advanced Server.
+
+`update_check`
+
+ Applies to `INSERT` and `UPDATE` SQL commands only.
+
+-   When set to `TRUE`, the policy is applied to newly inserted rows and to the modified image of updated rows. If any of the new or modified rows don't qualify according to the policy function predicate, then the `INSERT` or `UPDATE` command throws an exception and no rows are inserted or modified by the `INSERT` or `UPDATE` command.
+-   When set to `FALSE`, the policy isn't applied to newly inserted rows or the modified image of updated rows. Thus, a newly inserted row might not appear in the result set of a subsequent SQL command that invokes the same policy. Similarly, rows that qualified according to the policy prior to an `UPDATE` command might not appear in the result set of a subsequent SQL command that invokes the same policy.
+-   The default is `FALSE`.
+
+`enable`
+
+ When set to `TRUE`, the policy is enabled and applied to the SQL commands given by the `statement_types` parameter. When set to `FALSE` the policy is disabled and not applied to any SQL commands. You can enable the policy using the `ENABLE_POLICY` procedure. The default is `TRUE`.
+
+`static_policy`
+
+ In Oracle, when set to `TRUE`, the policy is *static*, which means the policy function is evaluated once per database object the first time it's invoked by a policy on that database object. The resulting policy function predicate string is saved in memory and reused for all invocations of that policy on that database object while the database server instance is running.
+
+-   When set to `FALSE`, the policy is *dynamic*, which means the policy function is reevaluated and the policy function predicate string regenerated for all invocations of the policy.
+-   The default is `FALSE`.
+
+    !!! Note
+        In Oracle 10g, the `policy_type` parameter was introduced, which is intended to replace the `static_policy` parameter. In Oracle, if the `policy_type` parameter isn't set to its default value of `NULL`, the `policy_type` parameter setting overrides the `static_policy` setting.
+
+    !!! Note
+        The setting of `static_policy` is ignored by EDB Postgres Advanced Server. EDB Postgres Advanced Server implements only the dynamic policy, regardless of the setting of the `static_policy` parameter.
+
+`policy_type`
+
+ In Oracle, determines when the policy function is reevaluated and, hence, if and when the predicate string returned by the policy function changes. The default is `NULL`.
+
+ !!! Note 
+    This parameter setting is ignored by EDB Postgres Advanced Server. EDB Postgres Advanced Server always assumes a dynamic policy.
+
+`long_predicate`
+
+ In Oracle, allows predicates up to 32K bytes if set to `TRUE`. Otherwise predicates are limited to 4000 bytes. The default is `FALSE`.
+
+ !!! Note 
+    This parameter setting is ignored by EDB Postgres Advanced Server. An EDB Postgres Advanced Server policy function can return a predicate of unlimited length for all practical purposes.
+
+`sec_relevant_cols`
+
+ Comma-separated list of columns of `object_name`. Provides *column-level Virtual Private Database* for the listed columns. The policy is enforced if any of the listed columns are referenced in a SQL command of a type listed in `statement_types`. The policy isn't enforced if no such columns are referenced.
+
+ The default is `NULL`, which has the same effect as if all of the database object’s columns were included in `sec_relevant_cols`.
+
+`sec_relevant_cols_opt`
+
+ In Oracle, if `sec_relevant_cols_opt` is set to `DBMS_RLS.ALL_ROWS` (`INTEGER` constant of value 1), then the columns listed in `sec_relevant_cols` return `NULL` on all rows where the applied policy predicate is false. (If `sec_relevant_cols_opt` isn't set to `DBMS_RLS.ALL_ROWS`, these rows aren't returned at all in the result set.) The default is `NULL`.
+
+ !!! Note
+     EDB Postgres Advanced Server doesn't support `DBMS_RLS.ALL_ROWS`. EDB Postgres Advanced Server throws an error if `sec_relevant_cols_opt` is set to `DBMS_RLS.ALL_ROWS` (`INTEGER` value of 1).
+
+### Examples
+
+This example uses the following policy function:
+
+```sql
+CREATE OR REPLACE FUNCTION verify_session_user (
+    p_schema        VARCHAR2,
+    p_object        VARCHAR2
+)
+RETURN VARCHAR2
+IS
+BEGIN
+    RETURN 'authid = SYS_CONTEXT(''USERENV'', ''SESSION_USER'')';
+END;
+```
+
+This function generates the predicate `authid = SYS_CONTEXT('USERENV', 'SESSION_USER')`, which is added to the `WHERE` clause of any SQL command of the type specified in the `ADD_POLICY` procedure.
+
+This limits the effect of the SQL command to those rows where the content of the `authid` column is the same as the session user.
+
+!!! Note
+    This example uses the `SYS_CONTEXT` function to return the login user name. In Oracle the `SYS_CONTEXT` function is used to return attributes of an *application context*. The first parameter of the `SYS_CONTEXT` function is the name of an application context. The second parameter is the name of an attribute set in the application context. `USERENV` is a special built-in namespace that describes the current session. EDB Postgres Advanced Server doesn't support application contexts. It supports only this specific usage of the `SYS_CONTEXT` function.
+
+The following anonymous block calls the `ADD_POLICY` procedure to create a policy named `secure_update`. The policy applies to the `vpemp` table using the function `verify_session_user` whenever an `INSERT`, `UPDATE`, or `DELETE` SQL command is given referencing the `vpemp` table.
+
+```sql
+DECLARE
+    v_object_schema         VARCHAR2(30) := 'public';
+    v_object_name           VARCHAR2(30) := 'vpemp';
+    v_policy_name           VARCHAR2(30) := 'secure_update';
+    v_function_schema       VARCHAR2(30) := 'enterprisedb';
+    v_policy_function       VARCHAR2(30) := 'verify_session_user';
+    v_statement_types       VARCHAR2(30) := 'INSERT,UPDATE,DELETE';
+    v_update_check          BOOLEAN      := TRUE;
+    v_enable                BOOLEAN      := TRUE;
+BEGIN
+    DBMS_RLS.ADD_POLICY(
+        v_object_schema,
+        v_object_name,
+        v_policy_name,
+        v_function_schema,
+        v_policy_function,
+        v_statement_types,
+        v_update_check,
+        v_enable
+    );
+END;
+```
+
+After successfully creating the policy, a terminal session is started by user `salesmgr`. The following query shows the content of the `vpemp` table:
+
+```sql
+edb=# \c edb salesmgr
+Password for user salesmgr:
+You are now connected to database "edb" as user "salesmgr".
+edb=> SELECT * FROM vpemp;
+__OUTPUT__
+ empno | ename  |    job    |   sal   |  comm   | deptno |   authid
+-------+--------+-----------+---------+---------+--------+-------------
+  7782 | CLARK  | MANAGER   | 2450.00 |         |     10 |
+  7839 | KING   | PRESIDENT | 5000.00 |         |     10 |
+  7934 | MILLER | CLERK     | 1300.00 |         |     10 |
+  7369 | SMITH  | CLERK     |  800.00 |         |     20 | researchmgr
+  7566 | JONES  | MANAGER   | 2975.00 |         |     20 | researchmgr
+  7788 | SCOTT  | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7876 | ADAMS  | CLERK     | 1100.00 |         |     20 | researchmgr
+  7902 | FORD   | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7499 | ALLEN  | SALESMAN  | 1600.00 |  300.00 |     30 | salesmgr
+  7521 | WARD   | SALESMAN  | 1250.00 |  500.00 |     30 | salesmgr
+  7654 | MARTIN | SALESMAN  | 1250.00 | 1400.00 |     30 | salesmgr
+  7698 | BLAKE  | MANAGER   | 2850.00 |         |     30 | salesmgr
+  7844 | TURNER | SALESMAN  | 1500.00 |    0.00 |     30 | salesmgr
+  7900 | JAMES  | CLERK     |  950.00 |         |     30 | salesmgr
+(14 rows)
+```
+
+An unqualified `UPDATE` command (no `WHERE` clause) is issued by the `salesmgr` user:
+
+```sql
+edb=> UPDATE vpemp SET comm = sal * .75;
+UPDATE 6
+```
+
+Instead of updating all rows in the table, the policy restricts the effect of the update to only those rows where the `authid` column contains the value `salesmgr` as specified by the policy function predicate `authid = SYS_CONTEXT('USERENV', 'SESSION_USER')`.
+
+The following query shows that the `comm` column was changed only for those rows where `authid` contains `salesmgr`. All other rows are unchanged.
+
+```sql
+edb=> SELECT * FROM vpemp;
+__OUTPUT__
+ empno | ename  |    job    |   sal   |  comm   | deptno |   authid
+-------+--------+-----------+---------+---------+--------+-------------
+  7782 | CLARK  | MANAGER   | 2450.00 |         |     10 |
+  7839 | KING   | PRESIDENT | 5000.00 |         |     10 |
+  7934 | MILLER | CLERK     | 1300.00 |         |     10 |
+  7369 | SMITH  | CLERK     |  800.00 |         |     20 | researchmgr
+  7566 | JONES  | MANAGER   | 2975.00 |         |     20 | researchmgr
+  7788 | SCOTT  | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7876 | ADAMS  | CLERK     | 1100.00 |         |     20 | researchmgr
+  7902 | FORD   | ANALYST   | 3000.00 |         |     20 | researchmgr
+  7499 | ALLEN  | SALESMAN  | 1600.00 | 1200.00 |     30 | salesmgr
+  7521 | WARD   | SALESMAN  | 1250.00 |  937.50 |     30 | salesmgr
+  7654 | MARTIN | SALESMAN  | 1250.00 |  937.50 |     30 | salesmgr
+  7698 | BLAKE  | MANAGER   | 2850.00 | 2137.50 |     30 | salesmgr
+  7844 | TURNER | SALESMAN  | 1500.00 | 1125.00 |     30 | salesmgr
+  7900 | JAMES  | CLERK     |  950.00 |  712.50 |     30 | salesmgr
+(14 rows)
+```
+
+Furthermore, since the `update_check` parameter was set to `TRUE` in the `ADD_POLICY` procedure, the following `INSERT` command throws an exception. The value given for the `authid` column, `researchmgr`, doesn't match the session user (`salesmgr`) and hence fails the policy.
+
+```sql
+edb=> INSERT INTO vpemp VALUES (9001,'SMITH','ANALYST',3200.00,NULL,20,
+'researchmgr');
+ERROR:  policy with check option violation
+DETAIL:  Policy predicate was evaluated to FALSE with the updated values
+```
+
+If `update_check` is set to `FALSE`, the preceding `INSERT` command succeeds.
+
+This example uses the `sec_relevant_cols` parameter to apply a policy only when certain columns are referenced in the SQL command. The following policy function is used for this example, which selects rows where the employee salary is less than `2000`.
+
+```sql
+CREATE OR REPLACE FUNCTION sal_lt_2000 (
+    p_schema        VARCHAR2,
+    p_object        VARCHAR2
+)
+RETURN VARCHAR2
+IS
+BEGIN
+    RETURN 'sal < 2000';
+END
+```
+
+The policy is created so that it's enforced only if a `SELECT` command includes columns `sal` or `comm`:
+
+```sql
+DECLARE
+    v_object_schema         VARCHAR2(30) := 'public';
+    v_object_name           VARCHAR2(30) := 'vpemp';
+    v_policy_name           VARCHAR2(30) := 'secure_salary';
+    v_function_schema       VARCHAR2(30) := 'enterprisedb';
+    v_policy_function       VARCHAR2(30) := 'sal_lt_2000';
+    v_statement_types       VARCHAR2(30) := 'SELECT';
+    v_sec_relevant_cols     VARCHAR2(30) := 'sal,comm';
+BEGIN
+    DBMS_RLS.ADD_POLICY(
+        v_object_schema,
+        v_object_name,
+        v_policy_name,
+        v_function_schema,
+        v_policy_function,
+        v_statement_types,
+        sec_relevant_cols => v_sec_relevant_cols
+    );
+END;
+```
+
+If a query doesn't reference columns `sal` or `comm`, then the policy isn't applied. The following query returns all 14 rows of table `vpemp`:
+
+```sql
+edb=# SELECT empno, ename, job, deptno, authid FROM vpemp;
+__OUTPUT__
+ empno | ename  |    job    | deptno |   authid
+-------+--------+-----------+--------+-------------
+  7782 | CLARK  | MANAGER   |     10 |
+  7839 | KING   | PRESIDENT |     10 |
+  7934 | MILLER | CLERK     |     10 |
+  7369 | SMITH  | CLERK     |     20 | researchmgr
+  7566 | JONES  | MANAGER   |     20 | researchmgr
+  7788 | SCOTT  | ANALYST   |     20 | researchmgr
+  7876 | ADAMS  | CLERK     |     20 | researchmgr
+  7902 | FORD   | ANALYST   |     20 | researchmgr
+  7499 | ALLEN  | SALESMAN  |     30 | salesmgr
+  7521 | WARD   | SALESMAN  |     30 | salesmgr
+  7654 | MARTIN | SALESMAN  |     30 | salesmgr
+  7698 | BLAKE  | MANAGER   |     30 | salesmgr
+  7844 | TURNER | SALESMAN  |     30 | salesmgr
+  7900 | JAMES  | CLERK     |     30 | salesmgr
+(14 rows)
+```
+
+If the query references the `sal` or `comm` columns, then the policy is applied to the query, eliminating any rows where `sal` is greater than or equal to `2000`:
+
+```sql
+edb=# SELECT empno, ename, job, sal, comm, deptno, authid FROM vpemp;
+__OUTPUT__
+ empno | ename  |   job    |   sal   |  comm   | deptno |   authid
+-------+--------+----------+---------+---------+--------+-------------
+  7934 | MILLER | CLERK    | 1300.00 |         |     10 |
+  7369 | SMITH  | CLERK    |  800.00 |         |     20 | researchmgr
+  7876 | ADAMS  | CLERK    | 1100.00 |         |     20 | researchmgr
+  7499 | ALLEN  | SALESMAN | 1600.00 | 1200.00 |     30 | salesmgr
+  7521 | WARD   | SALESMAN | 1250.00 |  937.50 |     30 | salesmgr
+  7654 | MARTIN | SALESMAN | 1250.00 |  937.50 |     30 | salesmgr
+  7844 | TURNER | SALESMAN | 1500.00 | 1125.00 |     30 | salesmgr
+  7900 | JAMES  | CLERK    |  950.00 |  712.50 |     30 | salesmgr
+(8 rows)
+```
+
+## DROP_POLICY
+
+The `DROP_POLICY` procedure deletes an existing policy. The `DROP_POLICY` procedure doesn't delete the policy function and database object associated with the policy.
+
+You must be a superuser to execute this procedure.
+
+```sql
+DROP_POLICY(<object_schema> VARCHAR2, <object_name> VARCHAR2,
+  <policy_name> VARCHAR2)
+```
+
+### Parameters
+
+`object_schema`
+
+ Name of the schema containing the database object to which the policy applies.
+
+`object_name`
+
+ Name of the database object to which the policy applies.
+
+`policy_name`
+
+ Name of the policy to delete.
+
+### Examples
+
+This example deletes policy `secure_update` on table `public.vpemp`:
+
+```sql
+DECLARE
+    v_object_schema         VARCHAR2(30) := 'public';
+    v_object_name           VARCHAR2(30) := 'vpemp';
+    v_policy_name           VARCHAR2(30) := 'secure_update';
+BEGIN
+    DBMS_RLS.DROP_POLICY(
+        v_object_schema,
+        v_object_name,
+        v_policy_name
+    );
+END;
+```
+
+## ENABLE_POLICY
+
+The `ENABLE_POLICY` procedure enables or disables an existing policy on the specified database object.
+
+You must be a superuser to execute this procedure.
+
+```sql
+ENABLE_POLICY(<object_schema> VARCHAR2, <object_name> VARCHAR2,
+  <policy_name> VARCHAR2, <enable> BOOLEAN)
+```
+
+### Parameters
+
+`object_schema`
+
+ Name of the schema containing the database object to which the policy applies.
+
+`object_name`
+
+ Name of the database object to which the policy applies.
+
+`policy_name`
+
+ Name of the policy to enable or disable.
+
+`enable`
+
+ When set to `TRUE`, the policy is enabled. When set to `FALSE`, the policy is disabled.
+
+### Examples
+
+This example disables policy `secure_update` on table `public.vpemp`:
+
+```sql
+DECLARE
+    v_object_schema         VARCHAR2(30) := 'public';
+    v_object_name           VARCHAR2(30) := 'vpemp';
+    v_policy_name           VARCHAR2(30) := 'secure_update';
+    v_enable                BOOLEAN := FALSE;
+BEGIN
+    DBMS_RLS.ENABLE_POLICY(
+        v_object_schema,
+        v_object_name,
+        v_policy_name,
+        v_enable
+    );
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/01_using_calendar_syntax_to_specify_a_repeating_interval.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/01_using_calendar_syntax_to_specify_a_repeating_interval.mdx
new file mode 100644
index 00000000000..d58c98840c1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/01_using_calendar_syntax_to_specify_a_repeating_interval.mdx
@@ -0,0 +1,34 @@
+---
+title: "Using calendar syntax to specify a repeating interval"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/01_using_calendar_syntax_to_specify_a_repeating_interval/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CREATE_JOB` and `CREATE_SCHEDULE` procedures use Oracle-style calendar syntax to define the interval with which a job or schedule is repeated. Provide the scheduling information in the `repeat_interval` parameter of each procedure.
+
+`repeat_interval` is a value or series of values that define the interval between the executions of the scheduled job. Each value is composed of a token, an equals sign, and the units on which the schedule executes. Separate multiple token values with a semi-colon (;).
+
+For example, the following value defines a schedule that's executed each weeknight at 5:45:
+
+ `FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=17;BYMINUTE=45`
+
+EDB Postgres Advanced Server supports the token types and syntax described in the table.
+
+| Token type   | Syntax                       | Valid values                                                                                                                                                                                                   |
+| ------------ | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `FREQ`       | `FREQ=predefined_interval`   | Where `predefined_interval` is one of the following: `YEARLY`, `MONTHLY`, `WEEKLY`, `DAILY`, `HOURLY`, `MINUTELY`. The `SECONDLY` keyword isn't supported.                                                              |
+| `BYMONTH`    | `BYMONTH=month(, month)...`  | Where `month` is the three-letter abbreviation of the month name: `JAN`, `FEB`, `MAR`, `APR`, `MAY`, `JUN`, `JUL`, `AUG`, `SEP`, `OCT`, `NOV`, `DEC`                                                           |
+| `BYMONTH`    | `BYMONTH=month (, month)...` | Where `month` is the numeric value representing the month: `1` \| `2` \| `3` \| `4` \| `5` \| `6` \| `7` \| `8` \| `9` \| `10` \| `11` \| `12`                                                                                       |
+| `BYMONTHDAY` | `BYMONTHDAY=day_of_month`    | Where `day_of_month` is a value from `1` through `31`                                                                                                                                                          |
+| `BYDAY`      | `BYDAY=weekday`              | Where `weekday` is a three-letter abbreviation or single-digit value representing the day of the week.                                                                                                         |
+|              |                              | `Monday` \| `MON` \| `1` \|                                                                                                                                                                                    |
+|              |                              | `Tuesday` \| `TUE` \| `2` \|                                                                                                                                                                                   |
+|              |                              | `Wednesday` \| `WED` \| `3` \|                                                                                                                                                                                 |
+|              |                              | `Thursday` \| `THU` \| `4` \|                                                                                                                                                                                  |
+|              |                              | `Friday` \| `FRI` \| `5` \|                                                                                                                                                                                    |
+|              |                              | `Saturday` \| `SAT` \| `6` \|                                                                                                                                                                                  |
+|              |                              | `Sunday` \| `SUN` \| `7` \|                                                                                                                                                                                    |
+| `BYDATE`     | `BYDATE=date(, date)...`     | Where date is `YYYYMMDD`.<br /><br />`YYYY` is a four-digit year representation of the year,<br />`MM` is a two-digit representation of the month,<br />and `DD` is a two-digit day representation of the day. |
+| `BYDATE`     | `BYDATE=date(, date)...`     | Where date is `MMDD`.<br /><br />`MM` is a two-digit representation of the month,<br />and `DD` is a two-digit day representation of the day                                                                   |
+| `BYHOUR`     | `BYHOUR=hour`                | Where `hour` is a value from `0` through `23`.                                                                                                                                                                 |
+| `BYMINUTE`   | `BYMINUTE=minute`            | Where `minute` is a value from `0` through `59`.                                                                                                                                                               |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/02_create_job.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/02_create_job.mdx
new file mode 100644
index 00000000000..3dd0d7423ff
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/02_create_job.mdx
@@ -0,0 +1,113 @@
+---
+title: "CREATE_JOB"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/02_create_job/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `CREATE_JOB` procedure to create a job. The procedure comes in two forms. The first form of the procedure specifies a schedule in the job definition as well as a job action to invoke when the job executes:
+
+```sql
+CREATE_JOB(
+  <job_name> IN VARCHAR2,
+  <job_type> IN VARCHAR2,
+  <job_action> IN VARCHAR2,
+  <number_of_arguments> IN PLS_INTEGER DEFAULT 0,
+  <start_date> IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
+  <repeat_interval> IN VARCHAR2 DEFAULT NULL,
+  <end_date> IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
+  <job_class> IN VARCHAR2 DEFAULT 'DEFAULT_JOB_CLASS',
+  <enabled> IN BOOLEAN DEFAULT FALSE,
+  <auto_drop> IN BOOLEAN DEFAULT TRUE,
+  <comments> IN VARCHAR2 DEFAULT NULL)
+```
+
+The second form uses a job schedule to specify the schedule on which the job executes and specifies the name of a program to execute when the job runs:
+
+```sql
+CREATE_JOB(
+  <job_name> IN VARCHAR2,
+  <program_name> IN VARCHAR2,
+  <schedule_name> IN VARCHAR2,
+  <job_class> IN VARCHAR2 DEFAULT 'DEFAULT_JOB_CLASS',
+  <enabled> IN BOOLEAN DEFAULT FALSE,
+  <auto_drop> IN BOOLEAN DEFAULT TRUE,
+  <comments> IN VARCHAR2 DEFAULT NULL)
+```
+
+## Parameters
+
+`job_name`
+
+ `job_name` specifies the optionally schema-qualified name of the job being created.
+
+`job_type`
+
+ `job_type` specifies the type of job. The current implementation of `CREATE_JOB` supports a job type of `PLSQL_BLOCK` or `STORED_PROCEDURE`.
+
+`job_action`
+
+-   If `job_type` is `PLSQL_BLOCK`, `job_action` specifies the content of the PL/SQL block to invoke when the job executes. The block must be terminated with a semi-colon (;).
+
+-   If `job_type` is `STORED_PROCEDURE`, `job_action` specifies the optionally schema-qualified name of the procedure.
+
+`number_of_arguments`
+
+ `number_of_arguments` is an integer value that specifies the number of arguments expected by the job. The default is `0`.
+
+`start_date`
+
+ `start_date` is a `TIMESTAMP WITH TIME ZONE` value that specifies the first time that the job is scheduled to execute. The default value is `NULL`, indicating to schedule the job to execute when the job is enabled.
+
+`repeat_interval`
+
+ `repeat_interval` is a `VARCHAR2` value that specifies how often the job repeats. If you don't specify a `repeat_interval`, the job executes only once. The default value is `NULL`.
+
+`end_date`
+
+ `end_date` is a `TIMESTAMP WITH TIME ZONE` value that specifies a time after which the job no longer executes. If you specify a date, the `end_date` must be after `start_date`. The default value is `NULL`.
+
+ If you don't specify an `end_date` and you do specify a `repeat_interval`, the job repeats indefinitely until you disable it.
+
+`program_name`
+
+ `program_name` is the name of a program for the job to execute.
+
+`schedule_name`
+
+ `schedule_name` is the name of the schedule associated with the job.
+
+`job_class`
+
+ `job_class` is accepted for compatibility and ignored.
+
+`enabled`
+
+ `enabled` is a Boolean value that specifies if the job is enabled when created. By default, a job is created in a disabled state, with `enabled` set to `FALSE`. To enable a job, specify a value of `TRUE` when creating the job, or enable the job with the `DBMS_SCHEDULER.ENABLE` procedure.
+
+`auto_drop`
+
+ The `auto_drop` parameter is accepted for compatibility and is ignored. By default, a job's status is changed to `DISABLED` after the time specified in `end_date`.
+
+`comments`
+
+ Use the `comments` parameter to specify a comment about the job.
+
+## Example
+
+This example shows a call to the `CREATE_JOB` procedure:
+
+```sql
+EXEC
+  DBMS_SCHEDULER.CREATE_JOB (
+    job_name        => 'update_log',
+    job_type        => 'PLSQL_BLOCK',
+    job_action      => 'BEGIN INSERT INTO my_log VALUES(current_timestamp);
+                        END;',
+    start_date      => '01-JUN-15 09:00:00.000000',
+    repeat_interval => 'FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=17;',
+    end_date        => NULL,
+    enabled         => TRUE,
+    comments        => 'This job adds a row to the my_log table.');
+```
+
+The code fragment creates a job named `update_log` that executes each weeknight at 5:00. The job executes a PL/SQL block that inserts the current timestamp into a logfile (`my_log`). Since no `end_date` is specified, the job executes until disabled by the `DBMS_SCHEDULER.DISABLE` procedure.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/03_create_program.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/03_create_program.mdx
new file mode 100644
index 00000000000..6680ad735e2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/03_create_program.mdx
@@ -0,0 +1,69 @@
+---
+title: "CREATE_PROGRAM"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/03_create_program/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `CREATE_PROGRAM` procedure to create a `DBMS_SCHEDULER` program. The signature is:
+
+```sql
+CREATE_PROGRAM(
+  <program_name> IN VARCHAR2,
+  <program_type> IN VARCHAR2,
+  <program_action> IN VARCHAR2,
+  <number_of_arguments> IN PLS_INTEGER DEFAULT 0,
+  <enabled> IN BOOLEAN DEFAULT FALSE,
+  <comments> IN VARCHAR2 DEFAULT NULL)
+```
+
+## Parameters
+
+`program_name`
+
+ `program_name` specifies the name of the program that's being created.
+
+`program_type`
+
+ `program_type` specifies the type of program. The current implementation of `CREATE_PROGRAM` supports a `program_type` of `PLSQL_BLOCK` or `PROCEDURE`.
+
+`program_action`
+
+-   If `program_type` is `PLSQL_BLOCK, program_action` contains the PL/SQL block that executes when the program is invoked. The PL/SQL block must be terminated with a semi-colon (;).
+
+-   If `program_type` is `PROCEDURE`, `program_action` contains the name of the stored procedure.
+
+`number_of_arguments`
+
+-   If `program_type` is `PLSQL_BLOCK`, this argument is ignored.
+
+-   If `program_type` is `PROCEDURE`, `number_of_arguments` specifies the number of arguments required by the procedure. The default value is `0`.
+
+`enabled`
+
+ `enabled` specifies if the program is created enabled or disabled:
+
+-   If `enabled` is `TRUE`, the program is created enabled.
+-   If `enabled` is `FALSE`, the program is created disabled. Use the `DBMS_SCHEDULER.ENABLE` program to enable a disabled program.
+
+    The default value is `FALSE`.
+
+`comments`
+
+ Use the `comments` parameter to specify a comment about the program. By default, this parameter is `NULL`.
+
+## Example
+
+The following call to the `CREATE_PROGRAM` procedure creates a program named `update_log`:
+
+```sql
+EXEC
+  DBMS_SCHEDULER.CREATE_PROGRAM (
+    program_name     => 'update_log',
+    program_type     => 'PLSQL_BLOCK',
+    program_action   => 'BEGIN INSERT INTO my_log VALUES(current_timestamp);
+                         END;',
+    enabled          => TRUE,
+    comments         => 'This program adds a row to the my_log table.');
+```
+
+`update_log` is a PL/SQL block that adds a row containing the current date and time to the `my_log` table. The program is enabled when the `CREATE_PROGRAM` procedure executes.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/04_create_schedule.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/04_create_schedule.mdx
new file mode 100644
index 00000000000..9cf4a6116ce
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/04_create_schedule.mdx
@@ -0,0 +1,59 @@
+---
+title: "CREATE_SCHEDULE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/04_create_schedule/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `CREATE_SCHEDULE` procedure to create a job schedule. The signature of the `CREATE_SCHEDULE` procedure is:
+
+```sql
+CREATE_SCHEDULE(
+  <schedule_name> IN VARCHAR2,
+  <start_date> IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
+  <repeat_interval> IN VARCHAR2,
+  <end_date> IN TIMESTAMP WITH TIME ZONE DEFAULT NULL,
+  <comments> IN VARCHAR2 DEFAULT NULL)
+```
+
+## Parameters
+
+`schedule_name`
+
+ `schedule_name` specifies the name of the schedule.
+
+`start_date`
+
+ `start_date` is a `TIMESTAMP WITH TIME ZONE` value that specifies the date and time that the schedule is eligible to execute. If you don't specify a `start_date`, the date that the job is enabled is used as the `start_date`. By default, `start_date` is `NULL`.
+
+`repeat_interval`
+
+ `repeat_interval` is a `VARCHAR2` value that specifies how often the job repeats. If you don't specify a `repeat_interval`, the job executes only once, on the date specified by `start_date`.
+
+ !!! Note 
+    You must provide a value for either `start_date` or `repeat_interval`. If both `start_date` and `repeat_interval` are `NULL`, the server returns an error.
+
+`end_date`
+
+ `end_date` is a `TIMESTAMP WITH TIME ZONE` value that specifies a time after which the schedule no longer executes. If you specify a date, the `end_date` must be after the `start_date`. The default value is `NULL`.
+
+ !!! Note
+     If you specify a `repeat_interval` and don't specify an `end_date`, the schedule repeats indefinitely until you disable it.
+
+`comments`
+
+ Use the `comments` parameter to specify a comment about the schedule. By default, this parameter is `NULL`.
+
+## Example
+
+This code fragment calls `CREATE_SCHEDULE` to create a schedule named `weeknights_at_5`:
+
+```sql
+EXEC
+  DBMS_SCHEDULER.CREATE_SCHEDULE (
+    schedule_name    => 'weeknights_at_5',
+    start_date       => '01-JUN-13 09:00:00.000000',
+    repeat_interval  => 'FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=17;',
+    comments         => 'This schedule executes each weeknight at 5:00');
+```
+
+The schedule executes each weeknight, at 5:00, effective after June 1, 2013. Since no `end_date` is specified, the schedule executes indefinitely until disabled with `DBMS_SCHEDULER.DISABLE`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/05_define_program_argument.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/05_define_program_argument.mdx
new file mode 100644
index 00000000000..c40b233be5e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/05_define_program_argument.mdx
@@ -0,0 +1,76 @@
+---
+title: "DEFINE_PROGRAM_ARGUMENT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/05_define_program_argument/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DEFINE_PROGRAM_ARGUMENT` procedure to define a program argument. The `DEFINE_PROGRAM_ARGUMENT` procedure comes in two forms. The first form defines an argument with a default value:
+
+```sql
+DEFINE_PROGRAM_ARGUMENT(
+  <program_name> IN VARCHAR2,
+  <argument_position> IN PLS_INTEGER,
+  <argument_name> IN VARCHAR2 DEFAULT NULL,
+  <argument_type> IN VARCHAR2,
+  <default_value> IN VARCHAR2,
+  <out_argument> IN BOOLEAN DEFAULT FALSE)
+```
+
+The second form defines an argument without a default value:
+
+```sql
+DEFINE_PROGRAM_ARGUMENT(
+  <program_name> IN VARCHAR2,
+  <argument_position> IN PLS_INTEGER,
+  <argument_name> IN VARCHAR2 DEFAULT NULL,
+  <argument_type> IN VARCHAR2,
+  <out_argument> IN BOOLEAN DEFAULT FALSE)
+```
+
+## Parameters
+
+`program_name`
+
+ `program_name` is the name of the program to which the arguments belong.
+
+`argument_position`
+
+ `argument_position` specifies the position of the argument as it's passed to the program.
+
+`argument_name`
+
+ `argument_name` specifies the optional name of the argument. By default, `argument_name` is `NULL`.
+
+`argument_type IN VARCHAR2`
+
+ `argument_type` specifies the data type of the argument.
+
+`default_value`
+
+ `default_value` specifies the default value assigned to the argument. `default_value` is overridden by a value specified by the job when the job executes.
+
+`out_argument IN BOOLEAN DEFAULT FALSE`
+
+ `out_argument` isn't currently used. If specified, the value must be `FALSE`.
+
+## Example
+
+This code fragment uses the `DEFINE_PROGRAM_ARGUMENT` procedure to define the first and second arguments in a program named `add_emp`:
+
+```sql
+EXEC
+  DBMS_SCHEDULER.DEFINE_PROGRAM_ARGUMENT(
+    program_name         => 'add_emp',
+    argument_position    => 1,
+    argument_name        => 'dept_no',
+    argument_type        => 'INTEGER,
+    default_value        => '20');
+EXEC
+  DBMS_SCHEDULER.DEFINE_PROGRAM_ARGUMENT(
+    program_name         => 'add_emp',
+    argument_position    => 2,
+    argument_name        => 'emp_name',
+    argument_type        => 'VARCHAR2');
+```
+
+The first argument is an `INTEGER` value named `dept_no` that has a default value of `20`. The second argument is a `VARCHAR2` value named `emp_name` and doesn't have a default value.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/06_dbms_scheduler_disable.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/06_dbms_scheduler_disable.mdx
new file mode 100644
index 00000000000..0a602498b6a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/06_dbms_scheduler_disable.mdx
@@ -0,0 +1,40 @@
+---
+title: "DISABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/06_dbms_scheduler_disable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dbms_scheduler_disable" class="registered_link"></div>
+
+Use the `DISABLE` procedure to disable a program or a job. The signature of the `DISABLE` procedure is:
+
+```sql
+DISABLE(
+  <name> IN VARCHAR2,
+  <force> IN BOOLEAN DEFAULT FALSE,
+  <commit_semantics> IN VARCHAR2 DEFAULT 'STOP_ON_FIRST_ERROR')
+```
+
+## Parameters
+
+`name`
+
+ `name` specifies the name of the program or job that's being disabled.
+
+`force`
+
+ `force` is accepted for compatibility and ignored.
+
+`commit_semantics`
+
+ `commit_semantics` tells the server how to handle an error encountered while disabling a program or job. By default, `commit_semantics` is set to `STOP_ON_FIRST_ERROR`, which means to stop when an error is encountered. Any programs or jobs that were successfully disabled before the error are committed to disk.
+
+ The `TRANSACTIONAL` and `ABSORB_ERRORS` keywords are accepted for compatibility and ignored.
+
+## Example
+
+The following call to the `DISABLE` procedure disables a program named `update_emp`:
+
+```sql
+DBMS_SCHEDULER.DISABLE('update_emp');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/07_drop_job.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/07_drop_job.mdx
new file mode 100644
index 00000000000..1f2b397cb44
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/07_drop_job.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP_JOB"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/07_drop_job/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DROP_JOB` procedure to drop a job, drop any arguments that belong to the job, and eliminate any future job executions. The signature of the procedure is:
+
+```sql
+DROP_JOB(
+  <job_name> IN VARCHAR2,
+  <force> IN BOOLEAN DEFAULT FALSE,
+  <defer> IN BOOLEAN DEFAULT FALSE,
+  <commit_semantics> IN VARCHAR2 DEFAULT 'STOP_ON_FIRST_ERROR')
+```
+
+## Parameters
+
+`job_name`
+
+ `job_name` specifies the name of the job that's being dropped.
+
+`force`
+
+ `force` is accepted for compatibility and ignored.
+
+`defer`
+
+ `defer` is accepted for compatibility and ignored.
+
+`commit_semantics`
+
+ `commit_semantics` tells the server how to handle an error encountered while dropping a program or job. By default, `commit_semantics` is set to `STOP_ON_FIRST_ERROR`, which means to stop when an error is encountered.
+
+ The `TRANSACTIONAL` and `ABSORB_ERRORS` keywords are accepted for compatibility and ignored.
+
+## Example
+
+The following call to `DROP_JOB` drops a job named `update_log`:
+
+```sql
+DBMS_SCHEDULER.DROP_JOB('update_log');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/08_drop_program.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/08_drop_program.mdx
new file mode 100644
index 00000000000..67cf326ab4f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/08_drop_program.mdx
@@ -0,0 +1,37 @@
+---
+title: "DROP_PROGRAM"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/08_drop_program/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DROP_PROGRAM` procedure drops a program. The signature of the `DROP_PROGRAM` procedure is:
+
+```sql
+DROP_PROGRAM(
+  <program_name> IN VARCHAR2,
+  <force> IN BOOLEAN DEFAULT FALSE)
+```
+
+## Parameters
+
+`program_name`
+
+ `program_name` specifies the name of the program that's being dropped.
+
+`force`
+
+ `force` is a Boolean value that tells the server how to handle programs with dependent jobs.
+
+-   Specify `FALSE` to return an error if the program is referenced by a job.
+
+-   Specify `TRUE` to disable any jobs that reference the program before dropping the program.
+
+  The default value is `FALSE`.
+
+## Example
+
+The following call to `DROP_PROGRAM` drops a job named `update_emp`:
+
+```sql
+DBMS_SCHEDULER.DROP_PROGRAM('update_emp');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/09_drop_program_argument.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/09_drop_program_argument.mdx
new file mode 100644
index 00000000000..c74c0e8002a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/09_drop_program_argument.mdx
@@ -0,0 +1,49 @@
+---
+title: "DROP_PROGRAM_ARGUMENT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/09_drop_program_argument/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DROP_PROGRAM_ARGUMENT` procedure to drop a program argument. The `DROP_PROGRAM_ARGUMENT` procedure comes in two forms. The first form uses an argument position to specify the argument to drop:
+
+```sql
+DROP_PROGRAM_ARGUMENT(
+  <program_name> IN VARCHAR2,
+  <argument_position> IN PLS_INTEGER)
+```
+
+The second form takes the argument name:
+
+```sql
+DROP_PROGRAM_ARGUMENT(
+  <program_name> IN VARCHAR2,
+  <argument_name> IN VARCHAR2)
+```
+
+## Parameters
+
+`program_name`
+
+ `program_name` specifies the name of the program that's being modified.
+
+`argument_position`
+
+ `argument_position` specifies the position of the argument that's being dropped.
+
+`argument_name`
+
+ `argument_name` specifies the name of the argument that's being dropped.
+
+## Examples
+
+The following call to `DROP_PROGRAM_ARGUMENT` drops the first argument in the `update_emp` program:
+
+```sql
+DBMS_SCHEDULER.DROP_PROGRAM_ARGUMENT('update_emp', 1);
+```
+
+The following call to `DROP_PROGRAM_ARGUMENT` drops an argument named `emp_name`:
+
+```sql
+DBMS_SCHEDULER.DROP_PROGRAM_ARGUMENT(update_emp', 'emp_name');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/10_drop_schedule.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/10_drop_schedule.mdx
new file mode 100644
index 00000000000..386025e5ec2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/10_drop_schedule.mdx
@@ -0,0 +1,36 @@
+---
+title: "DROP_SCHEDULE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/10_drop_schedule/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `DROP_SCHEDULE` procedure to drop a schedule. The signature is:
+
+```sql
+DROP_SCHEDULE(
+  <schedule_name> IN VARCHAR2,
+  <force> IN BOOLEAN DEFAULT FALSE)
+```
+
+## Parameters
+
+`schedule_name`
+
+ `schedule_name` specifies the name of the schedule that's being dropped.
+
+`force`
+
+ `force` specifies the behavior of the server if the specified schedule is referenced by any job:
+
+  -   Specify `FALSE` to return an error if the specified schedule is referenced by a job. This is the default behavior.
+  -   Specify `TRUE` to disable to any jobs that use the specified schedule before dropping the schedule. Any running jobs are allowed to complete before the schedule is dropped.
+
+## Example
+
+The following call to `DROP_SCHEDULE` drops a schedule named `weeknights_at_5`:
+
+```sql
+DBMS_SCHEDULER.DROP_SCHEDULE('weeknights_at_5', TRUE);
+```
+
+The server disables any jobs that use the schedule before dropping the schedule.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/11_dbms_scheduler_enable.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/11_dbms_scheduler_enable.mdx
new file mode 100644
index 00000000000..6095f1be5f5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/11_dbms_scheduler_enable.mdx
@@ -0,0 +1,37 @@
+---
+title: "ENABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/11_dbms_scheduler_enable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dbms_scheduler_enable" class="registered_link"></div>
+
+Use the `ENABLE` procedure to enable a disabled program or job.
+
+The signature of the `ENABLE` procedure is:
+
+```sql
+ENABLE(
+  <name> IN VARCHAR2,
+  <commit_semantics> IN VARCHAR2 DEFAULT 'STOP_ON_FIRST_ERROR')
+```
+
+## Parameters
+
+`name`
+
+ `name` specifies the name of the program or job that's being enabled.
+
+`commit_semantics`
+
+ `commit_semantics` tells the server how to handle an error encountered while enabling a program or job. By default, `commit_semantics` is set to `STOP_ON_FIRST_ERROR`, tellin the server to stop when it encounters an error.
+
+ The `TRANSACTIONAL` and `ABSORB_ERRORS` keywords are accepted for compatibility and ignored.
+
+## Example
+
+The following call to `DBMS_SCHEDULER.ENABLE` enables the `update_emp` program:
+
+```sql
+DBMS_SCHEDULER.ENABLE('update_emp');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/12_evaluate_calendar_string.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/12_evaluate_calendar_string.mdx
new file mode 100644
index 00000000000..159d56e3048
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/12_evaluate_calendar_string.mdx
@@ -0,0 +1,61 @@
+---
+title: "EVALUATE_CALENDAR_STRING"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/12_evaluate_calendar_string/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `EVALUATE_CALENDAR_STRING` procedure to evaluate the `repeat_interval` value specified when creating a schedule with the `CREATE_SCHEDULE` procedure. The `EVALUATE_CALENDAR_STRING` procedure returns the date and time that a specified schedule executes without actually scheduling the job.
+
+The signature of the `EVALUATE_CALENDAR_STRING` procedure is:
+
+```sql
+EVALUATE_CALENDAR_STRING(
+  <calendar_string> IN VARCHAR2,
+  <start_date> IN TIMESTAMP WITH TIME ZONE,
+  <return_date_after> IN TIMESTAMP WITH TIME ZONE,
+  <next_run_date> OUT TIMESTAMP WITH TIME ZONE)
+```
+
+## Parameters
+
+`calendar_string`
+
+ `calendar_string` is the calendar string that describes a `repeat_interval` that's being evaluated.
+
+`start_date IN TIMESTAMP WITH TIME ZONE`
+
+ `start_date` is the date and time after which the `repeat_interval` becomes valid.
+
+`return_date_after`
+
+ Use the `return_date_after` parameter to specify the date and time for `EVALUATE_CALENDAR_STRING` to use as a starting date when evaluating the `repeat_interval`.
+
+ For example, if you specify a `return_date_after` value of `01-APR-13 09.00.00.000000`, `EVALUATE_CALENDAR_STRING` returns the date and time of the first iteration of the schedule after April 1st, 2013.
+
+`next_run_date OUT TIMESTAMP WITH TIME ZONE`
+
+ `next_run_date` is an `OUT` parameter that contains the first occurrence of the schedule after the date specified by the `return_date_after` parameter.
+
+## Example
+
+This example evaluates a calendar string and returns the first date and time that the schedule will execute after June 15, 2013:
+
+```sql
+DECLARE
+  result     TIMESTAMP;
+BEGIN
+
+  DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING
+  (
+    'FREQ=DAILY;BYDAY=MON,TUE,WED,THU,FRI;BYHOUR=17;',
+    '15-JUN-2013', NULL, result
+  );
+
+    DBMS_OUTPUT.PUT_LINE('next_run_date: ' || result);
+END;
+/
+
+next_run_date: 17-JUN-13 05.00.00.000000 PM
+```
+
+Because June 15, 2013 is a Saturday, the schedule will execute on Monday, June 17, 2013 at 5:00 pm.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/13_run_job.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/13_run_job.mdx
new file mode 100644
index 00000000000..3e5aa609d45
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/13_run_job.mdx
@@ -0,0 +1,33 @@
+---
+title: "RUN_JOB"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/13_run_job/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `RUN_JOB` procedure to execute a job immediately. The signature of the `RUN_JOB` procedure is:
+
+```sql
+RUN_JOB(
+  <job_name> IN VARCHAR2,
+  <use_current_session> IN BOOLEAN DEFAULT TRUE
+```
+
+## Parameters
+
+`job_name`
+
+ `job_name` specifies the name of the job to execute.
+
+`use_current_session`
+
+ By default, the job executes in the current session. If specified, `use_current_session` must be set to `TRUE`. If `use_current_session` is set to `FALSE`, EDB Postgres Advanced Server returns an error.
+
+## Example
+
+The following call to `RUN_JOB` executes a job named `update_log`:
+
+```sql
+DBMS_SCHEDULER.RUN_JOB('update_log', TRUE);
+```
+
+Passing a value of `TRUE` as the second argument instructs the server to invoke the job in the current session.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/14_set_job_argument_value.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/14_set_job_argument_value.mdx
new file mode 100644
index 00000000000..1710fb791c6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/14_set_job_argument_value.mdx
@@ -0,0 +1,57 @@
+---
+title: "SET_JOB_ARGUMENT_VALUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/14_set_job_argument_value/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `SET_JOB_ARGUMENT_VALUE` procedure to specify a value for an argument. The `SET_JOB_ARGUMENT_VALUE` procedure comes in two forms. The first form specifies the argument to modify by position:
+
+```sql
+SET_JOB_ARGUMENT_VALUE(
+  <job_name> IN VARCHAR2,
+  <argument_position> IN PLS_INTEGER,
+  <argument_value> IN VARCHAR2)
+```
+
+The second form uses an argument name to specify the argument to modify:
+
+```sql
+SET_JOB_ARGUMENT_VALUE(
+  <job_name> IN VARCHAR2,
+  <argument_name> IN VARCHAR2,
+  <argument_value> IN VARCHAR2)
+```
+
+Argument values set by the `SET_JOB_ARGUMENT_VALUE` procedure override any values set by default.
+
+## Parameters
+
+`job_name`
+
+ `job_name` specifies the name of the job to which the modified argument belongs.
+
+`argument_position`
+
+ Use `argument_position` to specify the argument position for which the value is set.
+
+`argument_name`
+
+ Use `argument_name` to specify the argument by name for which the value is set.
+
+`argument_value`
+
+ `argument_value` specifies the new value of the argument.
+
+## Examples
+
+This example assigns a value of `30` to the first argument in the `update_emp` job:
+
+```sql
+DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE('update_emp', 1, '30');
+```
+
+This example sets the `emp_name` argument to `SMITH`:
+
+```sql
+DBMS_SCHEDULER.SET_JOB_ARGUMENT_VALUE('update_emp', 'emp_name', 'SMITH');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/index.mdx
new file mode 100644
index 00000000000..8bd89b36acc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/index.mdx
@@ -0,0 +1,45 @@
+---
+title: "DBMS_SCHEDULER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.28.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.201.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.159.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/15_dbms_scheduler/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_SCHEDULER` package's jobs are scheduled and run in the background by the `edb_job_scheduler` extension. For more information, see [EDB Job Scheduler extension](/pg_extensions/edb_job_scheduler).
+
+The `DBMS_SCHEDULER` package provides a way to create and manage Oracle-style jobs, programs, and job schedules. 
+
+The `DBMS_SCHEDULER` package implements the following functions and procedures:
+
+| Function/procedure                                                                                                                                | Return type | Description                                                                                                                       |
+| ------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `CREATE_JOB(job_name, job_type, job_action, number_of_arguments, start_date, repeat_interval, end_date, job_class, enabled, auto_drop, comments)` | n/a         | Use the first form of the `CREATE_JOB` procedure to create a job, specifying program and schedule details by means of parameters. |
+| `CREATE_JOB(job_name, program_name, schedule_name, job_class, enabled, auto_drop, comments)`                                                      | n/a         | Use the second form of `CREATE_JOB` to create a job that uses a named program and named schedule.                                 |
+| `CREATE_PROGRAM(program_name, program_type, program_action, number_of_arguments, enabled, comments)`                                              | n/a         | Use `CREATE_PROGRAM` to create a program.                                                                                         |
+| `CREATE_SCHEDULE(schedule_name, start_date, repeat_interval, end_date, comments)`                                                                 | n/a         | Use the `CREATE_SCHEDULE` procedure to create a schedule.                                                                         |
+| `DEFINE_PROGRAM_ARGUMENT(program_name, argument_position, argument_name, argument_type, default_value, out_argument)`                             | n/a         | Use the first form of the `DEFINE_PROGRAM_ARGUMENT` procedure to define a program argument that has a default value.              |
+| `DEFINE_PROGRAM_ARGUMENT(program_name, argument_position, argument_name, argument_type, out_argument)`                                            | n/a         | Use the first form of the `DEFINE_PROGRAM_ARGUMENT` procedure to define a program argument that doesn't have a default value.    |
+| `DISABLE(name, force, commit_semantics)`                                                                                                          | n/a         | Use the `DISABLE` procedure to disable a job or program.                                                                          |
+| `DROP_JOB(job_name, force, defer, commit_semantics)`                                                                                              | n/a         | Use the `DROP_JOB` procedure to drop a job.                                                                                       |
+| `DROP_PROGRAM(program_name, force)`                                                                                                               | n/a         | Use the `DROP_PROGRAM` procedure to drop a program.                                                                               |
+| `DROP_PROGRAM_ARGUMENT(program_name, argument_position)`                                                                                          | n/a         | Use the first form of `DROP_PROGRAM_ARGUMENT` to drop a program argument by specifying the argument position.                     |
+| `DROP_PROGRAM_ARGUMENT(program_name, argument_name)`                                                                                              | n/a         | Use the second form of `DROP_PROGRAM_ARGUMENT` to drop a program argument by specifying the argument name.                        |
+| `DROP_SCHEDULE(schedule_name, force)`                                                                                                             | n/a         | Use the `DROP SCHEDULE` procedure to drop a schedule.                                                                             |
+| `ENABLE(name, commit_semantics)`                                                                                                                  | n/a         | Use the `ENABLE` command to enable a program or job.                                                                              |
+| `EVALUATE_CALENDAR_STRING(calendar_string, start_date, return_date_after, next_run_date)`                                                         | n/a         | Use `EVALUATE_CALENDAR_STRING` to review the execution date described by a user-defined calendar schedule.                        |
+| `RUN_JOB(job_name, use_current_session, manually)`                                                                                                | n/a         | Use the `RUN_JOB` procedure to execute a job immediately.                                                                         |
+| `SET_JOB_ARGUMENT_VALUE(job_name, argument_position, argument_value)`                                                                             | n/a         | Use the first form of `SET_JOB_ARGUMENT_VALUE` to set the value of a job argument described by the argument's position.           |
+| `SET_JOB_ARGUMENT_VALUE(job_name, argument_name, argument_value)`                                                                                 | n/a         | Use the second form of `SET_JOB_ARGUMENT_VALUE` to set the value of a job argument described by the argument's name.              |
+
+EDB Postgres Advanced Server's implementation of `DBMS_SCHEDULER` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+
+<div class="toctree" maxdepth="6">
+
+using_calendar_syntax_to_specify_a_repeating_interval create_job create_program create_schedule define_program_argument dbms_scheduler_disable drop_job drop_program drop_program_argument drop_schedule dbms_scheduler_enable evaluate_calendar_string run_job set_job_argument_value
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/16_dbms_session.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/16_dbms_session.mdx
new file mode 100644
index 00000000000..25a3282992d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/16_dbms_session.mdx
@@ -0,0 +1,44 @@
+---
+title: "DBMS_SESSION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.090.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.29.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.202.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.116.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.160.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/16_dbms_session/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server provides support for the following `DBMS_SESSION.SET_ROLE` procedure:
+
+| Function/procedure   | Return type | Description                                                                           |
+| -------------------- | ----------- | ------------------------------------------------------------------------------------- |
+| `SET_ROLE(role_cmd)` | n/a         | Executes a `SET ROLE` statement followed by the string value specified in `role_cmd`. |
+
+EDB Postgres Advanced Server's implementation of `DBMS_SESSION` is a partial implementation when compared to Oracle's version. Only `DBMS_SESSION.SET_ROLE` is supported.
+
+## SET_ROLE
+
+The `SET_ROLE` procedure sets the current session user to the role specified in `role_cmd`. After invoking the `SET_ROLE` procedure, the current session uses the permissions assigned to the specified role. The signature of the procedure is:
+
+```sql
+SET_ROLE(<role_cmd>)
+```
+
+The `SET_ROLE` procedure appends the value specified for `role_cmd` to the `SET ROLE` statement and then invokes the statement.
+
+### Parameters
+
+`role_cmd`
+
+ `role_cmd` specifies a role name in the form of a string value.
+
+### Example
+
+This call to the `SET_ROLE` procedure invokes the `SET ROLE` command to set the identity of the current session user to manager:
+
+```sql
+edb=# exec DBMS_SESSION.SET_ROLE('manager');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/001_bind_array.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/001_bind_array.mdx
new file mode 100644
index 00000000000..2e3326c61cf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/001_bind_array.mdx
@@ -0,0 +1,94 @@
+---
+title: "BIND_ARRAY"
+---
+
+The `BIND_ARRAY` procedure binds a value or set of values to a variable in a cursor, based on the name of the variable.
+
+```sql
+BIND_ARRAY (<c> IN NUMBER, <name> IN VARCHAR2, 
+  <table_variable> IN { FLOAT_TABLE | BLOB_TABLE | CLOB_TABLE | VARCHAR2_TABLE | NUMBER_TABLE | TIMESTAMP_TABLE |
+  INTEGER_TABLE | ROWID_TABLE | TEXT_TABLE } [,<index1> IN NUMBER, <index2> IN NUMBER]);
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor for the SQL command with the values to be bound.
+
+`name`
+
+ Name of the collection. The name must be less than or equal to 30 bytes.
+
+`table_variable`
+
+ A local variable that is declared to be one of the following datatypes:
+
+| Datatype   | Description     | 
+| ---------- | --------------- |
+| <bflt_tab> | FLOAT_TABLE     |
+| <bl_tab>   | BLOB_TABLE      |
+| <cl_tab>   | CLOB_TABLE      |
+| <c_tab>    | VARCHAR2_TABLE  |
+| <n_tab>    | NUMBER_TABLE    |
+| <tms_tab>  | TIMESTAMP_TABLE |
+| <int_tab>  | INTEGER_TABLE   |
+| <rid_tab>  | ROWID_TABLE     |
+| <txt_tab>  | TEXT_TABLE      |
+
+
+`index1`
+
+Index for the table element that marks the lower bound of the range if you are binding a range. This value must be less than or equal to the value of `index2`. All elements between `index1` and `index2` are used in the bind. This is an optional parameter that can be used with three parameters or five parameters but not four. 
+
+`index2`
+
+Index for the table element that marks the upper bound of the range. This is an optional parameter that can be used with three parameters or five parameters but not four. 
+
+
+## Notes
+
+If you don't specify indexes in the bind call, and two different binds in a statement specify tables that contain a different number of elements, then the number of elements actually used is the minimum number between all tables. This is also the case if you specify indexes. The minimum range is selected between the two indexes for all tables.
+
+Not all bind variables in a query must be array binds. Some can be regular binds, and the same value is used for each element of the collections in expression evaluations and so forth.
+
+## Example
+
+```sql
+CREATE TABLE tab_test (col_int INTEGER, col_charactervarying VARCHAR(40));
+
+-- BIND_ARRAY (used for multiple insert/update/delete in single command
+DECLARE
+   c            INTEGER;
+   dbms_return  INTEGER;
+   res          NUMBER;
+   fetch_ret    INTEGER;
+   varint       DBMS_SQL.INTEGER_TABLE;
+BEGIN
+   c := DBMS_SQL.OPEN_CURSOR;
+   DBMS_SQL.PARSE (c,'INSERT into tab_test(col_int, col_charactervarying) values ( :bvarint, :bvarname )',
+            DBMS_SQL.NATIVE);
+   varint(1) := 10;
+   varint(2) := 11;
+   varint(4) := 12;
+   DBMS_SQL.BIND_ARRAY (c, 'bvarint', varint);
+   DBMS_SQL.BIND_VARIABLE (c, 'bvarname', 'edb_user');
+   dbms_return := DBMS_SQL.EXECUTE(c);
+   DBMS_OUTPUT.PUT_LINE(' RETURN VALUE ...' || dbms_return );
+   COMMIT;
+   DBMS_SQL.CLOSE_CURSOR (c);
+END;
+/
+
+-- this inserts three rows using bind_array so verify them in the table.
+SELECT * FROM tab_test;
+ col_int | col_charactervarying 
+---------+----------------------
+      10 | edb_user
+      11 | edb_user
+      12 | edb_user
+-- For col_int we are passing bind_array with the size of 3 elements, and as col_charactervarying we are 
+-- passing bind_variable. So for all the insertions, we are using same bind_variable (edb_user).
+
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/01_bind_variable.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/01_bind_variable.mdx
new file mode 100644
index 00000000000..623fd3dd0b2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/01_bind_variable.mdx
@@ -0,0 +1,77 @@
+---
+title: "BIND_VARIABLE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/01_bind_variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `BIND_VARIABLE` procedure associates a value with an `IN` or `IN OUT` bind variable in a SQL command.
+
+```sql
+BIND_VARIABLE(<c> NUMBER, <name> VARCHAR2,
+  <value> { BLOB | CLOB | FLOAT | INTEGER | NUMBER | ROWID | TIMESTAMP | VARCHAR2 }
+  [, <out_value_size> NUMBER ])
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor for the SQL command with bind variables.
+
+`name`
+
+ Name of the bind variable in the SQL command.
+
+`value`
+
+ Value to be assigned.
+
+`out_value_size`
+
+ If `name` is an `IN OUT` variable, defines the maximum length of the output value. If not specified, the length of `value` is assumed.
+
+## Examples
+
+The following anonymous block uses bind variables to insert a row into the `emp` table.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_sql           VARCHAR2(150) := 'INSERT INTO emp VALUES ' ||
+                        '(:p_empno, :p_ename, :p_job, :p_mgr, ' ||
+                        ':p_hiredate, :p_sal, :p_comm, :p_deptno)';
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+    v_mgr           emp.mgr%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_comm          emp.comm%TYPE;
+    v_deptno        emp.deptno%TYPE;
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    v_empno    := 9001;
+    v_ename    := 'JONES';
+    v_job      := 'SALESMAN';
+    v_mgr      := 7369;
+    v_hiredate := TO_DATE('13-DEC-07','DD-MON-YY');
+    v_sal      := 8500.00;
+    v_comm     := 1500.00;
+    v_deptno   := 40;
+    DBMS_SQL.BIND_VARIABLE(curid,':p_empno',v_empno);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_ename',v_ename);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_job',v_job);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_mgr',v_mgr);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_hiredate',v_hiredate);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_sal',v_sal);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_comm',v_comm);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_deptno',v_deptno);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+Number of rows processed: 1
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/02_bind_variable_char.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/02_bind_variable_char.mdx
new file mode 100644
index 00000000000..8e407d8e739
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/02_bind_variable_char.mdx
@@ -0,0 +1,30 @@
+---
+title: "BIND_VARIABLE_CHAR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/02_bind_variable_char/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `BIND_VARIABLE_CHAR` procedure associates a `CHAR` value with an `IN` or `IN OUT` bind variable in a SQL command.
+
+```sql
+BIND_VARIABLE_CHAR(<c> NUMBER, <name> VARCHAR2, <value> CHAR
+  [, <out_value_size> NUMBER ])
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor for the SQL command with bind variables.
+
+`name`
+
+ Name of the bind variable in the SQL command.
+
+`value`
+
+ Value of type `CHAR` to be assigned.
+
+`out_value_size`
+
+ If `name` is an `IN OUT` variable, defines the maximum length of the output value. If not specified, the length of `value` is assumed.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/03_bind_variable_raw.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/03_bind_variable_raw.mdx
new file mode 100644
index 00000000000..cfaf3b8f567
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/03_bind_variable_raw.mdx
@@ -0,0 +1,30 @@
+---
+title: "BIND_VARIABLE_RAW"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/03_bind_variable_raw/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `BIND_VARIABLE_RAW` procedure associates a `RAW` value with an `IN` or `IN OUT` bind variable in a SQL command.
+
+```sql
+BIND_VARIABLE_RAW(<c> NUMBER, <name> VARCHAR2, <value> RAW
+  [, <out_value_size> NUMBER ])
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor for the SQL command with bind variables.
+
+`name`
+
+ Name of the bind variable in the SQL command.
+
+`value`
+
+ Value of type `RAW` to be assigned.
+
+`out_value_size`
+
+ If `name` is an `IN OUT` variable, defines the maximum length of the output value. If not specified, the length of `value` is assumed.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/04_close_cursor.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/04_close_cursor.mdx
new file mode 100644
index 00000000000..85bd01eb17c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/04_close_cursor.mdx
@@ -0,0 +1,41 @@
+---
+title: "CLOSE_CURSOR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/04_close_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `CLOSE_CURSOR` procedure closes an open cursor. The resources allocated to the cursor are released and you can no longer use it.
+
+!!! Note
+When you convert a cursor using `TO_REFCURSOR`, you cannot call `CLOSE_CURSOR` for that cursor.
+!!!
+
+```sql
+CLOSE_CURSOR(<c> IN OUT NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor to be closed.
+
+## Examples
+
+This example closes an open cursor:
+
+```sql
+DECLARE
+    curid         NUMBER;
+    v_sql         VARCHAR2(150);
+    v_status      INTEGER;
+BEGIN
+    v_sql:='INSERT INTO emp VALUES (9001,''JONES'',''SALESMAN'',7369,TO_DATE(''13-DEC-07'',''DD-MON-YY''),8500.00,1500.00,50)';
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
+
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/05_column_value.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/05_column_value.mdx
new file mode 100644
index 00000000000..7500c4b8e65
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/05_column_value.mdx
@@ -0,0 +1,77 @@
+---
+title: "COLUMN_VALUE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/05_column_value/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `COLUMN_VALUE` procedure defines a variable to receive a value from a cursor.
+
+```sql
+COLUMN_VALUE(<c> NUMBER, <position> NUMBER, <value> OUT { BLOB | CLOB | DATE | FLOAT | 
+  INTEGER | NUMBER | TIMESTAMP | VARCHAR2 }
+  [, <column_error> OUT NUMBER [, <actual_length> OUT INTEGER ]])
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor returning data to the variable being defined.
+
+`position`
+
+ Position of the returned data in the cursor. The first value in the cursor is position 1.
+
+`value`
+
+ Variable receiving the data returned in the cursor by a prior fetch call.
+
+`column_error`
+
+ Error number associated with the column, if any.
+
+`actual_length`
+
+ Actual length of the data prior to any truncation.
+
+## Examples
+
+This example shows the portion of an anonymous block that receives the values from a cursor using the `COLUMN_VALUE` procedure.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_comm          NUMBER(7,2);
+    v_sql           VARCHAR2(50) := 'SELECT empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+	DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_ename);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_comm);
+    v_status := DBMS_SQL.EXECUTE(curid);          .
+    LOOP
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+        EXIT WHEN v_status = 0;
+        DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+        DBMS_SQL.COLUMN_VALUE(curid,2,v_ename);
+        DBMS_SQL.COLUMN_VALUE(curid,3,v_hiredate);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,5,v_comm);
+        DBMS_OUTPUT.PUT_LINE(v_empno || '   ' || RPAD(v_ename,10) || '  ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+    END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/06_column_value_char.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/06_column_value_char.mdx
new file mode 100644
index 00000000000..45603470b92
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/06_column_value_char.mdx
@@ -0,0 +1,34 @@
+---
+title: "COLUMN_VALUE_CHAR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/06_column_value_char/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `COLUMN_VALUE_CHAR` procedure defines a variable to receive a `CHAR` value from a cursor.
+
+```sql
+COLUMN_VALUE_CHAR(<c> NUMBER, <position> NUMBER, <value> OUT CHAR
+  [, <column_error> OUT NUMBER [, <actual_length> OUT INTEGER ]])
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor returning data to the variable being defined.
+
+`position`
+
+ Position of the returned data in the cursor. The first value in the cursor is position 1.
+
+`value`
+
+ Variable of data type `CHAR` receiving the data returned in the cursor by a prior fetch call.
+
+`column_error`
+
+ Error number associated with the column, if any.
+
+`actual_length`
+
+ Actual length of the data prior to any truncation.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07_column_value_raw.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07_column_value_raw.mdx
new file mode 100644
index 00000000000..52b86e0e8ca
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07_column_value_raw.mdx
@@ -0,0 +1,71 @@
+---
+title: "COLUMN_VALUE_RAW"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07_column_value_raw/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `COLUMN_VALUE_RAW` procedure defines a variable to receive a `RAW` value from a cursor.
+
+```sql
+COLUMN_VALUE_RAW(<c> NUMBER, <position> NUMBER, <value> OUT RAW
+  [, <column_error> OUT NUMBER [, <actual_length> OUT INTEGER ]])
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor returning data to the variable being defined.
+
+`position`
+
+ Position of the returned data in the cursor. The first value in the cursor is position 1.
+
+`value`
+
+ Variable of data type `RAW` receiving the data returned in the cursor by a prior fetch call.
+
+`column_error`
+
+ Error number associated with the column, if any.
+
+`actual_length`
+
+ Actual length of the data prior to any truncation.
+
+## COLUMN_VALUE_LONG
+
+The `COLUMN_VALUE_LONG` procedure returns a part of the value of a `LONG` column.
+
+```sql
+COLUMN_VALUE_LONG(<c> NUMBER, <position> NUMBER, <length> NUMBER,
+<offset> NUMBER, <value> OUT VARCHAR2, <value_length> OUT INTEGER)
+```
+
+### Parameters
+
+`c`
+
+ Cursor id of the cursor from which to get a value.
+
+`position`
+
+ Position of the column of which to get a value.
+
+`length`
+
+ Number of bytes of the long value to fetch.
+
+`offset`
+
+ Offset into the long field for start of fetch.
+
+`value`
+
+ Value of the column.
+
+`value_length`
+
+ Number of bytes returned in value.
+
+For an example, see [DEFINE_COLUMN_LONG](10_define_column_raw/#define_column_long).
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07a_column_value_long.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07a_column_value_long.mdx
new file mode 100644
index 00000000000..a48907c3bda
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07a_column_value_long.mdx
@@ -0,0 +1,103 @@
+---
+title: "COLUMN_VALUE_LONG"
+---
+
+The `COLUMN_VALUE_LONG` procedure gets part of a value of a `LONG` column to be returned and retrieved in a cursor. 
+
+```sql
+COLUMN_VALUE_LONG(<c> IN NUMBER, <position> IN NUMBER, <length> IN NUMBER, 
+   <offset> IN NUMBER, <value> OUT VARCHAR2, <value_length> OUT NUMBER);
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor returning data.
+
+`position`
+
+ Position of the returned data in the cursor. The first value in the cursor is position 1.
+
+`length`
+
+ Number of bytes of the long value to fetch.
+
+`offset`
+
+ Offset into the long field at which point the fetch begins.
+
+`value`
+
+ Value of the column as a VARCHAR2.
+
+ `value_length`
+
+ Number of bytes returned.
+
+
+### Examples
+
+```sql
+-- Creating the required object
+CREATE TABLE rm44142_dtypes (
+   col_long             LONG,
+   col_int  INTEGER);
+
+-- Insert data into table
+INSERT INTO rm44142_dtypes VALUES ('TestingForDefineColumnValueLong', 1);
+
+-- Use zero offset
+DECLARE
+   cur_id               INTEGER;
+   v_long       VARCHAR(20);
+   sql_stmt     VARCHAR2(50) := 'SELECT col_long ' || ' FROM rm44142_dtypes';
+   status       INTEGER;
+   length       INTEGER;
+
+BEGIN
+   cur_id := DBMS_SQL.OPEN_CURSOR;
+   DBMS_SQL.PARSE(cur_id, sql_stmt, DBMS_SQL.native);
+   DBMS_SQL.define_column_long(cur_id, 1);
+   status := DBMS_SQL.EXECUTE(cur_id);
+   status := DBMS_SQL.FETCH_ROWS(cur_id);
+   DBMS_SQL.COLUMN_VALUE_LONG(cur_id, 1, 7, 0, v_long, length);
+   DBMS_OUTPUT.PUT_LINE('col_long: ' || v_long);
+   DBMS_OUTPUT.PUT_LINE('value_length: ' || length);
+   DBMS_SQL.CLOSE_CURSOR(cur_id);
+END;
+
+Output:
+col_long: Testing
+value_length: 7
+
+EDB-SPL Procedure successfully completed
+
+
+-- Use positive offset
+DECLARE
+   cur_id               INTEGER;
+   v_long       VARCHAR2(20);
+   sql_stmt     VARCHAR2(50) := 'SELECT col_int, col_long ' || ' FROM rm44142_dtypes';
+   status       INTEGER;
+   length       INTEGER;
+
+BEGIN
+   cur_id := DBMS_SQL.OPEN_CURSOR;
+   DBMS_SQL.PARSE(cur_id, sql_stmt, DBMS_SQL.native);
+   DBMS_SQL.define_column_long(cur_id, 2);
+   status := DBMS_SQL.EXECUTE(cur_id);
+   status := DBMS_SQL.FETCH_ROWS(cur_id);
+   DBMS_SQL.COLUMN_VALUE_LONG(cur_id, 2, 12, 10, v_long, length);
+   DBMS_OUTPUT.PUT_LINE('col_long: ' || v_long);
+   DBMS_OUTPUT.PUT_LINE('value_length: ' || length);
+   DBMS_SQL.CLOSE_CURSOR(cur_id);
+END;
+
+Output:
+col_long: DefineColumn
+value_length: 12
+
+EDB-SPL Procedure successfully completed
+
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07b_column_value_rowid.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07b_column_value_rowid.mdx
new file mode 100644
index 00000000000..c83ae437f2e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07b_column_value_rowid.mdx
@@ -0,0 +1,75 @@
+---
+title: "COLUMN_VALUE_ROWID"
+---
+
+The `COLUMN_VALUE_ROWID` procedure defines a column of the type `ROWID` to be returned and retrieved in a cursor. 
+
+```sql
+COLUMN_VALUE_ROWID(<c> NUMBER, <position> NUMBER, <value> OUT ROWID
+  [, <column_error> OUT NUMBER [, <actual_length> OUT INTEGER ]]);
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor returning data to the variable being defined.
+
+`position`
+
+ Position of the returned data in the cursor. The first value in the cursor is position 1.
+
+`value`
+
+ The ROWID the data returned in the cursor by a prior fetch call.
+
+`column_error`
+
+ Error number associated with the column, if any.
+
+`actual_length`
+
+ Actual length of the data prior to any truncation.
+
+
+### Examples
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_rid           ROWID;
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_comm          NUMBER(7,2);
+    v_sql           VARCHAR2(55) := 'SELECT rid, empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN_rowid(curid,1, v_rid);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_ename,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,6,v_comm);
+    v_status := DBMS_SQL.EXECUTE(curid);
+LOOP        
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+EXIT WHEN v_status = 0;
+    DBMS_SQL.COLUMN_VALUE_rowid(curid, 1, v_rid);
+        DBMS_SQL.COLUMN_VALUE(curid,2,v_empno);
+DBMS_SQL.COLUMN_VALUE(curid,3,v_ename);
+DBMS_SQL.COLUMN_VALUE(curid,4,v_hiredate);
+DBMS_SQL.COLUMN_VALUE(curid,5,v_sal);
+DBMS_SQL.COLUMN_VALUE(curid,6,v_comm);
+DBMS_OUTPUT.PUT_LINE(v_rid || ' ' || v_empno || ' ' ||v_ename|| ' ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07c_define_array.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07c_define_array.mdx
new file mode 100644
index 00000000000..11510bfd62b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/07c_define_array.mdx
@@ -0,0 +1,103 @@
+---
+title: "DEFINE_ARRAY"
+---
+
+The `DEFINE_ARRAY` procedure defines the collection for a column into which you want to fetch rows with a FETCH_ROWS call. You can use this procedure to fetch multiple rows from a single SELECT statement. 
+
+When you fetch rows, they are copied into DBMS_SQL buffers until you run a COLUMN_VALUE call, which copies the rows into the table that was passed as an argument to the COLUMN_VALUE call.
+
+```sql
+DEFINE_ARRAY(<c> IN NUMBER, <position> IN NUMBER, 
+  <table_variable> IN { FLOAT_TABLE | BLOB_TABLE | CLOB_TABLE | VARCHAR2_TABLE | NUMBER_TABLE | TIMESTAMP_TABLE |
+  INTEGER_TABLE | ROWID_TABLE | TEXT_TABLE }, <cnt> IN NUMBER, <lower_bnd> IN NUMBER);
+```
+
+## Parameters
+
+`c`
+
+ID of the cursor to which you want to bind an array.
+
+`position`
+
+Relative position of the column in the array being defined. The first column is position 1.
+
+`table_variable`
+
+A datatype that can be any one of the following matching pairs:
+
+| Datatype   | Description      | 
+| ---------- | --------------- |
+| <bflt_tab> | FLOAT_TABLE     |
+| <bl_tab>   | BLOB_TABLE      |
+| <cl_tab>   | CLOB_TABLE      |
+| <c_tab>    | VARCHAR2_TABLE  |
+| <n_tab>    | NUMBER_TABLE    |
+| <tms_tab>  | TIMESTAMP_TABLE |
+| <int_tab>  | INTEGER_TABLE   |
+| <rid_tab>  | ROWID_TABLE     |
+| <txt_tab>  | TEXT_TABLE      |
+
+
+
+`cnt`
+
+Number of rows to fetch. Must be a positive integer.
+
+`lower_bnd`
+
+Results are copied into the collection, starting at this lower bound index.
+
+
+## Example
+
+```sql
+CREATE TABLE tab_test (col_int INTEGER, col_charactervarying VARCHAR(40));
+INSERT into tab_test(col_int, col_charactervarying) values (10, 'user1'), (10, 'user2'), (10, 'user3'), (10, 'user4');
+INSERT into tab_test(col_int, col_charactervarying) values (10, 'user1'), (10, 'user2'), (10, 'user3'), (10, 'user4');
+
+-- DEFINE_ARRAY (used in SELECT to get multipile rows)
+DECLARE
+    names    DBMS_SQL.VARCHAR2_TABLE;
+    dpt_id   DBMS_SQL.INTEGER_TABLE;
+    c        NUMBER;
+    r        NUMBER;
+    id       NUMBER;
+    sql_stmt VARCHAR2(32767) :=
+        'SELECT col_int, col_charactervarying FROM tab_test WHERE col_int = :b1';
+BEGIN
+    c := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(c, sql_stmt, dbms_sql.native);
+    id := 10;
+    DBMS_SQL.BIND_VARIABLE(c, 'b1', id);
+    DBMS_SQL.DEFINE_ARRAY(c, 1, dpt_id, 3, -3);
+    DBMS_SQL.DEFINE_ARRAY(c, 2, names, 3, -3);
+    r := DBMS_SQL.EXECUTE(c);
+    LOOP
+      r := DBMS_SQL.FETCH_ROWS(c);
+      EXIT WHEN r = 0;
+      DBMS_SQL.COLUMN_VALUE(c, 1, dpt_id);
+      DBMS_SQL.COLUMN_VALUE(c, 2, names);
+    END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(c);
+    DBMS_OUTPUT.PUT_LINE('last index in table = ' || names.LAST);
+    -- loop through the names and sals collections
+    FOR i IN names.FIRST .. names.LAST  LOOP
+      DBMS_OUTPUT.PUT_LINE(' name = ' ||names(i) || ' department_id = ' || dpt_id(i));
+    END LOOP;
+END;
+
+psql:bind_array.sql:67: last index in table = 4
+psql:bind_array.sql:67:  name = user1 department_id = 10
+psql:bind_array.sql:67:  name = user2 department_id = 10
+psql:bind_array.sql:67:  name = user3 department_id = 10
+psql:bind_array.sql:67:  name = user4 department_id = 10
+psql:bind_array.sql:67:  name = user1 department_id = 10
+psql:bind_array.sql:67:  name = user2 department_id = 10
+psql:bind_array.sql:67:  name = user3 department_id = 10
+psql:bind_array.sql:67:  name = user4 department_id = 10
+
+Here, count size is 3 so in one loop, we are printing 3 matching rows and total matching rows are 8.
+
+so 3,3,2 (total 3 loops--one loop will fetch 3 rows at a time because count is 3), and if we don't use define_array, then loop will be 8.
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/08_define_column.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/08_define_column.mdx
new file mode 100644
index 00000000000..f5092f719e0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/08_define_column.mdx
@@ -0,0 +1,109 @@
+---
+title: "DEFINE_COLUMN"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/08_define_column/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DEFINE_COLUMN` procedure defines a column or expression in the `SELECT` list to be returned and retrieved in a cursor.
+
+```sql
+DEFINE_COLUMN(<c> NUMBER, <position> NUMBER, <column> { BLOB | CLOB | DATE | FLOAT | 
+  INTEGER | NUMBER | TIMESTAMP | VARCHAR2 }
+  [, <column_size> NUMBER ])
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor associated with the `SELECT` command.
+
+`position`
+
+ Position of the column or expression in the `SELECT` list that's being defined.
+
+`column`
+
+ A variable of the same data type as the column or expression in position `position` of the `SELECT` list.
+
+`column_size`
+
+ The maximum length of the returned data. Specify `column_size` only if `column` is `VARCHAR2`. Returned data exceeding `column_size` is truncated to `column_size` characters.
+
+## Examples
+
+This example shows how the `empno`, `ename`, `hiredate`, `sal`, and `comm` columns of the `emp` table are defined with the `DEFINE_COLUMN` procedure.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_comm          NUMBER(7,2);
+    v_sql           VARCHAR2(50) := 'SELECT empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_ename,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_comm);
+    v_status := DBMS_SQL.EXECUTE(curid); 
+	LOOP        
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+		EXIT WHEN v_status = 0;
+        DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+		DBMS_SQL.COLUMN_VALUE(curid,2,v_ename);
+		DBMS_SQL.COLUMN_VALUE(curid,3,v_hiredate);
+		DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+		DBMS_SQL.COLUMN_VALUE(curid,5,v_comm);
+		DBMS_OUTPUT.PUT_LINE(v_empno || ' ' ||v_ename|| ' ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+	END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid); 
+END;
+```
+
+The following shows an alternative that produces the same results. The lengths of the data types are irrelevant. The `empno`, `sal`, and `comm` columns still return data equivalent to `NUMBER(4)` and `NUMBER(7,2)`, respectively, even though `v_num` is defined as `NUMBER(1)` (assuming the declarations in the `COLUMN_VALUE` procedure are of the appropriate maximum sizes). The `ename` column returns data up to 10 characters in length as defined by the `length` parameter in the `DEFINE_COLUMN` call, not by the data type declaration, `VARCHAR2(1)` declared for `v_varchar`. The actual size of the returned data is dictated by the `COLUMN_VALUE` procedure.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_num           NUMBER(1);
+    v_varchar       VARCHAR2(1);
+    v_date          DATE;
+    v_sql           VARCHAR2(50) := 'SELECT empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_num);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_varchar,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_date);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_num);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_num);
+    v_status := DBMS_SQL.EXECUTE(curid); 
+	LOOP
+		v_status := DBMS_SQL.FETCH_ROWS(curid);
+		EXIT WHEN v_status = 0;
+        DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+		DBMS_SQL.COLUMN_VALUE(curid,2,v_ename);
+		DBMS_SQL.COLUMN_VALUE(curid,3,v_hiredate);
+		DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+		DBMS_SQL.COLUMN_VALUE(curid,5,v_comm);
+		DBMS_OUTPUT.PUT_LINE(v_empno || ' ' ||v_ename|| ' ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+	END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);                    
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/09_define_column_char.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/09_define_column_char.mdx
new file mode 100644
index 00000000000..bc1dfbd6bf4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/09_define_column_char.mdx
@@ -0,0 +1,30 @@
+---
+title: "DEFINE_COLUMN_CHAR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/09_define_column_char/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DEFINE_COLUMN_CHAR` procedure defines a `CHAR` column or expression in the `SELECT` list to be returned and retrieved in a cursor.
+
+```sql
+DEFINE_COLUMN_CHAR(<c> NUMBER, <position> NUMBER, <column>
+CHAR, <column_size> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor associated with the `SELECT` command.
+
+`position`
+
+ Position of the column or expression in the `SELECT` list being defined.
+
+`column`
+
+ A `CHAR` variable.
+
+`column_size`
+
+ The maximum length of the returned data. Returned data exceeding `column_size` is truncated to `column_size` characters.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10_define_column_raw.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10_define_column_raw.mdx
new file mode 100644
index 00000000000..f707fdda13d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10_define_column_raw.mdx
@@ -0,0 +1,76 @@
+---
+title: "DEFINE_COLUMN_RAW"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10_define_column_raw/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DEFINE_COLUMN_RAW` procedure defines a `RAW` column or expression in the `SELECT` list to be returned and retrieved in a cursor.
+
+```sql
+DEFINE_COLUMN_RAW(<c> NUMBER, <position> NUMBER, <column> RAW,
+  <column_size> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor associated with the `SELECT` command.
+
+`position`
+
+ Position of the column or expression in the `SELECT` list being defined.
+
+`column`
+
+ A `RAW` variable.
+
+`column_size`
+
+ The maximum length of the returned data. Returned data exceeding `column_size` is truncated to `column_size` characters.
+
+## DEFINE_COLUMN_LONG
+
+<div id="define_column_long" class="registered_link"></div>
+
+The `DEFINE_COLUMN_LONG` procedure defines a long column for a `SELECT` cursor.
+
+```sql
+DEFINE_COLUMN_LONG(<c> NUMBER, <position> NUMBER)
+```
+
+### Parameters
+
+`c`
+
+ Cursor id of the cursor for a row defined to be selected.
+
+`position`
+
+ Position of the column in a row being defined.
+
+### Examples
+
+This example shows an anonymous block that defines a long column in the `SELECT` list using `DEFINE_COLUMN_LONG` procedure. It returns a part of the `LONG` column value into a variable using procedure `COLUMN_VALUE_LONG`.
+
+```sql
+DECLARE
+    curid          NUMBER;
+    v_ename        VARCHAR(20);
+    sql_stmt       VARCHAR2(50) := 'SELECT ename ' || ' FROM emp WHERE empno
+                                 = 7844';
+    v_status       INTEGER;
+    v_length       INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid, sql_stmt, DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN_LONG(curid, 1);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    v_status := DBMS_SQL.FETCH_ROWS(curid);
+    DBMS_SQL.COLUMN_VALUE_LONG(curid, 1, 7, 0, v_ename, v_length);
+    DBMS_OUTPUT.PUT_LINE('ename: ' || v_ename || ' & length: ' || v_length);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+ename: TURNER & length: 6
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10a_define_column_long.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10a_define_column_long.mdx
new file mode 100644
index 00000000000..6844b87ee15
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10a_define_column_long.mdx
@@ -0,0 +1,87 @@
+---
+title: "DEFINE_COLUMN_LONG"
+---
+
+The `DEFINE_COLUMN_LONG` procedure defines a column of the type `LONG` in the `SELECT` list to be returned and retrieved in a cursor.
+
+When you use this procedure, the column you are defining is identified by its relative position in the SELECT list of the statement in the specified cursor. The COLUMN value type determines the type of column being defined.
+
+```sql
+DEFINE_COLUMN_LONG(<c> IN NUMBER, <position> IN NUMBER);
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor from which a row is selected.
+
+`position`
+
+ Relative position of the column in the row being defined. The first column in a statement has position 1.
+
+
+### Examples
+
+```sql
+-- Creating the required object
+CREATE TABLE rm44142_dtypes (
+   col_long             LONG,
+   col_int  INTEGER);
+
+-- Insert data into table
+INSERT INTO rm44142_dtypes VALUES ('TestingForDefineColumnValueLong', 1);
+
+-- Use zero offset
+DECLARE
+   cur_id               INTEGER;
+   v_long       VARCHAR(20);
+   sql_stmt     VARCHAR2(50) := 'SELECT col_long ' || ' FROM rm44142_dtypes';
+   status       INTEGER;
+   length       INTEGER;
+
+BEGIN
+   cur_id := DBMS_SQL.OPEN_CURSOR;
+   DBMS_SQL.PARSE(cur_id, sql_stmt, DBMS_SQL.native);
+   DBMS_SQL.define_column_long(cur_id, 1);
+   status := DBMS_SQL.EXECUTE(cur_id);
+   status := DBMS_SQL.FETCH_ROWS(cur_id);
+   DBMS_SQL.COLUMN_VALUE_LONG(cur_id, 1, 7, 0, v_long, length);
+   DBMS_OUTPUT.PUT_LINE('col_long: ' || v_long);
+   DBMS_OUTPUT.PUT_LINE('value_length: ' || length);
+   DBMS_SQL.CLOSE_CURSOR(cur_id);
+END;
+
+Output:
+col_long: Testing
+value_length: 7
+
+EDB-SPL Procedure successfully completed
+
+-- Use positive offset
+DECLARE
+   cur_id               INTEGER;
+   v_long       VARCHAR2(20);
+   sql_stmt     VARCHAR2(50) := 'SELECT col_int, col_long ' || ' FROM rm44142_dtypes';
+   status       INTEGER;
+   length       INTEGER;
+
+BEGIN
+   cur_id := DBMS_SQL.OPEN_CURSOR;
+   DBMS_SQL.PARSE(cur_id, sql_stmt, DBMS_SQL.native);
+   DBMS_SQL.define_column_long(cur_id, 2);
+   status := DBMS_SQL.EXECUTE(cur_id);
+   status := DBMS_SQL.FETCH_ROWS(cur_id);
+   DBMS_SQL.COLUMN_VALUE_LONG(cur_id, 2, 12, 10, v_long, length);
+   DBMS_OUTPUT.PUT_LINE('col_long: ' || v_long);
+   DBMS_OUTPUT.PUT_LINE('value_length: ' || length);
+   DBMS_SQL.CLOSE_CURSOR(cur_id);
+END;
+
+Output:
+col_long: DefineColumn
+value_length: 12
+
+EDB-SPL Procedure successfully completed
+
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10b_define_column_rowid.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10b_define_column_rowid.mdx
new file mode 100644
index 00000000000..d091574e031
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/10b_define_column_rowid.mdx
@@ -0,0 +1,73 @@
+---
+title: "DEFINE_COLUMN_ROWID"
+---
+
+The `DEFINE_COLUMN_ROWID` procedure defines a column of the type `ROWID` in the `SELECT` list to be returned and retrieved in a cursor.
+
+!!! Note 
+In EDB Postgres Advanced Server, `ROWID` is a domain rather than a bigint.  
+!!!
+
+When you use this procedure the column you are defining is identified by its relative position in the SELECT list of the statement in the specified cursor. The COLUMN value type determines the type of column being defined.
+
+```sql
+DEFINE_COLUMN_ROWID(<c> IN NUMBER, <position> IN NUMBER, <column> IN NUMBER);
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor from which a row is selected.
+
+`position`
+
+ Relative position of the column in the row being defined. The first column in a statement has position 1.
+
+`column`
+
+ Value of the column. The type of this value determines the type for the column being defined.
+
+### Examples
+
+This example shows how the `empno`, `ename`, `hiredate`, `sal`, and `comm` columns of the `emp` table are defined with the `DEFINE_COLUMN_ROWID` procedure.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_rid           ROWID;
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    v_hiredate      DATE;
+    v_sal           NUMBER(7,2);
+    v_comm          NUMBER(7,2);
+    v_sql           VARCHAR2(55) := 'SELECT rid, empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN_rowid(curid,1, v_rid);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_ename,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,6,v_comm);
+    v_status := DBMS_SQL.EXECUTE(curid);
+LOOP        
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+EXIT WHEN v_status = 0;
+    DBMS_SQL.COLUMN_VALUE_rowid(curid, 1, v_rid);
+        DBMS_SQL.COLUMN_VALUE(curid,2,v_empno);
+DBMS_SQL.COLUMN_VALUE(curid,3,v_ename);
+DBMS_SQL.COLUMN_VALUE(curid,4,v_hiredate);
+DBMS_SQL.COLUMN_VALUE(curid,5,v_sal);
+DBMS_SQL.COLUMN_VALUE(curid,6,v_comm);
+DBMS_OUTPUT.PUT_LINE(v_rid || ' ' || v_empno || ' ' ||v_ename|| ' ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11_describe_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11_describe_columns.mdx
new file mode 100644
index 00000000000..c21a8cc05eb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11_describe_columns.mdx
@@ -0,0 +1,40 @@
+---
+title: "DESCRIBE_COLUMNS"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11_describe_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DESCRIBE_COLUMNS` procedure describes the columns returned by a cursor.
+
+```sql
+DESCRIBE_COLUMNS(<c> NUMBER, <col_cnt> OUT NUMBER, <desc_t> OUT
+  DESC_TAB);
+```
+
+## Parameters
+
+`c`
+
+ The cursor ID of the cursor.
+
+`col_cnt`
+
+ The number of columns in the cursor result set.
+
+`desc_tab`
+
+ The table that contains a description of each column returned by the cursor. The descriptions are of type `DESC_REC` and contain the following values:
+
+| Column name           | Type            |
+| --------------------- | --------------- |
+| `col_type`            | `INTEGER`       |
+| `col_max_len`         | `INTEGER`       |
+| `col_name`            | `VARCHAR2(128)` |
+| `col_name_len`        | `INTEGER`       |
+| `col_schema_name`     | `VARCHAR2(128)` |
+| `col_schema_name_len` | `INTEGER`       |
+| `col_precision`       | `INTEGER`       |
+| `col_scale`           | `INTEGER`       |
+| `col_charsetid`       | `INTEGER`       |
+| `col_charsetform`     | `INTEGER`       |
+| `col_null_ok`         | `BOOLEAN`       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11a_describe_columns2.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11a_describe_columns2.mdx
new file mode 100644
index 00000000000..ac338be78ec
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11a_describe_columns2.mdx
@@ -0,0 +1,77 @@
+---
+title: "DESCRIBE_COLUMNS2"
+---
+
+The `DESCRIBE_COLUMNS2` procedure describes specified columns returned by a cursor. This procedure provides an alternative to `DESCRIBE_COLUMN`.
+
+```sql
+DESCRIBE_COLUMNS2(<c> IN NUMBER, <col_cnt> OUT NUMBER, <desc_tab2> OUT
+  DESC_TAB2);
+```
+
+## Parameters
+
+`c`
+
+ The cursor ID of the cursor.
+
+`col_cnt`
+
+ The number of columns in the cursor result set.
+
+`desc_tab2`
+
+ The table that contains a description of each column returned by the cursor. The descriptions are of type `DESC_REC2` and contain the following values:
+
+| Column name           | Type            |
+| --------------------- | --------------- |
+| `col_type`            | `INTEGER`       |
+| `col_max_len`         | `INTEGER`       |
+| `col_name`            | `VARCHAR2(128)` |
+| `col_name_len`        | `INTEGER`       |
+| `col_schema_name`     | `VARCHAR2(128)` |
+| `col_schema_name_len` | `INTEGER`       |
+| `col_precision`       | `INTEGER`       |
+| `col_scale`           | `INTEGER`       |
+| `col_charsetid`       | `INTEGER`       |
+| `col_charsetform`     | `INTEGER`       |
+| `col_null_ok`         | `BOOLEAN`       |
+
+### Examples
+
+```sql
+DECLARE
+    c INTEGER := DBMS_SQL.OPEN_CURSOR;
+    l_columns DBMS_SQL.desc_tab2;
+    l_numcols INTEGER;
+    dbms_return INTEGER;
+BEGIN
+    DBMS_SQL.parse ( c, 'SELECT * FROM emp', DBMS_SQL.native );
+    dbms_return := DBMS_SQL.EXECUTE ( c );
+    DBMS_SQL.describe_columns2( c, l_numcols, l_columns );
+   DBMS_OUTPUT.PUT_LINE( 'Total # of Columns     :    '   || l_numcols);
+     DBMS_OUTPUT.put_line ( '--------------------------------------');
+    FOR colind IN 1 .. l_numcols
+    LOOP
+    DBMS_OUTPUT.PUT_LINE( 'Columns # :                 '   || colind);
+    DBMS_OUTPUT.put_line ( 'Column Name :               '   || l_columns ( colind ).col_name);
+    DBMS_OUTPUT.put_line ( 'Column Type :               '   || l_columns ( colind ).col_type);
+    DBMS_OUTPUT.put_line ( 'Column Max Length :         '   || l_columns ( colind ).col_max_len);
+    DBMS_OUTPUT.put_line ( 'Column Name Length :        '   || l_columns ( colind ).col_name_len);
+    DBMS_OUTPUT.put_line ( 'Column Schema Name :        '   || l_columns ( colind ).col_schema_name);
+    DBMS_OUTPUT.put_line ( 'Column Schema Name Length : '   || l_columns ( colind ).col_schema_name_len);
+    DBMS_OUTPUT.put_line ( 'Column Precision :          '   || l_columns ( colind ).col_precision);
+    DBMS_OUTPUT.put_line ( 'Column Scale :              '   || l_columns ( colind ).col_scale);
+    DBMS_OUTPUT.put_line ( 'Character Set ID :          '   || l_columns ( colind ).col_charsetid);
+    DBMS_OUTPUT.put_line ( 'Character Set Form :        '   || l_columns ( colind ).col_charsetform);
+    DBMS_OUTPUT.put ( 'Column Can be NULL :        ');
+    IF (l_columns ( colind ).col_null_ok) THEN
+            DBMS_OUTPUT.put_line ( 'NULL');
+    ELSE
+            DBMS_OUTPUT.put_line ( 'NOT NULL');
+    END IF;
+    DBMS_OUTPUT.put_line ( '--------------------------------------');
+    END LOOP;
+    DBMS_SQL.close_cursor ( c );
+END;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11b_describe_columns3.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11b_describe_columns3.mdx
new file mode 100644
index 00000000000..eeaa76877d1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/11b_describe_columns3.mdx
@@ -0,0 +1,74 @@
+---
+title: "DESCRIBE_COLUMNS3"
+---
+
+The `DESCRIBE_COLUMNS3` procedure describes specified columns returned by a cursor. This procedure provides an alternative to `DESCRIBE_COLUMN`.
+
+
+```sql
+DESCRIBE_COLUMNS3(<c> IN NUMBER, <col_cnt> OUT NUMBER, <desc_tab3> OUT
+  DESC_TAB3);
+```
+
+## Parameters
+
+`c`
+
+ The cursor ID of the cursor.
+
+`col_cnt`
+
+ The number of columns in the cursor result set.
+
+`desc_tab3`
+
+ The table that contains a description of each column returned by the cursor. The descriptions are of type `DESC_REC3` and contain the following values:
+
+| Column name           | Type              |
+| --------------------- | ----------------- |
+| `col_type`            | `INTEGER`         |
+| `col_max_len`         | `INTEGER`         |
+| `col_name`            | `VARCHAR2(128)`   |
+| `col_name_len`        | `INTEGER`         |
+| `col_schema_name`     | `VARCHAR2(128)`   |
+| `col_schema_name_len` | `INTEGER`         |
+| `col_precision`       | `INTEGER`         |
+| `col_scale`           | `INTEGER`         |
+| `col_charsetid`       | `INTEGER`         |
+| `col_charsetform`     | `INTEGER`         |
+| `col_null_ok`         | `BOOLEAN`         |
+| `col_type_name`       | `VARCHAR2(32767)` |
+| `col_type_name_len`   | `INTEGER`         |
+
+
+### Examples
+
+```sql
+CREATE TYPE PROJECT_DETAILS AS OBJECT
+      ( projname          VARCHAR2(20),
+        mgr               VARCHAR2(20));
+CREATE TABLE projecttab (deptno NUMBER, project PROJECT_DETAILS);
+
+DECLARE
+  curid      NUMBER;
+  desctab    DBMS_SQL.DESC_TAB3;
+  colcnt     NUMBER;
+  sql_stmt   VARCHAR2(200) := 'SELECT * FROM projecttab';
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid, sql_stmt, DBMS_SQL.NATIVE);
+    DBMS_SQL.DESCRIBE_COLUMNS3(curid, colcnt, desctab);
+    FOR i IN 1 .. colcnt LOOP
+      IF desctab(i).col_type = 109 THEN
+        DBMS_OUTPUT.PUT(desctab(i).col_name || ' is user-defined type: ');
+        DBMS_OUTPUT.PUT_LINE('COL_TYPE_NAME = ' || desctab(i).col_type_name
+       || ' COL_TYPE_NAME_LEN = ' || desctab(i).col_type_name_len);
+      ELSE
+       DBMS_OUTPUT.PUT(desctab(i).col_name || ' is not user-defined type: ');
+        DBMS_OUTPUT.PUT_LINE('COL_TYPE_NAME is NULL and '
+       || 'COL_TYPE_NAME_LEN = ' || desctab(i).col_type_name_len);
+      END IF;
+    END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/12_execute.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/12_execute.mdx
new file mode 100644
index 00000000000..fdc28bae4c7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/12_execute.mdx
@@ -0,0 +1,40 @@
+---
+title: "EXECUTE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/12_execute/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `EXECUTE` function executes a parsed SQL command or SPL block.
+
+```sql
+<status> INTEGER EXECUTE(<c> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the parsed SQL command or SPL block to execute.
+
+`status`
+
+ Number of rows processed if the SQL command was `DELETE`, `INSERT`, or `UPDATE`. `status` is meaningless for all other commands.
+
+## Examples
+
+The following anonymous block inserts a row into the `dept` table.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_sql           VARCHAR2(50);
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    v_sql := 'INSERT INTO dept VALUES (50, ''HR'', ''LOS ANGELES'')';
+    DBMS_SQL.PARSE(curid, v_sql, DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/13_execute_and_fetch.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/13_execute_and_fetch.mdx
new file mode 100644
index 00000000000..424110431f1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/13_execute_and_fetch.mdx
@@ -0,0 +1,96 @@
+---
+title: "EXECUTE_AND_FETCH"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/13_execute_and_fetch/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Function `EXECUTE_AND_FETCH` executes a parsed `SELECT` command and fetches one row.
+
+```sql
+<status> INTEGER EXECUTE_AND_FETCH(<c> NUMBER [, <exact> BOOLEAN ])
+```
+
+## Parameters
+
+`c`
+
+ Cursor id of the cursor for the `SELECT` command to execute.
+
+`exact`
+
+ If set to `TRUE`, an exception is thrown if the number of rows in the result set isn't exactly equal to 1. If set to `FALSE`, no exception is thrown. The default is `FALSE`. A `NO_DATA_FOUND` exception is thrown if `exact` is `TRUE` and there are no rows in the result set. A `TOO_MANY_ROWS` exception is thrown if `exact` is `TRUE` and more than one row is in the result set.
+
+`status`
+
+ Returns `1` if a row was successfully fetched, `0` if no rows to fetch. If an exception is thrown, no value is returned.
+
+## Examples
+
+This stored procedure uses the `EXECUTE_AND_FETCH` function to retrieve one employee using the employee’s name. An exception is thrown if the employee isn't found or more than one employee has the same name.
+
+```sql
+CREATE OR REPLACE PROCEDURE select_by_name(
+    p_ename         emp.ename%TYPE
+)
+IS
+    curid           NUMBER;
+    v_empno         emp.empno%TYPE;
+    v_hiredate      emp.hiredate%TYPE;
+    v_sal           emp.sal%TYPE;
+    v_comm          emp.comm%TYPE;
+    v_dname         dept.dname%TYPE;
+    v_disp_date     VARCHAR2(10);
+    v_sql           VARCHAR2(120) := 'SELECT empno, hiredate, sal, ' ||
+                                     'NVL(comm, 0), dname ' ||
+                                     'FROM emp e, dept d ' ||
+                                     'WHERE ename = :p_ename ' ||
+                                     'AND e.deptno = d.deptno';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.BIND_VARIABLE(curid,':p_ename',UPPER(p_ename));
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_comm);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_dname,14);
+    v_status := DBMS_SQL.EXECUTE_AND_FETCH(curid,TRUE);
+    DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+    DBMS_SQL.COLUMN_VALUE(curid,2,v_hiredate);
+    DBMS_SQL.COLUMN_VALUE(curid,3,v_sal);
+    DBMS_SQL.COLUMN_VALUE(curid,4,v_comm);
+    DBMS_SQL.COLUMN_VALUE(curid,5,v_dname);
+    v_disp_date := TO_CHAR(v_hiredate, 'MM/DD/YYYY');
+    DBMS_OUTPUT.PUT_LINE('Number    : ' || v_empno);
+    DBMS_OUTPUT.PUT_LINE('Name      : ' || UPPER(p_ename));
+    DBMS_OUTPUT.PUT_LINE('Hire Date : ' || v_disp_date);
+    DBMS_OUTPUT.PUT_LINE('Salary    : ' || v_sal);
+    DBMS_OUTPUT.PUT_LINE('Commission: ' || v_comm);
+    DBMS_OUTPUT.PUT_LINE('Department: ' || v_dname);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+EXCEPTION
+    WHEN NO_DATA_FOUND THEN
+        DBMS_OUTPUT.PUT_LINE('Employee ' || p_ename || ' not found');
+        DBMS_SQL.CLOSE_CURSOR(curid);
+    WHEN TOO_MANY_ROWS THEN
+        DBMS_OUTPUT.PUT_LINE('Too many employees named, ' ||
+            p_ename || ', found');
+        DBMS_SQL.CLOSE_CURSOR(curid);
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('The following is SQLERRM:');
+        DBMS_OUTPUT.PUT_LINE(SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('The following is SQLCODE:');
+        DBMS_OUTPUT.PUT_LINE(SQLCODE);
+        DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+EXEC select_by_name('MARTIN')
+
+Number    : 7654
+Name      : MARTIN
+Hire Date : 09/28/1981
+Salary    : 1250
+Commission: 1400
+Department: SALES
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/14_fetch_rows.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/14_fetch_rows.mdx
new file mode 100644
index 00000000000..90172e6bbc9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/14_fetch_rows.mdx
@@ -0,0 +1,84 @@
+---
+title: "FETCH_ROWS"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/14_fetch_rows/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `FETCH_ROWS` function retrieves a row from a cursor.
+
+```sql
+<status> INTEGER FETCH_ROWS(<c> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor from which to fetch a row.
+
+`status`
+
+ Returns `1` if a row was successfully fetched, `0` if no more rows to fetch.
+
+## Examples
+
+These examples fetch the rows from the `emp` table and display the results.
+
+```sql
+DECLARE
+    curid          NUMBER;
+    v_empno        NUMBER(4);
+    v_ename        VARCHAR2(10);
+    v_hiredate     DATE;
+    v_sal          NUMBER(7,2);
+    v_comm         NUMBER(7,2);
+    v_sql          VARCHAR2(50) := 'SELECT empno, ename, hiredate, sal, ' ||
+                                   'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_ename,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_comm);
+
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME       HIREDATE    SAL       COMM');
+    DBMS_OUTPUT.PUT_LINE('-----  ----------  ----------  --------  ' ||
+        '--------');
+    LOOP
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+        EXIT WHEN v_status = 0;
+        DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+        DBMS_SQL.COLUMN_VALUE(curid,2,v_ename);
+        DBMS_SQL.COLUMN_VALUE(curid,3,v_hiredate);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,5,v_comm);
+        DBMS_OUTPUT.PUT_LINE(v_empno || '   ' || RPAD(v_ename,10) || '  ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+    END LOOP;
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+EMPNO  ENAME       HIREDATE    SAL       COMM
+-----  ----------  ----------  --------  --------
+7369   SMITH       1980-12-17    800.00       .00
+7499   ALLEN       1981-02-20  1,600.00    300.00
+7521   WARD        1981-02-22  1,250.00    500.00
+7566   JONES       1981-04-02  2,975.00       .00
+7654   MARTIN      1981-09-28  1,250.00  1,400.00
+7698   BLAKE       1981-05-01  2,850.00       .00
+7782   CLARK       1981-06-09  2,450.00       .00
+7788   SCOTT       1987-04-19  3,000.00       .00
+7839   KING        1981-11-17  5,000.00       .00
+7844   TURNER      1981-09-08  1,500.00       .00
+7876   ADAMS       1987-05-23  1,100.00       .00
+7900   JAMES       1981-12-03    950.00       .00
+7902   FORD        1981-12-03  3,000.00       .00
+7934   MILLER      1982-01-23  1,300.00       .00
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/15_is_open.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/15_is_open.mdx
new file mode 100644
index 00000000000..cd1e2cec1c7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/15_is_open.mdx
@@ -0,0 +1,21 @@
+---
+title: "IS_OPEN"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/15_is_open/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `IS_OPEN` function tests whether the given cursor is open.
+
+```sql
+<status> BOOLEAN IS_OPEN(<c> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of the cursor to test.
+
+`status`
+
+ Set to `TRUE` if the cursor is open, set to `FALSE` if the cursor isn't open.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/16_last_row_count.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/16_last_row_count.mdx
new file mode 100644
index 00000000000..9ba5ca10d38
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/16_last_row_count.mdx
@@ -0,0 +1,111 @@
+---
+title: "LAST_ROW_COUNT"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/16_last_row_count/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `LAST_ROW_COUNT` function returns the number of rows that were currently fetched.
+
+```sql
+<rowcnt> INTEGER LAST_ROW_COUNT
+```
+
+## Parameters
+
+`rowcnt`
+
+ Number of row fetched thus far.
+
+## Examples
+
+This example uses the `LAST_ROW_COUNT` function to display the total number of rows fetched in the query.
+
+```sql
+DECLARE
+    curid          NUMBER;
+    v_empno        NUMBER(4);
+    v_ename        VARCHAR2(10);
+    v_hiredate     DATE;
+    v_sal          NUMBER(7,2);
+    v_comm         NUMBER(7,2);
+    v_sql          VARCHAR2(50) := 'SELECT empno, ename, hiredate, sal, ' ||
+                                    'comm FROM emp';
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    DBMS_SQL.DEFINE_COLUMN(curid,1,v_empno);
+    DBMS_SQL.DEFINE_COLUMN(curid,2,v_ename,10);
+    DBMS_SQL.DEFINE_COLUMN(curid,3,v_hiredate);
+    DBMS_SQL.DEFINE_COLUMN(curid,4,v_sal);
+    DBMS_SQL.DEFINE_COLUMN(curid,5,v_comm);
+
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME       HIREDATE    SAL       COMM');
+    DBMS_OUTPUT.PUT_LINE('-----  ----------  ----------  --------  ' ||
+        '--------');
+    LOOP
+        v_status := DBMS_SQL.FETCH_ROWS(curid);
+        EXIT WHEN v_status = 0;
+        DBMS_SQL.COLUMN_VALUE(curid,1,v_empno);
+        DBMS_SQL.COLUMN_VALUE(curid,2,v_ename);
+        DBMS_SQL.COLUMN_VALUE(curid,3,v_hiredate);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,4,v_sal);
+        DBMS_SQL.COLUMN_VALUE(curid,5,v_comm);
+        DBMS_OUTPUT.PUT_LINE(v_empno || '   ' || RPAD(v_ename,10) || '  ' ||
+            TO_CHAR(v_hiredate,'yyyy-mm-dd') || ' ' ||
+            TO_CHAR(v_sal,'9,999.99') || ' ' ||
+            TO_CHAR(NVL(v_comm,0),'9,999.99'));
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Number of rows: ' || DBMS_SQL.LAST_ROW_COUNT);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+EMPNO  ENAME       HIREDATE    SAL       COMM
+-----  ----------  ----------  --------  --------
+7369   SMITH       1980-12-17    800.00       .00
+7499   ALLEN       1981-02-20  1,600.00    300.00
+7521   WARD        1981-02-22  1,250.00    500.00
+7566   JONES       1981-04-02  2,975.00       .00
+7654   MARTIN      1981-09-28  1,250.00  1,400.00
+7698   BLAKE       1981-05-01  2,850.00       .00
+7782   CLARK       1981-06-09  2,450.00       .00
+7788   SCOTT       1987-04-19  3,000.00       .00
+7839   KING        1981-11-17  5,000.00       .00
+7844   TURNER      1981-09-08  1,500.00       .00
+7876   ADAMS       1987-05-23  1,100.00       .00
+7900   JAMES       1981-12-03    950.00       .00
+7902   FORD        1981-12-03  3,000.00       .00
+7934   MILLER      1982-01-23  1,300.00       .00
+Number of rows: 14
+```
+
+## LAST_ERROR_POSITION
+
+The `LAST_ERROR_POSITION` function returns an integer value indicating the byte offset in the SQL statement text where the error occurred. The error position of the first character in the SQL statement is at `1`.
+
+```sql
+LAST_ERROR_POSITION RETURN INTEGER;
+```
+
+### Examples
+
+This example shows an anonymous block that returns an error position with the `LAST_ERROR_POSITION` function.
+
+```sql
+DECLARE
+    curid             NUMBER;
+    sql_stmt          VARCHAR2(50) := 'SELECT empno FROM not_exist_table';
+    v_position        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid, sql_stmt, DBMS_SQL.native);
+EXCEPTION WHEN OTHERS THEN
+    v_position := DBMS_SQL.LAST_ERROR_POSITION;
+    DBMS_OUTPUT.PUT_LINE('error position = ' || v_position);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+error position = 19
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor.mdx
new file mode 100644
index 00000000000..df85c1b7e5f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor.mdx
@@ -0,0 +1,36 @@
+---
+title: "OPEN_CURSOR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/17_open_cursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `OPEN_CURSOR` function creates a cursor. A cursor must be used to parse and execute any dynamic SQL statement. Once a cursor is open, you can reuse it with the same or different SQL statements. You don't have to close the cursor and reopen it to reuse it.
+
+```sql
+<c> INTEGER OPEN_CURSOR
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID number associated with the newly created cursor.
+
+## Examples
+
+This example creates a new cursor:
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_sql           VARCHAR2(150);
+    v_status        INTEGER;
+BEGIN
+    v_sql:='INSERT INTO dept VALUES (50,''HR'',''LOS ANGELES'')';
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid,v_sql,DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/18_parse.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/18_parse.mdx
new file mode 100644
index 00000000000..765853955df
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/18_parse.mdx
@@ -0,0 +1,83 @@
+---
+title: "PARSE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/18_parse/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `PARSE` procedure parses a SQL command or SPL block. If the SQL command is a DDL command, it executes immediately and doesn't require that you run the `EXECUTE` function.
+
+```sql
+PARSE(<c> NUMBER, <statement> VARCHAR2, <language_flag> NUMBER)
+```
+
+## Parameters
+
+`c`
+
+ Cursor ID of an open cursor.
+
+`statement`
+
+ SQL command or SPL block to parse. A SQL command must not end with the semi-colon terminator. However an SPL block does require the semi-colon terminator.
+
+`language_flag`
+
+ Language flag provided for compatibility with Oracle syntax. Use `DBMS_SQL.V6`, `DBMS_SQL.V7` or `DBMS_SQL.native`. This flag is ignored, and all syntax is assumed to be in EDB EDB Postgres Advanced Server form.
+
+## Examples
+
+This anonymous block creates a table named, `job`. DDL statements are executed immediately by the `PARSE` procedure and don't require a separate `EXECUTE` step.
+
+```sql
+DECLARE
+    curid           NUMBER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    DBMS_SQL.PARSE(curid, 'CREATE TABLE job (jobno NUMBER(3), ' ||
+        'jname VARCHAR2(9))',DBMS_SQL.native);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
+
+The following inserts two rows into the `job` table.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_sql           VARCHAR2(50);
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    v_sql := 'INSERT INTO job VALUES (100, ''ANALYST'')';
+    DBMS_SQL.PARSE(curid, v_sql, DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    v_sql := 'INSERT INTO job VALUES (200, ''CLERK'')';
+    DBMS_SQL.PARSE(curid, v_sql, DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_OUTPUT.PUT_LINE('Number of rows processed: ' || v_status);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+
+Number of rows processed: 1
+Number of rows processed: 1
+```
+
+This anonymous block uses the `DBMS_SQL` package to execute a block containing two `INSERT` statements. The end of the block contains a terminating semi-colon. In the prior example, each `INSERT` statement doesn't have a terminating semi-colon.
+
+```sql
+DECLARE
+    curid           NUMBER;
+    v_sql           VARCHAR2(100);
+    v_status        INTEGER;
+BEGIN
+    curid := DBMS_SQL.OPEN_CURSOR;
+    v_sql := 'BEGIN ' ||
+               'INSERT INTO job VALUES (300, ''MANAGER''); '  ||
+               'INSERT INTO job VALUES (400, ''SALESMAN''); ' ||
+             'END;';
+    DBMS_SQL.PARSE(curid, v_sql, DBMS_SQL.native);
+    v_status := DBMS_SQL.EXECUTE(curid);
+    DBMS_SQL.CLOSE_CURSOR(curid);
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/19_to_cursor_number.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/19_to_cursor_number.mdx
new file mode 100644
index 00000000000..bf095161868
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/19_to_cursor_number.mdx
@@ -0,0 +1,47 @@
+---
+title: "TO_CURSOR_NUMBER"
+---
+
+The `TO_CURSOR_NUMBER` function transforms a ref cursor into a SQL cursor number.
+
+This function is useful to retrieve the metadata (columns, column types, and so forth) from a ref cursor, when you have a SYS_REFCURSOR variable with an unknown return structure.
+
+```sql
+TO_CURSOR_NUMBER (<rc> IN OUT SYS_REFCURSOR)
+    RETURN INTEGER;
+```
+
+## Parameters
+
+`rc`
+
+ The ref cursor to be transformed into a cursor number.
+
+## Examples
+
+```sql
+DECLARE
+    cur1        SYS_REFCURSOR;
+    cur_id      INTEGER;
+    tbl_desc    test_tbl%ROWTYPE;
+    totcols     INTEGER;
+    ret         INTEGER;
+    rowcnt      NUMBER;
+    col1_data   VARCHAR(30);
+    col2_data   VARCHAR(30);
+BEGIN
+    OPEN cur1 FOR 'SELECT * FROM test_tbl_tbl';
+    cur_id:= dbms_sql.to_cursor_number(cur1);
+
+    dbms_sql.define_column(cur_id, 1, tbl_desc.col1);
+    dbms_sql.define_column(cur_id, 2, tbl_desc.col2);
+
+    LOOP
+      ret := dbms_sql.FETCH_ROWS(cur_id);
+      EXIT WHEN ret = 0;
+      dbms_sql.column_value(cur_id, 1, tbl_desc.col1);
+      dbms_sql.column_value(cur_id, 2, tbl_desc.col2);
+      dbms_output.put_line('Col1: ' || tbl_desc.col1 || ' Col2: ' || tbl_desc.col2);
+    END LOOP;
+END;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx
new file mode 100644
index 00000000000..9026c136f1a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor.mdx
@@ -0,0 +1,87 @@
+---
+title: "TO_REFCURSOR"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/20_to_refcursor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `TO_REFCURSOR` function transforms an open cursor into a REF CURSOR for use in SQL statements. This program is only used with SELECT cursors.
+
+
+!!! Note
+When you convert a cursor using `TO_REFCURSOR`, you cannot call `CLOSE_CURSOR` for that cursor.
+!!!
+
+```sql
+TO_REFCURSOR (<cursor_number> IN OUT INTEGER) 
+  RETURN SYS_REFCURSOR;
+```
+
+## Parameter
+
+`cursor_number`
+
+ Cursor ID number to be transformed into a ref cursor.
+
+## Examples
+
+```sql
+CREATE TABLE student_info (id INTEGER PRIMARY KEY, first_name VARCHAR(20), last_name VARCHAR(20), dept_id int);
+INSERT INTO student_info VALUES                                                  
+    (1, 'Tia', 'Jackson', 10),                                                   
+    (2, 'Raj','Malhotra', 12),                                                   
+    (3, 'Nash','Cadogan', 13),                                                   
+    (4, 'Sam', 'Wordsworth', 10),                                                
+    (5, 'Roger', 'Zen', 10),                                                     
+    (6, 'Cale', 'Kingston', 12),                                                 
+    (7, 'Caleb', 'Johnson', 13);                                                 
+                                                                                 
+CREATE TABLE department_master (id number PRIMARY KEY, dept_name VARCHAR (20));  
+INSERT INTO department_master VALUES                                             
+    (10,'Science'),                                                              
+    (12, 'Maths'),                                                               
+    (13, 'Computers');                                                           
+                                                                                 
+CREATE OR REPLACE FUNCTION list_dept_student_info (qual IN VARCHAR2)             
+RETURN sys_refcursor                                                             
+IS                                                                               
+  dbmssql_cur   NUMBER;                                                          
+  curvar           sys_refcursor;                                                
+  execvar        PLS_INTEGER;                                                    
+BEGIN                                                                            
+  dbmssql_cur := DBMS_SQL.open_cursor;                                           
+  DBMS_SQL.parse (dbmssql_cur                                                    
+                 , 'SELECT first_name, last_name FROM student_info WHERE dept_id = (SELECT id FROM department_master WHERE dept_name LIKE :dept_id)'
+                 , DBMS_SQL.native                                               
+                 );                                                              
+  DBMS_SQL.bind_variable (dbmssql_cur                                            
+                           , 'dept_id'                                           
+                           , qual                                                
+                            );                                                   
+  execvar := DBMS_SQL.EXECUTE (dbmssql_cur);                                     
+  curvar := DBMS_SQL.to_refcursor (dbmssql_cur);                                 
+  RETURN curvar;                                                                 
+END;                                                                             
+DECLARE                                                                          
+   TYPE strings_t IS TABLE OF VARCHAR2 (200);                                    
+   curvar       sys_refcursor;                                                   
+   fnames      strings_t;                                                        
+   lnames      strings_t;                                                        
+BEGIN                                                                            
+   curvar :=  list_dept_student_info ('Science');                                
+   FETCH curvar                                                                  
+   BULK COLLECT INTO fnames, lnames;    
+   DBMS_OUTPUT.put_line ('Students in Science department');                      
+   FOR idx IN 1 .. fnames.COUNT                                                  
+   LOOP                                                                          
+      DBMS_OUTPUT.put_line (fnames(idx) || '  '||  lnames(idx));                 
+   END LOOP;                                                                     
+   CLOSE curvar;                                                                 
+END; 
+
+Students in Science department
+ Tia  Jackson
+ Sam  Wordsworth
+ Roger  Zen
+
+EDB-SPL Procedure successfully completed
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/index.mdx
new file mode 100644
index 00000000000..895fad44994
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/index.mdx
@@ -0,0 +1,64 @@
+---
+title: "DBMS_SQL"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.30.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.203.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.161.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/17_dbms_sql/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_SQL` package provides an application interface compatible with Oracle databases to the EDB dynamic SQL functionality. With `DBMS_SQL` you can construct queries and other commands at runtime rather than when you write the application. EDB Postgres Advanced Server offers native support for dynamic SQL. `DBMS_SQL` provides a way to use dynamic SQL in a way that's compatible with Oracle databases without modifying your application.
+
+`DBMS_SQL` assumes the privileges of the current user when executing dynamic SQL statements.
+
+EDB Postgres Advanced Server's implementation of `DBMS_SQL` is a partial implementation when compared to Oracle's version. Only those functions and procedures listed in the table are supported.
+
+| Function/procedure                                                                       | Function or procedure | Return type      | Description                                                            |
+| ---------------------------------------------------------------------------------------- | --------------------- | ---------------- | ---------------------------------------------------------------------- |
+| `BIND_ARRAY(c IN, name IN, table_variable IN [index1 IN, index2 IN])`                    | Procedure             | n/a              | Binds a value or set of values to a variable.                          |
+| `BIND_VARIABLE(c, name, value [, out_value_size ])`                                      | Procedure             | n/a              | Bind a value to a variable.                                            |
+| `BIND_VARIABLE_CHAR(c, name, value [, out_value_size ])`                                 | Procedure             | n/a              | Bind a `CHAR` value to a variable.                                     |
+| `BIND_VARIABLE_RAW(c, name, value [, out_value_size ])`                                  | Procedure             | n/a              | Bind a `RAW` value to a variable.                                      |
+| `CLOSE_CURSOR(c IN OUT)`                                                                 | Procedure             | n/a              | Close a cursor.                                                        |
+| `COLUMN_VALUE(c, position, value OUT [, column_error OUT [, actual_length OUT ]])`       | Procedure             | n/a              | Return a column value into a variable.                                 |
+| `COLUMN_VALUE_CHAR(c, position, value OUT [, column_error OUT [, actual_length OUT ]])`  | Procedure             | n/a              | Return a `CHAR` column value into a variable.                          |
+| `COLUMN_VALUE_RAW(c, position, value OUT [, column_error OUT [, actual_length OUT ]])`   | Procedure             | n/a              | Return a `RAW` column value into a variable.                           |
+| `COLUMN_VALUE_LONG(c, position, length, offset, value OUT, value_length OUT)`             | Procedure             | n/a              | Return a part of the `LONG` column value into a variable.              |
+| `COLUMN_VALUE_ROWID(c, position, value OUT [ column_error OUT [, actual_length OUT ]])`  | Procedure             | n/a              | Return a `ROWID` column in a cursor.                                   | 
+| `DEFINE_ARRAY(c IN, position IN, table_variable IN, cnt IN, lower_bnd IN )`              | Procedure             | n/a              | Define collection for column into which to fetch rows.                 |
+| `DEFINE_COLUMN(c, position, column [, column_size ])`                                    | Procedure             | n/a              | Define a column in the `SELECT` list.                                  |
+| `DEFINE_COLUMN_CHAR(c, position, column, column_size)`                                   | Procedure             | n/a              | Define a `CHAR` column in the `SELECT` list.                           |
+| `DEFINE_COLUMN_RAW(c, position, column, column_size)`                                    | Procedure             | n/a              | Define a `RAW` column in the `SELECT` list.                            |
+| `DEFINE_COLUMN_LONG(c, position)`                                                        | Procedure             | n/a              | Define a `LONG` column in the `SELECT` list.                           |
+| `DEFINE_COLUMN_ROWID(c IN, position IN, column IN)`                                      | Procedure             | n/a              | Define a `ROWID` column in the `SELECT` list.                          |
+| `DESCRIBE_COLUMNS(c IN, col_cnt OUT, desc_t OUT, DESC_TAB)`                              | Procedure             | n/a              | Define columns to hold a cursor result set.                            |
+| `DESCRIBE_COLUMNS2(c IN, col_cnt OUT, desc_t OUT, DESC_TAB)`                             | Procedure             | n/a              | Define columns to hold a cursor result set.                            |
+| `DESCRIBE_COLUMNS3(c IN, col_cnt OUT, desc_t OUT, DESC_TAB)`                             | Procedure             | n/a              | Define columns to hold a cursor result set.                            |
+| `EXECUTE(c)`                                                                             | Function              | `INTEGER`        | Execute a cursor.                                                      |
+| `EXECUTE_AND_FETCH(c [, exact ])`                                                        | Function              | `INTEGER`        | Execute a cursor and fetch a single row.                               |
+| `FETCH_ROWS(c)`                                                                          | Function              | `INTEGER`        | Fetch rows from the cursor.                                            |
+| `IS_OPEN(c)`                                                                             | Function              | `BOOLEAN`        | Check if a cursor is open.                                             |
+| `LAST_ROW_COUNT`                                                                         | Function              | `INTEGER`        | Return cumulative number of rows fetched.                              |
+| `LAST_ERROR_POSITION`                                                                    | Function              | `INTEGER`        | Return byte offset in the SQL statement text where the error occurred. |
+| `OPEN_CURSOR`                                                                            | Function              | `INTEGER`        | Open a cursor.                                                         |
+| `PARSE(c, statement, language_flag)`                                                     | Procedure             | n/a              | Parse a statement.                                                     |
+| `TO_CURSOR_NUMBER (rc IN OUT )`                                                          | Function              | `INTEGER`        | Transform a ref cursor into a SQL cursor number.                       |
+| `TO_REFCURSOR (cursor_number IN OUT)`                                                    | Function              | `SYS_REFCURSOR ` | Transform an open cursor into a REF CURSOR. 
+| `VARIABLE_VALUE`                                                                         |                       |                  | Not supported in EPAS                                                  |
+
+
+The following table lists the public variables available in the `DBMS_SQL` package.
+
+| Public variables | Data type | Value | Description                                                                               |
+| ---------------- | --------- | ----- | ----------------------------------------------------------------------------------------- |
+| `native`         | `INTEGER` | `1`   | Provided for compatibility with Oracle syntax. See `DBMS_SQL.PARSE` for more information. |
+| `V6`             | `INTEGER` | `2`   | Provided for compatibility with Oracle syntax. See `DBMS_SQL.PARSE` for more information. |
+| `V7`             | `INTEGER` | `3`   | Provided for compatibility with Oracle syntax. See `DBMS_SQL.PARSE` for more information  |
+
+<div class="toctree" maxdepth="5">
+
+bind_variable bind_variable_char bind_variable_raw close_cursor column_value column_value_char column_value_raw define_column define_column_char define_column_raw describe_columns execute execute_and_fetch fetch_rows is_open last_row_count open_cursor parse
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_utility.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_utility.mdx
new file mode 100644
index 00000000000..304894334a3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/18_dbms_utility.mdx
@@ -0,0 +1,867 @@
+---
+title: "DBMS_UTILITY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.31.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.204.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.162.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/18_dbms_utility/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `DBMS_UTILITY` package provides support for the following utility programs. EDB Postgres Advanced Server's implementation of `DBMS_UTILITY` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in the table are supported.
+
+| Function/procedure                                                                                             | Function or procedure | Return type      | Description                                                  |
+| -------------------------------------------------------------------------------------------------------------- | --------------------- | ---------------- | ------------------------------------------------------------ |
+| `ANALYZE_DATABASE(method [, estimate_rows [, estimate_percent [, method_opt ]]])`                              | Procedure             | n/a              | Analyze database tables.                                     |
+| `ANALYZE_PART_OBJECT(schema, object_name [, object_type [, command_type [, command_opt [, sample_clause ]]]])` | Procedure             | n/a              | Analyze a partitioned table.                                 |
+| `ANALYZE_SCHEMA(schema, method [, estimate_rows [, estimate_percent [, method_opt ]]])`                        | Procedure             | n/a              | Analyze schema tables.                                       |
+| `CANONICALIZE(name, canon_name OUT, canon_len)`                                                                | Procedure             | n/a              | Canonicalize a string, e.g., strip off white space.       |
+| `COMMA_TO_TABLE(list, tablen OUT, tab OUT)`                                                                    | Procedure             | n/a              | Convert a comma-delimited list of names to a table of names. |
+| `DB_VERSION(version OUT, compatibility OUT)`                                                                   | Procedure             | n/a              | Get the database version.                                    |
+| `EXEC_DDL_STATEMENT (parse_string)`                                                                            | Procedure             | n/a              | Execute a DDL statement.                                     |
+| `EXPAND_SQL_TEXT(input_sql_text, output_sql_text)`                                                             | Function              | `TEXT`           | Returns expanded SQL references to view.                     |                          
+| `FORMAT_CALL_STACK`                                                                                            | Function              | `TEXT`           | Formats the current call stack.                              |
+| `FORMAT_ERROR_BACKTRACE`                                                                                       | Function              | `TEXT`           | Formats the current error call backtrace.                    |
+| `FORMAT_ERROR_STACK`                                                                                           | Function              | `TEXT`           | Get the exception name.                                      |
+| `GET_CPU_TIME`                                                                                                 | Function              | `NUMBER`         | Get the current CPU time.                                    |
+| `GET_DEPENDENCY(type, schema, name)`                                                                           | Procedure             | n/a              | Get objects that depend on the given object.                 |
+| `GET_HASH_VALUE(name, base, hash_size)`                                                                        | Function              | `NUMBER`         | Compute a hash value.                                        |
+| `GET_PARAMETER_VALUE(parnam, intval OUT, strval OUT)`                                                          | Procedure             | `BINARY_INTEGER` | Get database initialization parameter settings.              |
+| `GET_TIME`                                                                                                     | Function              | `NUMBER`         | Get the current time.                                        |
+| `NAME_TOKENIZE(name, a OUT, b OUT, c OUT, dblink OUT, nextpos OUT)`                                            | Procedure             | n/a              | Parse the given name into its component parts.               |
+| `TABLE_TO_COMMA(tab, tablen OUT, list OUT)`                                                                    | Procedure             | n/a              | Convert a table of names to a comma-delimited list.          |
+
+The following table lists the public variables available in the `DBMS_UTILITY` package.
+
+| Public variables            | Data type     | Value | Description                         |
+| --------------------------- | ------------- | ----- | ----------------------------------- |
+| `inv_error_on_restrictions` | `PLS_INTEGER` | `1`   | Used by the `INVALIDATE` procedure. |
+| `lname_array`               | `TABLE`       |       | For lists of long names.            |
+| `uncl_array`                | `TABLE`       |       | For lists of users and names.       |
+
+<div id="lname_array" class="registered_link"></div>
+
+## LNAME_ARRAY
+
+The `LNAME_ARRAY` is for storing lists of long names including fully qualified names.
+
+```sql
+TYPE lname_array IS TABLE OF VARCHAR2(4000) INDEX BY BINARY_INTEGER;
+```
+
+<div id="uncl_array" class="registered_link"></div>
+
+## UNCL_ARRAY
+
+The `UNCL_ARRAY` is for storing lists of users and names.
+
+```sql
+TYPE uncl_array IS TABLE OF VARCHAR2(227) INDEX BY BINARY_INTEGER;
+```
+
+## ANALYZE_DATABASE, ANALYZE SCHEMA and ANALYZE PART_OBJECT
+
+The `ANALYZE_DATABASE(), ANALYZE_SCHEMA() and ANALYZE_PART_OBJECT()` procedures gather statistics on tables in the database. When you execute the `ANALYZE` statement, Postgres samples the data in a table and records distribution statistics in the `pg_statistics system` table.
+
+`ANALYZE_DATABASE`, `ANALYZE_SCHEMA`, and `ANALYZE_PART_OBJECT` differ primarily in the number of tables that are processed:
+
+-   `ANALYZE_DATABASE` analyzes all tables in all schemas in the current database.
+-   `ANALYZE_SCHEMA` analyzes all tables in a given schema (in the current database).
+-   `ANALYZE_PART_OBJECT` analyzes a single table.
+
+The syntax for the `ANALYZE` commands are:
+
+```sql
+ANALYZE_DATABASE(<method> VARCHAR2 [, <estimate_rows> NUMBER
+  [, <estimate_percent> NUMBER [, <method_opt> VARCHAR2 ]]])
+
+ANALYZE_SCHEMA(<schema> VARCHAR2, <method> VARCHAR2
+  [, <estimate_rows> NUMBER [, <estimate_percent> NUMBER
+  [, <method_opt> VARCHAR2 ]]])
+
+ANALYZE_PART_OBJECT(<schema> VARCHAR2, <object_name> VARCHAR2
+  [, <object_type> CHAR [, <command_type> CHAR
+  [, <command_opt> VARCHAR2 [, <sample_clause> ]]]])
+```
+
+### Parameters for `ANALYZE_DATABASE` and `ANALYZE_SCHEMA`
+
+`method`
+
+  Determines whether the `ANALYZE` procedure populates the `pg_statistics` table or removes entries from the `pg_statistics` table. If you specify a method of `DELETE`, the `ANALYZE` procedure removes the relevant rows from `pg_statistics`. If you specify a method of `COMPUTE` or `ESTIMATE`, the `ANALYZE` procedure analyzes a table (or multiple tables) and records the distribution information in `pg_statistics`. There's no difference between `COMPUTE` and `ESTIMATE`. Both methods execute the Postgres `ANALYZE` statement. All other parameters are validated and then ignored.
+
+`estimate_rows`
+
+ Number of rows upon which to base estimated statistics. One of `estimate_rows` or `estimate_percent` must be specified if the method is `ESTIMATE`.
+
+ This argument is ignored but is included for compatibility.
+
+`estimate_percent`
+
+ Percentage of rows upon which to base estimated statistics. One of `estimate_rows` or `estimate_percent` must be specified if the method is `ESTIMATE`.
+
+ This argument is ignored but is included for compatibility.
+
+`method_opt`
+
+ Object types to analyze. Any combination of the following:
+
+```text
+[ FOR TABLE ]
+
+[ FOR ALL [ INDEXED ] COLUMNS ] [ SIZE n ]
+
+[ FOR ALL INDEXES ]
+```
+
+ This argument is ignored but is included for compatibility.
+
+### Parameters for `ANALYZE_PART_OBJECT`
+
+`schema`
+
+ Name of the schema whose objects to analyze.
+
+`object_name`
+
+ Name of the partitioned object to analyze.
+
+`object_type`
+
+ Type of object to analyze. Valid values are: `T` – table, `I` – index.
+
+ This argument is ignored but is included for compatibility.
+
+`command_type`
+
+ Type of analyze functionality to perform. Valid values are: 
+ -  `E` &mdash; Gather estimated statistics based on a specified number of rows or a percentage of rows in the `sample_clause` clause. 
+ -  `C` &mdash; Compute exact statistics. 
+ -  `V` &mdash; Validate the structure and integrity of the partitions.
+
+ This argument is ignored but is included for compatibility.
+
+`command_opt`
+
+ For `command_type` `C` or `E`, can be any combination of:
+
+```text
+[ FOR TABLE ]
+
+[ FOR ALL COLUMNS ]
+
+[ FOR ALL LOCAL INDEXES ]
+```
+
+ For `command_type V`, can be `CASCADE` if `object_type` is `T`.
+
+ This argument is ignored but is included for compatibility.
+
+`sample_clause`
+
+ If `command_type` is `E`, contains the following clause to specify the number of rows or percentage of rows on which to base the estimate.
+
+ `SAMPLE n { ROWS | PERCENT }`
+
+ This argument is ignored but is included for compatibility.
+
+## CANONICALIZE
+
+The `CANONICALIZE` procedure performs the following operations on an input string:
+
+-   If the string isn't double quoted, verifies that it uses the characters of a legal identifier. If not, an exception is thrown. If the string is double quoted, all characters are allowed.
+-   If the string isn't double quoted and doesn't contain periods, uppercases all alphabetic characters and eliminates leading and trailing spaces.
+-   If the string is double quoted and doesn't contain periods, strips off the double quotes.
+-   If the string contains periods and no portion of the string is double quoted, uppercases each portion of the string and encloses each portion in double quotes.
+-   If the string contains periods and portions of the string are double quoted, returns: 
+    -  The double-quoted portions unchanged, including the double quotes
+    -  The non-double-quoted portions uppercased and enclosed in double quotes.
+
+```sql
+CANONICALIZE(<name> VARCHAR2, <canon_name> OUT VARCHAR2,
+  <canon_len> BINARY_INTEGER)
+```
+
+### Parameters
+
+`name`
+
+ String to canonicalize.
+
+`canon_name`
+
+ The canonicalized string.
+
+`canon_len`
+
+ Number of bytes in `name` to canonicalize starting from the first character.
+
+### Examples
+
+This procedure applies the `CANONICALIZE` procedure on its input parameter and displays the results.
+
+```sql
+CREATE OR REPLACE PROCEDURE canonicalize (
+    p_name      VARCHAR2,
+    p_length    BINARY_INTEGER DEFAULT 30
+)
+IS
+    v_canon     VARCHAR2(100);
+BEGIN
+    DBMS_UTILITY.CANONICALIZE(p_name,v_canon,p_length);
+    DBMS_OUTPUT.PUT_LINE('Canonicalized name ==>' || v_canon || '<==');
+    DBMS_OUTPUT.PUT_LINE('Length: ' || LENGTH(v_canon));
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+EXEC canonicalize('Identifier')
+Canonicalized name ==>IDENTIFIER<==
+Length: 10
+
+EXEC canonicalize('"Identifier"')
+Canonicalized name ==>Identifier<==
+Length: 10
+
+EXEC canonicalize('"_+142%"')
+Canonicalized name ==>_+142%<==
+Length: 6
+
+EXEC canonicalize('abc.def.ghi')
+Canonicalized name ==>"ABC"."DEF"."GHI"<==
+Length: 17
+
+EXEC canonicalize('"abc.def.ghi"')
+Canonicalized name ==>abc.def.ghi<==
+Length: 11
+
+EXEC canonicalize('"abc".def."ghi"')
+Canonicalized name ==>"abc"."DEF"."ghi"<==
+Length: 17
+
+EXEC canonicalize('"abc.def".ghi')
+Canonicalized name ==>"abc.def"."GHI"<==
+Length: 15
+```
+
+## COMMA_TO_TABLE
+
+The `COMMA_TO_TABLE` procedure converts a comma-delimited list of names into a table of names. Each entry in the list becomes a table entry. Format the names as valid identifiers.
+
+```sql
+COMMA_TO_TABLE(<list> VARCHAR2, <tablen> OUT BINARY_INTEGER,
+  <tab> OUT { LNAME_ARRAY | UNCL_ARRAY })
+```
+
+### Parameters
+
+`list`
+
+ Comma-delimited list of names.
+
+`tablen`
+
+ Number of entries in `tab`.
+
+`tab`
+
+ Table containing the individual names in `list`.
+
+`LNAME_ARRAY`
+
+ A `DBMS_UTILITY LNAME_ARRAY`, as described in [LNAME_ARRAY](#lname_array).
+
+`UNCL_ARRAY`
+
+ A `DBMS_UTILITY UNCL_ARRAY`, as described in [UNCL_ARRAY](#uncl_array).
+
+### Examples
+
+This procedure uses the `COMMA_TO_TABLE` procedure to convert a list of names to a table. It then displays the table entries.
+
+```sql
+CREATE OR REPLACE PROCEDURE comma_to_table (
+    p_list      VARCHAR2
+)
+IS
+    r_lname     DBMS_UTILITY.LNAME_ARRAY;
+    v_length    BINARY_INTEGER;
+BEGIN
+    DBMS_UTILITY.COMMA_TO_TABLE(p_list,v_length,r_lname);
+    FOR i IN 1..v_length LOOP
+        DBMS_OUTPUT.PUT_LINE(r_lname(i));
+    END LOOP;
+END;
+
+EXEC comma_to_table('edb.dept, edb.emp, edb.jobhist')
+
+edb.dept
+edb.emp
+edb.jobhist
+```
+
+## DB_VERSION
+
+The `DB_VERSION` procedure returns the version number of the database.
+
+```sql
+DB_VERSION(<version> OUT VARCHAR2, <compatibility> OUT VARCHAR2)
+```
+
+### Parameters
+
+`version`
+
+ Database version number.
+
+`compatibility`
+
+ Compatibility setting of the database (to be implementation-defined as to its meaning).
+
+### Examples
+
+The following anonymous block displays the database version information.
+
+
+```sql
+DECLARE
+    v_version       VARCHAR2(150);
+    v_compat        VARCHAR2(150);
+BEGIN
+    DBMS_UTILITY.DB_VERSION(v_version,v_compat);
+    DBMS_OUTPUT.PUT_LINE('Version: '       || v_version);
+    DBMS_OUTPUT.PUT_LINE('Compatibility: ' || v_compat);
+END;
+
+Version: PostgreSQL 15.2 (EnterpriseDB Advanced Server 15.2.0 (Debian 15.2.0-1.bullseye)) on x86_64-pc-linux-gnu, 
+compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
+Compatibility: PostgreSQL 15.2 (EnterpriseDB Advanced Server 15.2.0 (Debian 15.2.0-1.bullseye)) on x86_64-pc-linux-gnu, 
+compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
+```
+
+## EXEC_DDL_STATEMENT
+
+`EXEC_DDL_STATEMENT` executes a `DDL` command.
+
+```sql
+EXEC_DDL_STATEMENT(<parse_string> VARCHAR2)
+```
+
+### Parameters
+
+`parse_string`
+
+ The DDL command to execute.
+
+### Examples
+
+The following anonymous block creates the `job` table.
+
+```sql
+BEGIN
+    DBMS_UTILITY.EXEC_DDL_STATEMENT(
+        'CREATE TABLE job (' ||
+          'jobno NUMBER(3),' ||
+          'jname VARCHAR2(9))'
+    );
+END;
+```
+
+If the `parse_string` doesn't include a valid DDL statement, EDB Postgres Advanced Server returns an error:
+
+```sql
+edb=#  exec dbms_utility.exec_ddl_statement('select rownum from dual');
+ERROR:  EDB-20001: 'parse_string' must be a valid DDL statement
+```
+
+In this case, EDB Postgres Advanced Server's behavior differs from Oracle's. Oracle accepts the invalid `parse_string` without complaint.
+
+## EXPAND_SQL_TEXT
+
+The `EXPAND_SQL_TEXT` function returns an expanded version of a given SQL query by replacing view references with its definition. 
+
+```sql
+DBMS_UTILITY.EXPAND_SQL_TEXT(<input_sql_text> CLOB, <output_sql_text> OUT CLOB)
+```
+
+### Parameters 
+
+`input_sql_text`
+ 
+ The SQL query to expand. 
+
+`output_sql_text`
+
+ The expanded version of the given SQL query.
+
+### Example
+
+The following anonymous block returns an expanded version of the SQL query `SELECT * from vemp`: 
+
+```sql
+BEGIN
+DBMS_UTILITY.expand_sql_text (    input_sql_text  => 'SELECT * from vemp',    output_sql_text => result  );
+DBMS_OUTPUT.put_line(result);
+END;
+ SELECT empno,
+    ename,
+    job,
+    mgr,
+    hiredate,
+    sal,
+    comm,
+    deptno
+   FROM ( SELECT emp.empno,
+            emp.ename,
+            emp.job,
+            emp.mgr,
+            emp.hiredate,
+            emp.sal,
+            emp.comm,
+            emp.deptno
+           FROM emp) vemp
+
+EDB-SPL Procedure successfully completed
+```
+
+## FORMAT_CALL_STACK
+
+The `FORMAT_CALL_STACK` function returns the formatted contents of the current call stack.
+
+```sql
+DBMS_UTILITY.FORMAT_CALL_STACK
+return VARCHAR2
+```
+
+You can use this function in a stored procedure, function, or package to return the current call stack in a readable format. This function is useful for debugging.
+
+## FORMAT_ERROR_BACKTRACE
+
+The `FORMAT_ERROR_BACKTRACE` function returns the current error call stack, that is, function name and lines that lead up to the exception.
+
+```sql
+DBMS_UTILITY.FORMAT_ERROR_BACKTRACE
+return VARCHAR2
+```
+
+You can use this function in a stored procedure, function, or package to return the current error call backtrace in a readable format. This function is useful for debugging.
+
+## FORMAT_ERROR_STACK
+
+The `FORMAT_ERROR_STACK` function returns the current exception name.
+
+```sql
+DBMS_UTILITY.FORMAT_ERROR_STACK
+return VARCHAR2
+```
+
+You can use this function in a stored procedure, function, or package to return the current exception name. This function is useful for debugging.
+
+!!! Note
+    The output of the functions `FORMAT_ERROR_STACK` and `FORMAT_ERROR_BACKTRACE` is partially compatible with Oracle. However, it eases the migration from Oracle to EPAS.
+
+## GET_CPU_TIME
+
+The `GET_CPU_TIME` function returns the CPU time in hundredths of a second from some arbitrary point in time.
+
+```sql
+<cputime> NUMBER GET_CPU_TIME
+```
+
+### Parameters
+
+`cputime`
+
+ Number of hundredths of a second of CPU time.
+
+### Examples
+
+This `SELECT` command retrieves the current CPU time, which is 603 hundredths of a second or .0603 seconds.
+
+```sql
+SELECT DBMS_UTILITY.GET_CPU_TIME FROM DUAL;
+__OUTPUT__
+get_cpu_time
+--------------
+        603
+```
+
+## GET_DEPENDENCY
+
+The `GET_DEPENDENCY` procedure lists the objects that depend on the specified object. `GET_DEPENDENCY` doesn't show dependencies for functions or procedures.
+
+```sql
+GET_DEPENDENCY(<type> VARCHAR2, <schema> VARCHAR2,
+  <name> VARCHAR2)
+```
+
+### Parameters
+
+`type`
+
+ The object type of `name`. Valid values are `INDEX`, `PACKAGE`, `PACKAGE BODY`, `SEQUENCE`, `TABLE`, `TRIGGER`, `TYPE`, and `VIEW`.
+
+`schema`
+
+ Name of the schema in which `name` exists.
+
+`name`
+
+ Name of the object for which to obtain dependencies.
+
+### Examples
+
+The following anonymous block finds dependencies on the `EMP` table:
+
+```sql
+BEGIN
+    DBMS_UTILITY.GET_DEPENDENCY('TABLE','public','EMP');
+END;
+__OUTPUT__
+DEPENDENCIES ON public.EMP
+------------------------------------------------------------------
+*TABLE public.EMP()
+*   CONSTRAINT c public.emp()
+*   CONSTRAINT f public.emp()
+*   CONSTRAINT p public.emp()
+*   TYPE public.emp()
+*   CONSTRAINT c public.emp()
+*   CONSTRAINT f public.jobhist()
+*   VIEW .empname_view()
+```
+
+## GET_HASH_VALUE
+
+The `GET_HASH_VALUE` function computes a hash value for a given string.
+
+```sql
+<hash> NUMBER GET_HASH_VALUE(<name> VARCHAR2, <base> NUMBER,
+   <hash_size> NUMBER)
+```
+
+### Parameters
+
+`name`
+
+ The string for which to compute a hash value.
+
+`base`
+
+ Starting value at which to generate hash values.
+
+`hash_size`
+
+ The number of hash values for the desired hash table.
+
+`hash`
+
+ The generated hash value.
+
+### Examples
+
+The following anonymous block creates a table of hash values using the `ename` column of the `emp` table and then displays the key along with the hash value. The hash values start at 100 with a maximum of 1024 distinct values.
+
+```sql
+DECLARE
+    v_hash          NUMBER;
+    TYPE hash_tab IS TABLE OF NUMBER INDEX BY VARCHAR2(10);
+    r_hash          HASH_TAB;
+    CURSOR emp_cur IS SELECT ename FROM emp;
+BEGIN
+    FOR r_emp IN emp_cur LOOP
+        r_hash(r_emp.ename) :=
+            DBMS_UTILITY.GET_HASH_VALUE(r_emp.ename,100,1024);
+    END LOOP;
+    FOR r_emp IN emp_cur LOOP
+        DBMS_OUTPUT.PUT_LINE(RPAD(r_emp.ename,10) || ' ' ||
+            r_hash(r_emp.ename));
+    END LOOP;
+END;
+
+SMITH      377
+ALLEN      740
+WARD       718
+JONES      131
+MARTIN     176
+BLAKE      568
+CLARK      621
+SCOTT      1097
+KING       235
+TURNER     850
+ADAMS      156
+JAMES      942
+FORD       775
+MILLER     148
+```
+
+## GET_PARAMETER_VALUE
+
+The `GET_PARAMETER_VALUE` procedure retrieves database initialization parameter settings.
+
+```sql
+<status> BINARY_INTEGER GET_PARAMETER_VALUE(<parnam> VARCHAR2,
+   <intval> OUT INTEGER, <strval> OUT VARCHAR2)
+```
+
+### Parameters
+
+`parnam`
+
+ Name of the parameter whose value to return. The parameters are listed in the `pg_settings` system view.
+
+`intval`
+
+ Value of an integer parameter or the length of `strval`.
+
+`strval`
+
+ Value of a string parameter.
+
+`status`
+
+ Returns `0` if the parameter value is `INTEGER` or `BOOLEAN`. Returns `1` if the parameter value is a string.
+
+### Examples
+
+The following anonymous block shows the values of two initialization parameters.
+
+```sql
+DECLARE
+    v_intval        INTEGER;
+    v_strval        VARCHAR2(80);
+BEGIN
+    DBMS_UTILITY.GET_PARAMETER_VALUE('max_fsm_pages', v_intval, v_strval);
+    DBMS_OUTPUT.PUT_LINE('max_fsm_pages' || ': ' || v_intval);
+    DBMS_UTILITY.GET_PARAMETER_VALUE('client_encoding', v_intval, v_strval);
+    DBMS_OUTPUT.PUT_LINE('client_encoding' || ': ' || v_strval);
+END;
+
+max_fsm_pages: 72625
+client_encoding: SQL_ASCII
+```
+
+## GET_TIME
+
+The `GET_TIME` function returns the current time in hundredths of a second.
+
+```sql
+<time> NUMBER GET_TIME
+```
+
+### Parameters
+
+`time`
+
+ Number of hundredths of a second from the time when the program started.
+
+### Examples
+
+This example shows calls to the `GET_TIME` function.
+
+```sql
+SELECT DBMS_UTILITY.GET_TIME FROM DUAL;
+__OUTPUT__
+ get_time
+----------
+  1555860
+```
+```sql
+SELECT DBMS_UTILITY.GET_TIME FROM DUAL;
+__OUTPUT__
+ get_time
+----------
+  1556037
+```
+
+## NAME_TOKENIZE
+
+The `NAME_TOKENIZE` procedure parses a name into its component parts. Names without double quotes are uppercased. The double quotes are stripped from names with double quotes.
+
+```sql
+NAME_TOKENIZE(<name> VARCHAR2, <a> OUT VARCHAR2,
+  <b> OUT VARCHAR2, <c> OUT VARCHAR2, <dblink> OUT VARCHAR2,
+  <nextpos> OUT BINARY_INTEGER)
+```
+
+### Parameters
+
+`name`
+
+ String containing a name in the following format:
+
+ `a[.b[.c]][@dblink ]`
+
+`a`
+
+ Returns the leftmost component.
+
+`b`
+
+ Returns the second component, if any.
+
+`c`
+
+ Returns the third component, if any.
+
+`dblink`
+
+ Returns the database link name.
+
+`nextpos`
+
+ Position of the last character parsed in name.
+
+### Examples
+
+This stored procedure displays the returned parameter values of the `NAME_TOKENIZE` procedure for various names.
+
+```sql
+CREATE OR REPLACE PROCEDURE name_tokenize (
+    p_name          VARCHAR2
+)
+IS
+    v_a             VARCHAR2(30);
+    v_b             VARCHAR2(30);
+    v_c             VARCHAR2(30);
+    v_dblink        VARCHAR2(30);
+    v_nextpos       BINARY_INTEGER;
+BEGIN
+    DBMS_UTILITY.NAME_TOKENIZE(p_name,v_a,v_b,v_c,v_dblink,v_nextpos);
+    DBMS_OUTPUT.PUT_LINE('name   : ' || p_name);
+    DBMS_OUTPUT.PUT_LINE('a      : ' || v_a);
+    DBMS_OUTPUT.PUT_LINE('b      : ' || v_b);
+    DBMS_OUTPUT.PUT_LINE('c      : ' || v_c);
+    DBMS_OUTPUT.PUT_LINE('dblink : ' || v_dblink);
+    DBMS_OUTPUT.PUT_LINE('nextpos: ' || v_nextpos);
+END;
+```
+
+Tokenize the name, `emp`:
+
+```sql
+BEGIN
+    name_tokenize('emp');
+END;
+
+name   : emp
+a      : EMP
+b      :
+c      :
+dblink :
+nextpos: 3
+```
+
+Tokenize the name, `edb.list_emp`:
+
+```sql
+BEGIN
+    name_tokenize('edb.list_emp');
+END;
+
+name   : edb.list_emp
+a      : EDB
+b      : LIST_EMP
+c      :
+dblink :
+nextpos: 12
+```
+
+Tokenize the name, `"edb"."Emp_Admin".update_emp_sal`:
+
+```sql
+BEGIN
+    name_tokenize('"edb"."Emp_Admin".update_emp_sal');
+END;
+
+name   : "edb"."Emp_Admin".update_emp_sal
+a      : edb
+b      : Emp_Admin
+c      : UPDATE_EMP_SAL
+dblink :
+nextpos: 32
+```
+
+Tokenize the name `edb.emp@edb_dblink`:
+
+```sql
+BEGIN
+    name_tokenize('edb.emp@edb_dblink');
+END;
+
+name   : edb.emp@edb_dblink
+a      : EDB
+b      : EMP
+c      :
+dblink : EDB_DBLINK
+nextpos: 18
+```
+
+## TABLE_TO_COMMA
+
+The `TABLE_TO_COMMA` procedure converts table of names into a comma-delimited list of names. Each table entry becomes a list entry. Format the names as valid identifiers.
+
+```sql
+TABLE_TO_COMMA(<tab> { LNAME_ARRAY | UNCL_ARRAY },
+  <tablen> OUT BINARY_INTEGER, <list> OUT VARCHAR2)
+```
+
+### Parameters
+
+`tab`
+
+ Table containing names.
+
+`LNAME_ARRAY`
+
+ A `DBMS_UTILITY LNAME_ARRAY`, as described in [LNAME ARRAY](#lname_array).
+
+`UNCL_ARRAY`
+
+ A `DBMS_UTILITY UNCL_ARRAY`, as described [UNCL_ARRAY](#uncl_array).
+
+`tablen`
+
+ Number of entries in `list`.
+
+`list`
+
+ Comma-delimited list of names from `tab`.
+
+### Examples
+
+This example first uses the `COMMA_TO_TABLE` procedure to convert a comma-delimited list to a table. The `TABLE_TO_COMMA` procedure then converts the table back to a comma-delimited list that it displays.
+
+```sql
+CREATE OR REPLACE PROCEDURE table_to_comma (
+    p_list      VARCHAR2
+)
+IS
+    r_lname     DBMS_UTILITY.LNAME_ARRAY;
+    v_length    BINARY_INTEGER;
+    v_listlen   BINARY_INTEGER;
+    v_list      VARCHAR2(80);
+BEGIN
+    DBMS_UTILITY.COMMA_TO_TABLE(p_list,v_length,r_lname);
+    DBMS_OUTPUT.PUT_LINE('Table Entries');
+    DBMS_OUTPUT.PUT_LINE('-------------');
+    FOR i IN 1..v_length LOOP
+        DBMS_OUTPUT.PUT_LINE(r_lname(i));
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('-------------');
+    DBMS_UTILITY.TABLE_TO_COMMA(r_lname,v_listlen,v_list);
+    DBMS_OUTPUT.PUT_LINE('Comma-Delimited List: ' || v_list);
+END;
+
+EXEC table_to_comma('edb.dept, edb.emp, edb.jobhist')
+
+Table Entries
+-------------
+edb.dept
+edb.emp
+edb.jobhist
+-------------
+Comma-Delimited List: edb.dept, edb.emp, edb.jobhist
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/01_base64_decode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/01_base64_decode.mdx
new file mode 100644
index 00000000000..62cef76d647
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/01_base64_decode.mdx
@@ -0,0 +1,50 @@
+---
+title: "BASE64_DECODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/01_base64_decode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `BASE64_DECODE` function to translate a Base64 encoded string to the original value originally encoded by `BASE64_ENCODE`. The signature is:
+
+```sql
+BASE64_DECODE (<r> IN RAW)
+```
+
+This function returns a `RAW` value.
+
+## Parameters
+
+`r`
+
+ `r` is the string that contains the Base64 encoded data to translate to `RAW` form.
+
+## Examples
+
+Before executing the following example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command instructs the server to escape any non-printable characters and to display `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+<https://www.postgresql.org/docs/current/static/datatype-binary.html>
+
+This example encodes and then decodes a string that contains the SQL abc. It uses `BASE64_ENCODE` for encoding and `BASE64_DECODE` for decoding.
+
+```sql
+edb=# SELECT UTL_ENCODE.BASE64_ENCODE(CAST ('abc' AS RAW));
+__OUTPUT__
+ base64_encode
+---------------
+ YWJj
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.BASE64_DECODE(CAST ('YWJj' AS RAW));
+__OUTPUT__
+ base64_decode
+---------------
+ abc
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/02_base64_encode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/02_base64_encode.mdx
new file mode 100644
index 00000000000..033aff33389
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/02_base64_encode.mdx
@@ -0,0 +1,58 @@
+---
+title: "BASE64_ENCODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/02_base64_encode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `BASE64_ENCODE` function to translate and encode a string in Base64 format, as described in RFC 4648. This function can be useful when composing `MIME` email that you intend to send using the `UTL_SMTP` package. The `BASE64_ENCODE` function has two signatures:
+
+```sql
+BASE64_ENCODE(<r> IN RAW)
+```
+
+and
+
+```sql
+BASE64_ENCODE(<loid> IN OID)
+```
+
+This function returns a `RAW` value or an `OID`.
+
+## Parameters
+
+`r`
+
+ `r` specifies the `RAW` string to translate to Base64.
+
+`loid`
+
+ `loid` specifies the object ID of a large object to translate to Base64.
+
+## Examples
+
+Before executing the example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command instructs the server to escape any nonprintable characters and to display `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+This example first encodes a string that contains the text `abc` using `BASE64_ENCODE` and then decodes the string using `BASE64_DECODE`: 
+
+```sql
+edb=# SELECT UTL_ENCODE.BASE64_ENCODE(CAST ('abc' AS RAW));
+__OUTPUT__
+ base64_encode
+---------------
+ YWJj
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.BASE64_DECODE(CAST ('YWJj' AS RAW));
+__OUTPUT__
+ base64_decode
+---------------
+ abc
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/03_mimeheader_decode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/03_mimeheader_decode.mdx
new file mode 100644
index 00000000000..1a56aa3f2f6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/03_mimeheader_decode.mdx
@@ -0,0 +1,41 @@
+---
+title: "MIMEHEADER_DECODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/03_mimeheader_decode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `MIMEHEADER_DECODE` function to decode values that are encoded by the `MIMEHEADER_ENCODE` function. The signature is:
+
+```sql
+MIMEHEADER_DECODE(<buf> IN VARCHAR2)
+```
+
+This function returns a `VARCHAR2` value.
+
+## Parameters
+
+`buf`
+
+ `buf` contains the value encoded by `MIMEHEADER_ENCODE` to decode.
+
+## Examples
+
+These examples use the `MIMEHEADER_ENCODE` and `MIMEHEADER_DECODE` functions to first encode and then decode a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.MIMEHEADER_ENCODE('What is the date?') FROM DUAL;
+__OUTPUT__
+      mimeheader_encode
+------------------------------
+ =?UTF8?Q?What is the date??=
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.MIMEHEADER_DECODE('=?UTF8?Q?What is the date??=')
+FROM DUAL;
+__OUTPUT__
+ mimeheader_decode
+-------------------
+ What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/04_mimeheader_encode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/04_mimeheader_encode.mdx
new file mode 100644
index 00000000000..73fafc1194f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/04_mimeheader_encode.mdx
@@ -0,0 +1,53 @@
+---
+title: "MIMEHEADER_ENCODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/04_mimeheader_encode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `MIMEHEADER_ENCODE` function to convert a string into mime header format and then encode the string. The signature is:
+
+```sql
+MIMEHEADER_ENCODE(<buf> IN VARCHAR2, <encode_charset> IN VARCHAR2
+DEFAULT NULL, <encoding> IN INTEGER DEFAULT NULL)
+```
+
+This function returns a `VARCHAR2` value.
+
+## Parameters
+
+`buf`
+
+ `buf` contains the string to format and encode. The string is a `VARCHAR2` value.
+
+`encode_charset`
+
+ `encode_charset` specifies the character set to which to convert the string before formatting and encoding it. The default value is `NULL`.
+
+`encoding`
+
+ `encoding` specifies the encoding type used when encoding the string. You can specify:
+
+-   `Q` to enable quoted-printable encoding. If you don't specify a value, `MIMEHEADER_ENCODE` uses quoted-printable encoding.
+-   `B` to enable base-64 encoding.
+
+## Examples
+
+These example use the `MIMEHEADER_ENCODE` and `MIMEHEADER_DECODE` functions to first encode and then decode a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.MIMEHEADER_ENCODE('What is the date?') FROM DUAL;
+__OUTPUT__
+      mimeheader_encode
+------------------------------
+ =?UTF8?Q?What is the date??=
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.MIMEHEADER_DECODE('=?UTF8?Q?What is the date??=')
+FROM DUAL;
+__OUTPUT__
+ mimeheader_decode
+-------------------
+ What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/05_quoted_printable_decode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/05_quoted_printable_decode.mdx
new file mode 100644
index 00000000000..bd02684763b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/05_quoted_printable_decode.mdx
@@ -0,0 +1,50 @@
+---
+title: "QUOTED_PRINTABLE_DECODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/05_quoted_printable_decode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `QUOTED_PRINTABLE_DECODE` function to translate an encoded quoted-printable string into a decoded `RAW` string.
+
+The signature is:
+
+```sql
+QUOTED_PRINTABLE_DECODE(<r> IN RAW)
+```
+
+This function returns a `RAW` value.
+
+## Parameters
+
+`r`
+
+ `r` contains the encoded string to decode. The string is a `RAW` value encoded by `QUOTED_PRINTABLE_ENCODE`.
+
+## Examples
+
+Before executing the example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command escapes any nonprintable characters and displays `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+This example first encodes and then decodes a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.QUOTED_PRINTABLE_ENCODE('E=mc2') FROM DUAL;
+__OUTPUT__
+quoted_printable_encode
+-------------------------
+ E=3Dmc2
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.QUOTED_PRINTABLE_DECODE('E=3Dmc2') FROM DUAL;
+__OUTPUT__
+ quoted_printable_decode
+-------------------------
+ E=mc2
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/06_quoted_printable_encode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/06_quoted_printable_encode.mdx
new file mode 100644
index 00000000000..c5f2138a159
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/06_quoted_printable_encode.mdx
@@ -0,0 +1,48 @@
+---
+title: "QUOTED_PRINTABLE_ENCODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/06_quoted_printable_encode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `QUOTED_PRINTABLE_ENCODE` function to translate and encode a string in quoted-printable format. The signature is:
+
+```sql
+QUOTED_PRINTABLE_ENCODE(<r> IN RAW)
+```
+
+This function returns a `RAW` value.
+
+## Parameters
+
+`r`
+
+ `r` contains the string (a `RAW` value) to encode in a quoted-printable format.
+
+## Examples
+
+Before executing the example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command escapes any nonprintable characters and displays `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+This example first encodes and then decodes a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.QUOTED_PRINTABLE_ENCODE('E=mc2') FROM DUAL;
+__OUTPUT__
+quoted_printable_encode
+-------------------------
+ E=3Dmc2
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.QUOTED_PRINTABLE_DECODE('E=3Dmc2') FROM DUAL;
+__OUTPUT__
+ quoted_printable_decode
+-------------------------
+ E=mc2
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/07_text_decode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/07_text_decode.mdx
new file mode 100644
index 00000000000..86184305906
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/07_text_decode.mdx
@@ -0,0 +1,54 @@
+---
+title: "TEXT_DECODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/07_text_decode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `TEXT_DECODE` function to translate and decode an encoded string to the `VARCHAR2` value that was originally encoded by the `TEXT_ENCODE` function. The signature is:
+
+```sql
+TEXT_DECODE(<buf> IN VARCHAR2, <encode_charset> IN VARCHAR2 DEFAULT
+NULL, <encoding> IN PLS_INTEGER DEFAULT NULL)
+```
+
+This function returns a `VARCHAR2` value.
+
+## Parameters
+
+`buf`
+
+ `buf` contains the encoded string to translate to the original value encoded by `TEXT_ENCODE`.
+
+`encode_charset`
+
+ `encode_charset` specifies the character set to which to translate the string before encoding. The default value is `NULL`.
+
+`encoding`
+
+ `encoding` specifies the encoding type used by `TEXT_DECODE`. Specify:
+
+-   `UTL_ENCODE.BASE64` to specify base-64 encoding.
+-   `UTL_ENCODE.QUOTED_PRINTABLE` to specify quoted printable encoding. This is the default.
+
+## Examples
+
+This example uses the `TEXT_ENCODE` and `TEXT_DECODE` functions to first encode and then decode a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.TEXT_ENCODE('What is the date?', 'BIG5',
+UTL_ENCODE.BASE64) FROM DUAL;
+__OUTPUT__
+       text_encode
+--------------------------
+V2hhdCBpcyB0aGUgZGF0ZT8=
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.TEXT_DECODE('V2hhdCBpcyB0aGUgZGF0ZT8=', 'BIG5',
+UTL_ENCODE.BASE64) FROM DUAL;
+__OUTPUT__
+    text_decode
+-------------------
+What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/08_text_encode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/08_text_encode.mdx
new file mode 100644
index 00000000000..1e8749756de
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/08_text_encode.mdx
@@ -0,0 +1,54 @@
+---
+title: "TEXT_ENCODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/08_text_encode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `TEXT_ENCODE` function to translate a string to a user-specified character set and then encode the string. The signature is:
+
+```sql
+TEXT_DECODE(<buf> IN VARCHAR2, <encode_charset> IN VARCHAR2 DEFAULT
+NULL, <encoding> IN PLS_INTEGER DEFAULT NULL)
+```
+
+This function returns a `VARCHAR2` value.
+
+## Parameters
+
+`buf`
+
+ `buf` contains the encoded string to translate to the specified character set and encode with `TEXT_ENCODE`.
+
+`encode_charset`
+
+ `encode_charset` specifies the character set to which to translate the value before encoding. The default value is `NULL`.
+
+`encoding`
+
+ `encoding` specifies the encoding type used by `TEXT_ENCODE`. Specify:
+
+-   `UTL_ENCODE.BASE64` to specify base-64 encoding.
+-   `UTL_ENCODE.QUOTED_PRINTABLE` to specify quoted printable encoding. This is the default.
+
+## Examples
+
+This example uses the `TEXT_ENCODE` and `TEXT_DECODE` functions to first encode and then decode a string:
+
+```sql
+edb=# SELECT UTL_ENCODE.TEXT_ENCODE('What is the date?', 'BIG5',
+UTL_ENCODE.BASE64) FROM DUAL;
+__OUTPUT__
+       text_encode
+--------------------------
+V2hhdCBpcyB0aGUgZGF0ZT8=
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.TEXT_DECODE('V2hhdCBpcyB0aGUgZGF0ZT8=', 'BIG5',
+UTL_ENCODE.BASE64) FROM DUAL;
+__OUTPUT__
+    text_decode
+-------------------
+What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/09_uudecode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/09_uudecode.mdx
new file mode 100644
index 00000000000..f011c62a078
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/09_uudecode.mdx
@@ -0,0 +1,58 @@
+---
+title: "UUDECODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/09_uudecode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `UUDECODE` function to translate and decode a uuencode encoded string to the `RAW` value that was originally encoded by the `UUENCODE` function. The signature is:
+
+```sql
+UUDECODE(<r> IN RAW)
+```
+
+This function returns a `RAW` value.
+
+If you're using the EDB Postgres Advanced Server `UUDECODE` function to decode uuencoded data that was created by the Oracle implementation of the `UTL_ENCODE.UUENCODE` function, then you must first set the EDB Postgres Advanced Server configuration parameter `utl_encode.uudecode_redwood` to `TRUE` before invoking the EDB Postgres Advanced Server `UUDECODE` function on the Oracle-created data. For example, this situation might occur if you migrated Oracle tables containing uuencoded data to an EDB Postgres Advanced Server database.
+
+The uuencoded data created by the Oracle version of the `UUENCODE` function results in a format that differs from the uuencoded data created by the EDB Postgres Advanced Server `UUENCODE` function. As a result, attempting to use the EDB Postgres Advanced Server `UUDECODE` function on the Oracle uuencoded data results in an error unless the configuration parameter `utl_encode.uudecode_redwood` is set to `TRUE`.
+
+However, if you're using the EDB Postgres Advanced Server `UUDECODE` function on uuencoded data created by the EDB Postgres Advanced Server `UUENCODE` function, then `utl_encode.uudecode_redwood` must be set to `FALSE`, which is the default setting.
+
+## Parameters
+
+`r`
+
+ `r` contains the uuencoded string to translate to `RAW`.
+
+## Examples
+
+Before executing the example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command escapes any nonprintable characters and to displays `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+This example uses `UUENCODE` and `UUDECODE` to first encode and then decode a string:
+
+```sql
+edb=# SET bytea_output = escape;
+SET
+edb=# SELECT UTL_ENCODE.UUENCODE('What is the date?') FROM DUAL;
+__OUTPUT__
+                              uuencode
+--------------------------------------------------------------------
+begin 0 uuencode.txt\01215VAA="!I<R!T:&4@9&%T93\\`\012`\012end\012
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.UUDECODE
+edb-# ('begin 0 uuencode.txt\01215VAA="!I<R!T:&4@9&%T93\\`\012`\012end\012')
+edb-# FROM DUAL;
+__OUTPUT__
+     uudecode
+-------------------
+What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/10_uuencode.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/10_uuencode.mdx
new file mode 100644
index 00000000000..a87e2f55e98
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/10_uuencode.mdx
@@ -0,0 +1,72 @@
+---
+title: "UUENCODE"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/10_uuencode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Use the `UUENCODE` function to translate `RAW` data into a uuencode formatted encoded string. The signature is:
+
+```sql
+UUENCODE(<r> IN RAW, <type> IN INTEGER DEFAULT 1, <filename> IN
+VARCHAR2 DEFAULT NULL, <permission> IN VARCHAR2 DEFAULT NULL)
+```
+
+This function returns a `RAW` value.
+
+## Parameters
+
+`r`
+
+ `r` contains the `RAW` string to translate to uuencode format.
+
+`type`
+
+ `type` is an `INTEGER` value or constant that specifies the type of uuencoded string that to return. The default value is `1`. The possible values are:
+
+| Value     | Constant       |
+| --------- | -------------- |
+| `1`       | `complete`     |
+| `2`       | `header_piece` |
+| `3`       | `middle_piece` |
+| `4`       | `end_piece`    |
+
+`filename`
+
+ `filename` is a `VARCHAR2` value that specifies the file name that you want to embed in the encoded form. If you don't specify a file name, `UUENCODE` includes a file name of `uuencode.txt` in the encoded form.
+
+`permission`
+
+ `permission` is a `VARCHAR2` that specifies the permission mode. The default value is `NULL`.
+
+## Examples
+
+Before executing the example, invoke the command:
+
+```sql
+SET bytea_output = escape;
+```
+
+This command escapes any nonprintable characters and displays `BYTEA` or `RAW` values onscreen in readable form. For more information, see the [Postgres core documentation](https://www.postgresql.org/docs/current/static/datatype-binary.html).
+
+This example uses `UUENCODE` and `UUDECODE` to first encode and then decode a string:
+
+```sql
+edb=# SET bytea_output = escape;
+SET
+edb=# SELECT UTL_ENCODE.UUENCODE('What is the date?') FROM DUAL;
+__OUTPUT__
+                              uuencode
+--------------------------------------------------------------------
+ begin 0 uuencode.txt\01215VAA="!I<R!T:&4@9&%T93\\`\012`\012end\012
+(1 row)
+```
+```sql
+edb=# SELECT UTL_ENCODE.UUDECODE
+edb-# ('begin 0 uuencode.txt\01215VAA="!I<R!T:&4@9&%T93\\`\012`\012end\012')
+edb-# FROM DUAL;
+__OUTPUT__
+     uudecode
+-------------------
+ What is the date?
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/index.mdx
new file mode 100644
index 00000000000..75c0a0884f6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/index.mdx
@@ -0,0 +1,32 @@
+---
+title: "UTL_ENCODE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.32.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.205.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.163.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/19_utl_encode/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_ENCODE` package provides a way to encode and decode data. EDB Postgres Advanced Server supports the following functions and procedures:
+
+| Function/procedure                                 | Return type | Description                                                                                                          |
+| -------------------------------------------------- | ----------- | -------------------------------------------------------------------------------------------------------------------- |
+| `BASE64_DECODE(r)`                                 | `RAW`       | Use the `BASE64_DECODE` function to translate a Base64 encoded string to the original `RAW` value.                   |
+| `BASE64_ENCODE(r)`                                 | `RAW`       | Use the `BASE64_ENCODE` function to translate a `RAW` string to an encoded Base64 value.                             |
+| `BASE64_ENCODE(loid)`                              | `TEXT`      | Use the `BASE64_ENCODE` function to translate a `TEXT` string to an encoded Base64 value.                            |
+| `MIMEHEADER_DECODE(buf)`                           | `VARCHAR2`  | Use the `MIMEHEADER_DECODE` function to translate an encoded `MIMEHEADER` formatted string to its original value.   |
+| `MIMEHEADER_ENCODE(buf, encode_charset, encoding)` | `VARCHAR2`  | Use the `MIMEHEADER_ENCODE` function to convert and encode a string in `MIMEHEADER` format.                          |
+| `QUOTED_PRINTABLE_DECODE(r)`                       | `RAW`       | Use the `QUOTED_PRINTABLE_DECODE` function to translate an encoded string to a `RAW` value.                          |
+| `QUOTED_PRINTABLE_ENCODE(r)`                       | `RAW`       | Use the `QUOTED_PRINTABLE_ENCODE` function to translate an input string to a quoted-printable formatted `RAW` value. |
+| `TEXT_DECODE(buf, encode_charset, encoding)`       | `VARCHAR2`  | Use the `TEXT_DECODE` function to decode a string encoded by `TEXT_ENCODE`.                                          |
+| `TEXT_ENCODE(buf, encode_charset, encoding)`       | `VARCHAR2`  | Use the `TEXT_ENCODE` function to translate a string to a user-specified character set, and then encode the string.  |
+| `UUDECODE(r)`                                      | `RAW`       | Use the `UUDECODE` function to translate a uuencode encoded string to a `RAW` value.                                 |
+| `UUENCODE(r, type, filename, permission)`          | `RAW`       | Use the `UUENCODE` function to translate a `RAW` string to an encoded uuencode value.                                |
+
+<div class="toctree" maxdepth="6">
+
+base64_decode base64_encode mimeheader_decode mimeheader_encode quoted_printable_decode quoted_printable_encode text_decode text_encode uudecode uuencode
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/20_utl_file.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/20_utl_file.mdx
new file mode 100644
index 00000000000..fe6c5184dfc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/20_utl_file.mdx
@@ -0,0 +1,1213 @@
+---
+title: "UTL_FILE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.33.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.206.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.164.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/20_utl_file/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_FILE` package reads from and writes to files on the operating system’s file system. A superuser must grant non-superusers `EXECUTE` privilege on the `UTL_FILE` package before they can use any of the functions or procedures in the package. For example, the following command grants the privilege to user `mary`:
+
+```sql
+GRANT EXECUTE ON PACKAGE SYS.UTL_FILE TO mary;
+```
+
+Also, the operating system username `enterprisedb` must have the appropriate read/write permissions on the directories and files that the `UTL_FILE` functions and procedures access. If the required file permissions aren't in place, an exception is thrown in the `UTL_FILE` function or procedure.
+
+A handle to the file to write to or read from is used to reference the file. The *file handle* is defined by a public variable `UTL_FILE.FILE_TYPE` in the `UTL_FILE` package. A variable of type `FILE_TYPE` must be declared to receive the file handle returned by calling the `FOPEN` function. The file handle is then used for all subsequent operations on the file.
+
+References to directories on the file system are done using the directory name or alias that's assigned to the directory using the `CREATE DIRECTORY` command.
+
+The procedures and functions available in the `UTL_FILE` package are listed in the following table.
+
+| Function/procedure                                                             | Return type | Description                                                                                                                                                                      |
+| ------------------------------------------------------------------------------ | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `FCLOSE(file IN OUT)`                                                          | n/a         | Closes the specified file identified by `file`.                                                                                                                                  |
+| `FCLOSE_ALL`                                                                   | n/a         | Closes all open files.                                                                                                                                                           |
+| `FCOPY(location, filename, dest_dir, dest_file [, start_line [, end_line ] ])` | n/a         | Copies `filename` in the directory identified by `location` to file `dest_file` in directory `dest_dir`, from line `start_line` to line `end_line`.               |
+| `FFLUSH(file)`                                                                 | n/a         | Forces data in the buffer to be written to disk in the file identified by `file`.                                                                                                |
+| `FGETATTR(location, filename, exists, file_length, block_size)`                | n/a         | Retrieves the attributes for a file when its `filename` and `location` are given.                                                                                                    |
+| `FGETPOS(file)`                                                                | `INTEGER`   | Returns the relative offset position in the opened file as an integer, in bytes.                                                                                                                             |
+| `FOPEN(location, filename, open_mode [, max_linesize ])`                       | `FILE_TYPE` | Opens file `filename` in the directory identified by `location`.                                                                                                               |
+| `FOPEN_NCHAR(location, filename, open_mode, max_linesize)`                     | `FILE_TYPE` | Opens file `filename` in the directory identified by `location` to read and/or write Unicode character set data.                                                                                                     |
+| `FREMOVE(location, filename)`                                                  | n/a         | Removes the specified file from the file system.                                                                                                                                 |
+| `FRENAME(location, filename, dest_dir, dest_file [, overwrite ])`              | n/a         | Renames the specified file.                                                                                                                                                      |
+| `FSEEK(file, absolute_offset, relative_offset)`                                | n/a         | Moves the file pointer within a given file by the number of bytes specified.                                                                                                                                         |
+| `GET_LINE(file, buffer OUT)`                                                   | n/a         | Reads a line of text into the variable `buffer` from the file identified by `file`.                                                                                                |
+| `GET_RAW(file, buffer OUT [, len ])`                                           | `BYTEA`     | Reads a `RAW` string value from a file, keeps those into read buffer, and adjusts the file pointer accordingly by the number of bytes read, ignoring the end-of-file terminator.  |
+| `IS_OPEN(file)`                                                                | `BOOLEAN`   | Determines whether the given file is open.                                                                                                                                |
+| `NEW_LINE(file [, lines ])`                                                    | n/a         | Writes an end-of-line character sequence into the file.                                                                                                                          |
+| `PUT(file, buffer)`                                                            | n/a         | Writes `buffer` to the given file. `PUT` doesn't write an end-of-line character sequence.                                                                                       |
+| `PUT_LINE(file, buffer)`                                                       | n/a         | Writes `buffer` to the given file. An end-of-line character sequence is added by the `PUT_LINE` procedure.                                                                       |
+| `PUTF(file, format [, arg1 ] [, ...])`                                         | n/a         | Writes a formatted string to the given file. You can specify up to five substitution parameters, `arg1,...arg5`, for replacement in `format`.                                    |
+| `PUT_NCHAR(file, buffer)`                                                      | n/a         | Writes `buffer` to the given file and converts data to Unicode. `PUT` doesn't write an end-of-line character sequence.                                                                  |
+| `PUT_RAW(file, buffer [, autoflush ])`                                         | `BOOLEAN`   | Accepts a `RAW` data value as input and writes those values to the output buffer.                                                                                                |
+
+EDB Postgres Advanced Server's implementation of `UTL_FILE` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in the table are supported.
+
+## UTL_FILE exception codes
+
+If a call to a `UTL_FILE` procedure or function raises an exception, you can use the condition name to catch the exception. The `UTL_FILE` package reports the following exception codes compatible with Oracle databases.
+
+| Exception code     | Condition name        |
+| ------------------ | --------------------- |
+| `-29283`           | `invalid_operation`   |
+| `-29285`           | `write_error`         |
+| `-29284`           | `read_error`          |
+| `-29282`           | `invalid_filehandle`  |
+| `-29287`           | `invalid_maxlinesize` |
+| `-29281`           | `invalid_mode`        |
+| `-29280`           | `invalid_path`        |
+
+## Setting file permissions with utl_file.umask
+
+When a `UTL_FILE` function or procedure creates a file, the following are the default file permissions:
+
+```shell
+-rw------- 1 enterprisedb enterprisedb 21 Jul 24 16:08 utlfile
+```
+
+All permissions are denied on users belonging to the `enterprisedb` group as well as all other users. Only the `enterprisedb` user has read and write permissions on the created file.
+
+If you want to have a different set of file permissions on files created by the `UTL_FILE` functions and procedures, set the `utl_file.umask` configuration parameter.
+
+The `utl_file.umask` parameter sets the *file mode creation mask* (or simply the *mask*) in a manner similar to the Linux `umask` command. This parameter is for use only in the EDB Postgres Advanced Server `UTL_FILE` package.
+
+!!! Note
+    The `utl_file.umask` parameter isn't supported on Windows systems.
+
+The value specified for `utl_file.umask` is a 3- or 4-character octal string that's valid for the Linux `umask` command. The setting determines the permissions on files created by the `UTL_FILE` functions and procedures. (Refer to any information source regarding Linux or Unix systems for information on file permissions and the use of the `umask` command.)
+
+### Example
+
+This example sets the file permissions with `utl_file.umask`.
+
+First, set up the directory in the file system for the `UTL_FILE` package to use. Be sure the applicable operating system account `enterprisedb` or `postgres` can read and write in the directory.
+
+```shell
+mkdir /tmp/utldir
+chmod 777 /tmp/utldir
+```
+
+The `CREATE DIRECTORY` command is issued in `psql` to create the directory database object using the file system directory you created:
+
+```sql
+CREATE DIRECTORY utldir AS '/tmp/utldir';
+```
+
+Set the `utl_file.umask` configuration parameter. The following setting allows the file owner any permission. Group users and other users are permitted any permission except for the execute permission.
+
+```sql
+SET utl_file.umask TO '0011';
+```
+
+In the same session during which the `utl_file.umask` parameter is set to the desired value, run the `UTL_FILE` functions and procedures.
+
+```sql
+DECLARE
+    v_utlfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'utldir';
+    v_filename      VARCHAR2(20) := 'utlfile';
+BEGIN
+    v_utlfile := UTL_FILE.FOPEN(v_directory, v_filename, 'w');
+    UTL_FILE.PUT_LINE(v_utlfile, 'Simple one-line file');
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_utlfile);
+END;
+```
+
+The permission settings on the resulting file show that, in addition to the file owner, group users and other users have read and write permissions on the file.
+
+```shell
+$ pwd
+/tmp/utldir
+$ ls -l
+total 4
+-rw-rw-rw- 1 enterprisedb enterprisedb 21 Jul 24 16:04 utlfile
+```
+
+You can also set this parameter on a per-role basis with the `ALTER ROLE` command. You can set it for a single database with the `ALTER DATABASE` command or for the entire database server instance by setting it in the `postgresql.conf` file.
+
+## FCLOSE
+
+The `FCLOSE` procedure closes an open file.
+
+```sql
+FCLOSE(<file> IN OUT FILE_TYPE)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing a file handle of the file to close.
+
+## FCLOSE_ALL
+
+The `FLCLOSE_ALL` procedures closes all open files. The procedure executes successfully even if there are no open files to close.
+
+```sql
+FCLOSE_ALL
+```
+
+## FCOPY
+
+The `FCOPY` procedure copies text from one file to another.
+
+```sql
+FCOPY(<location> VARCHAR2, <filename> VARCHAR2, <dest_dir> VARCHAR2, <dest_file> VARCHAR2
+  [, <start_line> PLS_INTEGER [, <end_line> PLS_INTEGER ] ])
+```
+
+### Parameters
+
+`location`
+
+ Directory name of the directory containing the file to copy, as stored in `pg_catalog.edb_dir.dirname`.
+
+`filename`
+
+ Name of the source file to copy.
+
+`dest_dir`
+
+ Directory name of the directory to which to copy the file, as stored in `pg_catalog.edb_dir.dirname`.
+
+`dest_file`
+
+ Name of the destination file.
+
+`start_line`
+
+ Line number in the source file from which copying begins. The default is `1`.
+
+`end_line`
+
+ Line number of the last line in the source file to copy. If omitted or null, copying goes to the last line of the file.
+
+### Examples
+
+This example makes a copy of a file `C:\TEMP\EMPDIR\empfile.csv`, which contains a comma-delimited list of employees from the `emp` table. The copy, `empcopy.csv`, is then listed.
+
+```sql
+CREATE DIRECTORY empdir AS 'C:/TEMP/EMPDIR';
+
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_src_dir       VARCHAR2(50) := 'empdir';
+    v_src_file      VARCHAR2(20) := 'empfile.csv';
+    v_dest_dir      VARCHAR2(50) := 'empdir';
+    v_dest_file     VARCHAR2(20) := 'empcopy.csv';
+    v_emprec        VARCHAR2(120);
+    v_count         INTEGER := 0;
+BEGIN
+    UTL_FILE.FCOPY(v_src_dir,v_src_file,v_dest_dir,v_dest_file);
+    v_empfile := UTL_FILE.FOPEN(v_dest_dir,v_dest_file,'r');
+    DBMS_OUTPUT.PUT_LINE('The following is the destination file, ''' ||
+        v_dest_file || '''');
+    LOOP
+        UTL_FILE.GET_LINE(v_empfile,v_emprec);
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+        v_count := v_count + 1;
+    END LOOP;
+    EXCEPTION
+        WHEN NO_DATA_FOUND THEN
+            UTL_FILE.FCLOSE(v_empfile);
+            DBMS_OUTPUT.PUT_LINE(v_count || ' records retrieved');
+        WHEN OTHERS THEN
+            DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+            DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+The following is the destination file, 'empcopy.csv'
+7369,SMITH,CLERK,7902,17-DEC-80,800,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81,1600,300,30
+7521,WARD,SALESMAN,7698,22-FEB-81,1250,500,30
+7566,JONES,MANAGER,7839,02-APR-81,2975,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81,1250,1400,30
+7698,BLAKE,MANAGER,7839,01-MAY-81,2850,,30
+7782,CLARK,MANAGER,7839,09-JUN-81,2450,,10
+7788,SCOTT,ANALYST,7566,19-APR-87,3000,,20
+7839,KING,PRESIDENT,,17-NOV-81,5000,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81,1500,0,30
+7876,ADAMS,CLERK,7788,23-MAY-87,1100,,20
+7900,JAMES,CLERK,7698,03-DEC-81,950,,30
+7902,FORD,ANALYST,7566,03-DEC-81,3000,,20
+7934,MILLER,CLERK,7782,23-JAN-82,1300,,10
+14 records retrieved
+```
+
+## FFLUSH
+
+The `FFLUSH` procedure flushes unwritten data from the write buffer to the file.
+
+```sql
+FFLUSH(<file> FILE_TYPE)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing a file handle.
+
+### Examples
+
+Each line is flushed after the `NEW_LINE` procedure is called.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'w');
+    FOR i IN emp_cur LOOP
+        UTL_FILE.PUT(v_empfile,i.empno);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.ename);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.job);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.mgr);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.hiredate);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.sal);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.comm);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.deptno);
+        UTL_FILE.NEW_LINE(v_empfile);
+        UTL_FILE.FFLUSH(v_empfile);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_empfile);
+END;
+```
+## FGETATTR
+
+The `FGETATTR` function retrieves the attributes for a given file. When you enter `filename` and `location` values, it returns whether the file exists. If the file exists, it also returns `file_length` and `block_size` values. If the file doesn't exist or an error occurs, the attributes return as `NULL`. 
+
+```sql
+FGETATTR(<location> VARCHAR2, <filename> VARCHAR2, <exists> BOOLEAN, <file_length> NUMBER, <block_size> BINARY_INTEGER)
+```
+
+### Parameters
+
+`location`
+ 
+ Name of the directory containing the file whose attributes are being retrieved, stored in `pg_catalog.edb_dir.dirname`.
+
+`filename`
+
+ Name of the file whose attributes are being retrieved.
+
+`exists` 
+
+ Report of whether the file exists. 
+
+`file_length`
+
+ Size of the file in bytes. 
+
+`block_size` 
+
+ System block size of the file in bytes.
+
+### Examples
+
+This example retrieves the attributes for the file `empfile.csv`:
+
+```sql
+DECLARE
+   l_file_exists BOOLEAN;
+   l_file_len    NUMBER;
+   l_blocksize   BINARY_INTEGER;
+   f utl_file.file_type;
+   v_empfile       UTL_FILE.FILE_TYPE;
+   v_directory     VARCHAR2(50) := 'empdir';
+   v_filename      VARCHAR2(20) := 'empfile.csv';
+     
+BEGIN
+   utl_file.fgetattr(
+     location    => v_directory,
+     filename    => v_filename,
+     fexists     => l_file_exists,
+     file_length => l_file_len,
+     block_size  => l_blocksize);
+   IF l_file_exists THEN
+     dbms_output.put_line('File found, size=' || l_file_len);
+   ELSE
+     dbms_output.put_line('File not found.');
+   END IF;
+END;
+File found, size=677
+```
+
+## FGETPOS
+
+The `FGETPOS` function returns the relative offset position in the opened file as an integer, in bytes.
+
+```sql
+FGETPOS(<file>)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the opened file.  
+
+### Examples
+
+Thus example finds the position of the file `empfile.csv`:
+
+```sql
+declare
+    f utl_file.file_type;
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+  pos int;
+begin
+  f := utl_file.fopen(v_directory, v_filename, 'r');
+  utl_file.fseek(f, 15);
+  pos := utl_file.fgetpos(f);
+  dbms_output.put_line('1.position: ' || pos);
+  utl_file.fseek(f, NULL, -5);
+  pos := utl_file.fgetpos(f);
+  dbms_output.put_line('2.position: ' || pos);
+  utl_file.fclose(f);
+end;
+1.position: 15
+2.position: 10
+```
+
+## FOPEN
+
+The `FOPEN` function opens a file for I/O.
+
+```sql
+<filetype> FILE_TYPE FOPEN(<location> VARCHAR2, <filename> VARCHAR2,<open_mode> VARCHAR2
+  [, <max_linesize> BINARY_INTEGER ])
+```
+
+### Parameters
+
+`location`
+
+ Directory name of the directory containing the file to open, as stored in `pg_catalog.edb_dir.dirname`.
+
+`filename`
+
+ Name of the file to open.
+
+`open_mode`
+
+ Mode in which to open the file. Modes are: 
+    - `a` &mdash; Append to file.
+    - `r` &mdash; Read from file. 
+    - `w` &mdash; Write to file.
+
+`max_linesize`
+
+ Maximum size of a line in characters. In read mode, an exception is thrown if you try to read a line exceeding `max_linesize`. In write and append modes, an exception is thrown if you try to write a line exceeding `max_linesize`. The end-of-line characters aren't included in determining if the maximum line size is exceeded. This behavior isn't compatible with Oracle databases. Oracle counts the end-of-line characters.
+
+`filetype`
+
+ Variable of type `FILE_TYPE` containing the file handle of the opened file.
+
+## FOPEN_NCHAR
+
+The `FOPEN_NCHAR` procedure opens the file `filename` in the directory identified by `location` to read and/or write Unicode character set data. 
+
+```sql
+FOPEN_NCHAR(location VARCHAR2, filename VARCHAR2, open_mode VARCHAR2, max_linesize INTEGER)
+```
+
+### Parameters 
+
+`location`
+
+ Name of the directory containing the file to open, stored in `pg_catalog.edb_dir.dirname`.
+
+`filename` 
+
+ Name of the file to open.
+
+`open_mode`
+
+ Mode in which to open the file. Modes are: 
+    - `a` &mdash; Append to file.
+    - `r` &mdash; Read from file. 
+    - `w` &mdash; Write to file.
+
+`max_linesize`
+
+ Maximum size of a line in characters. In read mode, an exception is thrown if you try to read a line exceeding `max_linesize`. In write and append modes, an exception is thrown if you try to write a line exceeding `max_linesize`. The end-of-line characters aren't included in determining if the maximum line size is exceeded. This behavior isn't compatible with Oracle databases. Oracle counts the end-of-line characters.
+
+### Examples
+
+Thus example opens the file `empfile1.csv`:
+
+```sql
+declare
+    f utl_file.file_type;
+    t text;
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile1.csv';
+    txt1            text;
+begin
+  f := utl_file.fopen_nchar(v_directory, v_filename, 'w');
+  utl_file.put_nchar(f, 'Hello - 1'::text);
+  utl_file.put_nchar(f, 100::numeric);
+  utl_file.put_nchar(f, '2006-08-13 12:34:56'::timestamp);
+  utl_file.put_nchar(f, '2001-12-27 04:05:06.789-08'::pg_catalog.date);
+  utl_file.put_nchar(f, '2001-12-27 04:05:06.789-08'::time);
+  utl_file.fclose(f);
+
+  f := utl_file.fopen_nchar(v_directory, v_filename, 'r');
+  loop
+    utl_file.get_line_nchar(f, txt1);
+    raise notice '%', txt1;
+  end loop;
+exception
+  when no_data_found then
+    raise notice 'finish % ', sqlerrm;
+    utl_file.fclose(f);
+
+end;
+NOTICE:  Hello - 110013-AUG-06 12:34:5627-DEC-01 00:00:00 +00:0004:05:06.789
+NOTICE:  finish no data found 
+```
+
+## FREMOVE
+
+The `FREMOVE` procedure removes a file from the system.
+
+```sql
+FREMOVE(<location> VARCHAR2, <filename> VARCHAR2)
+```
+
+An exception is thrown if the file doesn't exist.
+
+### Parameters
+
+`location`
+
+ Directory name of the directory containing the file to remove, as stored in `pg_catalog.edb_dir.dirname`.
+
+`filename`
+
+ Name of the file to remove.
+
+### Examples
+
+This example removes the file `empfile.csv`:
+
+```sql
+DECLARE
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+BEGIN
+    UTL_FILE.FREMOVE(v_directory,v_filename);
+    DBMS_OUTPUT.PUT_LINE('Removed file: ' || v_filename);
+    EXCEPTION
+        WHEN OTHERS THEN
+            DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+            DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+Removed file: empfile.csv
+```
+
+## FRENAME
+
+The `FRENAME` procedure renames a file, effectively moving a file from one location to another.
+
+```sql
+FRENAME(<location> VARCHAR2, <filename> VARCHAR2, <dest_dir> VARCHAR2, <dest_file> VARCHAR2,
+  [ <overwrite> BOOLEAN ])
+```
+
+### Parameters
+
+`location`
+
+ Directory name of the directory containing the file to rename, as stored in `pg_catalog.edb_dir.dirname`.
+
+`filename`
+
+ Name of the source file to rename.
+
+`dest_dir`
+
+ Directory name of the directory to which to locate the renamed file, as stored in `pg_catalog.edb_dir.dirname`.
+
+`dest_file`
+
+ New name of the file.
+
+`overwrite`
+
+ Replaces any existing file named `dest_file` in `dest_dir` if set to `TRUE`. An exception is thrown if set to `FALSE` (the default).
+
+### Examples
+
+This example renames a file, `C:\TEMP\EMPDIR\empfile.csv`, containing a comma-delimited list of employees from the `emp` table. The renamed file, `C:\TEMP\NEWDIR\newemp.csv`, is then listed.
+
+```sql
+CREATE DIRECTORY "newdir" AS 'C:/TEMP/NEWDIR';
+
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_src_dir       VARCHAR2(50) := 'empdir';
+    v_src_file      VARCHAR2(20) := 'empfile.csv';
+    v_dest_dir      VARCHAR2(50) := 'newdir';
+    v_dest_file     VARCHAR2(50) := 'newemp.csv';
+    v_replace       BOOLEAN := FALSE;
+    v_emprec        VARCHAR2(120);
+    v_count         INTEGER := 0;
+BEGIN
+    UTL_FILE.FRENAME(v_src_dir,v_src_file,v_dest_dir,
+        v_dest_file,v_replace);
+    v_empfile := UTL_FILE.FOPEN(v_dest_dir,v_dest_file,'r');
+    DBMS_OUTPUT.PUT_LINE('The following is the renamed file, ''' ||
+        v_dest_file || '''');
+    LOOP
+        UTL_FILE.GET_LINE(v_empfile,v_emprec);
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+        v_count := v_count + 1;
+    END LOOP;
+    EXCEPTION
+        WHEN NO_DATA_FOUND THEN
+            UTL_FILE.FCLOSE(v_empfile);
+            DBMS_OUTPUT.PUT_LINE(v_count || ' records retrieved');
+        WHEN OTHERS THEN
+            DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+            DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+The following is the renamed file, 'newemp.csv'
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+14 records retrieved
+```
+
+## FSEEK
+
+The `FSEEK` procedure moves the file pointer within a given file by the number of bytes specified. 
+
+```sql
+FSEEK( <file> FILE_TYPE, <absolute_offset> INTEGER, <relative_offset> INTEGER)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file where the file pointer is being moved.
+
+`absolute_offset` 
+
+ The absolute number of bytes to move the file pointer.
+
+`relative_offset` 
+
+ The relative number of bytes to move the file pointer. 
+
+### Examples 
+
+This examples moves the file pointer in the file `empfile.csv`:
+
+```sql
+declare
+    f utl_file.file_type;
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+  pos int;
+begin
+  f := utl_file.fopen(v_directory, v_filename, 'r');
+  utl_file.fseek(f, 15);
+  pos := utl_file.fgetpos(f);
+  dbms_output.put_line('1.position: ' || pos);
+  utl_file.fseek(f, NULL, -5);
+  pos := utl_file.fgetpos(f);
+  dbms_output.put_line('2.position: ' || pos);
+  utl_file.fclose(f);
+end;
+1.position: 15
+2.position: 10
+```
+
+## GET_LINE
+
+The `GET_LINE` procedure reads a line of text from a given file up to but not including the end-of-line terminator. A `NO_DATA_FOUND` exception is thrown when there are no more lines to read.
+
+```sql
+GET_LINE(<file> FILE_TYPE, <buffer> OUT VARCHAR2)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the opened file.
+
+`buffer`
+
+ Variable to receive a line from the file.
+
+### Examples
+
+The following anonymous block reads through and displays the records in file `empfile.csv`.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    v_emprec        VARCHAR2(120);
+    v_count         INTEGER := 0;
+BEGIN
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'r');
+    LOOP
+        UTL_FILE.GET_LINE(v_empfile,v_emprec);
+        DBMS_OUTPUT.PUT_LINE(v_emprec);
+        v_count := v_count + 1;
+    END LOOP;
+    EXCEPTION
+        WHEN NO_DATA_FOUND THEN
+            UTL_FILE.FCLOSE(v_empfile);
+            DBMS_OUTPUT.PUT_LINE('End of file ' || v_filename || ' - ' ||
+                v_count || ' records retrieved');
+        WHEN OTHERS THEN
+            DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+            DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+End of file empfile.csv - 14 records retrieved
+```
+
+## GET_RAW
+
+The `GET_RAW` procedure reads a `RAW` string value from a file, keeps those into read buffer, and adjusts the file pointer accordingly by the number of bytes read. `GET_RAW` ignores the end-of-file terminator. `INVALID_FILEHANDLE`, `INVALID_OPERATION`, and `READ_ERROR` exceptions are thrown when there are no more lines to read.
+
+```sql
+GET_RAW(<file> FILE_TYPE, <buffer> OUT BYTEA [, <len> INTEGER ])
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the opened file.
+
+`buffer`
+
+ Assign `RAW` data from the file to the read buffer.
+
+`len`
+
+ The number of bytes read from a file. Default is `NULL`. If `NULL`, `len` tries to read a maximum of 32767 `RAW` bytes.
+ 
+### Examples
+
+This example attempts to read a `RAW` string value from the file.
+
+```sql
+CREATE DIRECTORY empdir  AS '/TMP/EMPDIR';
+
+CREATE or REPLACE FUNCTION read_bin_file() RETURN void AS
+
+DECLARE
+    v_tempfile      UTL_FILE.FILE_TYPE;
+    v_filename      VARCHAR2(20) := 'sample.png';
+    v_temprec       BYTEA;
+    v_count         INTEGER := 0;
+BEGIN
+    v_tempfile := UTL_FILE.FOPEN('empdir', v_filename, 'rb');
+    UTL_FILE.GET_RAW(v_tempfile,v_temprec);
+    INSERT INTO emp VALUES (1, v_temprec);
+EXCEPTION
+    WHEN NO_DATA_FOUND THEN
+       RAISE NOTICE 'Finish % ', SQLERRM;
+       UTL_FILE.FCLOSE(v_tempfile);
+END;
+
+edb=# SELECT read_bin_file();
+__OUTPUT__
+ read_bin_file 
+---------------
+ (1 row)
+```
+
+## IS_OPEN
+
+The `IS_OPEN` function determines whether a file is open.
+
+```sql
+<status> BOOLEAN IS_OPEN(<file> FILE_TYPE)
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to test.
+
+`status`
+
+ `TRUE` if the file is open, `FALSE` otherwise.
+
+## NEW_LINE
+
+The `NEW_LINE` procedure writes an end-of-line character sequence in the file.
+
+```sql
+NEW_LINE(<file> FILE_TYPE [, <lines> INTEGER ])
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write end-of-line character sequences.
+
+`lines`
+
+ Number of end-of-line character sequences to write. The default is `1`.
+
+### Examples
+
+This example writes a file containing a double-spaced list of employee records.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'w');
+    FOR i IN emp_cur LOOP
+        UTL_FILE.PUT(v_empfile,i.empno);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.ename);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.job);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.mgr);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.hiredate);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.sal);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.comm);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.deptno);
+        UTL_FILE.NEW_LINE(v_empfile,2);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_empfile);
+END;
+
+Created file: empfile.csv
+```
+
+This file is then displayed:
+
+```sql
+C:\TEMP\EMPDIR>TYPE empfile.csv
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+## PUT
+
+The `PUT` procedure writes a string to the given file. No end-of-line character sequence is written at the end of the string. Use the `NEW_LINE` procedure to add an end-of-line character sequence.
+
+```sql
+PUT(<file> FILE_TYPE, <buffer> { DATE | NUMBER | TIMESTAMP | VARCHAR2 })
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write the given string.
+
+`buffer`
+
+ Text to write to the specified file.
+
+### Examples
+
+This example uses the `PUT` procedure to create a comma-delimited file of employees from the `emp` table.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'w');
+    FOR i IN emp_cur LOOP
+        UTL_FILE.PUT(v_empfile,i.empno);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.ename);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.job);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.mgr);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.hiredate);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.sal);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.comm);
+        UTL_FILE.PUT(v_empfile,',');
+        UTL_FILE.PUT(v_empfile,i.deptno);
+        UTL_FILE.NEW_LINE(v_empfile);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_empfile);
+END;
+
+Created file: empfile.csv
+```
+
+The following are the contents of `empfile.csv`:
+
+```sql
+C:\TEMP\EMPDIR>TYPE empfile.csv
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+## PUT_LINE
+
+The `PUT_LINE` procedure writes a single line to a file, including an end-of-line character sequence.
+
+```sql
+PUT_LINE(<file> FILE_TYPE, <buffer> { DATE | NUMBER | TIMESTAMP | VARCHAR2 })
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write the line.
+
+`buffer`
+
+ Text to write to the file.
+
+### Examples
+
+This example uses the `PUT_LINE` procedure to create a comma-delimited file of employees from the `emp` table.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    v_emprec        VARCHAR2(120);
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'w');
+    FOR i IN emp_cur LOOP
+        v_emprec := i.empno || ',' || i.ename || ',' || i.job || ',' ||
+            NVL(LTRIM(TO_CHAR(i.mgr,'9999')),'') || ',' || i.hiredate ||
+            ',' || i.sal || ',' ||
+            NVL(LTRIM(TO_CHAR(i.comm,'9990.99')),'') || ',' || i.deptno;
+        UTL_FILE.PUT_LINE(v_empfile,v_emprec);
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_empfile);
+END;
+```
+
+The following are the contents of `empfile.csv`:
+
+```sql
+C:\TEMP\EMPDIR>TYPE empfile.csv
+
+7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+## PUTF
+
+The `PUTF` procedure writes a formatted string to a file.
+
+```sql
+PUTF(<file> FILE_TYPE, <format> VARCHAR2 [, <arg1> VARCHAR2] [, ...])
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write the formatted line.
+
+`format`
+
+ String to format the text written to the file. The special character sequence `%s` is substituted by the value of `arg`. The special character sequence `\n` indicates a new line. In EDB Postgres Advanced Server, specify a new line character with two consecutive backslashes instead of one: `\\n`. This characteristic isn't compatible with Oracle databases.
+
+`arg1`
+
+ Up to five arguments, `arg1`,...`arg5`, to substitute in the format string for each occurrence of `%s`. The first arg is substituted for the first occurrence of `%s`, the second arg is substituted for the second occurrence of `%s`, and so on.
+
+### Examples
+
+The following anonymous block produces formatted output containing data from the `emp` table. 
+
+!!! Note
+    The E literal syntax and double backslashes for the new-line character sequence in the format string aren't compatible with Oracle databases.
+
+```sql
+DECLARE
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile.csv';
+    v_format        VARCHAR2(200);
+    CURSOR emp_cur IS SELECT * FROM emp ORDER BY empno;
+BEGIN
+    v_format := E'%s %s, %s\\nSalary: $%s Commission: $%s\\n\\n';
+    v_empfile := UTL_FILE.FOPEN(v_directory,v_filename,'w');
+    FOR i IN emp_cur LOOP
+        UTL_FILE.PUTF(v_empfile,v_format,i.empno,i.ename,i.job,i.sal,
+            NVL(i.comm,0));
+    END LOOP;
+    DBMS_OUTPUT.PUT_LINE('Created file: ' || v_filename);
+    UTL_FILE.FCLOSE(v_empfile);
+EXCEPTION
+    WHEN OTHERS THEN
+        DBMS_OUTPUT.PUT_LINE('SQLERRM: ' || SQLERRM);
+        DBMS_OUTPUT.PUT_LINE('SQLCODE: ' || SQLCODE);
+END;
+
+Created file: empfile.csv
+```
+
+The following are the contents of `empfile.csv`:
+
+```sql
+C:\TEMP\EMPDIR>TYPE empfile.csv
+7369 SMITH, CLERK
+Salary: $800.00 Commission: $0
+7499 ALLEN, SALESMAN
+Salary: $1600.00 Commission: $300.00
+7521 WARD, SALESMAN
+Salary: $1250.00 Commission: $500.00
+7566 JONES, MANAGER
+Salary: $2975.00 Commission: $0
+7654 MARTIN, SALESMAN
+Salary: $1250.00 Commission: $1400.00
+7698 BLAKE, MANAGER
+Salary: $2850.00 Commission: $0
+7782 CLARK, MANAGER
+Salary: $2450.00 Commission: $0
+7788 SCOTT, ANALYST
+Salary: $3000.00 Commission: $0
+7839 KING, PRESIDENT
+Salary: $5000.00 Commission: $0
+7844 TURNER, SALESMAN
+Salary: $1500.00 Commission: $0.00
+7876 ADAMS, CLERK
+Salary: $1100.00 Commission: $0
+7900 JAMES, CLERK
+Salary: $950.00 Commission: $0
+7902 FORD, ANALYST
+Salary: $3000.00 Commission: $0
+7934 MILLER, CLERK
+Salary: $1300.00 Commission: $0
+```
+
+## PUT_NCHAR
+
+The `PUT_NCHAR` procedure writes `buffer` to the given file and converts data to Unicode. `PUT` doesn't write an end-of-line character sequence.   
+
+```sql
+PUT_NCHAR(<file> FILE_TYPE, <buffer> NVARCHAR2)
+```
+
+### Parameters 
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write the line.
+
+`buffer`
+
+ Variable to write `RAW` data to the output buffer.
+
+### Examples 
+
+This example writes `buffer` to the file `empfile.csv` and converts data to Unicode:
+
+```sql
+declare
+    f utl_file.file_type;
+    t text;
+    v_empfile       UTL_FILE.FILE_TYPE;
+    v_directory     VARCHAR2(50) := 'empdir';
+    v_filename      VARCHAR2(20) := 'empfile1.csv';
+    txt1            text;
+begin
+  f := utl_file.fopen_nchar(v_directory, v_filename, 'w');
+  utl_file.put_nchar(f, 'Hello - 1'::text);
+  utl_file.put_nchar(f, 100::numeric);
+  utl_file.put_nchar(f, '2006-08-13 12:34:56'::timestamp);
+  utl_file.put_nchar(f, '2001-12-27 04:05:06.789-08'::pg_catalog.date);
+  utl_file.put_nchar(f, '2001-12-27 04:05:06.789-08'::time);
+  utl_file.fclose(f);
+
+  f := utl_file.fopen_nchar(v_directory, v_filename, 'r');
+  loop
+    utl_file.get_line_nchar(f, txt1);
+    raise notice '%', txt1;
+  end loop;
+exception
+  when no_data_found then
+    raise notice 'finish % ', sqlerrm;
+    utl_file.fclose(f);
+
+end;
+NOTICE:  Hello - 110013-AUG-06 12:34:5627-DEC-01 00:00:00 +00:0004:05:06.789
+NOTICE:  finish no data found 
+```
+
+## PUT_RAW
+
+The `PUT_RAW` procedure accepts a `RAW` data value and writes those values to the output buffer. `INVALID_FILEHANDLE`, `INVALID_OPERATION`, `WRITE_ERROR`, and `VALUE_ERROR` exceptions are thrown when there are no more lines to read.
+                                                                                             
+```sql
+PUT_RAW(<file> FILE_TYPE, <buffer> BYTEA [, <autoflush> BOOLEAN ])
+```
+
+### Parameters
+
+`file`
+
+ Variable of type `FILE_TYPE` containing the file handle of the file to which to write the line.
+
+`buffer`
+
+ Variable to write `RAW` data to the output buffer.
+
+`autoflush`
+
+ If `TRUE`, performs a flush after writing the value to the output buffer. By default, `autoflush` is `FALSE`.
+
+### Examples
+
+This example writes the `RAW` data value from the `emp` table.
+
+```sql
+CREATE or REPLACE FUNCTION write_bin_file() RETURN void AS
+
+DECLARE
+    v_tempfile      UTL_FILE.FILE_TYPE;
+    v_filename      VARCHAR2(20) := 'sample.png';
+    v_temprec       BYTEA;
+BEGIN
+SELECT imagerawdata INTO v_temprec from emp;
+    v_tempfile := UTL_FILE.FOPEN('empdir', v_filename, 'wb');
+    UTL_FILE.PUT_RAW(v_tempfile,v_temprec, TRUE);
+    UTL_FILE.FCLOSE(v_tempfile);
+END;
+
+edb=# SELECT write_bin_file();
+__OUTPUT__
+ write_bin_file 
+--------------- 
+(1 row)
+```
+
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/21_utl_http.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/21_utl_http.mdx
new file mode 100644
index 00000000000..278f5cc3379
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/21_utl_http.mdx
@@ -0,0 +1,1025 @@
+---
+title: "UTL_HTTP"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.34.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.207.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.165.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/21_utl_http/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_HTTP` package provides a way to use the HTTP or HTTPS protocol to retrieve information found at a URL. EDB Postgres Advanced Server supports the following functions and procedures.
+
+| Function/procedure                                 | Return type             | Description                                                                                    |
+| -------------------------------------------------- | ----------------------- | ---------------------------------------------------------------------------------------------- |
+| `BEGIN_REQUEST(url, method, http_version)`         | `UTL_HTTP.REQ`          | Initiates a new HTTP request.                                                                  |
+| `END_REQUEST(r IN OUT)`                            | n/a                     | Ends an HTTP request before allowing it to complete.                                           |
+| `END_RESPONSE(r IN OUT)`                           | n/a                     | Ends the HTTP response.                                                                        |
+| `END_OF_BODY(r IN OUT)`                            | n/a                     | Ends package body.                                                                              |
+| `GET_BODY_CHARSET`                                 | `VARCHAR2`              | Returns the default character set of the body of future HTTP requests.                         |
+| `GET_BODY_CHARSET(charset OUT)`                    | n/a                     | Returns the default character set of the body of future HTTP requests.                         |
+| `GET_FOLLOW_REDIRECT(max_redirects OUT)`           | n/a                     | Current setting for the maximum number of redirections allowed.                                |
+| `GET_HEADER(r IN OUT, n, name OUT, value OUT)`     | n/a                     | Returns the nth header of the HTTP response.                                                   |
+| `GET_HEADER_BY_NAME(r IN OUT, name, value OUT, n)` | n/a                     | Returns the HTTP response header for the specified name.                                       |
+| `GET_HEADER_COUNT(r IN OUT)`                       | `INTEGER`               | Returns the number of HTTP response headers.                                                   |
+| `GET_RESPONSE(r IN OUT)`                           | `UTL_HTTP.RESP`         | Returns the HTTP response.                                                                     |
+| `GET_RESPONSE_ERROR_CHECK(enable OUT)`             | n/a                     | Returns whether or not response error check is set.                                            |
+| `GET_TRANSFER_TIMEOUT(timeout OUT)`                | n/a                     | Returns the transfer timeout setting for HTTP requests.                                        |
+| `READ_LINE(r IN OUT, data OUT, remove_crlf)`       | n/a                     | Returns the HTTP response body in text form until the end of line.                             |
+| `READ_RAW(r IN OUT, data OUT, len)`                | n/a                     | Returns the HTTP response body in binary form for a specified number of bytes.                 |
+| `READ_TEXT(r IN OUT, data OUT, len)`               | n/a                     | Returns the HTTP response body in text form for a specified number of characters.              |
+| `REQUEST(url)`                                     | `VARCHAR2`              | Returns the content of a web page.                                                             |
+| `REQUEST_PIECES(url, max_pieces)`                  | `UTL_HTTP. HTML_PIECES` | Returns a table of 2000-byte segments retrieved from an URL.                                   |
+| `SET_BODY_CHARSET(charset)`                        | n/a                     | Sets the default character set of the body of future HTTP requests.                            |
+| `SET_FOLLOW_REDIRECT(max_redirects)`               | n/a                     | Sets the maximum number of times to follow the redirect instruction.                           |
+| `SET_FOLLOW_REDIRECT(r IN OUT, max_redirects)`     | n/a                     | Sets the maximum number of times to follow the redirect instruction for an individual request. |
+| `SET_HEADER(r IN OUT, name, value)`                | n/a                     | Sets the HTTP request header.                                                                  |
+| `SET_RESPONSE_ERROR_CHECK(enable)`                 | n/a                     | Determines whether to treat HTTP 4xx and 5xx status codes as errors.           |
+| `SET_TRANSFER_TIMEOUT(timeout)`                    | n/a                     | Sets the default transfer timeout value for HTTP requests.                                    |
+| `SET_TRANSFER_TIMEOUT(r IN OUT, timeout)`          | n/a                     | Sets the transfer timeout value for an individual HTTP request.                                |
+| `WRITE_LINE(r IN OUT, data)`                       | n/a                     | Writes CRLF-terminated data to the HTTP request body in TEXT form.                             |
+| `WRITE_RAW(r IN OUT, data)`                        | n/a                     | Writes data to the HTTP request body in BINARY form.                                           |
+| `WRITE_TEXT(r IN OUT, data)`                       | n/a                     | Writes data to the HTTP request body in TEXT form.                                             |
+
+EDB Postgres Advanced Server's implementation of `UTL_HTTP` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in the table are supported.
+
+!!! Note
+    In EDB Postgres Advanced Server, an `HTTP 4xx` or `HTTP 5xx` response produces a database error. In Oracle, you can configure this option. It is `FALSE` by default.
+
+In EDB Postgres Advanced Server, the `UTL_HTTP` text interfaces expect the downloaded data to be in the database encoding. All interfaces that are currently available are text interfaces. In Oracle, the encoding is detected from HTTP headers. Without the header, the default is configurable and defaults to `ISO-8859-1`.
+
+EDB Postgres Advanced Server ignores all cookies it receives.
+
+The `UTL_HTTP` exceptions that can be raised in Oracle aren't recognized by EDB Postgres Advanced Server. In addition, the error codes returned by EDB Postgres Advanced Server aren't the same as those returned by Oracle.
+
+## UTL_HTTP exception codes
+
+If a call to a `UTL_HTTP` procedure or function raises an exception, you can use the condition name to catch the exception. The `UTL_HTTP` package reports the following exception codes compatible with Oracle databases.
+
+| Exception code     | Condition name     | Description                              | Raised where                                 |
+| ------------------ | ------------------ | ---------------------------------------- | ------------------------------------------------ |
+| `-29266`           | `END_OF_BODY`      | The end of HTTP response body is reached | `READ_LINE, READ_RAW`, and `READ_TEXT` functions |
+
+To use the `UTL_HTTP.END_OF_BODY` exception, first you need to run the `utl_http_public.sql` file from the `contrib/utl_http` directory of your installation directory.
+
+Various public constants are available with `UTL_HTTP`. These are listed in the following tables.
+
+The following table contains `UTL_HTTP` public constants defining HTTP versions and port assignments.
+
+| HTTP versions                 |                                        |
+| ----------------------------- | -------------------------------------- |
+| `HTTP_VERSION_1_0`            | `CONSTANT VARCHAR2(64) := 'HTTP/1.0';` |
+| `HTTP_VERSION_1_1`            | `CONSTANT VARCHAR2(64) := 'HTTP/1.1';` |
+| **Standard port assignments** |                                        |
+| `DEFAULT_HTTP_PORT`           | `CONSTANT INTEGER := 80;`              |
+| `DEFAULT_HTTPS_PORT`          | `CONSTANT INTEGER := 443;`             |
+
+The following table contains `UTL_HTTP` public status code constants.
+
+| 1XX Informational             |                            |
+| ----------------------------- | -------------------------- |
+| `HTTP_CONTINUE`               | `CONSTANT INTEGER := 100;` |
+| `HTTP_SWITCHING_PROTOCOLS`    | `CONSTANT INTEGER := 101;` |
+| `HTTP_PROCESSING`             | `CONSTANT INTEGER := 102;` |
+| **2XX success**               |                            |
+| `HTTP_OK`                     | `CONSTANT INTEGER := 200;` |
+| `HTTP_CREATED`                | `CONSTANT INTEGER := 201;` |
+| `HTTP_ACCEPTED`               | `CONSTANT INTEGER := 202;` |
+| `HTTP_NON_AUTHORITATIVE_INFO` | `CONSTANT INTEGER := 203;` |
+| `HTTP_NO_CONTENT`             | `CONSTANT INTEGER := 204;` |
+| `HTTP_RESET_CONTENT`          | `CONSTANT INTEGER := 205;` |
+| `HTTP_PARTIAL_CONTENT`        | `CONSTANT INTEGER := 206;` |
+| `HTTP_MULTI_STATUS`           | `CONSTANT INTEGER := 207;` |
+| `HTTP_ALREADY_REPORTED`       | `CONSTANT INTEGER := 208;` |
+| `HTTP_IM_USED`                | `CONSTANT INTEGER := 226;` |
+| **3XX redirection**           |                            |
+| `HTTP_MULTIPLE_CHOICES`       | `CONSTANT INTEGER := 300;` |
+| `HTTP_MOVED_PERMANENTLY`      | `CONSTANT INTEGER := 301;` |
+| `HTTP_FOUND`                  | `CONSTANT INTEGER := 302;` |
+| `HTTP_SEE_OTHER`              | `CONSTANT INTEGER := 303;` |
+| `HTTP_NOT_MODIFIED`           | `CONSTANT INTEGER := 304;` |
+| `HTTP_USE_PROXY`              | `CONSTANT INTEGER := 305;` |
+| `HTTP_SWITCH_PROXY`           | `CONSTANT INTEGER := 306;` |
+| `HTTP_TEMPORARY_REDIRECT`     | `CONSTANT INTEGER := 307;` |
+| `HTTP_PERMANENT_REDIRECT`     | `CONSTANT INTEGER := 308;` |
+
+| 4XX client error                            |                            |
+| ------------------------------------------- | -------------------------- |
+| `HTTP_BAD_REQUEST`                          | `CONSTANT INTEGER := 400;` |
+| `HTTP_UNAUTHORIZED`                         | `CONSTANT INTEGER := 401;` |
+| `HTTP_PAYMENT_REQUIRED`                     | `CONSTANT INTEGER := 402;` |
+| `HTTP_FORBIDDEN`                            | `CONSTANT INTEGER := 403;` |
+| `HTTP_NOT_FOUND`                            | `CONSTANT INTEGER := 404;` |
+| `HTTP_METHOD_NOT_ALLOWED`                   | `CONSTANT INTEGER := 405;` |
+| `HTTP_NOT_ACCEPTABLE`                       | `CONSTANT INTEGER := 406;` |
+| `HTTP_PROXY_AUTH_REQUIRED`                  | `CONSTANT INTEGER := 407;` |
+| `HTTP_REQUEST_TIME_OUT`                     | `CONSTANT INTEGER := 408;` |
+| `HTTP_CONFLICT`                             | `CONSTANT INTEGER := 409;` |
+| `HTTP_GONE`                                 | `CONSTANT INTEGER := 410;` |
+| `HTTP_LENGTH_REQUIRED`                      | `CONSTANT INTEGER := 411;` |
+| `HTTP_PRECONDITION_FAILED`                  | `CONSTANT INTEGER := 412;` |
+| `HTTP_REQUEST_ENTITY_TOO_LARGE`             | `CONSTANT INTEGER := 413;` |
+| `HTTP_REQUEST_URI_TOO_LARGE`                | `CONSTANT INTEGER := 414;` |
+| `HTTP_UNSUPPORTED_MEDIA_TYPE`               | `CONSTANT INTEGER := 415;` |
+| `HTTP_REQ_RANGE_NOT_SATISFIABLE`            | `CONSTANT INTEGER := 416;` |
+| `HTTP_EXPECTATION_FAILED`                   | `CONSTANT INTEGER := 417;` |
+| `HTTP_I_AM_A_TEAPOT`                        | `CONSTANT INTEGER := 418;` |
+| `HTTP_AUTHENTICATION_TIME_OUT`              | `CONSTANT INTEGER := 419;` |
+| `HTTP_ENHANCE_YOUR_CALM`                    | `CONSTANT INTEGER := 420;` |
+| `HTTP_UNPROCESSABLE_ENTITY`                 | `CONSTANT INTEGER := 422;` |
+| `HTTP_LOCKED`                               | `CONSTANT INTEGER := 423;` |
+| `HTTP_FAILED_DEPENDENCY`                    | `CONSTANT INTEGER := 424;` |
+| `HTTP_UNORDERED_COLLECTION`                 | `CONSTANT INTEGER := 425;` |
+| `HTTP_UPGRADE_REQUIRED`                     | `CONSTANT INTEGER := 426;` |
+| `HTTP_PRECONDITION_REQUIRED`                | `CONSTANT INTEGER := 428;` |
+| `HTTP_TOO_MANY_REQUESTS`                    | `CONSTANT INTEGER := 429;` |
+| `HTTP_REQUEST_HEADER_FIELDS_TOO_LARGE`      | `CONSTANT INTEGER := 431;` |
+| `HTTP_NO_RESPONSE`                          | `CONSTANT INTEGER := 444;` |
+| `HTTP_RETRY_WITH`                           | `CONSTANT INTEGER := 449;` |
+| `HTTP_BLOCKED_BY_WINDOWS_PARENTAL_CONTROLS` | `CONSTANT INTEGER := 450;` |
+| `HTTP_REDIRECT`                             | `CONSTANT INTEGER := 451;` |
+| `HTTP_REQUEST_HEADER_TOO_LARGE`             | `CONSTANT INTEGER := 494;` |
+| `HTTP_CERT_ERROR`                           | `CONSTANT INTEGER := 495;` |
+| `HTTP_NO_CERT`                              | `CONSTANT INTEGER := 496;` |
+| `HTTP_HTTP_TO_HTTPS`                        | `CONSTANT INTEGER := 497;` |
+| `HTTP_CLIENT_CLOSED_REQUEST`                | `CONSTANT INTEGER := 499;` |
+
+| 5XX server error                       |                            |
+| -------------------------------------- | -------------------------- |
+| `HTTP_INTERNAL_SERVER_ERROR`           | `CONSTANT INTEGER := 500;` |
+| `HTTP_NOT_IMPLEMENTED`                 | `CONSTANT INTEGER := 501;` |
+| `HTTP_BAD_GATEWAY`                     | `CONSTANT INTEGER := 502;` |
+| `HTTP_SERVICE_UNAVAILABLE`             | `CONSTANT INTEGER := 503;` |
+| `HTTP_GATEWAY_TIME_OUT`                | `CONSTANT INTEGER := 504;` |
+| `HTTP_VERSION_NOT_SUPPORTED`           | `CONSTANT INTEGER := 505;` |
+| `HTTP_VARIANT_ALSO_NEGOTIATES`         | `CONSTANT INTEGER := 506;` |
+| `HTTP_INSUFFICIENT_STORAGE`            | `CONSTANT INTEGER := 507;` |
+| `HTTP_LOOP_DETECTED`                   | `CONSTANT INTEGER := 508;` |
+| `HTTP_BANDWIDTH_LIMIT_EXCEEDED`        | `CONSTANT INTEGER := 509;` |
+| `HTTP_NOT_EXTENDED`                    | `CONSTANT INTEGER := 510;` |
+| `HTTP_NETWORK_AUTHENTICATION_REQUIRED` | `CONSTANT INTEGER := 511;` |
+| `HTTP_NETWORK_READ_TIME_OUT_ERROR`     | `CONSTANT INTEGER := 598;` |
+| `HTTP_NETWORK_CONNECT_TIME_OUT_ERROR`  | `CONSTANT INTEGER := 599;` |
+
+## HTML_PIECES
+
+The `UTL_HTTP` package declares a type named `HTML_PIECES`, which is a table of type `VARCHAR2 (2000)` indexed by `BINARY INTEGER`. A value of this type is returned by the `REQUEST_PIECES` function.
+
+```sql
+TYPE html_pieces IS TABLE OF VARCHAR2(2000) INDEX BY BINARY_INTEGER;
+```
+
+## REQ
+
+The `REQ` record type holds information about each HTTP request.
+
+```sql
+TYPE req IS RECORD (
+    url             VARCHAR2(32767),    -- URL to be accessed
+    method          VARCHAR2(64),       -- HTTP method
+    http_version    VARCHAR2(64),       -- HTTP version
+    private_hndl    INTEGER             -- Holds handle for this request
+);
+```
+
+## RESP
+
+The `RESP` record type holds information about the response from each HTTP request.
+
+```sql
+TYPE resp IS RECORD (
+    status_code     INTEGER,            -- HTTP status code
+    reason_phrase   VARCHAR2(256),      -- HTTP response reason phrase
+    http_version    VARCHAR2(64),       -- HTTP version
+    private_hndl    INTEGER             -- Holds handle for this response
+);
+```
+
+## BEGIN_REQUEST
+
+The `BEGIN_REQUEST` function initiates a new HTTP request. A network connection is established to the web server with the specified URL. The signature is:
+
+```sql
+BEGIN_REQUEST(<url> IN VARCHAR2, <method> IN VARCHAR2 DEFAULT
+'GET ', <http_version> IN VARCHAR2 DEFAULT NULL) RETURN
+UTL_HTTP.REQ
+```
+
+The `BEGIN_REQUEST` function returns a record of type `UTL_HTTP.REQ`.
+
+### Parameters
+
+`url`
+
+ `url` is the Uniform Resource Locator from which `UTL_HTTP` returns content.
+
+`method`
+
+ `method` is the HTTP method to use. The default is `GET`.
+
+`http_version`
+
+ `http_version` is the HTTP protocol version sending the request. Specify either `HTTP/1.0` or `HTTP/1.1`. The default is null. In that case, the latest HTTP protocol version supported by the `UTL_HTTP` package is used, which is 1.1.
+
+## END_REQUEST
+
+The `END_REQUEST` procedure terminates an HTTP request. Use the `END_REQUEST` procedure to terminate an HTTP request without completing it and waiting for the response. The normal process is to begin the request, get the response, and then close the response. The signature is:
+
+```sql
+END_REQUEST(<r> IN OUT UTL_HTTP.REQ)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+## END_RESPONSE
+
+The `END_RESPONSE` procedure terminates the HTTP response. The `END_RESPONSE` procedure completes the HTTP request and response. This is the normal method to end the request and response process. The signature is:
+
+```sql
+END_RESPONSE(<r> IN OUT UTL_HTTP.RESP)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the `HTTP` response record.
+
+## GET_BODY_CHARSET
+
+The `GET_BODY_CHARSET` program is available in the form of both a procedure and a function. A call to `GET_BODY_CHARSET` returns the default character set of the body of future HTTP requests.
+
+The procedure signature is:
+
+```sql
+GET_BODY_CHARSET(<charset> OUT VARCHAR2)
+```
+
+The function signature is:
+
+```sql
+GET_BODY_CHARSET() RETURN VARCHAR2
+```
+
+This function returns a `VARCHAR2` value.
+
+### Parameters
+
+`charset`
+
+ `charset` is the character set of the body.
+
+### Examples
+
+This example shows the use of the `GET_BODY_CHARSET` function.
+
+```sql
+edb=# SELECT UTL_HTTP.GET_BODY_CHARSET() FROM DUAL;
+__OUTPUT__
+ get_body_charset
+------------------
+ ISO-8859-1
+(1 row)
+```
+
+## GET_FOLLOW_REDIRECT
+
+The `GET_FOLLOW_REDIRECT` procedure returns the current setting for the maximum number of redirections allowed. The signature is:
+
+```sql
+GET_FOLLOW_REDIRECT(<max_redirects> OUT INTEGER)
+```
+
+### Parameters
+
+`max_redirects`
+
+ `max_redirects` is the maximum number of redirections allowed.
+
+## GET_HEADER
+
+The `GET_HEADER` procedure returns the `nth` header of the HTTP response. The signature is:
+
+```sql
+GET_HEADER(<r> IN OUT UTL_HTTP.RESP, <n> INTEGER, <name> OUT
+VARCHAR2, <value> OUT VARCHAR2)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+`n`
+
+ `n` is the `nth` header of the HTTP response record to retrieve.
+
+`name`
+
+ `name` is the name of the response header.
+
+`value`
+
+ `value` is the value of the response header.
+
+### Examples
+
+This example retrieves the header count and then the headers.
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+    v_name          VARCHAR2(30);
+    v_value         VARCHAR2(200);
+    v_header_cnt    INTEGER;
+BEGIN
+ -- Initiate request and get response
+    v_req := UTL_HTTP.BEGIN_REQUEST('www.enterprisedb.com');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+
+ -- Get header count
+    v_header_cnt := UTL_HTTP.GET_HEADER_COUNT(v_resp);
+    DBMS_OUTPUT.PUT_LINE('Header Count: ' || v_header_cnt);
+
+ -- Get all headers
+    FOR i IN 1 .. v_header_cnt LOOP
+        UTL_HTTP.GET_HEADER(v_resp, i, v_name, v_value);
+        DBMS_OUTPUT.PUT_LINE(v_name || ': ' || v_value);
+    END LOOP;
+
+ -- Terminate request
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+The following is the output from the example.
+
+```text
+Header Count: 23
+Age: 570
+Cache-Control: must-revalidate
+Content-Type: text/html; charset=utf-8
+Date: Wed, 30 Apr 2015 14:57:52 GMT
+ETag: "aab02f2bd2d696eed817ca89ef411dda"
+Expires: Sun, 19 Nov 1978 05:00:00 GMT
+Last-Modified: Wed, 30 Apr 2015 14:15:49 GMT
+RTSS: 1-1307-3
+Server: Apache/2.2.3 (Red Hat)
+Set-Cookie:
+SESS2771d0952de2a1a84d322a262e0c173c=jn1u1j1etmdi5gg4lh8hakvs01;
+expires=Fri, 23-May-2015 18:21:43 GMT; path=/; domain=.enterprisedb.com
+Vary: Accept-Encoding
+Via: 1.1 varnish
+X-EDB-Backend: ec
+X-EDB-Cache: HIT
+X-EDB-Cache-Address: 10.31.162.212
+X-EDB-Cache-Server: ip-10-31-162-212
+X-EDB-Cache-TTL: 600.000
+X-EDB-Cacheable: MAYBE: The user has a cookie of some sort. Maybe it's
+double choc-chip!
+X-EDB-Do-GZIP: false
+X-Powered-By: PHP/5.2.17
+X-Varnish: 484508634 484506789
+transfer-encoding: chunked
+Connection: keep-alive
+```
+
+## GET_HEADER_BY_NAME
+
+The `GET_HEADER_BY_NAME` procedure returns the header of the HTTP response according to the specified name. The signature is:
+
+```sql
+GET_HEADER_BY_NAME(<r> IN OUT UTL_HTTP.RESP, <name> VARCHAR2,
+<value> OUT VARCHAR2, <n> INTEGER DEFAULT 1)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+`name`
+
+ `name` is the name of the response header to retrieve.
+
+`value`
+
+ `value` is the value of the response header.
+
+`n`
+
+ `n` is the `nth` header of the HTTP response record to retrieve according to the values specified by `name`. The default is `1`.
+
+### Examples
+
+The following example retrieves the header for Content-Type.
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+    v_name          VARCHAR2(30) := 'Content-Type';
+    v_value         VARCHAR2(200);
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('www.enterprisedb.com');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    UTL_HTTP.GET_HEADER_BY_NAME(v_resp, v_name, v_value);
+    DBMS_OUTPUT.PUT_LINE(v_name || ': ' || v_value);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+
+Content-Type: text/html; charset=utf-8
+```
+
+## GET_HEADER_COUNT
+
+The `GET_HEADER_COUNT` function returns the number of HTTP response headers. The signature is:
+
+```sql
+GET_HEADER_COUNT(<r> IN OUT UTL_HTTP.RESP) RETURN INTEGER
+```
+
+This function returns an `INTEGER` value.
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+## GET_RESPONSE
+
+The `GET_RESPONSE` function sends the network request and returns any HTTP response. The signature is:
+
+```sql
+GET_RESPONSE(<r> IN OUT UTL_HTTP.REQ) RETURN UTL_HTTP.RESP
+```
+
+This function returns a `UTL_HTTP.RESP` record.
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+## GET_RESPONSE_ERROR_CHECK
+
+The `GET_RESPONSE_ERROR_CHECK` procedure returns whether response error check is set. The signature is:
+
+```sql
+GET_RESPONSE_ERROR_CHECK(<enable> OUT BOOLEAN)
+```
+
+### Parameters
+
+`enable`
+
+ `enable` returns `TRUE` if response error check is set. Otherwise it returns `FALSE`.
+
+## GET_TRANSFER_TIMEOUT
+
+The `GET_TRANSFER_TIMEOUT` procedure returns the current default transfer timeout setting for HTTP requests. The signature is:
+
+```sql
+GET_TRANSFER_TIMEOUT(<timeout> OUT INTEGER)
+```
+
+### Parameters
+
+`timeout`
+
+ `timeout` is the transfer timeout setting in seconds.
+
+## READ_LINE
+
+The `READ_LINE` procedure returns the data from the HTTP response body in text form until the end of line is reached. A `CR` character, a `LF` character, a `CR LF` sequence, or the end of the response body constitutes the end of line. The signature is:
+
+```sql
+READ_LINE(<r> IN OUT UTL_HTTP.RESP, <data> OUT VARCHAR2,
+<remove_crlf> BOOLEAN DEFAULT FALSE)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+`data`
+
+ `data` is the response body in text form.
+
+`remove_crlf`
+
+ Set `remove_crlf` to `TRUE` to remove new line characters. The default is `FALSE`.
+
+### Examples
+
+This example retrieves and displays the body of the specified website.
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+    v_value         VARCHAR2(1024);
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.enterprisedb.com');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    LOOP
+        UTL_HTTP.READ_LINE(v_resp, v_value, TRUE);
+        DBMS_OUTPUT.PUT_LINE(v_value);
+    END LOOP;
+    EXCEPTION
+        WHEN OTHERS THEN
+            UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+The following is the output.
+
+```sql
+__OUTPUT__
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en" dir="ltr">
+
+  <!-- ___________________________ HEAD ___________________________ -->
+
+  <head>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+
+
+    <title>EnterpriseDB | The Postgres Database Company</title>
+
+    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+<meta name="keywords" content="postgres, postgresql, postgresql installer,
+mysql migration, open source database, training, replication" />
+<meta name="description" content="The leader in open source database
+products, services, support, training and expertise based on PostgreSQL.
+Free downloads, documentation, and tutorials." />
+<meta name="abstract" content="The Enterprise PostgreSQL Company" />
+<link rel="EditURI" type="application/rsd+xml" title="RSD" href="http://
+www.enterprisedb.com/blogapi/rsd" />
+<link rel="alternate" type="application/rss+xml" title="EnterpriseDB RSS"
+href="http://www.enterprisedb.com/rss.xml" />
+<link rel="shortcut icon" href="/sites/all/themes/edb_pixelcrayons/
+favicon.ico" type="image/x-icon" />
+    <link type="text/css" rel="stylesheet" media="all" href="/sites/default/
+    files/css/css_db11adabae0aed6b79a2c3c52def4754.css" />
+<!--[if IE 6]>
+<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/
+oho_basic/css/ie6.css?g" />
+<![endif]-->
+<!--[if IE 7]>
+<link type="text/css" rel="stylesheet" media="all" href="/sites/all/themes/
+oho_basic/css/ie7.css?g" />
+<![endif]-->
+    <script type="text/javascript" src="/sites/default/files/js/
+    js_74d97b1176812e2fd6e43d62503a5204.js"></script>
+<script type="text/javascript">
+<!--//--><![CDATA[//><!--
+```
+
+## READ_RAW
+
+The `READ_RAW` procedure returns the data from the HTTP response body in binary form. The number of bytes returned is specified by the `len` parameter. The signature is:
+
+```sql
+READ_RAW(<r> IN OUT UTL_HTTP.RESP, <data> OUT RAW, <len> INTEGER)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+`data`
+
+ `data` is the response body in binary form.
+
+`len`
+
+ Set `len` to the number of bytes of data to return.
+
+### Examples
+
+This example retrieves and displays the first 150 bytes in binary form.
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+    v_data          RAW;
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.enterprisedb.com');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    UTL_HTTP.READ_RAW(v_resp, v_data, 150);
+    DBMS_OUTPUT.PUT_LINE(v_data);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+The following is the output from the example.
+
+```sql
+__OUTPUT__
+\x3c21444f43545950452068746d6c205055424c494320222d2f2f5733432f2f4454442058485
+44d4c20312e30205374726963742f2f454e220d0a202022687474703a2f2f7777772e77332e6f
+72672f54522f7868746d6c312f4454442f7868746d6c312d7374726963742e647464223e0d0a3
+c68746d6c20786d6c6e733d22687474703a2f2f7777772e77332e6f72672f313939392f
+```
+
+## READ_TEXT
+
+The `READ_TEXT` procedure returns the data from the HTTP response body in text form. The maximum number of characters returned is specified by the `len` parameter. The signature is:
+
+```sql
+READ_TEXT(<r> IN OUT UTL_HTTP.RESP, <data> OUT VARCHAR2, <len> INTEGER)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP response record.
+
+`data`
+
+ `data` is the response body in text form.
+
+`len`
+
+ Set `len` to the maximum number of characters to return.
+
+### Examples
+
+This example retrieves the first 150 characters:
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+    v_data          VARCHAR2(150);
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.enterprisedb.com');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    UTL_HTTP.READ_TEXT(v_resp, v_data, 150);
+    DBMS_OUTPUT.PUT_LINE(v_data);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+The following is the output:
+
+```sql
+__OUTPUT__
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/
+```
+
+## REQUEST
+
+The `REQUEST` function returns the first 2000 bytes retrieved from a URL. The signature is:
+
+```sql
+REQUEST(<url> IN VARCHAR2) RETURN VARCHAR2
+```
+
+If the data found at the URL is longer than 2000 bytes, the remainder is discarded. If the data found at the given URL is shorter than 2000 bytes, the result is shorter than 2000 bytes.
+
+### Parameters
+
+`url`
+
+ `url` is the Uniform Resource Locator from which `UTL_HTTP` returns content.
+
+### Example
+
+This command returns the first 2000 bytes retrieved from the EDB website:
+
+```sql
+SELECT UTL_HTTP.REQUEST('http://www.enterprisedb.com/') FROM DUAL;
+```
+
+## REQUEST_PIECES
+
+The `REQUEST_PIECES` function returns a table of 2000-byte segments retrieved from a URL. The signature is:
+
+```sql
+REQUEST_PIECES(<url> IN VARCHAR2, <max_pieces> NUMBER IN
+DEFAULT 32767) RETURN UTL_HTTP.HTML_PIECES
+```
+
+### Parameters
+
+`url`
+
+ `url` is the Uniform Resource Locator from which `UTL_HTTP` returns content.
+
+`max_pieces`
+
+ `max_pieces` specifies the maximum number of 2000-byte segments that the `REQUEST_PIECES` function returns. If `max_pieces` specifies more units than are available at the specified URL, the final unit contains fewer bytes.
+
+### Example
+
+This example returns the first four 2000-byte segments retrieved from the EDB website:
+
+```sql
+DECLARE
+    result UTL_HTTP.HTML_PIECES;
+BEGIN
+result := UTL_HTTP.REQUEST_PIECES('http://www.enterprisedb.com/', 4);
+END;
+```
+
+## SET_BODY_CHARSET
+
+The `SET_BODY_CHARSET` procedure sets the default character set of the body of future HTTP requests. The signature is:
+
+```sql
+SET_BODY_CHARSET(<charset> VARCHAR2 DEFAULT NULL)
+```
+
+### Parameters
+
+`charset`
+
+ `charset` is the character set of the body of future requests. The default is null, meaning the database character set is assumed.
+
+## SET_FOLLOW_REDIRECT
+
+The `SET_FOLLOW_REDIRECT` procedure sets the maximum number of times to follow the HTTP redirect instruction in the response to this request or future requests. This procedures has two signatures:
+
+```sql
+SET_FOLLOW_REDIRECT(<max_redirects> IN INTEGER DEFAULT 3)
+```
+
+and
+
+```sql
+SET_FOLLOW_REDIRECT(<r> IN OUT UTL_HTTP.REQ, <max_redirects>
+IN INTEGER DEFAULT 3)
+```
+
+Use the second form to change the maximum number of redirections for an individual request that a request inherits from the session default settings.
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`max_redirects`
+
+ `max_redirects` is the maximum number of redirections allowed. Set to `0` to disable redirections. The default is `3`.
+
+## SET_HEADER
+
+The `SET_HEADER` procedure sets the HTTP request header. The signature is:
+
+```sql
+SET_HEADER(<r> IN OUT UTL_HTTP.REQ, <name> IN VARCHAR2, <value>
+IN VARCHAR2 DEFAULT NULL)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`name`
+
+ `name` is the name of the request header.
+
+`value`
+
+ `value` is the value of the request header. The default is null.
+
+## SET_RESPONSE_ERROR_CHECK
+
+The `SET_RESPONSE_ERROR_CHECK` procedure determines whether to interpret HTTP 4xx and 5xx status codes returned by the `GET_RESPONSE` function as errors. The signature is:
+
+```sql
+SET_RESPONSE_ERROR_CHECK(<enable> IN BOOLEAN DEFAULT FALSE)
+```
+
+### Parameters
+
+`enable`
+
+ Set `enable` to `TRUE` if you want to treat HTTP 4xx and 5xx status codes as errors. The default is `FALSE`.
+
+## SET_TRANSFER_TIMEOUT
+
+The `SET_TRANSFER_TIMEOUT` procedure sets the default transfer timeout setting for waiting for a response from an HTTP request. This procedure has two signatures:
+
+```sql
+SET_TRANSFER_TIMEOUT(<timeout> IN INTEGER DEFAULT 60)
+```
+
+and
+
+```sql
+SET_TRANSFER_TIMEOUT(<r> IN OUT UTL_HTTP.REQ, <timeout> IN
+INTEGER DEFAULT 60)
+```
+
+Use the second form to change the transfer timeout setting for an individual request that a request inherits from the session default settings.
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`timeout`
+
+ `timeout` is the transfer timeout setting in seconds for HTTP requests. The default is 60 seconds.
+
+## WRITE_LINE
+
+The `WRITE_LINE` procedure writes data to the HTTP request body in text form. The text is terminated with a CRLF character pair. The signature is:
+
+```sql
+WRITE_LINE(<r> IN OUT UTL_HTTP.REQ, <data> IN VARCHAR2)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`data`
+
+ `data` is the request body in `TEXT` form.
+
+### Example
+
+This example writes data (`Account balance $500.00`) in text form to the request body to send using the HTTP `POST` method. The data is sent to a web application that accepts and processes data (`post.php`).
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.example.com/post.php',
+       'POST');
+    UTL_HTTP.SET_HEADER(v_req, 'Content-Length', '23');
+    UTL_HTTP.WRITE_LINE(v_req, 'Account balance $500.00');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    DBMS_OUTPUT.PUT_LINE('Status Code: ' || v_resp.status_code);
+    DBMS_OUTPUT.PUT_LINE('Reason Phrase: ' || v_resp.reason_phrase);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+Assuming the web application successfully processed the `POST` method, the following output is displayed:
+
+```sql
+__OUTPUT__
+Status Code: 200
+Reason Phrase: OK
+```
+
+## WRITE_RAW
+
+The `WRITE_RAW` procedure writes data to the HTTP request body in binary form. The signature is:
+
+```sql
+WRITE_RAW(<r> IN OUT UTL_HTTP.REQ, <data> IN RAW)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`data`
+
+ `data` is the request body in binary form.
+
+### Example
+
+This example writes data in binary form to the request body to send using the HTTP `POST` method to a web application that accepts and processes such data.
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.example.com/post.php',
+       'POST');
+    UTL_HTTP.SET_HEADER(v_req, 'Content-Length', '23');
+    UTL_HTTP.WRITE_RAW(v_req, HEXTORAW
+('54657374696e6720504f5354206d6574686f6420696e20485454502072657175657374'));
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    DBMS_OUTPUT.PUT_LINE('Status Code: ' || v_resp.status_code);
+    DBMS_OUTPUT.PUT_LINE('Reason Phrase: ' || v_resp.reason_phrase);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+The text string shown in the `HEXTORAW` function is the hexadecimal translation of the text `Testing POST method in HTTP request`.
+
+When the web application successfully processes the `POST` method, the following output is displayed:
+
+```sql
+__OUTPUT__
+Status Code: 200
+Reason Phrase: OK
+```
+
+## WRITE_TEXT
+
+The `WRITE_TEXT` procedure writes data to the HTTP request body in text form. The signature is:
+
+```sql
+WRITE_TEXT(<r> IN OUT UTL_HTTP.REQ, <data> IN VARCHAR2)
+```
+
+### Parameters
+
+`r`
+
+ `r` is the HTTP request record.
+
+`data`
+
+ `data` is the request body in text form.
+
+### Example
+
+This example writes data (`Account balance $500.00`) in text form to the request body to send using the HTTP `POST` method. The data is sent to a web application that accepts and processes data (`post.php`).
+
+```sql
+DECLARE
+    v_req           UTL_HTTP.REQ;
+    v_resp          UTL_HTTP.RESP;
+BEGIN
+    v_req := UTL_HTTP.BEGIN_REQUEST('http://www.example.com/post.php',
+       'POST');
+    UTL_HTTP.SET_HEADER(v_req, 'Content-Length', '23');
+    UTL_HTTP.WRITE_TEXT(v_req, 'Account balance $500.00');
+    v_resp := UTL_HTTP.GET_RESPONSE(v_req);
+    DBMS_OUTPUT.PUT_LINE('Status Code: ' || v_resp.status_code);
+    DBMS_OUTPUT.PUT_LINE('Reason Phrase: ' || v_resp.reason_phrase);
+    UTL_HTTP.END_RESPONSE(v_resp);
+END;
+```
+
+When the web application successfully processes the `POST` method, the following output is displayed:
+
+```sql
+__OUTPUT__
+Status Code: 200
+Reason Phrase: OK
+```
+
+## END_OF_BODY
+
+The `END_OF_BODY` exception is raised when it reaches the end of the HTTP response body.
+
+### Example
+
+This example handles the exception and writes `Exception caught` in text form to the request body to send using the HTTP `POST` method. The data is sent to a web application that accepts and processes data (`post.php`).
+
+```sql
+DECLARE
+    req UTL_HTTP.REQ;
+    resp UTL_HTTP.RESP;
+    value VARCHAR2(32768);
+BEGIN
+    req := UTL_HTTP.BEGIN_REQUEST('https://www.google.com/');
+    resp := UTL_HTTP.GET_RESPONSE(req);
+LOOP
+    UTL_HTTP.READ_LINE(resp, value, TRUE);
+END LOOP;
+    UTL_HTTP.END_RESPONSE(resp);
+EXCEPTION
+    WHEN UTL_HTTP.END_OF_BODY THEN
+        DBMS_OUTPUT.PUT_LINE('Exception caught');
+        UTL_HTTP.END_RESPONSE(resp);
+END;
+```
+
+When the web application successfully processes the `POST` method, the following output is displayed:
+
+```sql
+__OUTPUT__
+Output is:
+Exception caught
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/22_utl_mail.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/22_utl_mail.mdx
new file mode 100644
index 00000000000..24c6794b51a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/22_utl_mail.mdx
@@ -0,0 +1,219 @@
+---
+title: "UTL_MAIL"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.35.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.208.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.166.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/22_utl_mail/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_MAIL` package manages email. EDB Postgres Advanced Server supports the following procedures.
+
+| Function/procedure                                                                                                                                        | Return Type | Description                                                                 |
+| --------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------- |
+| `SEND(sender, recipients, cc, bcc, subject, message [, mime_type [, priority ]])`                                                                         | n/a         | Packages and sends an email to an SMTP server.                             |
+| `SEND_ATTACH_RAW(sender, recipients, cc, bcc, subject, message, mime_type, priority, attachment [, att_inline [, att_mime_type [, att_filename ]]])`      | n/a         | Same as the `SEND` procedure but with `BYTEA` or large object attachments. |
+| `SEND_ATTACH_VARCHAR2(sender, recipients, cc, bcc, subject, message, mime_type, priority, attachment [, att_inline [, att_mime_type [, att_filename ]]])` | n/a         | Same as the `SEND` procedure but with `VARCHAR2` attachments.              |
+
+!!! Note
+    An administrator must grant execute privileges to each user or group before they can use this package.
+
+## SEND
+
+The `SEND` procedure sends an email to an SMTP server.
+
+```sql
+SEND(<sender> VARCHAR2, <recipients> VARCHAR2, <cc> VARCHAR2,
+  <bcc> VARCHAR2, <subject> VARCHAR2, <message> VARCHAR2
+  [, <mime_type> VARCHAR2 [, <priority> PLS_INTEGER ]])
+```
+
+### Parameters
+
+`sender`
+
+ Email address of the sender.
+
+`recipients`
+
+ Comma-separated email addresses of the recipients.
+
+`cc`
+
+ Comma-separated email addresses of copy recipients.
+
+`bcc`
+
+ Comma-separated email addresses of blind copy recipients.
+
+`subject`
+
+ Subject line of the email.
+
+`message`
+
+ Body of the email.
+
+`mime_type`
+
+ Mime type of the message. The default is `text/plain; charset=us-ascii`.
+
+`priority`
+
+ Priority of the email The default is `3`.
+
+### Examples
+
+The following anonymous block sends a simple email message.
+
+```sql
+DECLARE
+    v_sender        VARCHAR2(30);
+    v_recipients    VARCHAR2(60);
+    v_subj          VARCHAR2(20);
+    v_msg           VARCHAR2(200);
+BEGIN
+    v_sender := 'jsmith@enterprisedb.com';
+    v_recipients := 'ajones@enterprisedb.com,rrogers@enterprisedb.com';
+    v_subj := 'Holiday Party';
+    v_msg := 'This year''s party is scheduled for Friday, Dec. 21 at ' ||
+             '6:00 PM. Please RSVP by Dec. 15th.';
+    UTL_MAIL.SEND(v_sender,v_recipients,NULL,NULL,v_subj,v_msg);
+END;
+```
+
+## SEND_ATTACH_RAW
+
+The `SEND_ATTACH_RAW` procedure sends an email to an SMTP server with an attachment containing either `BYTEA` data or a large object (identified by the large object's `OID`). You can write the call to `SEND_ATTACH_RAW` in two ways:
+
+```sql
+SEND_ATTACH_RAW(<sender> VARCHAR2, <recipients> VARCHAR2,
+  <cc> VARCHAR2, <bcc> VARCHAR2, <subject> VARCHAR2, <message> VARCHAR2,
+  <mime_type> VARCHAR2, <priority> PLS_INTEGER,
+  <attachment> BYTEA[, <att_inline> BOOLEAN
+  [, <att_mime_type> VARCHAR2[, <att_filename> VARCHAR2 ]]])
+```
+
+or
+
+```sql
+SEND_ATTACH_RAW(<sender> VARCHAR2, <recipients> VARCHAR2,
+  <cc> VARCHAR2, <bcc> VARCHAR2, <subject> VARCHAR2, <message> VARCHAR2,
+  <mime_type> VARCHAR2, <priority> PLS_INTEGER, <attachment> OID
+  [, <att_inline> BOOLEAN [, <att_mime_type> VARCHAR2
+  [, <att_filename> VARCHAR2 ]]])
+```
+
+### Parameters
+
+`sender`
+
+ Email address of the sender.
+
+`recipients`
+
+ Comma-separated email addresses of the recipients.
+
+`cc`
+
+ Comma-separated email addresses of copy recipients.
+
+`bcc`
+
+ Comma-separated email addresses of blind copy recipients.
+
+`subject`
+
+ Subject line of the email.
+
+`message`
+
+ Body of the email.
+
+`mime_type`
+
+ Mime type of the message. The default is `text/plain; charset=us-ascii`.
+
+`priority`
+
+ Priority of the email. The default is `3`.
+
+`attachment`
+
+ The attachment.
+
+`att_inline`
+
+ If set to `TRUE`, then the attachment is viewable inline. The default is `TRUE`.
+
+`att_mime_type`
+
+ Mime type of the attachment. The default is `application/octet`.
+
+`att_filename`
+
+ The file name containing the attachment. The default is `NULL`.
+
+## SEND_ATTACH_VARCHAR2
+
+The `SEND_ATTACH_VARCHAR2` procedure sends an email to an SMTP server with a text attachment.
+
+```sql
+SEND_ATTACH_VARCHAR2(<sender> VARCHAR2, <recipients> VARCHAR2, <cc>
+VARCHAR2, <bcc> VARCHAR2, <subject> VARCHAR2, <message> VARCHAR2,
+<mime_type> VARCHAR2, <priority> PLS_INTEGER, <attachment> VARCHAR2 [,
+<att_inline> BOOLEAN [, <att_mime_type> VARCHAR2 [, <att_filename> VARCHAR2
+]]])
+```
+
+### Parameters
+
+`sender`
+
+ Email address of the sender.
+
+`recipients`
+
+ Comma-separated email addresses of the recipients.
+
+`cc`
+
+ Comma-separated email addresses of copy recipients.
+
+`bcc`
+
+ Comma-separated email addresses of blind copy recipients.
+
+`subject`
+
+ Subject line of the email.
+
+`message`
+
+ Body of the email.
+
+`mime_type`
+
+ Mime type of the message. The default is `text/plain; charset=us-ascii`.
+
+`priority`
+
+ Priority of the email The default is `3.`
+
+`attachment`
+
+ The `VARCHAR2` attachment.
+
+`att_inline`
+
+ If set to `TRUE`, then the attachment is viewable inline. The default is `TRUE`.
+
+`att_mime_type`
+
+ Mime type of the attachment. The default is `text/plain; charset=us-ascii`.
+
+`att_filename`
+
+ The file name containing the attachment. The default is `NULL`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/23_utl_raw.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/23_utl_raw.mdx
new file mode 100644
index 00000000000..ce67794877b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/23_utl_raw.mdx
@@ -0,0 +1,280 @@
+---
+title: "UTL_RAW"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.36.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.209.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.167.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/23_utl_raw/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_RAW` package allows you to manipulate or retrieve the length of raw data types.
+
+!!! Note
+    An administrator must grant execute privileges to each user or group before they can use this package.
+
+| Function/procedure                                                   | Function or procedure | Return type | Description                                                                                  |
+| -------------------------------------------------------------------- | --------------------- | ----------- | -------------------------------------------------------------------------------------------- |
+| `CAST_TO_RAW(c IN VARCHAR2)`                                         | Function              | `RAW`       | Converts a `VARCHAR2` string to a `RAW` value.                                               |
+| `CAST_TO_VARCHAR2(r IN RAW)`                                         | Function              | `VARCHAR2`  | Converts a `RAW` value to a `VARCHAR2` string.                                               |
+| `CONCAT(r1 IN RAW, r2 IN RAW, r3 IN RAW,…)`                          | Function              | `RAW`       | Concatenates multiple `RAW` values into a single `RAW` value.                                 |
+| `CONVERT(r IN RAW, to_charset IN VARCHAR2, from_charset IN VARCHAR2)`| Function              | `RAW`       | Converts encoded data from one encoding to another and returns the result as a `RAW` value. |
+| `LENGTH(r IN RAW)`                                                   | Function              | `NUMBER`    | Returns the length of a `RAW` value.                                                         |
+| `SUBSTR(r IN RAW, pos IN INTEGER, len IN INTEGER)`                   | Function              | `RAW`       | Returns a portion of a `RAW` value.                                                          |
+
+EDB Postgres Advanced Server's implementation of `UTL_RAW` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in the table are supported.
+
+## CAST_TO_RAW
+
+The `CAST_TO_RAW` function converts a `VARCHAR2` string to a `RAW` value. The signature is:
+
+```sql
+CAST_TO_RAW(<c> VARCHAR2)
+```
+
+The function returns a `RAW` value if you pass a non-`NULL` value. If you pass a `NULL` value, the function returns `NULL`.
+
+### Parameters
+
+`c`
+
+ The `VARCHAR2` value to convert to `RAW`.
+
+### Example
+
+This example uses the `CAST_TO_RAW` function to convert a `VARCHAR2` string to a `RAW` value:
+
+```sql
+DECLARE
+  v VARCHAR2;
+  r RAW;
+BEGIN
+  v := 'Accounts';
+  dbms_output.put_line(v);
+  r := UTL_RAW.CAST_TO_RAW(v);
+  dbms_output.put_line(r);
+END;
+```
+
+The result set includes the content of the original string and the converted `RAW` value:
+
+```text
+Accounts
+\x4163636f756e7473
+```
+
+## CAST_TO_VARCHAR2
+
+The `CAST_TO_VARCHAR2` function converts `RAW` data to `VARCHAR2` data. The signature is:
+
+```sql
+CAST_TO_VARCHAR2(<r> RAW)
+```
+
+The function returns a `VARCHAR2` value if you pass a non-`NULL` value. If you pass a `NULL` value, the function returns `NULL`.
+
+### Parameters
+
+`r`
+
+ The `RAW` value to convert to a `VARCHAR2` value.
+
+### Example
+
+This example uses the `CAST_TO_VARCHAR2` function to convert a `RAW` value to a `VARCHAR2` string:
+
+```sql
+DECLARE
+  r RAW;
+  v VARCHAR2;
+BEGIN
+  r := '\x4163636f756e7473'
+  dbms_output.put_line(v);
+  v := UTL_RAW.CAST_TO_VARCHAR2(r);
+  dbms_output.put_line(r);
+END;
+```
+
+The result set includes the content of the original string and the converted `RAW` value:
+
+```text
+\x4163636f756e7473
+Accounts
+```
+
+## CONCAT
+
+The `CONCAT` function concatenates multiple `RAW` values into a single `RAW` value. The signature is:
+
+```sql
+CONCAT(<r1> RAW, <r2> RAW, <r3> RAW,…)
+```
+
+The function returns a `RAW` value. Unlike the Oracle implementation, the EDB Postgres Advanced Server implementation is a variadic function and doesn't place a restriction on the number of values that can be concatenated.
+
+### Parameters
+
+`r1, r2, r3,…`
+
+ The `RAW` values for `CONCAT` to concatenate.
+
+### Example
+
+This example uses the `CONCAT` function to concatenate multiple `RAW` values into a single `RAW` value:
+
+```sql
+SELECT UTL_RAW.CAST_TO_VARCHAR2(UTL_RAW.CONCAT('\x61', '\x62', '\x63')) FROM
+DUAL;
+__OUTPUT__
+ concat
+--------
+ abc
+(1 row)
+```
+
+The result (the concatenated values) is then converted to `VARCHAR2` format by the `CAST_TO_VARCHAR2` function.
+
+## CONVERT
+
+The `CONVERT` function converts a string from one encoding to another encoding and returns the result as a `RAW` value. The signature is:
+
+```sql
+CONVERT(<r> RAW, <to_charset> VARCHAR2, <from_charset> VARCHAR2)
+```
+
+The function returns a `RAW` value.
+
+### Parameters
+
+`r`
+
+ The `RAW` value to convert.
+
+`to_charset`
+
+ The name of the encoding to which `r` is converted.
+
+`from_charset`
+
+ The name of the encoding from which `r` is converted.
+
+### Example
+
+This example uses the `UTL_RAW.CAST_TO_RAW` function to convert a `VARCHAR2` string (`Accounts`) to a raw value. It then converts the value from `UTF8` to `LATIN7` and then from `LATIN7` to `UTF8`:
+
+```sql
+DECLARE
+  r RAW;
+  v VARCHAR2;
+BEGIN
+  v:= 'Accounts';
+  dbms_output.put_line(v);
+  r:= UTL_RAW.CAST_TO_RAW(v);
+  dbms_output.put_line(r);
+  r:= UTL_RAW.CONVERT(r, 'UTF8', 'LATIN7');
+  dbms_output.put_line(r);
+  r:= UTL_RAW.CONVERT(r, 'LATIN7', 'UTF8');
+  dbms_output.put_line(r);
+```
+
+The example returns the `VARCHAR2` value, the `RAW` value, and the converted values:
+
+```text
+Accounts
+\x4163636f756e7473
+\x4163636f756e7473
+\x4163636f756e7473
+```
+
+## LENGTH
+
+The `LENGTH` function returns the length of a `RAW` value. The signature is:
+
+```sql
+LENGTH(<r> RAW)
+```
+
+The function returns a `RAW` value.
+
+### Parameters
+
+`r`
+
+ The `RAW` value for `LENGTH` to evaluate.
+
+### Example
+
+This example uses the `LENGTH` function to return the length of a `RAW` value:
+
+```sql
+SELECT UTL_RAW.LENGTH(UTL_RAW.CAST_TO_RAW('Accounts')) FROM DUAL;
+__OUTPUT__
+ length
+--------
+ 8
+(1 row)
+```
+
+This example uses the `LENGTH` function to return the length of a `RAW` value that includes multi-byte characters:
+
+```sql
+SELECT UTL_RAW.LENGTH(UTL_RAW.CAST_TO_RAW('独孤求败'));
+__OUTPUT__
+ length
+--------
+     12
+(1 row)
+```
+
+## SUBSTR
+
+The `SUBSTR` function returns a substring of a `RAW` value. The signature is:
+
+```sql
+SUBSTR (<r> RAW, <pos> INTEGER, <len> INTEGER)
+```
+
+This function returns a `RAW` value.
+
+### Parameters
+
+`r`
+
+ The `RAW` value from which the substring is returned.
+
+`pos`
+
+ The position of the first byte of the returned substring in the `RAW` value .
+
+-   If `pos` is `0` or `1`, the substring begins at the first byte of the `RAW` value.
+-   If `pos` is greater than one, the substring begins at the first byte specified by `pos`. For example, if `pos` is `3`, the substring begins at the third byte of the value.
+-   If `pos` is negative, the substring begins at `pos` bytes from the end of the source value. For example, if `pos` is `-3`, the substring begins at the third byte from the end of the value.
+
+`len`
+
+ The maximum number of bytes to return.
+
+### Example
+
+This example uses the `SUBSTR` function to select a substring that begins `3` bytes from the start of a `RAW` value:
+
+```sql
+SELECT UTL_RAW.SUBSTR(UTL_RAW.CAST_TO_RAW('Accounts'), 3, 5) FROM DUAL;
+__OUTPUT__
+ substr
+--------
+ count
+(1 row)
+```
+
+This example uses the `SUBSTR` function to select a substring that starts 5 bytes from the end of a `RAW` value:
+
+```sql
+SELECT UTL_RAW.SUBSTR(UTL_RAW.CAST_TO_RAW('Accounts'), -5 , 3) FROM DUAL;
+__OUTPUT__
+ substr
+--------
+ oun
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/24_utl_smtp.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/24_utl_smtp.mdx
new file mode 100644
index 00000000000..333a53a2dcb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/24_utl_smtp.mdx
@@ -0,0 +1,462 @@
+---
+title: "UTL_SMTP"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.37.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.210.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.168.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/24_utl_smtp/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_SMTP` package sends emails over the Simple Mail Transfer Protocol (SMTP).
+
+!!! Note
+    An administrator must grant execute privileges to each user or group before they can use this package.
+
+| Function/procedure                               | Function or procedure | Return type  | Description                                                                      |
+| ------------------------------------------------ | --------------------- | ------------ | -------------------------------------------------------------------------------- |
+| `CLOSE_DATA(c IN OUT)`                           | Procedure             | n/a          | End an email message.                                                          |
+| `COMMAND(c IN OUT, cmd [, arg ])`                | Both                  | `REPLY`      | Execute an SMTP command.                                                         |
+| `COMMAND_REPLIES(c IN OUT, cmd [, arg ])`        | Function              | `REPLIES`    | Execute an SMTP command where multiple reply lines are expected.                 |
+| `DATA(c IN OUT, body VARCHAR2)`                  | Procedure             | n/a          | Specify the body of an email message.                                           |
+| `EHLO(c IN OUT, domain)`                         | Procedure             | n/a          | Perform initial handshaking with an SMTP server and return extended information. |
+| `HELO(c IN OUT, domain)`                         | Procedure             | n/a          | Perform initial handshaking with an SMTP server                                  |
+| `HELP(c IN OUT [, command ])`                    | Function              | `REPLIES`    | Send the `HELP` command.                                                         |
+| `MAIL(c IN OUT, sender [, parameters ])`         | Procedure             | n/a          | Start a mail transaction.                                                        |
+| `NOOP(c IN OUT)`                                 | Both                  | `REPLY`      | Send the null command.                                                           |
+| `OPEN_CONNECTION(host [, port [, tx_timeout ]])` | Function              | `CONNECTION` | Open a connection.                                                               |
+| `OPEN_DATA(c IN OUT)`                            | Both                  | `REPLY`      | Send the `DATA` command.                                                         |
+| `QUIT(c IN OUT)`                                 | Procedure             | n/a          | Terminate the SMTP session and disconnect.                                       |
+| `RCPT(c IN OUT, recipient [, parameters ])`      | Procedure             | n/a          | Specify the recipient of an email message.                                      |
+| `RSET(c IN OUT)`                                 | Procedure             | n/a          | Terminate the current mail transaction.                                          |
+| `VRFY(c IN OUT, recipient)`                      | Function              | `REPLY`      | Validate an email address.                                                      |
+| `WRITE_DATA(c IN OUT, data)`                     | Procedure             | n/a          | Write a portion of the email message.                                           |
+
+EDB Postgres Advanced Server's implementation of `UTL_SMTP` is a partial implementation when compared to Oracle's version. Only the functions and procedures listed in the table are supported.
+
+The following table lists the public variables available in the `UTL_SMTP` package.
+
+| Public variables | Data type | Value | Description                        |
+| ---------------- | --------- | ----- | ---------------------------------- |
+| `connection`     | `RECORD`  |       | Description of an SMTP connection. |
+| `reply`          | `RECORD`  |       | SMTP reply line.                   |
+
+## CONNECTION
+
+The `CONNECTION` record type provides a description of an SMTP connection.
+
+```sql
+TYPE connection IS RECORD (
+    host            VARCHAR2(255),
+    port            PLS_INTEGER,
+    tx_timeout      PLS_INTEGER
+);
+```
+
+<div id="reply_replies" class="registered_link"></div>
+
+## REPLY/REPLIES
+
+The `REPLY` record type provides a description of an SMTP reply line. `REPLIES` is a table of multiple SMTP reply lines.
+
+```sql
+TYPE reply IS RECORD (
+    code            INTEGER,
+    text            VARCHAR2(508)
+);
+TYPE replies IS TABLE OF reply INDEX BY BINARY_INTEGER;
+```
+
+## CLOSE_DATA
+
+The `CLOSE_DATA` procedure terminates an email message by sending the following sequence:
+
+`<CR><LF>.<CR><LF>`
+
+This is a single period at the beginning of a line.
+
+```sql
+CLOSE_DATA(<c> IN OUT CONNECTION)
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection to close.
+
+## COMMAND
+
+The `COMMAND` procedure executes an SMTP command. If you're expecting multiple reply lines, use `COMMAND_REPLIES`.
+
+```sql
+<reply> REPLY COMMAND(<c> IN OUT CONNECTION, <cmd> VARCHAR2
+   [, <arg> VARCHAR2 ])
+
+COMMAND(<c> IN OUT CONNECTION, <cmd> VARCHAR2 [, <arg> VARCHAR2 ])
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection to which to send the command.
+
+`cmd`
+
+ The SMTP command to process.
+
+`arg`
+
+ An argument to the SMTP command. The default is null.
+
+`reply`
+
+ SMTP reply to the command. If SMTP returns multiple replies, only the last one is returned in `reply`.
+
+ See [Reply/Replies](#replyreplies) for a description of `REPLY` and `REPLIES`.
+
+## COMMAND_REPLIES
+
+The `COMMAND_REPLIES` function processes an SMTP command that returns multiple reply lines. Use `COMMAND` if you expect only a single reply line.
+
+```sql
+<replies> REPLIES COMMAND(<c> IN OUT CONNECTION, <cmd> VARCHAR2
+   [, <arg> VARCHAR2 ])
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection to which to send the command.
+
+`cmd`
+
+ The SMTP command to process.
+
+`arg`
+
+ An argument to the SMTP command. The default is null.
+
+`replies`
+
+ SMTP reply lines to the command. See [Reply/Replies](#replyreplies) for a description of `REPLY` and `REPLIES`.
+
+## DATA
+
+The `DATA` procedure specifies the body of the email message. The message is terminated with a `<CR><LF>.<CR><LF>` sequence.
+
+```sql
+DATA(<c> IN OUT CONNECTION, <body> VARCHAR2)
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection to which to send the command.
+
+`body`
+
+ Body of the email message to send.
+
+## EHLO
+
+The `EHLO` procedure performs initial handshaking with the SMTP server after establishing the connection. The `EHLO` procedure allows the client to identify itself to the SMTP server according to RFC 821. RFC 1869 specifies the format of the information returned in the server’s reply. The `HELO` procedure performs the equivalent functionality but returns less information about the server.
+
+```sql
+EHLO(<c> IN OUT CONNECTION, <domain> VARCHAR2)
+```
+
+### Parameters
+
+`c`
+
+ The connection to the SMTP server over which to perform handshaking.
+
+`domain`
+
+ Domain name of the sending host.
+
+## HELO
+
+The `HELO` procedure performs initial handshaking with the SMTP server after establishing the connection. The `HELO` procedure allows the client to identify itself to the SMTP server according to RFC 821. The `EHLO` procedure performs the equivalent functionality but returns more information about the server.
+
+```sql
+HELO(<c> IN OUT, <domain> VARCHAR2)
+```
+
+### Parameters
+
+`c`
+
+ The connection to the SMTP server over which to perform handshaking.
+
+`domain`
+
+ Domain name of the sending host.
+
+## HELP
+
+The `HELP` function sends the `HELP` command to the SMTP server.
+
+```sql
+<replies> REPLIES HELP(<c> IN OUT CONNECTION [, <command> VARCHAR2 ])
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection to which to send the command.
+
+`command`
+
+ Command for which you want help.
+
+`replies`
+
+ SMTP reply lines to the command. See [Reply/Replies](#replyreplies) for a description of `REPLY` and `REPLIES`.
+
+## MAIL
+
+The `MAIL` procedure initiates a mail transaction.
+
+```sql
+MAIL(<c> IN OUT CONNECTION, <sender> VARCHAR2 [, <parameters> VARCHAR2 ])
+```
+
+### Parameters
+
+`c`
+
+ Connection to SMTP server on which to start a mail transaction.
+
+`sender`
+
+ The sender’s email address.
+
+`parameters`
+
+ Mail command parameters in the format `key=value` as defined in RFC 1869.
+
+## NOOP
+
+The `NOOP` function/procedure sends the null command to the SMTP server. The `NOOP` has no effect on the server except to obtain a successful response.
+
+```sql
+<reply> REPLY NOOP(<c> IN OUT CONNECTION)
+
+NOOP(<c> IN OUT CONNECTION)
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection on which to send the command.
+
+`reply`
+
+ SMTP reply to the command. If SMTP returns multiple replies, only the last one is returned in `reply`. See [Reply/Replies](#replyreplies) for a description of `REPLY` and `REPLIES`.
+
+## OPEN_CONNECTION
+
+The `OPEN_CONNECTION` functions open a connection to an SMTP server.
+
+```sql
+<c> CONNECTION OPEN_CONNECTION(<host> VARCHAR2 [, <port>
+PLS_INTEGER [, <tx_timeout> PLS_INTEGER DEFAULT NULL]])
+```
+
+### Parameters
+
+`host`
+
+ Name of the SMTP server.
+
+`port`
+
+ Port number on which the SMTP server is listening. The default is `25`.
+
+`tx_timeout`
+
+ Timeout value in seconds. Specify `0` to indicate not to wait. Set this value to null to wait indefinitely. The default is null.
+
+`c`
+
+ Connection handle returned by the SMTP server.
+
+## OPEN_DATA
+
+The `OPEN_DATA` procedure sends the `DATA` command to the SMTP server.
+
+```sql
+OPEN_DATA(<c> IN OUT CONNECTION)
+```
+
+### Parameters
+
+`c`
+
+ SMTP connection on which to send the command.
+
+## QUIT
+
+The `QUIT` procedure closes the session with an SMTP server.
+
+```sql
+QUIT(<c> IN OUT CONNECTION)
+```
+
+### Parameters
+
+`c`
+
+ SMTP connection to terminate.
+
+## RCPT
+
+The `RCPT` procedure provides the email address of the recipient. To schedule multiple recipients, invoke `RCPT` multiple times.
+
+```sql
+RCPT(<c> IN OUT CONNECTION, <recipient> VARCHAR2 [, <parameters> VARCHAR2 ])
+```
+
+### Parameters
+
+`c`
+
+ Connection to SMTP server on which to add a recipient.
+
+`recipient`
+
+ The recipient’s email address.
+
+`parameters`
+
+ Mail command parameters in the format `key=value` as defined in RFC 1869.
+
+## RSET
+
+The `RSET` procedure terminates the current mail transaction.
+
+```sql
+RSET(<c> IN OUT CONNECTION)
+```
+
+### Parameters
+
+`c`
+
+ SMTP connection on which to cancel the mail transaction.
+
+## VRFY
+
+The `VRFY` function validates and verifies the recipient’s email address. If valid, the recipient’s full name and fully qualified mailbox are returned.
+
+```sql
+<reply> REPLY VRFY(<c> IN OUT CONNECTION, <recipient> VARCHAR2)
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection on which to verify the email address.
+
+`recipient`
+
+ The recipient’s email address to verify.
+
+`reply`
+
+ SMTP reply to the command. If SMTP returns multiple replies, only the last one is returned in `reply`. See [Reply/Replies](#replyreplies) for a description of `REPLY` and `REPLIES`.
+
+## WRITE_DATA
+
+The `WRITE_DATA` procedure adds `VARCHAR2` data to an email message. You can call the `WRITE_DATA` procedure repeatedly to add data.
+
+```sql
+WRITE_DATA(<c> IN OUT CONNECTION, <data> VARCHAR2)
+```
+
+### Parameters
+
+`c`
+
+ The SMTP connection on which to add data.
+
+`data`
+
+ Data to add to the email message. The data must conform to the RFC 822 specification.
+
+## Comprehensive example
+
+This procedure constructs and sends a text email message using the `UTL_SMTP` package.
+
+```sql
+CREATE OR REPLACE PROCEDURE send_mail (
+    p_sender        VARCHAR2,
+    p_recipient     VARCHAR2,
+    p_subj          VARCHAR2,
+    p_msg           VARCHAR2,
+    p_mailhost      VARCHAR2
+)
+IS
+    v_conn          UTL_SMTP.CONNECTION;
+    v_crlf          CONSTANT VARCHAR2(2) := CHR(13) || CHR(10);
+    v_port          CONSTANT PLS_INTEGER := 25;
+BEGIN
+    v_conn := UTL_SMTP.OPEN_CONNECTION(p_mailhost,v_port);
+    UTL_SMTP.HELO(v_conn,p_mailhost);
+    UTL_SMTP.MAIL(v_conn,p_sender);
+    UTL_SMTP.RCPT(v_conn,p_recipient);
+    UTL_SMTP.DATA(v_conn, SUBSTR(
+        'Date: ' || TO_CHAR(SYSDATE,
+        'Dy, DD Mon YYYY HH24:MI:SS') || v_crlf
+        || 'From: ' || p_sender || v_crlf
+        || 'To: ' || p_recipient || v_crlf
+        || 'Subject: ' || p_subj || v_crlf
+        || p_msg
+        , 1, 32767));
+    UTL_SMTP.QUIT(v_conn);
+END;
+
+EXEC send_mail('asmith@enterprisedb.com','pjones@enterprisedb.com','Holiday
+Party','Are you planning to attend?','smtp.enterprisedb.com');
+```
+
+This example uses the `OPEN_DATA`, `WRITE_DATA`, and `CLOSE_DATA` procedures instead of the `DATA` procedure.
+
+```sql
+CREATE OR REPLACE PROCEDURE send_mail_2 (
+    p_sender        VARCHAR2,
+    p_recipient     VARCHAR2,
+    p_subj          VARCHAR2,
+    p_msg           VARCHAR2,
+    p_mailhost      VARCHAR2
+)
+IS
+    v_conn          UTL_SMTP.CONNECTION;
+    v_crlf          CONSTANT VARCHAR2(2) := CHR(13) || CHR(10);
+    v_port          CONSTANT PLS_INTEGER := 25;
+BEGIN
+    v_conn := UTL_SMTP.OPEN_CONNECTION(p_mailhost,v_port);
+    UTL_SMTP.HELO(v_conn,p_mailhost);
+    UTL_SMTP.MAIL(v_conn,p_sender);
+    UTL_SMTP.RCPT(v_conn,p_recipient);
+    UTL_SMTP.OPEN_DATA(v_conn);
+    UTL_SMTP.WRITE_DATA(v_conn,'From: ' || p_sender || v_crlf);
+    UTL_SMTP.WRITE_DATA(v_conn,'To: ' || p_recipient || v_crlf);
+    UTL_SMTP.WRITE_DATA(v_conn,'Subject: ' || p_subj || v_crlf);
+    UTL_SMTP.WRITE_DATA(v_conn,v_crlf || p_msg);
+    UTL_SMTP.CLOSE_DATA(v_conn);
+    UTL_SMTP.QUIT(v_conn);
+END;
+
+EXEC send_mail_2('asmith@enterprisedb.com','pjones@enterprisedb.com','Holiday
+Party','Are you planning to attend?','smtp.enterprisedb.com');
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/25_utl_url.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/25_utl_url.mdx
new file mode 100644
index 00000000000..43b9bedce04
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/25_utl_url.mdx
@@ -0,0 +1,158 @@
+---
+title: "UTL_URL"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.38.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.211.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.169.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/25_utl_url/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `UTL_URL` package provides a way to escape illegal and reserved characters in a URL.
+
+| Function/procedure                                | Return type | Description                                                                       |
+| ------------------------------------------------- | ----------- | --------------------------------------------------------------------------------- |
+| `ESCAPE(url, escape_reserved_chars, url_charset)` | `VARCHAR2`  | Use the `ESCAPE` function to escape any illegal and reserved characters in a URL. |
+| `UNESCAPE(url, url_charset)`                      | `VARCHAR2`  | Use the `UNESCAPE` function to convert a URL to its original form.                  |
+
+The `UTL_URL` package returns the `BAD_URL` exception if the call to a function includes a URL formed incorrectly.
+
+## ESCAPE
+
+Use the `ESCAPE` function to escape illegal and reserved characters in a URL. The signature is:
+
+```sql
+ESCAPE(<url> VARCHAR2, <escape_reserved_chars> BOOLEAN,
+<url_charset> VARCHAR2)
+```
+
+Reserved characters are replaced with a percent sign followed by the two-digit hex code of the ASCII value for the escaped character.
+
+### Parameters
+
+`url`
+
+ `url` specifies the Uniform Resource Locator that `UTL_URL` escapes.
+
+`escape_reserved_chars`
+
+ `escape_reserved_chars` is a Boolean value that instructs the `ESCAPE` function to escape reserved characters as well as illegal characters:
+
+-   If `escaped_reserved_chars` is `FALSE`, `ESCAPE` escapes only the illegal characters in the specified URL.
+-   If `escape_reserved_chars` is `TRUE`, `ESCAPE` escapes both the illegal characters and the reserved characters in the specified URL.
+
+    By default, `escape_reserved_chars` is `FALSE`.
+
+    In a URL, legal characters are:
+
+    | Uppercase A through Z | Lowercase a through z | 0 through 9           |
+    | --------------------- | --------------------- | --------------------- |
+    | asterisk (\*)         | exclamation point (!) | hyphen (-)            |
+    | left parenthesis (()  | period (.)            | right parenthesis ()) |
+    | single-quote (')      | tilde (~)             | underscore (\_)       |
+
+    Some characters are legal in some parts of a URL while illegal in others. To review comprehensive rules about illegal characters, refer to RFC 2396. Some examples of characters that are considered illegal in any part of a URL are:
+
+    | Illegal character     | Escape sequence |
+    | --------------------- | --------------- |
+    | a blank space ( )     | `%20`           |
+    | curly braces ({ or }) | `%7b` and `%7d` |
+    | hash mark (#)         | `%23`           |
+
+    The `ESCAPE` function treats the following characters as reserved and escapes them if `escape_reserved_chars` is set to `TRUE`:
+
+    | Reserved character | Escape sequence |
+    | ------------------ | --------------- |
+    | ampersand (&)      | `%5C`           |
+    | at sign (@)        | `%25`           |
+    | colon (:)          | `%3a`           |
+    | comma (,)          | `%2c`           |
+    | dollar sign ($)    | `%24`           |
+    | equal sign (=)     | `%3d`           |
+    | plus sign (+)      | `%2b`           |
+    | question mark (?)  | `%3f`           |
+    | semi-colon (;)     | `%3b`           |
+    | slash (/)          | `%2f`           |
+
+`url_charset`
+
+ `url_charset` specifies a character set to which to convert a given character before escaping it. If `url_charset` is `NULL`, the character isn't converted. The default value of `url_charset` is `ISO-8859-1`.
+
+### Examples
+
+This anonymous block uses the `ESCAPE` function to escape the blank spaces in the URL:
+
+```sql
+DECLARE
+  result varchar2(400);
+BEGIN
+ result := UTL_URL.ESCAPE('http://www.example.com/Using the ESCAPE
+function.html');
+  DBMS_OUTPUT.PUT_LINE(result);
+END;
+```
+
+The resulting escaped URL is:
+
+```text
+http://www.example.com/Using%20the%20ESCAPE%20function.html
+```
+
+Suppose you include a value of `TRUE` for the `escape_reserved_chars` parameter when invoking the function:
+
+```sql
+DECLARE
+  result varchar2(400);
+BEGIN
+ result := UTL_URL.ESCAPE('http://www.example.com/Using the ESCAPE
+function.html', TRUE);
+  DBMS_OUTPUT.PUT_LINE(result);
+END;
+```
+
+The `ESCAPE` function escapes the reserved characters as well as the illegal characters in the URL:
+
+```text
+http%3A%2F%2Fwww.example.com%2FUsing%20the%20ESCAPE%20function.html
+```
+
+## UNESCAPE
+
+The `UNESCAPE` function removes escape characters added to an URL by the `ESCAPE` function, converting the URL to its original form.
+
+The signature is:
+
+```sql
+UNESCAPE(<url> VARCHAR2, <url_charset> VARCHAR2)
+```
+
+### Parameters
+
+`url`
+
+ `url` specifies the Uniform Resource Locator that `UTL_URL` unescapes.
+
+`url_charset`
+
+ After unescaping a character, the character is assumed to be in `url_charset` encoding and is converted from that encoding to database encoding before being returned. If `url_charset` is `NULL`, the character isn't converted. The default value of `url_charset` is `ISO-8859-1`.
+
+### Examples
+
+This anonymous block uses the `ESCAPE` function to escape the blank spaces in the URL:
+
+```sql
+DECLARE
+  result varchar2(400);
+BEGIN
+ result := 
+UTL_URL.UNESCAPE('http://www.example.com/Using%20the%20UNESCAPE%20function.html');
+  DBMS_OUTPUT.PUT_LINE(result);
+END;
+```
+
+The resulting (unescaped) URL is:
+
+```text
+http://www.example.com/Using the UNESCAPE function.html
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/address.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/address.mdx
new file mode 100644
index 00000000000..c936fdeaa73
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/address.mdx
@@ -0,0 +1,34 @@
+---
+title: ADDRESS
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/address/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<ADDRESS>` and `</ADDRESS>` tags, which specify the address, author, and signature of a document.
+
+## Syntax
+
+The following is the syntax for HTP: 
+
+```
+HTP.ADDRESS (
+   cvalue         IN       VARCHAR2
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ADDRESS (cvalue, cnowrap, cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cvalue | The string between the `<ADDRESS>` and `</ADDRESS>` tags |
+| cnowrap | If the value for this parameter isn't `NULL`, adds the NOWRAP attribute in the tag |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/anchor.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/anchor.mdx
new file mode 100644
index 00000000000..04355617e79
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/anchor.mdx
@@ -0,0 +1,44 @@
+--- 
+title: ANCHOR and ANCHOR2
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/anchor/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<A>` and `</A>` HTML tags, which specify the source or destination of a hypertext link.
+
+## Syntax 
+
+The following is the syntax for HTP: 
+
+```
+HTP.ANCHOR (
+   curl           IN       VARCHAR2
+   ctext          IN       VARCHAR2
+   cname          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.ANCHOR2 (
+   curl           IN       VARCHAR2
+   ctext          IN       VARCHAR2
+   cname          IN       VARCHAR2   DEFAULT NULL
+   ctarget        IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ANCHOR (curl, ctext, cname, cattributes) RETURN VARCHAR2;
+
+HTF.ANCHOR2 (curl, ctext, cname, ctarget, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  | 
+| --------- | -------- |
+| curl | The value for the HREF attribute |
+| ctext | The string that goes between the `<A>` and `</A>` tags | 
+| cname | The value for the NAME attribute | 
+| ctarget | The value for the TARGET attribute | 
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/applet.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/applet.mdx
new file mode 100644
index 00000000000..0ebc49198f5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/applet.mdx
@@ -0,0 +1,38 @@
+---
+title: APPLETOPEN and APPLETCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/applet/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+`htp.appletopen` generates the `<APPLET>` HTML tag, which invokes a Java applet. Close the applet with `htp.appletclose`, which generates the `</APPLET>` HTML tag.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.APPLETOPEN(
+   ccode          IN       VARCHAR2
+   cheight        IN       NUMBER
+   cwidth         IN       NUMBER
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+
+HTP.APPLETCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.APPLETOPEN(ccode, cheight, cwidth, cattributes) RETURN VARCHAR2;
+
+HTF.APPLETCLOSE RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ccode | The value for the CODE attribute, which specifies the name of the applet class | 
+| cheight | The value for the HEIGHT attribute |
+| cwidth | The value for the WIDTH attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/area.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/area.mdx
new file mode 100644
index 00000000000..ac6f0d5d183
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/area.mdx
@@ -0,0 +1,38 @@
+---
+title: AREA
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/area/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<AREA>` HTML tag, which defines a client-side image map.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.AREA(
+   ccoords        IN       VARCHAR2
+   cshape         IN       VARCHAR2   DEFAULT NULL
+   chref          IN       VARCHAR2   DEFAULT NULL
+   cnohref        IN       VARCHAR2   DEFAULT NULL
+   ctarget        IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.AREA(ccoords, cshape, chref, cnohref, ctarget, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ccoords | The value for the COORDS attribute |
+| cshape | The value for the SHAPE attribute | 
+| chref | The value for the HREF attribute | 
+| cnohref | If the value for this parameter isn't `NULL`, adds the NOHREF attribute to the tag |
+| ctarget | The value for the TARGET attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/base.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/base.mdx
new file mode 100644
index 00000000000..d3cb2133352
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/base.mdx
@@ -0,0 +1,28 @@
+---
+title: BASE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/base/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<BASE>` HTML tag, which records the URL of the document.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BASE(ctarget, cattributes) RETURN VARCHAR2;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BASE(ctarget, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctarget | The value for the TARGET attribute, which establishes a window name to which all links in this document are targeted |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/basefont.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/basefont.mdx
new file mode 100644
index 00000000000..c80c9ad4da4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/basefont.mdx
@@ -0,0 +1,27 @@
+---
+title: BASEFONT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/basefont/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<BASEFONT>` HTML tag, which specifies the base font size for a web page.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```     
+HTP.BASEFONT(nsize IN INTEGER);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BASEFONT(nsize) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| nsize | The value for the SIZE attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bgsound.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bgsound.mdx
new file mode 100644
index 00000000000..b1d1a64a3d5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bgsound.mdx
@@ -0,0 +1,32 @@
+---
+title: BGSOUND
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bgsound/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<BGSOUND>` HTML tag, which includes audio for a web page.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BGSOUND(
+   csrc           IN       VARCHAR2
+   cloop          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BGSOUND(csrc, cloop, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| csrc | The value for the SRC attribute |
+| cloop | The value for the LOOP attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/big.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/big.mdx
new file mode 100644
index 00000000000..ea63e9de339
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/big.mdx
@@ -0,0 +1,30 @@
+---
+title: BIG
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/big/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<BIG>` and `</BIG>` tags, which increase font size.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BIG(
+ctext       IN VARCHAR2 CHARACTER SET ANY_CS,
+cattributes IN VARCHAR2 DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BIG(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text that goes between the tags |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/blockquote.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/blockquote.mdx
new file mode 100644
index 00000000000..f55608867fd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/blockquote.mdx
@@ -0,0 +1,36 @@
+---
+title: BLOCKQUOTEOPEN and BLOCKQUOTECLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/blockquote/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<BLOCKQUOTE>` and `</BLOCKQUOTE>` tags, which mark a block of quoted text.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BLOCKQUOTEOPEN (
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.blockquoteClose;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BLOCKQUOTEOPEN (cnowrap, cclear, cattributes) RETURN VARCHAR2;
+
+HTF.BLOCKQUOTECLOSE RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cnowrap | If the value for this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/body.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/body.mdx
new file mode 100644
index 00000000000..d0ff38b9112
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/body.mdx
@@ -0,0 +1,34 @@
+---
+title: BODYOPEN and BODYCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/body/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<BODY>` and `</BODY>` tags, which mark the body section of an HTML document.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BODYOPEN(
+   cbackground    IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.bodyClose;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BODYOPEN(cbackground, cattributes) RETURN VARCHAR2;
+
+HTF.BODYCLOSE RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cbackground | The value for the BACKGROUND attribute, which specifies a graphic file to use for the background of the document |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bold.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bold.mdx
new file mode 100644
index 00000000000..07bfaae2a5b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bold.mdx
@@ -0,0 +1,31 @@
+---
+title: BOLD
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/bold/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<B>` and `</B>` tags, which display the text in bold.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.BOLD (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.BOLD (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text that goes between the tags |
+| cattributes | Other attributes to include as is in the tag |
+
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/br_and_nl.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/br_and_nl.mdx
new file mode 100644
index 00000000000..9d0561236e2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/br_and_nl.mdx
@@ -0,0 +1,36 @@
+---
+title: BR and NL
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/br_and_nl/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<BR>` tag, which begins a new line of text.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.NL (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.br (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.NL (cclear, cattributes) RETURN VARCHAR2;
+
+HTF.BR (cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/caption.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/caption.mdx
new file mode 100644
index 00000000000..8bfd74f7e79
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/caption.mdx
@@ -0,0 +1,32 @@
+---
+title: TABLECAPTION
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/caption/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This procedure and function generates the `<CAPTION>` and `</CAPTION>` tags, which insert a caption in an HTML table.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TABLECAPTION (
+   ccaption       IN       VARCHAR2
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.TABLECAPTION (ccaption, calign, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ccaption | The text for the caption |
+| calign | The value for the ALIGN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/center.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/center.mdx
new file mode 100644
index 00000000000..087f4a169be
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/center.mdx
@@ -0,0 +1,27 @@
+---
+title: CENTER
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/center/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<CENTER>` and `</CENTER>` tags, which center text in a web page.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.CENTER(ctext IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.CENTER(ctext IN VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | Centers the text |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/centeropen_and_centerclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/centeropen_and_centerclose.mdx
new file mode 100644
index 00000000000..5217f638461
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/centeropen_and_centerclose.mdx
@@ -0,0 +1,25 @@
+---
+title: CENTEROPEN and CENTERCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/centeropen_and_centerclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<CENTER>` and `</CENTER>` tags, which mark the text to center.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.CENTEROPEN;
+
+HTP.CENTERCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.CENTEROPEN RETURN VARCHAR2;
+
+HTF.CENTERCLOSE RETURN VARCHAR2;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/cite.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/cite.mdx
new file mode 100644
index 00000000000..f3c8395c437
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/cite.mdx
@@ -0,0 +1,30 @@
+---
+title: CITE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/cite/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<CITE>` and `</CITE>` tags, which render text as a citation.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.CITE (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.CITE (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose |
+| --------- | -------- |
+| ctext | The text to render as a citation |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/code.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/code.mdx
new file mode 100644
index 00000000000..3fc0bd04351
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/code.mdx
@@ -0,0 +1,30 @@
+---
+title: CODE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/code/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<CODE>` and `</CODE>` tags, which render text in a monospace font.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.CODE (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.CODE (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose |
+| --------- | -------- |
+| ctext | The text to render as code |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/comment.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/comment.mdx
new file mode 100644
index 00000000000..e0248c2e096
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/comment.mdx
@@ -0,0 +1,27 @@
+---
+title: COMMENT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/comment/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the comment tags `<!-- ctext -->`.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.COMMENT (ctext IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.COMMENT (ctext IN VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text in the comment |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dfn.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dfn.mdx
new file mode 100644
index 00000000000..ee71338f245
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dfn.mdx
@@ -0,0 +1,29 @@
+---
+title: DFN
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dfn/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<DFN>` and `</DFN>` tags, which render text in italics.
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.DFN(ctext IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DFN(ctext IN VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters 
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in italics |
+
+
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dirlist.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dirlist.mdx
new file mode 100644
index 00000000000..9dedafd6a48
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dirlist.mdx
@@ -0,0 +1,25 @@
+---
+title: DIRLIST
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dirlist/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<DIR>` and `</DIR>` tags, which create a directory list section. 
+
+## Syntax 
+
+The following is the syntax for HTP:
+
+```
+HTP.DIRLISTOPEN;
+
+HTP.DIRLISTCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DIRLISTOPEN RETURN VARCHAR2;
+
+HTF.DIRLISTCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/div.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/div.mdx
new file mode 100644
index 00000000000..663c4aeb52f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/div.mdx
@@ -0,0 +1,30 @@
+---
+title: DIV
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/div/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<DIV>` tag, which creates document divisions.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.DIV(
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DIV(calign, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| calign | The value for the ALIGN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistdef.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistdef.mdx
new file mode 100644
index 00000000000..c936afbb4e3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistdef.mdx
@@ -0,0 +1,32 @@
+---
+title: DLISTDEF
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistdef/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<DD>` tag, which inserts a definition of terms. Use this tag for a definition list `<DL>`. Terms are tagged `<DT>`, and definitions are tagged `<DD>`.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+htp.DLISTDEF(
+   ctext          IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DLISTDEF(ctext, cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The definition for the term |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistopen_and_dlistclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistopen_and_dlistclose.mdx
new file mode 100644
index 00000000000..2c41386b77a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistopen_and_dlistclose.mdx
@@ -0,0 +1,34 @@
+---
+title: DLISTOPEN and DLISTCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistopen_and_dlistclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<DL>` and `</DL>` tags, which create a definition list.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.DLISTOPEN (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.dlistClose;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DLISTOPEN (cclear, cattributes) RETURN VARCHAR2;
+
+HTF.DLISTCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistterm.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistterm.mdx
new file mode 100644
index 00000000000..e26a27c86d1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistterm.mdx
@@ -0,0 +1,32 @@
+---
+title: DLISTTERM
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/dlistterm/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<DT>` tag, which defines a term in a definition list `<DL>`.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.DLISTTERM (
+   ctext          IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.DLISTTERM (ctext, cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The term |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/em_and_emphasis.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/em_and_emphasis.mdx
new file mode 100644
index 00000000000..81e5a0768ce
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/em_and_emphasis.mdx
@@ -0,0 +1,36 @@
+---
+title: EM and EMPHASIS
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/em_and_emphasis/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<EM>` and `</EM>` tags, which define text to emphasize.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.EM (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.emphasis (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.EM (ctext, cattributes) RETURN VARCHAR2;
+
+HTF.EMPHASIS (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to emphasize |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/escape_sc.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/escape_sc.mdx
new file mode 100644
index 00000000000..90732d44ef5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/escape_sc.mdx
@@ -0,0 +1,32 @@
+---
+title: ESCAPE_SC
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/escape_sc/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure replaces characters that have special meaning in HTML with their escape sequences. The following characters are converted:
+
+- `&` to `&amp;`
+- `""` to `&quot:`
+- `<` to `&lt;`
+- `>` to `&gt;`
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.ESCAPE_SC(ctext IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ESCAPE_SC(ctext in VARCHAR2) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The string to convert |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/font.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/font.mdx
new file mode 100644
index 00000000000..13fdc6b736a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/font.mdx
@@ -0,0 +1,38 @@
+---
+title: FONT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/font/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<FONT>` and `</FONT>` tags, which mark text with the specified font characteristics.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FONTOPEN(
+   ccolor         IN       VARCHAR2   DEFAULT NULL
+   cface          IN       VARCHAR2   DEFAULT NULL
+   csize          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.fontClose;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FONTOPEN(ccolor, cface, csize, cattributes) RETURN VARCHAR2;
+
+HTF.FONTCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ccolor | The value for the COLOR attribute |
+| cface | The value for the FACE attribute |
+| csize | The value for the SIZE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formcheckbox.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formcheckbox.mdx
new file mode 100644
index 00000000000..b2962bc5fa2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formcheckbox.mdx
@@ -0,0 +1,34 @@
+---
+title: FORMCHECKBOX
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formcheckbox/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="checkbox"`. This tag inserts a check box element in a form. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMCHECKBOX (
+   cname          IN       VARCHAR2
+   cvalue         IN       VARCHAR2   DEFAULT 'on'
+   cchecked       IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMCHECKBOX (cname, cvalue, cchecked, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cvalue | The value for the VALUE attribute |
+| cchecked | If the value for this parameter isn't `NULL`, adds the CHECKED attribute to the tag |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formfile.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formfile.mdx
new file mode 100644
index 00000000000..0b7a9e6778c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formfile.mdx
@@ -0,0 +1,32 @@
+---
+title: FORMFILE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formfile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="file"`. This tag allows the user to select files whose contents can be submitted with a form.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMFILE(
+   cname          IN       varchar2
+   caccept        IN       varchar2   DEFAULT NULL
+   cattributes    IN       varchar2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMFILE (cname, caccept, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| caccept | A comma-seperated list of MIME types for upload |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formhidden.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formhidden.mdx
new file mode 100644
index 00000000000..35d07acf007
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formhidden.mdx
@@ -0,0 +1,32 @@
+---
+title: FORMHIDDEN
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formhidden/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="hidden"`. This tag inserts a hidden form element that the user doesn't see. It submits additional values to the script.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMHIDDEN (
+   cname          IN       VARCHAR2
+   cvalue         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMHIDDEN (cname, cvalue, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cvalue | The value for the VALUE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formimage.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formimage.mdx
new file mode 100644
index 00000000000..9bd5454ed42
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formimage.mdx
@@ -0,0 +1,34 @@
+---
+title: FORMIMAGE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formimage/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="image"`. This tag creates an image field that the user clicks to submit the form.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMIMAGE (
+   cname          IN       VARCHAR2
+   csrc           IN       VARCHAR2
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMIMAGE (cname, csrc, calign, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| csrc | The value for the SRC attribute, which specifies the image file |
+| calign | The value for the ALIGN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formopen_and_formclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formopen_and_formclose.mdx
new file mode 100644
index 00000000000..a81a24bc88c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formopen_and_formclose.mdx
@@ -0,0 +1,40 @@
+---
+title: FORMOPEN and FORMCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formopen_and_formclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<FORM>` and `</FORM>` tags, which create a form section in an HTML document.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMOPEN (
+   curl           IN       VARCHAR2
+   cmethod        IN       VARCHAR2   DEFAULT 'POST'
+   ctarget        IN       VARCHAR2   DEFAULT NULL
+   cenctype       IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.FORMCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMOPEN (curl, cmethod, ctarget, cenctype, cattributes) RETURN VARCHAR2;
+
+HTF.FORMCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| curl | The URL of the WRB or CGI script where the contents of the form are sent (required) |
+| cmethod | The value for the METHOD attribute, either `'GET'` or `'POST'` |
+| ctarget | The value for the TARGET attribute |
+| cenctype | The value for the ENCTYPE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formpassword.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formpassword.mdx
new file mode 100644
index 00000000000..ace60a3db66
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formpassword.mdx
@@ -0,0 +1,36 @@
+---
+title: FORMPASSWORD
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formpassword/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="password"`. This tag creates a single-line text entry field.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMPASSWORD (
+   cname          IN       VARCHAR2
+   csize          IN       VARCHAR2
+   cmaxlength     IN       VARCHAR2   DEFAULT NULL
+   cvalue         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMPASSWORD (cname, csize, cmaxlength, cvalue, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| csize | The value for the SIZE attribute |
+| cmaxlength | The value for the MAXLENGTH attribute |
+| cvalue | The value for the VALUE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formradio.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formradio.mdx
new file mode 100644
index 00000000000..ed3a1741b4b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formradio.mdx
@@ -0,0 +1,34 @@
+---
+title: FORMRADIO
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formradio/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="radio"`. This tag creates a radio button (single-selection option) on the HTML form. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMRADIO (
+   cname          IN       VARCHAR2
+   cvalue         IN       VARCHAR2
+   cchecked       IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMRADIO (cname, cvalue, cchecked, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cvalue | The value for the VALUE attribute |
+| cchecked | If the value for this parameter isn't `NULL`, adds the CHECKED attribute to the tag |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formreset.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formreset.mdx
new file mode 100644
index 00000000000..007d7e03d72
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formreset.mdx
@@ -0,0 +1,30 @@
+---
+title: FORMRESET
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formreset/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="reset"`. This tag creates a button that resets the form fields to their initial values.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMRESET (
+   cvalue         IN       VARCHAR2   DEFAULT 'Reset'
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMRESET (cvalue, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cvalue | The value for the VALUE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectopen_and_formselectclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectopen_and_formselectclose.mdx
new file mode 100644
index 00000000000..391fb91c87f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectopen_and_formselectclose.mdx
@@ -0,0 +1,38 @@
+---
+title: FROMSELECTOPEN and FORMSELECTCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectopen_and_formselectclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<SELECT>` and `</SELECT>` tags, which create a select form element. A select form element is a list box from which the user selects one or more values. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+Htp.FORMSELECTOPEN (
+   cname          IN       VARCHAR2
+   cprompt        IN       VARCHAR2   DEFAULT NULL
+   nsize          IN       INTEGER    DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.formSelectClose;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMSELECTOPEN (cname, cprompt, nsize, cattributes) RETURN VARCHAR2;
+
+HTF.FORMSELECTCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cprompt | The string preceding the list box |
+| nsize | The value for the SIZE attribute |
+| cattributes | Other attributes to include as is in the tag|
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectoption.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectoption.mdx
new file mode 100644
index 00000000000..f98f8dea1f9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectoption.mdx
@@ -0,0 +1,32 @@
+---
+title: FORMSELECTOPTION
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formselectoption/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<OPTION>` tag, which represents one choice in a `<SELECT>` element.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMSELECTOPTION (
+   cvalue         IN       VARCHAR2
+   cselected      IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMSELECTOPTION (cvalue, cselected, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cvalue | The text for the option |
+| cselected | If the value for this parameter isn't `NULL`, adds the SELECTED attribute to the tag |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formsubmit.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formsubmit.mdx
new file mode 100644
index 00000000000..881f3591046
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formsubmit.mdx
@@ -0,0 +1,32 @@
+---
+title: FORMSUBMIT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formsubmit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE="submit"`. This tag creates a button that submits the form.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMSUBMIT (
+   cname          IN       VARCHAR2   DEFAULT NULL
+   cvalue         IN       VARCHAR2   DEFAULT 'Submit'
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMSUBMIT (cname, cvalue, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cvalue | The value for the VALUE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtext.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtext.mdx
new file mode 100644
index 00000000000..7c380ad81f8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtext.mdx
@@ -0,0 +1,36 @@
+---
+title: FORMTEXT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtext/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<INPUT>` tag with `TYPE=""text""`. This tag creates a field for a single line of text.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMTEXT (
+   cname          IN       VARCHAR2
+   csize          IN       VARCHAR2   DEFAULT NULL
+   cmaxlength     IN       VARCHAR2   DEFAULT NULL
+   cvalue         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMTEXT (cname, csize, cmaxlength, cvalue, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| csize | The value for the SIZE attribute |
+| cmaxlength | The value for the MAXLENGTH attribute |
+| cvalue | The value for the VALUE attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea.mdx
new file mode 100644
index 00000000000..4ec3f2ae3d7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea.mdx
@@ -0,0 +1,50 @@
+---
+title: FORMTEXTAREAOPEN, FORMTEXTAREAOPEN2, and FORMTEXTAREACLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<TEXTAREA>` and `</TEXTAREA>` tags, which create a text area form element. The difference between the two open functions and procedures is that `htp.formTextareaOpen2` has the `cwrap` parameter, which specifies a wrap style.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMTEXTAREAOPEN (
+   cname          IN       VARCHAR2
+   nrows          IN       INTEGER
+   ncolumns       IN       INTEGER
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.FORMTEXTAREAOPEN2(
+   cname          IN       VARCHAR2
+   nrows          IN       INTEGER
+   ncolumns       IN       INTEGER
+   calign         IN       V2         DEFAULT NULL
+   cwrap          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.FORMTEXTAREACLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMTEXTAREAOPEN (cname, nrows, ncolumns, calign, cattributes) RETURN VARCHAR2;
+
+HTF.FORMTEXTAREAOPEN2(cname, nrows, ncolumns, calign, cwrap, cattributes) RETURN VARCHAR2;
+HTF.FORMTEXTAREACLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| nrows | The integer value for the ROWS attribute  |
+| ncolumns | The integer value for the COLS attribute |
+| calign | The value for the ALIGN attribute |
+| cwrap | The value for the WRAP attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea_and_formtextarea2.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea_and_formtextarea2.mdx
new file mode 100644
index 00000000000..7ea76446c0a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea_and_formtextarea2.mdx
@@ -0,0 +1,47 @@
+---
+title: FORMTEXTAREA and FORMTEXTAREA2
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/formtextarea_and_formtextarea2/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<TEXTAREA>` tag, which creates a text field that has no predefined text in the text area. This field allows the user to enter several lines of text.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FORMTEXTAREA (
+   cname          IN       VARCHAR2
+   nrows          IN       INTEGER
+   ncolumns       IN       INTEGER
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.FORMTEXTAREA2 (
+   cname          IN       VARCHAR2
+   nrows          IN       INTEGER
+   ncolumns       IN       INTEGER
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cwrap          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       varchar2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FORMTEXTAREA (cname, nrows, ncolumns, calign, cattributes) RETURN VARCHAR2;
+
+HTF.FORMTEXTAREA2 (cname, nrows, ncolumns, calign, cwrap, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| nrows | The integer value for the ROWS attribute|
+| ncolumns | The integer value for the COLS attribute |
+| calign | The value for the ALIGN attribute |
+| cwrap | The value for the WRAP attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/frame.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/frame.mdx
new file mode 100644
index 00000000000..51a61866b7a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/frame.mdx
@@ -0,0 +1,40 @@
+---
+title: FRAME
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/frame/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<FRAME>` tag, which defines the characteristics of a frame created by a `<FRAMESET>` tag.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FRAME(
+   csrc           IN       VARCHAR2
+   cname          IN       VARCHAR2   DEFAULT NULL
+   cmarginwidth   IN       VARCHAR2   DEFAULT NULL
+   cmarginheight  IN       VARCHAR2   DEFAULT NULL
+   cscrolling     IN       VARCHAR2   DEFAULT NULL
+   cnoresize      IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FRAME (csrc, cname, cmarginwidth, cmarginheight, cscrolling, cnoresize, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| csrc | The URL to display in the frame |
+| cname | The value for the NAME attribute |
+| cmarginwidth | The value for the MARGINWIDTH attribute |
+| cmarginheight | The value for the MARGINHEIGHT attribute |
+| cscrolling | The value for the SCROLLING attribute |
+| noresize | If the value for this parameter isn't `NULL`, adds the NORESIZE attribute to the tag |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/framesetopen_and_framsetclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/framesetopen_and_framsetclose.mdx
new file mode 100644
index 00000000000..7ce6c45d02b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/framesetopen_and_framsetclose.mdx
@@ -0,0 +1,36 @@
+---
+title: FRAMESETOPEN and FRAMESETCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/framesetopen_and_framsetclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<FRAMESET>` and `</FRAMESET>` tags, which define a frame set section.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.FRAMESETOPEN(
+   crows          IN       VARCHAR2   DEFAULT NULL
+   ccols          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       varchar2   DEFAULT NULL);
+
+HTP.FRAMESETCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.FRAMESETOPEN (crows, ccols, cattributes) RETURN VARCHAR2;
+
+HTF.FORMSETCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| crows | The value for the ROWS attribute |
+| ccols | The value for the COLS attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/header.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/header.mdx
new file mode 100644
index 00000000000..659a9075c1a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/header.mdx
@@ -0,0 +1,38 @@
+---
+title: HEADER
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/header/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates heading tags (`<H1>` to `<H6>`) and their corresponding closing tags (`</H1>` to `</H6>`).
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.HEADER (
+   nsize          IN       INTEGER
+   cheader        IN       VARCHAR2
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.HEADER (nsize, cheader, calign, cnowrap, cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| nsize | The heading level, set as an integer between 1 and 6 |
+| calign | The value for the ALIGN attribute |
+| cheader | The text to display in the heading |
+| cnowrap | The value for the NOWRAP attribute |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/headopen_and_headclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/headopen_and_headclose.mdx
new file mode 100644
index 00000000000..735b16c3904
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/headopen_and_headclose.mdx
@@ -0,0 +1,25 @@
+---
+title: HEADOPEN and HEADCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/headopen_and_headclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<HEAD>` and `</HEAD>` tags, which mark the HTML document head section.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.HEADOPEN;
+
+HTP.HEADCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.HEADOPEN RETURN VARCHAR2;
+
+HTF.HEADCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/hr.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/hr.mdx
new file mode 100644
index 00000000000..4ccab45cd29
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/hr.mdx
@@ -0,0 +1,37 @@
+---
+title: HR
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/hr/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<HR>` tag, which generates a line in the HTML document.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.HR (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   csrc           IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.LINE (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   csrc           IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.HR (cclear, csrc, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute |
+| csrc | The value for the SRC attribute, which specifies a custom image as the source of the line |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/htmlopen_and_htmlclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/htmlopen_and_htmlclose.mdx
new file mode 100644
index 00000000000..0aa13478517
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/htmlopen_and_htmlclose.mdx
@@ -0,0 +1,25 @@
+---
+title: HTMLOPEN and HTMLCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/htmlopen_and_htmlclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<HTML>` and `</HTML>` tags, which mark the beginning and the end of an HTML document.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.HTMLOPEN;
+
+HTP.HTMLCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.HTMLOPEN RETURN VARCHAR2;
+
+HTF.HTMLCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/img.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/img.mdx
new file mode 100644
index 00000000000..bb1a38d1215
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/img.mdx
@@ -0,0 +1,46 @@
+---
+title: IMG and IMG2
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/img/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<IMG>` tag, which loads an image onto the HTML page. The difference between these syntaxes is that `htp.img2` uses the `cusemap` parameter.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.IMG (
+   curl           IN       VARCHAR2   DEFAULT NULL
+   calign         IN       VARCHAR2   DEFAULT NULL
+   calt           IN       VARCHAR2   DEFAULT NULL
+   cismap         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+htp.img2(
+   calign         IN       VARCHAR2   DEFAULT NULL
+   calt           IN       VARCHAR2   DEFAULT NULL
+   cismap         IN       VARCHAR2   DEFAULT NULL
+   cusemap        IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.IMG (curl, calign, calt, cismap, cattributes) RETURN VARCHAR2;
+
+HTF.IMG2(curl, calign, calt, cismap, cusemap, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| curl | The value for the SRC attribute. |
+| calign | The value for the ALIGN attribute. |
+| calt | The value for the ALT attribute, which specifies alternative text to display if the browser doesn't support images. |
+| cismap | If the value for this parameter isn't `NULL`, adds the ISMAP attribute to the tag. The attribute indicates that the image is an imagemap. |
+| cusemap | The value for the USEMAP attribute, which specifies a client-side image map. |
+| cattributes | Other attributes to include as is in the tag. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/index.mdx
new file mode 100644
index 00000000000..16412ca465d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/index.mdx
@@ -0,0 +1,18 @@
+---
+title: HTP and HTF
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The hypertext procedures (HTP) and hypertext functions (HTF) Oracle packages generate HTML tags. Each HTP has a corresponding HTF. They generate the same HTML tags and use the same parameters, but their syntaxes differ. For example, `htp.address` and `htf.address` both generate the `<ADDRESS>` and `</ADDRESS>` tags and use the same parameters. However, they have different syntaxes: 
+
+```
+HTP.ADDRESS (
+   cvalue         IN       VARCHAR2
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+```
+HTF.ADDRESS (cvalue, cnowrap, cclear, cattributes) RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/isindex.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/isindex.mdx
new file mode 100644
index 00000000000..8747fa5e00f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/isindex.mdx
@@ -0,0 +1,30 @@
+---
+title: ISINDEX
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/isindex/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure creates a single entry field with a text prompt, such as `"Enter value"`,  and then sends that value to the URL of the page or program.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.ISINDEX (
+   cprompt        IN       VARCHAR2    DEFAULT NULL
+   curl           IN       VARCHAR2    DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ISINDEX (cprompt, curl) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cprompt | The value for the PROMPT attribute |
+| curl | The value for the HREF attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/italic.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/italic.mdx
new file mode 100644
index 00000000000..5ef06d8e682
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/italic.mdx
@@ -0,0 +1,30 @@
+---
+title: ITALIC
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/italic/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<I>` and `</I>` tags, which render the text in italics.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.ITALIC (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ITALIC (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose |
+| --------- | -------- |
+| ctext | The text to be rendered in italics |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/kbd_and_keyboard.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/kbd_and_keyboard.mdx
new file mode 100644
index 00000000000..9ac1536acc9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/kbd_and_keyboard.mdx
@@ -0,0 +1,36 @@
+---
+title: KBD and KEYBOARD
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/kbd_and_keyboard/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<KBD>` and `</KBD>` tags, which render the text in a monospace font.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.KEYBOARD (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.KBD (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.KEYBOARD (ctext, cattributes) RETURN VARCHAR2;
+
+HTF.KBD (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in monospace |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrel.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrel.mdx
new file mode 100644
index 00000000000..1118039f943
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrel.mdx
@@ -0,0 +1,32 @@
+---
+title: LINKREL
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrel/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<LINK>` tag with the REL attribute. The REL attribute is the relationship described by the hypertext link from the anchor to the target.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.LINKREL (
+   crel           IN       VARCHAR2
+   curl           IN       VARCHAR2
+   ctitle         IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.LINKREL (crel, curl, ctitle) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| crel | The value for the REL attribute |
+| curl | The value for the HREF attribute |
+| ctitle | The value for the TITLE attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrev.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrev.mdx
new file mode 100644
index 00000000000..a70966927ea
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrev.mdx
@@ -0,0 +1,32 @@
+---
+title: LINKREV
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/linkrev/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<LINK>` tag with the REV attribute. The REV attribute is the relationship described by the hypertext link from the target to the anchor. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.LINKREV (
+   crev           IN       VARCHAR2
+   curl           IN       VARCHAR2
+   ctitle         IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.LINKREV (crev, curl, ctitle) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| crev | The value for the REV attribute |
+| curl | The value for the HREF attribute |
+| ctitle | The value for the TITLE attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listheader.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listheader.mdx
new file mode 100644
index 00000000000..0e20b4065c7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listheader.mdx
@@ -0,0 +1,30 @@
+---
+title: LISTHEADER
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listheader/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<LH>` and `</LH>` tags, which print an HTML tag at the beginning of the list.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.LISTHEADER (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.LISTHEADER (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to place between `<LH>` and `</LH>` |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listingopen_and_listingclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listingopen_and_listingclose.mdx
new file mode 100644
index 00000000000..ca9919655e0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listingopen_and_listingclose.mdx
@@ -0,0 +1,25 @@
+---
+title: LISTINGOPEN and LISTINGCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listingopen_and_listingclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<LISTING>` and `</LISTING>` tags, which mark a section of fixed-width text in the body of an HTML page.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.LISTINGOPEN;
+
+HTP.LISTINGCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.LISTINGOPEN RETURN VARCHAR2;
+
+HTF.LISTINGCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listitem.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listitem.mdx
new file mode 100644
index 00000000000..3a528b0846c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listitem.mdx
@@ -0,0 +1,36 @@
+---
+title: LISTITEM
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/listitem/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<LI>` tag, which creates a list item.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.LISTITEM (
+   ctext          IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cdingbat       IN       VARCHAR2   DEFAULT NULL
+   csrc           IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.LISTITEM (ctext, cclear, cdingbat, csrc, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text for the list item |
+| cclear | The value for the CLEAR attribute |
+| cdingbat | The value for the DINGBAT attribute |
+| csrc | The value for the SRC attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mailto.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mailto.mdx
new file mode 100644
index 00000000000..419efe287b8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mailto.mdx
@@ -0,0 +1,34 @@
+---
+title: MAILTO
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mailto/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<A>` tag with HREF set to `'mailto'` prepended to the mail address argument.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.MAILTO (
+   caddress       IN       VARCHAR2
+   ctext          IN       VARCHAR2
+   cname          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.MAILTO (caddress, ctext, cname, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| caddress | The email address of the recipient |
+| ctext | The clickable portion of the link |
+| cname | The value for the NAME attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mapopen_and_mapclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mapopen_and_mapclose.mdx
new file mode 100644
index 00000000000..6c6ceb64719
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mapopen_and_mapclose.mdx
@@ -0,0 +1,34 @@
+---
+title: MAPOPEN and MAPCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/mapopen_and_mapclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<MAP>` and `</MAP>` tags, which mark a set of regions in a client-side image map.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.MAPOPEN(
+   cname          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.MAPCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.MAPOPEN(cname, cattributes) RETURN VARCHAR2;
+
+HTF.MAPCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/menulistopen_and_menulistclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/menulistopen_and_menulistclose.mdx
new file mode 100644
index 00000000000..daf2d6fac2a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/menulistopen_and_menulistclose.mdx
@@ -0,0 +1,25 @@
+---
+title: MENULISTOPEN and MENULISTCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/menulistopen_and_menulistclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These function and procedure generate the `<MENU>` and `</MENU>` tags, which create a list consisting of one line for each item. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.MENULISTOPEN;
+
+HTP.MENULISTCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.MENULISTOPEN RETURN VARCHAR2;
+
+HTF.MENULISTCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/meta.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/meta.mdx
new file mode 100644
index 00000000000..f18917f30e9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/meta.mdx
@@ -0,0 +1,32 @@
+---
+title: META
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/meta/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<META>` tag, which embeds meta-information about the document and specifies values for HTTP headers.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.META (
+   chttp_equiv    IN       VARCHAR2
+   cname          IN       VARCHAR2
+   ccontent       IN       VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.META (chttp_equiv, cname, ccontent) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| chttp_equiv | The value for the HTTP-EQUIV attribute |
+| cname | The value for the NAME attribute |
+| ccontent | The value for the CONTENT attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/nobr.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/nobr.mdx
new file mode 100644
index 00000000000..4915360f787
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/nobr.mdx
@@ -0,0 +1,27 @@
+---
+title: NOBR
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/nobr/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<NOBR>` and `</NOBR>` tags, which turn off line breaks for the tagged text.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.NOBR(ctext in VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.NOBR(ctext) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text that to render without a line break |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/noframesopen_and_noframesclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/noframesopen_and_noframesclose.mdx
new file mode 100644
index 00000000000..a963532f498
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/noframesopen_and_noframesclose.mdx
@@ -0,0 +1,25 @@
+---
+title: NOFRAMESOPEN and NOFRAMESCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/noframesopen_and_noframesclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<NOFRAMES>` and `</NOFRAMES>` tags, which mark a no-frames section.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.NOFRAMESOPEN
+
+HTP.NOFRAMESCLOSE
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.NOFRAMESOPEN RETURN VARCHAR2;
+
+HTF.NOFRAMESCLOSE RETURN VARCHAR2;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/olistopen_and_olistclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/olistopen_and_olistclose.mdx
new file mode 100644
index 00000000000..5fcea853353
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/olistopen_and_olistclose.mdx
@@ -0,0 +1,36 @@
+---
+title: OLISTOPEN and OLISTCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/olistopen_and_olistclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<OL>` and `</OL>` tags, which define an ordered (numbered) list.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.OLISTOPEN (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cwrap          IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.OLISTCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.OLISTOPEN (cclear, cwrap, cattributes) RETURN VARCHAR2;
+
+HTF.OLISTCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute |
+| cwrap | The value for the WRAP attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/para_and_paragraph.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/para_and_paragraph.mdx
new file mode 100644
index 00000000000..8f9d7d46358
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/para_and_paragraph.mdx
@@ -0,0 +1,38 @@
+---
+title: PARA and PARAGRAPH
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/para_and_paragraph/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<P>` tag, which marks the text as a paragraph. `htp.paragraph` enables you to add attributes to the tag.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PARA;
+
+HTP.PARAGRAPH (
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.PARA RETURN VARCHAR2;
+
+HTF.PARAGRAPH (calign, cnowrap, cclear, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| calign | The value for the ALIGN attribute |
+| cnowrap | If the value for this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/param.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/param.mdx
new file mode 100644
index 00000000000..646e64c9f48
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/param.mdx
@@ -0,0 +1,30 @@
+---
+title: PARAM
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/param/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<PARAM>` tag, which specifies parameter values for Java applets.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PARAM(
+   cname          IN       VARCHAR2
+   cvalue         IN       VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.PARAM(cname, cvalue) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cname | The value for the NAME attribute |
+| cvalue | The value for the VALUE attribute |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/plaintext.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/plaintext.mdx
new file mode 100644
index 00000000000..6afb38f2158
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/plaintext.mdx
@@ -0,0 +1,30 @@
+---
+title: PLAINTEXT
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/plaintext/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<PLAINTEXT>` and `</PLAINTEXT>` tags, which render text in a fixed-width font.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PLAINTEXT(
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.PLAINTEXT(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in fixed-width font |
+| cattributes | Other attributes to include as is in the tag |
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/preopen_and_preclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/preopen_and_preclose.mdx
new file mode 100644
index 00000000000..411d06abfba
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/preopen_and_preclose.mdx
@@ -0,0 +1,36 @@
+---
+title: PREOPEN and PRECLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/preopen_and_preclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These functions and procedures generate the `<PRE>` and `</PRE>` tags, which mark preformatted text in the body of the HTML page.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PREOPEN (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cwidth         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.PRECLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.PREOPEN (cclear, cwidth, cattributes) RETURN VARCHAR2;
+
+HTF.PRECLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute |
+| cwidth | The value for the WIDTH attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/print_and_prn.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/print_and_prn.mdx
new file mode 100644
index 00000000000..9ab97db52f1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/print_and_prn.mdx
@@ -0,0 +1,31 @@
+---
+title: PRINT and PRN
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/print_and_prn/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+`htp.print` generates the specified parameter as a string terminated with the `\n` newline character. The `\n` character is different from `<BR>`. 
+`htp.prn` generates the specified parameter as a string. Unlike `print`, the string isn't terminated with the `\n` newline character. 
+
+!!! Note
+    `PRINT` and `PRN` operate only as HTPs.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PRINT (cbuf IN VARCHAR2);
+HTP.PRINT (dbuf IN DATE);
+HTP.PRINT (nbuf IN NUMBER);
+
+HTP.PRN (cbuf IN VARCHAR2);
+HTP.PRN (dbuf IN DATE);
+HTP.PRN (nbuf IN NUMBER);
+```
+
+## Parameters
+
+| Parameter | Purpose |
+| --------- | -------- |
+| cbuf, dbuf, and nbuf | The string to generate |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/prints_and_ps.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/prints_and_ps.mdx
new file mode 100644
index 00000000000..bf11fc4c73d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/prints_and_ps.mdx
@@ -0,0 +1,30 @@
+---
+title: PRINTS and PS
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/prints_and_ps/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These procedures generate a string and replace the following characters with the corresponding escape sequence:
+
+- `<` with `&lt;`
+- `>` with `&gt;`
+- `""` with `&quot;`
+- `&` with `&amp;`
+
+!!! Note
+    `PRINTS` and `PS` operate only as HTPs. 
+    
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.PRINTS(ctext IN VARCHAR2);
+HTP.PS(ctext IN VARCHAR2);
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The string on which to perform character substitution |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/s.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/s.mdx
new file mode 100644
index 00000000000..d4b48d8e894
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/s.mdx
@@ -0,0 +1,30 @@
+---
+title: S
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/s/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<S>` and `</S>` tags, which render the text with a strikethrough.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.S(
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.S(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render with a strikethrough |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sample.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sample.mdx
new file mode 100644
index 00000000000..36120ad7fcb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sample.mdx
@@ -0,0 +1,30 @@
+---
+title: SAMPLE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sample/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<SAMP>` and `</SAMP>` tags, which render text in a monospace font.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.SAMPLE (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.SAMPLE (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in a monospace font |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/small.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/small.mdx
new file mode 100644
index 00000000000..c3388b08489
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/small.mdx
@@ -0,0 +1,30 @@
+---
+title: SMALL
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/small/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<SMALL>` and `</SMALL>` tags, which render text in a small font.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.SMALL(
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.SMALL(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in a small font |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strike.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strike.mdx
new file mode 100644
index 00000000000..5df0df0836a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strike.mdx
@@ -0,0 +1,30 @@
+---
+title: STRIKE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strike/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<STRIKE>` and `</STRIKE>` tags, which render text with a strikethrough.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.STRIKE(
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.STRIKE(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render with a strikethrough |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strong.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strong.mdx
new file mode 100644
index 00000000000..8d4907869ae
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strong.mdx
@@ -0,0 +1,30 @@
+---
+title: STRONG
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/strong/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<STRONG>` and `</STRONG>` tags, which render text in bold.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.STRONG (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.STRONG (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in bold |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/style.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/style.mdx
new file mode 100644
index 00000000000..604f6bd9e90
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/style.mdx
@@ -0,0 +1,27 @@
+---
+title: STYLE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/style/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<STYLE>` and `</STYLE>` tags, which include a style sheet in the web page.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.STYLE(cstyle IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.STYLE(cstyle) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cstyle | The style information to include |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sub.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sub.mdx
new file mode 100644
index 00000000000..d32461c7681
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sub.mdx
@@ -0,0 +1,32 @@
+---
+title: SUB
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sub/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<SUB>` and `</SUB>` tags, which render text in subscript.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.SUB(
+   ctext          IN       VARCHAR2
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.SUB(ctext, calign, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in subscript |
+| calign | The value for the ALIGN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sup.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sup.mdx
new file mode 100644
index 00000000000..aad1bd94e1c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sup.mdx
@@ -0,0 +1,32 @@
+---
+title: SUP
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/sup/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<SUP>` and `</SUP>` tags, which render text in superscript.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.SUP(
+   ctext          IN       VARCHAR2
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.SUP(ctext, calign, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in superscript |
+| calign | The value for the ALIGN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tabledata.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tabledata.mdx
new file mode 100644
index 00000000000..d6d2e2535f0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tabledata.mdx
@@ -0,0 +1,40 @@
+---
+title: TABLEDATA
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tabledata/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TD>` and `</TD>` tags, which insert data into a cell of an HTML table.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TABLEDATA (
+   cvalue         IN       VARCHAR2   DEFAULT NULL
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cdp            IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   crowspan       IN       VARCHAR2   DEFAULT NULL
+   ccolspan       IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.TABLEDATA (cvalue, calign, cdp, cnowrap, crowspan, ccolspan, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cvalue | The data for the cell in the table |
+| calign | The value for the ALIGN attribute |
+| cdp | The value for the DP attribute |
+| cnowrap | If the value of this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| crowspan | The value for the ROWSPAN attribute |
+| ccolspan | The value for the COLSPAN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableheader.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableheader.mdx
new file mode 100644
index 00000000000..5b0827a63ed
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableheader.mdx
@@ -0,0 +1,40 @@
+---
+title: TABLEHEADER
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableheader/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TH>` and `</TH>` tags, which insert a header cell in an HTML table. The `<TH>` tag is similar to the `<TD>` tag except that the text in the row is usually rendered in bold.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TABLEHEADER (
+   cvalue         IN       VARCHAR2   DEFAULT NULL
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cdp            IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   crowspan       IN       VARCHAR2   DEFAULT NULL
+   ccolspan       IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTP.TABLEHEADER (cvalue, calign, cdp, cnowrap, crowspan, ccolspan, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose |
+| --------- | -------- |
+| cvalue | The data for the cell in the table |
+| calign | The value for the ALIGN attribute |
+| cdp | The value for the DP attribute |
+| cnowrap | If the value of this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| crowspan | The value for the ROWSPAN attribute |
+| ccolspan| The value for the COLSPAN attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableopen_and_tableclose.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableopen_and_tableclose.mdx
new file mode 100644
index 00000000000..3902fc6df51
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableopen_and_tableclose.mdx
@@ -0,0 +1,40 @@
+---
+title: TABLEOPEN and TABLECLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tableopen_and_tableclose/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TABLE>` and `</TABLE>` tags, which define an HTML table.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TABLEOPEN (
+   cborder        IN       VARCHAR2   DEFAULT NULL
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.TABLECLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.TABLEOPEN (cborder, calign, cnowrap, cclear, cattributes) RETURN VARCHAR2;
+
+HTF.TABLECLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cborder | The value for the BORDER attribute |
+| calign | The value for the ALIGN attribute |
+| cnowrap | If the value of this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| cclear | The value for the CLEAR attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tablerow.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tablerow.mdx
new file mode 100644
index 00000000000..3c33016a5b4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tablerow.mdx
@@ -0,0 +1,40 @@
+---
+title: TABLEROWOPEN and TABLEROWCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/tablerow/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TR>` and `</TR>` tags, which insert a row in an HTML table.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TABLEROWOPEN (
+   calign         IN       VARCHAR2   DEFAULT NULL
+   cvalign        IN       VARCHAR2   DEFAULT NULL
+   cdp            IN       VARCHAR2   DEFAULT NULL
+   cnowrap        IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.TABLEROWCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.TABLEROWOPEN (calign, cvalign,cdp, cnowrap, cattributes) RETURN VARCHAR2;
+
+HTF.TABLEROWCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| calign | The value for the ALIGN attribute |
+| cvalign | The value for the VALIGN attribute |
+| cdp | The value for the DP attribute |
+| cnowrap | If the value of this parameter isn't `NULL`, adds the NOWRAP attribute to the tag |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/teletype.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/teletype.mdx
new file mode 100644
index 00000000000..0eba71b37ad
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/teletype.mdx
@@ -0,0 +1,30 @@
+---
+title: TELETYPE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/teletype/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TT>` and `</TT>` tags, which render text in a fixed-width, typewriter font such as Courier.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TELETYPE (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.TELETYPE (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in a fixed-width typewriter font |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/title.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/title.mdx
new file mode 100644
index 00000000000..ea67de88be6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/title.mdx
@@ -0,0 +1,27 @@
+---
+title: TITLE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/title/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<TITLE>` and `</TITLE>` tags, which specify the text to display in the title bar of the browser window.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.TITLE (ctitle IN VARCHAR2);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.TITLE (ctitle) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctitle | The text to display in the title bar of the browser window |
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ulist.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ulist.mdx
new file mode 100644
index 00000000000..f112c327e1d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ulist.mdx
@@ -0,0 +1,40 @@
+---
+title: ULISTOPEN and ULISTCLOSE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/ulist/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These function and procedure generate the `<UL>` and `</UL>` tags, which define an unordered (bullet) list. 
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.ULISTOPEN (
+   cclear         IN       VARCHAR2   DEFAULT NULL
+   cwrap          IN       VARCHAR2   DEFAULT NULL
+   cdingbat       IN       VARCHAR2   DEFAULT NULL
+   csrc           IN       VARCHAR2   DEFAULT NULL
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+
+HTP.ULISTCLOSE;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.ULISTOPEN (cclear, cwrap, cdingbat, csrc, cattributes) RETURN VARCHAR2;
+
+HTF.ULISTCLOSE RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| cclear | The value for the CLEAR attribute |
+| cwrap | The value for the WRAP attribute |
+| cdingbat | The value for the DINGBAT attribute |
+| csrc | The value for the SRC attribute |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/underline.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/underline.mdx
new file mode 100644
index 00000000000..360ef7d0a82
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/underline.mdx
@@ -0,0 +1,30 @@
+---
+title: UNDERLINE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/underline/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<U>` and `</U>` tags, which render text with an underline.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.UNDERLINE(
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.UNDERLINE(ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render with an underline |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/variable.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/variable.mdx
new file mode 100644
index 00000000000..520c9db170f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/variable.mdx
@@ -0,0 +1,30 @@
+---
+title: VARIABLE
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/variable/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<VAR>` and `</VAR>` tags, which render text in italics.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.VARIABLE (
+   ctext          IN       VARCHAR2
+   cattributes    IN       VARCHAR2   DEFAULT NULL);
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.VARIABLE (ctext, cattributes) RETURN VARCHAR2;
+```
+
+## Parameters
+
+| Parameter | Purpose  |
+| --------- | -------- |
+| ctext | The text to render in italics |
+| cattributes | Other attributes to include as is in the tag |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/wbr.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/wbr.mdx
new file mode 100644
index 00000000000..4a43bd17829
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/wbr.mdx
@@ -0,0 +1,21 @@
+---
+title: WBR
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/htp_and_htf/wbr/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+This function and procedure generates the `<WBR>` tag, which inserts a soft line break in text marked as NOBR.
+
+## Syntax
+
+The following is the syntax for HTP:
+
+```
+HTP.WBR;
+```
+
+The following is the syntax for HTF:
+
+```
+HTF.WBR RETURN WBR;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/index.mdx
new file mode 100644
index 00000000000..9eec8aa4825
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/index.mdx
@@ -0,0 +1,25 @@
+---
+title: "Built-in packages"
+indexCards: simple
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.11.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/03_built-in_packages/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Built-in packages are provided with EDB Postgres Advanced Server. For certain packages, non-superusers must be explicitly granted the `EXECUTE` privilege on the package before using any of the package’s functions or procedures. For most of the built-in packages, `EXECUTE` privilege is granted to `PUBLIC` by default.
+
+For information about using the `GRANT` command to provide access to a package, see [SQL reference](../../epas_compat_sql/).
+
+All built-in packages are owned by the special `sys` user that must be specified when granting or revoking privileges on built-in packages:
+
+```sql
+GRANT EXECUTE ON PACKAGE SYS.UTL_FILE TO john;
+```
+
+<div class="toctree" maxdepth="5">
+
+dbms_alert dbms_aq dbms_aqadm dbms_crypto dbms_job dbms_lob dbms_lock dbms_mview dbms_output dbms_privilege_capture dbms_pipe dbms_profiler dbms_random dbms_redact dbms_rls dbms_scheduler dbms_session dbms_sql dbms_utility utl_encode utl_file utl_http utl_mail utl_raw utl_smtp utl_url
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/index.mdx
new file mode 100644
index 00000000000..7cc91e08cdf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_bip_guide/index.mdx
@@ -0,0 +1,14 @@
+---
+navTitle: Built-in packages
+title: "Built-in packages"
+description: "Listing of the built-in package support provided by EDB Postgres Advanced Server"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/Database_Compatibility_for_Oracle_Developers_Built-in_Package_Guide.1.01.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-built-in-package-guide/9.6/toc.html"
+redirects:
+  - /epas/latest/epas_compat_bip_guide/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+Database compatibility for Oracle means that an application runs in an Oracle environment as well as in the EDB Postgres Advanced Server environment with minimal or no changes to the application code. EDB Postgres Advanced Server provides packages that support this compatibility.
+
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx
new file mode 100644
index 00000000000..998d0219e04
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/index.mdx
@@ -0,0 +1,17 @@
+---
+navTitle: Catalog Views
+title: "Database compatibility for Oracle developers: catalog views"
+indexCards: simple
+description: "Listing of the catalog views support provided by EDB Postgres Advanced Server"
+redirects:
+  - /epas/latest/epas_compat_cat_views/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_ora_dev_guide/08_oracle_catalog_views/
+---
+
+Catalog views provide information about database objects. There are two catagories of catalog views:
+
+- Oracle catalog views provide information about database objects in a manner compatible with the Oracle data dictionary views.
+
+- System catalog views are present in PostgreSQL and might have extra information when accessed in EDB Postgres Advanced Server.
+
+These features related to the catalog views support are provided by EDB Postgres Advanced Server.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/02_all_all_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/02_all_all_tables.mdx
new file mode 100644
index 00000000000..97e876ee8ce
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/02_all_all_tables.mdx
@@ -0,0 +1,24 @@
+---
+title: "ALL_ALL_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.107.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.225.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.171.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/02_all_all_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_all_tables" class="registered_link"></div>
+
+The `ALL_ALL_TABLES` view provides information about the tables the current user can access.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the table’s owner.                                                                                                   |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                            |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, then default tablespace `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING (5)` | Included only for compatibility. Always set to `VALID`.                                                                           |
+| `temporary`       | `TEXT`                  | `Y` if the table is temporary, `N` if the table is permanent.                                                                     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/03_all_cons_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/03_all_cons_columns.mdx
new file mode 100644
index 00000000000..85509631258
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/03_all_cons_columns.mdx
@@ -0,0 +1,24 @@
+---
+title: "ALL_CONS_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.108.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.226.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.172.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/03_all_cons_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_cons_columns" class="registered_link"></div>
+
+The `ALL_CONS_COLUMNS` view provides information about the columns specified in constraints placed on tables accessible by the current user.
+
+| Name              | Type       | Description                                              |
+| ----------------- | ---------- | -------------------------------------------------------- |
+| `owner`           | `TEXT`     | User name of the constraint’s owner.                     |
+| `schema_name`     | `TEXT`     | Name of the schema in which the constraint belongs.      |
+| `constraint_name` | `TEXT`     | Name of the constraint.                                  |
+| `table_name`      | `TEXT`     | Name of the table to which the constraint belongs.       |
+| `column_name`     | `TEXT`     | Name of the column referenced in the constraint.         |
+| `position`        | `SMALLINT` | Position of the column in the object definition.         |
+| `constraint_def`  | `TEXT`     | Definition of the constraint.                            |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/04_all_constraints.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/04_all_constraints.mdx
new file mode 100644
index 00000000000..b5f6ce6f750
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/04_all_constraints.mdx
@@ -0,0 +1,31 @@
+---
+title: "ALL_CONSTRAINTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.109.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.227.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.173.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/04_all_constraints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_constraints" class="registered_link"></div>
+
+The `ALL_CONSTRAINTS` view provides information about the constraints placed on tables accessible by the current user.
+
+| Name                | Type      | Description                                                                                                                                                                                                                                                    |
+| ------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`             | `TEXT`    | User name of the constraint’s owner.                                                                                                                                                                                                                           |
+| `schema_name`       | `TEXT`    | Name of the schema in which the constraint belongs.                                                                                                                                                                                                            |
+| `constraint_name`   | `TEXT`    | Name of the constraint.                                                                                                                                                                                                                                    |
+| `constraint_type`   | `TEXT`    | The constraint type. Possible values are: `C` – check constraint; `F` – foreign key constraint; `P` – primary key constraint; `U` – unique key constraint; `R` – referential integrity constraint; `V` – constraint on a view; `O` – with read-only, on a view |
+| `table_name`        | `TEXT`    | Name of the table to which the constraint belongs.                                                                                                                                                                                                             |
+| `search_condition`  | `TEXT`    | Search condition that applies to a check constraint.                                                                                                                                                                                                           |
+| `r_owner`           | `TEXT`    | Owner of a table referenced by a referential constraint.                                                                                                                                                                                                       |
+| `r_constraint_name` | `TEXT`    | Name of the constraint definition for a referenced table.                                                                                                                                                                                                      |
+| `delete_rule`       | `TEXT`    | Delete rule for a referential constraint. Possible values are: `C` – cascade; `R` – restrict; `N` – no action                                                                                                                                              |
+| `deferrable`        | `BOOLEAN` | Specified if the constraint is deferrable (`T` or `F`).                                                                                                                                                                                                        |
+| `deferred`          | `BOOLEAN` | Specified if the constraint was deferred (`T` or `F`).                                                                                                                                                                                                    |
+| `index_owner`       | `TEXT`    | User name of the index owner.                                                                                                                                                                                                                                  |
+| `index_name`        | `TEXT`    | Name of the index.                                                                                                                                                                                                                                         |
+| `constraint_def`    | `TEXT`    | Definition of the constraint.                                                                                                                                                                                                                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/05_all_col_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/05_all_col_privs.mdx
new file mode 100644
index 00000000000..1392dcfefb2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/05_all_col_privs.mdx
@@ -0,0 +1,25 @@
+---
+title: "ALL_COL_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/05_all_col_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_col_privs" class="registered_link"></div>
+
+The `ALL_COL_PRIVS` view provides the following types of privileges:
+
+-   Column object privileges for which a current user is either an object owner, grantor, or grantee.
+-   Column object privileges for which `PUBLIC` is the grantee.
+
+| Name           | Type                     | Description                                                                                                                                                                                                                                                         |
+| -------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantor`      | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `grantee`      | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `table_schema` | `CHARACTER VARYING(128)` | Name of the user who owns the object.                                                                                                                                                                                                                               |
+| `schema_name`  | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`   | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `column_name`  | `CHARACTER VARYING(128)` | Column name.                                                                                                                                                                                                                                                        |
+| `privilege`    | `CHARACTER VARYING(40)`  | Privilege on the column.                                                                                                                                                                                                                                            |
+| `grantable`    | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the `GRANTEE` (recipient of the privilege) can grant the privilege to others. The value can be `YES` if the grantee has administrator privileges. |
+| `common`       | `CHARACTER VARYING(3)`   | Included for compatibility only. Always `NO`.                                                                                                                                                                                                                       |
+| `inherited`    | `CHARACTER VARYING(3)`   | Included for compatibility only. Always `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/06_all_db_links.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/06_all_db_links.mdx
new file mode 100644
index 00000000000..e8a579c5148
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/06_all_db_links.mdx
@@ -0,0 +1,22 @@
+---
+title: "ALL_DB_LINKS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.110.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.228.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.174.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/06_all_db_links/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_db_links" class="registered_link"></div>
+
+The `ALL_DB_LINKS` view provides information about the database links accessible by the current user.
+
+| Name       | Type                | Description                                                     |
+| ---------- | ------------------- | --------------------------------------------------------------- |
+| `owner`    | `TEXT`              | User name of the database link’s owner.                         |
+| `db_link`  | `TEXT`              | Name of the database link.                                      |
+| `type`     | `CHARACTER VARYING` | Type of remote server. Value is `REDWOOD` or `EDB`.             |
+| `username` | `TEXT`              | User name of the user logging in.                               |
+| `host`     | `TEXT`              | Name or IP address of the remote server.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/07_all_dependencies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/07_all_dependencies.mdx
new file mode 100644
index 00000000000..9048e9fd565
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/07_all_dependencies.mdx
@@ -0,0 +1,22 @@
+---
+title: "ALL_DEPENDENCIES"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/07_all_dependencies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_dependencies" class="registered_link"></div>
+
+The `ALL_DEPENDENCIES` view provides information about the dependencies between database objects that the current user can access, except for synonyms.
+
+| Name                     | Type                     | Description                                                |
+| ------------------------ | ------------------------ | ---------------------------------------------------------- |
+| `owner`                  | `CHARACTER VARYING(128)` | Owner of dependent object.                                 |
+| `schema_name`            | `CHARACTER VARYING(128)` | Name of the schema in which the dependent object resides.  |
+| `name`                   | `CHARACTER VARYING(128)` | Name of the dependent object.                              |
+| `type`                   | `CHARACTER VARYING(18)`  | Type of the dependent object.                              |
+| `referenced_owner`       | `CHARACTER VARYING(128)` | Owner of the referenced object.                            |
+| `referenced_schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the referenced object resides. |
+| `referenced_name`        | `CHARACTER VARYING(128)` | Name of the referenced object.                             |
+| `referenced_type`        | `CHARACTER VARYING(18)`  | Type of the referenced object.                             |
+| `referenced_link_name`   | `CHARACTER VARYING(128)` | Included for compatibility only. Always `NULL`.            |
+| `dependency_type`        | `CHARACTER VARYING(4)`   | Included for compatibility only. Always set to `HARD`.     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/08_all_directories.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/08_all_directories.mdx
new file mode 100644
index 00000000000..0b6b2d52008
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/08_all_directories.mdx
@@ -0,0 +1,18 @@
+---
+title: "ALL_DIRECTORIES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.111.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/08_all_directories/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_directories" class="registered_link"></div>
+
+The `ALL_DIRECTORIES` view provides information about all directories created with the `CREATE DIRECTORY` command.
+
+| Name             | Type                      | Description                               |
+| ---------------- | ------------------------- | ----------------------------------------- |
+| `owner`          | `CHARACTER VARYING(30)`   | User name of the directory owner.         |
+| `directory_name` | `CHARACTER VARYING(30)`   | Alias name assigned to the directory.     |
+| `directory_path` | `CHARACTER VARYING(4000)` | Path to the directory.                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx
new file mode 100644
index 00000000000..b919b3b35bf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns.mdx
@@ -0,0 +1,28 @@
+---
+title: "ALL_IND_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.112.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.229.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.175.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/09_all_ind_columns/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/09_all_ind_columns/
+---
+
+<div id="all_ind_columns" class="registered_link"></div>
+
+The `ALL_IND_COLUMNS` view provides information about columns included in indexes on the tables accessible by the current user.
+
+| Name              | Type           | Description                                                      |
+| ----------------- | -------------- | ---------------------------------------------------------------- |
+| `index_owner`     | `TEXT`         | User name of the index owner.                                    |
+| `schema_name`     | `TEXT`         | Name of the schema in which the index belongs.                   |
+| `index_name`      | `TEXT`         | Name of the index.                                               |
+| `table_owner`     | `TEXT`         | User name of the table owner.                                    |
+| `table_name`      | `TEXT`         | Name of the table to which the index belongs.                    |
+| `column_name`     | `TEXT`         | Name of the column.                                              |
+| `column_position` | `SMALLINT`     | Position of the column in the index.                             |
+| `column_length`   | `SMALLINT`     | Length of the column in bytes.                                   |
+| `char_length`     | `NUMERIC`      | Length of the column in characters.                              |
+| `descend`         | `CHARACTER(1)` | Always set to `Y` (descending). Included only for compatibility. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/10_all_indexes.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/10_all_indexes.mdx
new file mode 100644
index 00000000000..94ed1d38762
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/10_all_indexes.mdx
@@ -0,0 +1,35 @@
+---
+title: "ALL_INDEXES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.113.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.230.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.176.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/10_all_indexes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_indexes" class="registered_link"></div>
+
+The `ALL_INDEXES` view provides information about the indexes on tables that the current user can access.
+
+| Name              | Type                    | Description                                                                                          |
+| ----------------- | ----------------------- | ---------------------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the index owner.                                                                      |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the index belongs.                                                       |
+| `index_name`      | `TEXT`                  | Name of the index.                                                                               |
+| `index_type`      | `TEXT`                  | The index type is always `BTREE`. Included for compatibility only.                                   |
+| `table_owner`     | `TEXT`                  | User name of the owner of the indexed table.                                                         |
+| `table_name`      | `TEXT`                  | Name of the indexed table.                                                                       |
+| `table_type`      | `TEXT`                  | Included for compatibility only. Always set to `TABLE`.                                              |
+| `uniqueness`      | `TEXT`                  | Indicates if the index is `UNIQUE` or `NONUNIQUE`.                                                   |
+| `compression`     | `CHARACTER(1)`          | Always set to `N` (not compressed). Included only for compatibility.                                 |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides if not the default tablespace.              |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan the index.                                                    |
+| `logging`         | `TEXT`                  | Included only for compatibility. Always set to `LOGGING`.                                           |
+| `status`          | `TEXT`                  | Included only for compatibility. Always set to `VALID`.                                              |
+| `partitioned`     | `CHARACTER(3)`          | Indicates that the index is partitioned. Always set to `NO`.                              |
+| `temporary`       | `CHARACTER(1)`          | Indicates that an index is on a temporary table. Included only for compatibility. Always set to `N`. |
+| `secondary`       | `CHARACTER(1)`          | Included only for compatibility. Always set to `N`.                                                  |
+| `join_index`      | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                                 |
+| `dropped`         | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                                 |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/11_all_jobs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/11_all_jobs.mdx
new file mode 100644
index 00000000000..15d656545e0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/11_all_jobs.mdx
@@ -0,0 +1,35 @@
+---
+title: "ALL_JOBS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.114.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.231.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.177.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/11_all_jobs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_jobs" class="registered_link"></div>
+
+The `ALL_JOBS` view provides information about all jobs that reside in the database.
+
+| Name          | Type                       | Description                                                                                   |
+| ------------- | -------------------------- | --------------------------------------------------------------------------------------------- |
+| `job`         | `INTEGER`                  | The identifier of the job (Job ID).                                                           |
+| `log_user`    | `TEXT`                     | Name of the user that submitted the job.                                                  |
+| `priv_user`   | `TEXT`                     | Same as `log_user`. Included only for compatibility.                                          |
+| `schema_user` | `TEXT`                     | Name of the schema used to parse the job.                                                 |
+| `last_date`   | `TIMESTAMP WITH TIME ZONE` | Last date that this job executed successfully.                                            |
+| `last_sec`    | `TEXT`                     | Same as `last_date`.                                                                          |
+| `this_date`   | `TIMESTAMP WITH TIME ZONE` | Date that the job began executing.                                                        |
+| `this_sec`    | `TEXT`                     | Same as `this_date`.                                                                          |
+| `next_date`   | `TIMESTAMP WITH TIME ZONE` | Next date for this job to execute.                                                   |
+| `next_sec`    | `TEXT`                     | Same as `next_date`.                                                                          |
+| `total_time`  | `INTERVAL`                 | Execution time of this job, in seconds.                                                  |
+| `broken`      | `TEXT`                     | If `Y`, no attempt is be made to run this job. If `N`, this job attempts to run.          |
+| `interval`    | `TEXT`                     | Determines how often the job repeats.                                                   |
+| `failures`    | `BIGINT`                   | Number of times that the job failed to complete since its last successful execution. |
+| `what`        | `TEXT`                     | Job definition (PL/SQL code block) that runs when the job executes.                       |
+| `nls_env`     | `CHARACTER VARYING(4000)`  | Always `NULL`. Provided only for compatibility.                                               |
+| `misc_env`    | `BYTEA`                    | Always `NULL`. Provided only for compatibility.                                               |
+| `instance`    | `NUMERIC`                  | Always `0`. Provided only for compatibility.                                                  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/12_all_objects.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/12_all_objects.mdx
new file mode 100644
index 00000000000..bfe076e976f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/12_all_objects.mdx
@@ -0,0 +1,25 @@
+---
+title: "ALL_OBJECTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.115.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.232.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.178.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/12_all_objects/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_objects" class="registered_link"></div>
+
+The `ALL_OBJECTS` view provides information about all objects that reside in the database.
+
+| Name            | Type                | Description                                                                                                                                                  |
+| --------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `owner`         | `TEXT`              | User name of the object’s owner.                                                                                                                             |
+| `schema_name`   | `TEXT`              | Name of the schema in which the object belongs.                                                                                                              |
+| `object_name`   | `TEXT`              | Name of the object.                                                                                                                                          |
+| `object_type`   | `TEXT`              | Type of the object. Possible values are: `INDEX`, `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, `SEQUENCE`, `SYNONYM`, `TABLE`, `TRIGGER`, and `VIEW` |
+| `created`       | `DATE`              | Timestamp for when the object was created.                                                                                                                     |
+| `last_ddl_time` | `DATE`              | Timestamp for the last modification of an object resulting from a DDL statement, including grants and revokes.                                                |
+| `status`        | `CHARACTER VARYING` | Whether or not the state of the object is valid. Included only for compatibility. Always set to `VALID`.                                          |
+| `temporary`     | `TEXT`              | `Y` if a temporary object, `N` if this is a permanent object.                                                                                                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/13_all_part_key_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/13_all_part_key_columns.mdx
new file mode 100644
index 00000000000..b76fecca067
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/13_all_part_key_columns.mdx
@@ -0,0 +1,23 @@
+---
+title: "ALL_PART_KEY_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.116.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.233.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.179.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/13_all_part_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_part_key_columns" class="registered_link"></div>
+
+The `ALL_PART_KEY_COLUMNS` view provides information about the key columns of the partitioned tables that reside in the database.
+
+| Name              | Type           | Description                                               |
+| ----------------- | -------------- | --------------------------------------------------------- |
+| `owner`           | `TEXT`         | Owner of the table.                                       |
+| `schema_name`     | `TEXT`         | Name of the schema in which the table resides.            |
+| `name`            | `TEXT`         | Name of the table in which the column resides.            |
+| `object_type`     | `CHARACTER(5)` | For compatibility only. Always `TABLE`.                   |
+| `column_name`     | `TEXT`         | Name of the column on which the key is defined.           |
+| `column_position` | `INTEGER`      | `1` for the first column, `2` for the second column, and so on. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/14_all_part_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/14_all_part_tables.mdx
new file mode 100644
index 00000000000..c49ed1ce9d7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/14_all_part_tables.mdx
@@ -0,0 +1,44 @@
+---
+title: "ALL_PART_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-only for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.117.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-only for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.234.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.180.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/14_all_part_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_part_tables" class="registered_link"></div>
+
+The `ALL_PART_TABLES` view provides information about all of the partitioned tables that reside in the database.
+
+| Name                        | Type                      | Description                                                  |
+| --------------------------- | ------------------------- | ------------------------------------------------------------ |
+| `owner`                     | `TEXT`                    | Owner of the partitioned table.                          |
+| `schema_name`               | `TEXT`                    | Name of the schema in which the table resides.           |
+| `table_name`                | `TEXT`                    | Name of the table.                                       |
+| `partitioning_type`         | `TEXT`                    | Partitioning type used to define table partitions.       |
+| `subpartitioning_type`      | `TEXT`                    | Subpartitioning type used to define table subpartitions. |
+| `partition_count`           | `BIGINT`                  | Number of partitions in the table.                       |
+| `def_subpartition_count`    | `INTEGER`                 | Number of subpartitions in the table.                    |
+| `partitioning_key_count`    | `INTEGER`                 | Number of partitioning keys specified.                   |
+| `subpartitioning_key_count` | `INTEGER`                 | Number of subpartitioning keys specified.                |
+| `status`                    | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `VALID`.             |
+| `def_tablespace_name`       | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_free`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_used`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_ini_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_max_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_initial_extent`        | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_next_extent`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_min_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_max_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_increase`          | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_freelists`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_freelist_groups`       | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_logging`               | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `YES`.               |
+| `def_compression`           | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `NONE`.              |
+| `def_buffer_pool`           | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `DEFAULT`.           |
+| `ref_ptn_constraint_name`   | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `interval`                  | `CHARACTER VARYING(1000)` | Provided only for compatibility. Always `NULL`.              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/15_all_policies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/15_all_policies.mdx
new file mode 100644
index 00000000000..6aefda8d6be
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/15_all_policies.mdx
@@ -0,0 +1,35 @@
+---
+title: "ALL_POLICIES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.118.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.235.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.181.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/15_all_policies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_policies" class="registered_link"></div>
+
+The `ALL_POLICIES` view provides information on all policies in the database. This view is accessible only to superusers.
+
+| Name             | Type   | Description                                                                                                                |
+| ---------------- | ------ | -------------------------------------------------------------------------------------------------------------------------- |
+| `object_owner`   | `TEXT` | Name of the owner of the object.                                                                                           |
+| `schema_name`    | `TEXT` | Name of the schema in which the object belongs.                                                                            |
+| `object_name`    | `TEXT` | Name of the object on which the policy applies.                                                                            |
+| `policy_group`   | `TEXT` | Included only for compatibility. Always set to an empty string.                                                            |
+| `policy_name`    | `TEXT` | Name of the policy.                                                                                                        |
+| `pf_owner`       | `TEXT` | Name of the schema containing the policy function or the schema containing the package that contains the policy function. |
+| `package`        | `TEXT` | Name of the package containing the policy function if the function belongs to a package.                                 |
+| `function`       | `TEXT` | Name of the policy function.                                                                                               |
+| `sel`            | `TEXT` | Whether or not the policy applies to `SELECT` commands. Possible values are `YES` or `NO`.                                 |
+| `ins`            | `TEXT` | Whether or not the policy applies to `INSERT` commands. Possible values are `YES` or `NO`.                                 |
+| `upd`            | `TEXT` | Whether or not the policy applies to `UPDATE` commands. Possible values are `YES` or `NO`.                                 |
+| `del`            | `TEXT` | Whether or not the policy applies to `DELETE` commands. Possible values are `YES` or `NO`.                                 |
+| `idx`            | `TEXT` | Whether or not the policy applies to index maintenance. Possible values are `YES` or `NO`.                                 |
+| `chk_option`     | `TEXT` | Whether or not the check option is in force for `INSERT` and `UPDATE` commands. Possible values are `YES` or `NO`.         |
+| `enable`         | `TEXT` | Whether or not the policy is enabled on the object. Possible values are `YES` or `NO`.                                     |
+| `static_policy`  | `TEXT` | Included only for compatibility. Always set to `NO`.                                                                       |
+| `policy_type`    | `TEXT` | Included only for compatibility. Always set to `UNKNOWN`.                                                                  |
+| `long_predicate` | `TEXT` | Included for compatibility only. Always set to `YES`.                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/16_all_queues.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/16_all_queues.mdx
new file mode 100644
index 00000000000..f872d8c246e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/16_all_queues.mdx
@@ -0,0 +1,28 @@
+---
+title: "ALL_QUEUES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.119.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/16_all_queues/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_queues" class="registered_link"></div>
+
+The `ALL_QUEUES` view provides information about any currently defined queues.
+
+| Name              | Type                | Description                                                                          |
+| ----------------- | ------------------- | ------------------------------------------------------------------------------------ |
+| `owner`           | `TEXT`              | User name of the queue owner.                                                        |
+| `name`            | `TEXT`              | Name of the queue.                                                               |
+| `queue_table`     | `TEXT`              | Name of the queue table in which the queue resides.                              |
+| `qid`             | `OID`               | The system-assigned object ID of the queue.                                          |
+| `queue_type`      | `CHARACTER VARYING` | The queue type. Can be `EXCEPTION_QUEUE`, `NON_PERSISTENT_QUEUE`, or `NORMAL_QUEUE`. |
+| `max_retries`     | `NUMERIC`           | The maximum number of dequeue attempts.                                              |
+| `retrydelay`      | `NUMERIC`           | The maximum time allowed between retries.                                            |
+| `enqueue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows enqueuing, `NO` if the queue does not.                     |
+| `dequeue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows dequeuing, `NO` if the queue does not.                     |
+| `retention`       | `CHARACTER VARYING` | The number of seconds that a processed message is retained in the queue.             |
+| `user_comment`    | `CHARACTER VARYING` | User-specified comment.                                                            |
+| `network_name`    | `CHARACTER VARYING` | Name of the network on which the queue resides.                                  |
+| `sharded`         | `CHARACTER VARYING` | `YES` if the queue resides on a sharded network, `NO` if the queue does not.         |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/17_all_queue_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/17_all_queue_tables.mdx
new file mode 100644
index 00000000000..91ba3cb10dd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/17_all_queue_tables.mdx
@@ -0,0 +1,28 @@
+---
+title: "ALL_QUEUE_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.120.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/17_all_queue_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_queue_tables" class="registered_link"></div>
+
+The `ALL_QUEUE_TABLES` view provides information about all of the queue tables in the database.
+
+| Name                 | Type                | Description                                                                                  |
+| -------------------- | ------------------- | -------------------------------------------------------------------------------------------- |
+| `owner`              | `TEXT`              | Role name of the owner of the queue table.                                                   |
+| `queue_table`        | `TEXT`              | User-specified name of the queue table.                                                  |
+| `type`               | `CHARACTER VARYING` | Type of data stored in the queue table.                                                  |
+| `object_type`        | `TEXT`              | User-defined payload type.                                                               |
+| `sort_order`         | `CHARACTER VARYING` | Order in which the queue table is sorted.                                                |
+| `recipients`         | `CHARACTER VARYING` | Always `SINGLE`.                                                                             |
+| `message_grouping`   | `CHARACTER VARYING` | Always `NONE`.                                                                               |
+| `compatible`         | `CHARACTER VARYING` | Release number of the EDB Postgres Advanced Server release with which this queue table is compatible. |
+| `primary_instance`   | `NUMERIC`           | Always `0`.                                                                                  |
+| `secondary_instance` | `NUMERIC`           | Always `0`.                                                                                  |
+| `owner_instance`     | `NUMERIC`           | Instance number of the instance that owns the queue table.                               |
+| `user_comment`       | `CHARACTER VARYING` | User comment provided when the table was created.                                        |
+| `secure`             | `CHARACTER VARYING` | `YES` indicates that the queue table is secure. `NO` indicates that it isn't.               |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/18_all_sequences.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/18_all_sequences.mdx
new file mode 100644
index 00000000000..0db35474cd1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/18_all_sequences.mdx
@@ -0,0 +1,27 @@
+---
+title: "ALL_SEQUENCES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.121.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.236.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.182.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/18_all_sequences/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_sequences" class="registered_link"></div>
+
+The `ALL_SEQUENCES` view provides information about all user-defined sequences on which the user has `SELECT` or `UPDATE` privileges.
+
+| Name             | Type                | Description                                                                       |
+| ---------------- | ------------------- | --------------------------------------------------------------------------------- |
+| `sequence_owner` | `TEXT`              | User name of the sequence owner.                                                |
+| `schema_name`    | `TEXT`              | Name of the schema in which the sequence resides.                                 |
+| `sequence_name`  | `TEXT`              | Name of the sequence.                                                             |
+| `min_value`      | `NUMERIC`           | Lowest value that the server assigns to the sequence.                         |
+| `max_value`      | `NUMERIC`           | Highest value that the server assigns to the sequence.                        |
+| `increment_by`   | `NUMERIC`           | Value added to the current sequence number to create the next sequent number. |
+| `cycle_flag`     | `CHARACTER VARYING` | Specifies whether the sequence wraps when it reaches `min_value` or `max_value`. |
+| `order_flag`     | `CHARACTER VARYING` | Always returns `Y`.                                                                |
+| `cache_size`     | `NUMERIC`           | Number of preallocated sequence numbers stored in memory.                    |
+| `last_number`    | `NUMERIC`           | Value of the last sequence number saved to disk.                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx
new file mode 100644
index 00000000000..e8850148a5b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/19_all_source.mdx
@@ -0,0 +1,24 @@
+---
+title: "ALL_SOURCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.122.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.237.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.183.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/19_all_source/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/19_all_source/
+---
+
+<div id="all_source" class="registered_link"></div>
+
+The `ALL_SOURCE` view provides a source code listing of the following program types: functions, procedures, triggers, package specifications, and package bodies.
+
+| Name          | Type      | Description                                                                                              |
+| ------------- | --------- | -------------------------------------------------------------------------------------------------------- |
+| `owner`       | `TEXT`    | User name of the program owner.                                                                        |
+| `schema_name` | `TEXT`    | Name of the schema in which the program belongs.                                                         |
+| `name`        | `TEXT`    | Name of the program.                                                                                     |
+| `type`        | `TEXT`    | Type of program. Possible values are: `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, and `TRIGGER` |
+| `line`        | `INTEGER` | Source code line number relative to a given program.                                                     |
+| `text`        | `TEXT`    | Line of source code text.                                                                                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/20_all_subpart_key_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/20_all_subpart_key_columns.mdx
new file mode 100644
index 00000000000..614359a8fd3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/20_all_subpart_key_columns.mdx
@@ -0,0 +1,23 @@
+---
+title: "ALL_SUBPART_KEY_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.123.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.238.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.184.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/20_all_subpart_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_subpart_key_columns" class="registered_link"></div>
+
+The `ALL_SUBPART_KEY_COLUMNS` view provides information about the key columns of those partitioned tables that are subpartitioned that reside in the database.
+
+| Name              | Type           | Description                                               |
+| ----------------- | -------------- | --------------------------------------------------------- |
+| `owner`           | `TEXT`         | Owner of the table.                                   |
+| `schema_name`     | `TEXT`         | Name of the schema in which the table resides.        |
+| `name`            | `TEXT`         | Name of the table in which the column resides.        |
+| `object_type`     | `CHARACTER(5)` | Only for compatibility. Always `TABLE`.                   |
+| `column_name`     | `TEXT`         | Name of the column on which the key is defined.       |
+| `column_position` | `INTEGER`      | `1` for the first column, `2` for the second column, and so on. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/21_all_synonyms.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/21_all_synonyms.mdx
new file mode 100644
index 00000000000..0d8e56af5ba
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/21_all_synonyms.mdx
@@ -0,0 +1,24 @@
+---
+title: "ALL_SYNONYMS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.124.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.239.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.185.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/21_all_synonyms/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_synonyms" class="registered_link"></div>
+
+The `ALL_SYNONYMS` view provides information on all synonyms that the current user can reference.
+
+| Name                | Type   | Description                                          |
+| ------------------- | ------ | ---------------------------------------------------- |
+| `owner`             | `TEXT` | User name of the synonym owner.                    |
+| `schema_name`       | `TEXT` | Name of the schema in which the synonym resides. |
+| `synonym_name`      | `TEXT` | Name of the synonym.                                 |
+| `table_owner`       | `TEXT` | User name of the object owner.                     |
+| `table_schema_name` | `TEXT` | Name of the schema in which the table resides.   |
+| `table_name`        | `TEXT` | Name of the object that the synonym refers to.   |
+| `db_link`           | `TEXT` | Name of any associated database link.            |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx
new file mode 100644
index 00000000000..b49f01eed69
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns.mdx
@@ -0,0 +1,29 @@
+---
+title: "ALL_TAB_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.125.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.240.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.186.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/22_all_tab_columns/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/22_all_tab_columns/
+---
+
+<div id="all_tab_columns" class="registered_link"></div>
+
+The `ALL_TAB_COLUMNS` view provides information on all columns in all user-defined tables and views.
+
+| Name             | Type                | Description                                                                                                             |
+| ---------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `owner`          | `CHARACTER VARYING` | User name of the owner of the table or view in which the column resides.                                                |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the table or view resides.                                                                  |
+| `table_name`     | `CHARACTER VARYING` | Name of the table or view.                                                                                              |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                     |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                 |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                      |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                              |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the table or view.                                                               |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/23_all_tab_partitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/23_all_tab_partitions.mdx
new file mode 100644
index 00000000000..c7598cf6831
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/23_all_tab_partitions.mdx
@@ -0,0 +1,52 @@
+---
+title: "ALL_TAB_PARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.126.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.241.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.187.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/23_all_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_tab_partitions" class="registered_link"></div>
+
+The `ALL_TAB_PARTITIONS` view provides information about all of the partitions that reside in the database.
+
+| Name                 | Type                          | Description                                                                                                                               |
+| -------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `table_owner`        | `TEXT`                        | Owner of the table in which the partition resides.                                                                                    |
+| `schema_name`        | `TEXT`                        | Name of the schema in which the table resides.                                                                                        |
+| `table_name`         | `TEXT`                        | Name of the table.                                                                                                                    |
+| `composite`          | `TEXT`                        | `YES` if the table is subpartitioned, `NO` if the table isn't subpartitioned.                                                            |
+| `partition_name`     | `TEXT`                        | Name of the partition.                                                                                                                |
+| `subpartition_count` | `BIGINT`                      | Number of subpartitions in the partition.                                                                                             |
+| `high_value`         | `TEXT`                        | High-partitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`  | `INTEGER`                     | Length of high-partitioning value.                                                                                                    |
+| `partition_position` | `INTEGER`                     | Ordinal position of this partition.                                                                                                   |
+| `tablespace_name`    | `TEXT`                        | Name of the tablespace in which the partition resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `pct_free`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_used`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `ini_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `initial_extent`     | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `next_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `min_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_increase`       | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `freelists`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `freelist_groups`    | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `logging`            | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `compression`        | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                           |
+| `num_rows`           | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                             |
+| `blocks`             | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                              |
+| `empty_blocks`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_space`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `chain_cnt`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_row_len`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `sample_size`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `last_analyzed`      | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                           |
+| `buffer_pool`        | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                           |
+| `global_stats`       | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `user_stats`         | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                             |
+| `backing_table`      | `REGCLASS`                    | Name of the partition backing table.                                                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/24_all_tab_subpartitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/24_all_tab_subpartitions.mdx
new file mode 100644
index 00000000000..07d587b568c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/24_all_tab_subpartitions.mdx
@@ -0,0 +1,51 @@
+---
+title: "ALL_TAB_SUBPARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.127.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.242.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.188.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/24_all_tab_subpartitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_tab_subpartitions" class="registered_link"></div>
+
+The `ALL_TAB_SUBPARTITIONS` view provides information about all of the subpartitions that reside in the database.
+
+| Name                    | Type                          | Description                                                                                                                                  |
+| ----------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `table_owner`           | `TEXT`                        | Owner of the table in which the subpartition resides.                                                                                    |
+| `schema_name`           | `TEXT`                        | Name of the schema in which the table resides.                                                                                           |
+| `table_name`            | `TEXT`                        | Name of the table.                                                                                                                       |
+| `partition_name`        | `TEXT`                        | Name of the partition.                                                                                                                   |
+| `subpartition_name`     | `TEXT`                        | Name of the subpartition.                                                                                                                |
+| `high_value`            | `TEXT`                        | High-subpartitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`     | `INTEGER`                     | Length of high-partitioning value.                                                                                                       |
+| `subpartition_position` | `INTEGER`                     | Ordinal position of this subpartition.                                                                                                   |
+| `tablespace_name`       | `TEXT`                        | Name of the tablespace in which the subpartition resides. If the tablespace name is not specified, then default tablespace `PG_DEFAULT`. |
+| `pct_free`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_used`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `ini_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `initial_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `next_extent`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `min_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_increase`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `freelists`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `freelist_groups`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `logging`               | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `compression`           | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                              |
+| `num_rows`              | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                                |
+| `blocks`                | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                                 |
+| `empty_blocks`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_space`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `chain_cnt`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_row_len`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `sample_size`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `last_analyzed`         | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                              |
+| `buffer_pool`           | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                              |
+| `global_stats`          | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `user_stats`            | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                                |
+| `backing_table`         | `REGCLASS`                    | Name of the subpartition backing table.                                                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx
new file mode 100644
index 00000000000..fb4943a7db9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs.mdx
@@ -0,0 +1,27 @@
+---
+title: "ALL_TAB_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/25_all_tab_privs/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/25_all_tab_privs/
+---
+
+<div id="all_tab_privs" class="registered_link"></div>
+
+The `ALL_TAB_PRIVS` view provides the following types of privileges:
+
+-   Object privileges for which a current user is either an object owner, grantor, or grantee.
+-   Object privileges for which the `PUBLIC` is the grantee.
+
+| Name           | Type                     | Description                                                                                                                                                                                                                                                         |
+| -------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantor`      | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `grantee`      | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `table_schema` | `CHARACTER VARYING(128)` | Name of the user who owns the object.                                                                                                                                                                                                                               |
+| `schema_name`  | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`   | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `privilege`    | `CHARACTER VARYING(40)`  | Privilege name.                                                                                                                                                                                                                                                     |
+| `grantable`    | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the `GRANTEE` (recipient of the privilege) can in turn grant the privilege to others. The value can be `YES` if the grantee has administrator privileges. |
+| `hierarchy`    | `CHARACTER VARYING(3)`   | The value can be `YES` or `NO`. The value can be `YES` if the privilege is `SELECT`.                                                                                                                                                                       |
+| `common`       | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
+| `type`         | `CHARACTER VARYING(24)`  | Type of object.                                                                                                                                                                                                                                                     |
+| `inherited`    | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/26_all_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/26_all_tables.mdx
new file mode 100644
index 00000000000..1332de3eaf0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/26_all_tables.mdx
@@ -0,0 +1,24 @@
+---
+title: "ALL_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.128.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.243.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.189.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/26_all_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_tables" class="registered_link"></div>
+
+The `ALL_TABLES` view provides information on all user-defined tables.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the table’s owner.                                                                                                   |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                                |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, the default tablespace `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING(5)`  | Whether or not the state of the table is valid. Included only for compatibility. Always set to `VALID`.                |
+| `temporary`       | `CHARACTER(1)`          | `Y` if this is a temporary table, `N` if this isn't a temporary table.                                                           |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/27_all_triggers.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/27_all_triggers.mdx
new file mode 100644
index 00000000000..001105df81d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/27_all_triggers.mdx
@@ -0,0 +1,30 @@
+---
+title: "ALL_TRIGGERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.129.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.244.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.190.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/27_all_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_triggers" class="registered_link"></div>
+
+The `ALL_TRIGGERS` view provides information about the triggers on tables that the current user can accessed.
+
+| Name               | Type   | Description                                                                                                    |
+| ------------------ | ------ | -------------------------------------------------------------------------------------------------------------- |
+| `owner`            | `TEXT` | User name of the trigger owner.                                                                              |
+| `schema_name`      | `TEXT` | Name of the schema in which the trigger resides.                                                           |
+| `trigger_name`     | `TEXT` | Name of the trigger.                                                                                       |
+| `trigger_type`     | `TEXT` | The type of the trigger. Possible values are: `BEFORE ROW`, `BEFORE STATEMENT`, `AFTER ROW`, `AFTER STATEMENT`. |
+| `triggering_event` | `TEXT` | The event that fires the trigger.                                                                              |
+| `table_owner`      | `TEXT` | The user name of the owner of the table on which the trigger is defined.                                       |
+| `base_object_type` | `TEXT` | Included only for compatibility. Value is always `TABLE`.                                                 |
+| `table_name`       | `TEXT` | Name of the table on which the trigger is defined.                                                         |
+| `referencing_name` | `TEXT` | Included only for compatibility. Value is always `REFERENCING NEW AS NEW OLD AS OLD`.                     |
+| `status`           | `TEXT` | Status indicates if the trigger is enabled `(VALID)` or disabled `(NOTVALID)`.                                 |
+| `description`      | `TEXT` | Included only for compatibility.                                                                               |
+| `trigger_body`     | `TEXT` | The body of the trigger.                                                                                       |
+| `action_statement` | `TEXT` | The SQL command that executes when the trigger fires.                                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/28_all_types.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/28_all_types.mdx
new file mode 100644
index 00000000000..9a54d783258
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/28_all_types.mdx
@@ -0,0 +1,23 @@
+---
+title: "ALL_TYPES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.130.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.245.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.191.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/28_all_types/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_types" class="registered_link"></div>
+
+The `ALL_TYPES` view provides information about the object types available to the current user.
+
+| Name          | Type      | Description                                                                    |
+| ------------- | --------- | ------------------------------------------------------------------------------ |
+| `owner`       | `TEXT`    | Owner of the object type.                                                  |
+| `schema_name` | `TEXT`    | Name of the schema in which the type is defined.                           |
+| `type_name`   | `TEXT`    | Name of the type.                                                          |
+| `type_oid`    | `OID`     | Object identifier (OID) of the type.                                       |
+| `typecode`    | `TEXT`    | Typecode of the type. Possible values are: `OBJECT`, `COLLECTION`, `OTHER` |
+| `attributes`  | `INTEGER` | Number of attributes in the type.                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/29_all_users.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/29_all_users.mdx
new file mode 100644
index 00000000000..41b226b12d1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/29_all_users.mdx
@@ -0,0 +1,21 @@
+---
+title: "ALL_USERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.131.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.246.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.192.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/29_all_users/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_users" class="registered_link"></div>
+
+The `ALL_USERS` view provides information on all user names.
+
+| Name            | Type   | Description                                                                                                    |
+| --------------- | ------ | -------------------------------------------------------------------------------------------------------------- |
+| `username`      | `TEXT` | Name of the user.                                                                                              |
+| `user_id`       | `OID`  | Numeric user id assigned to the user.                                                                          |
+| `created`       | `DATE` | Timestamp for when an object was created.                                                                       |
+| `last_ddl_time` | `DATE` | Timestamp for the last modification of an object resulting from a DDL statement, including grants and revokes.  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/30_all_view_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/30_all_view_columns.mdx
new file mode 100644
index 00000000000..db8d32d5fb4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/30_all_view_columns.mdx
@@ -0,0 +1,28 @@
+---
+title: "ALL_VIEW_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.132.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.247.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.193.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/30_all_view_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_view_columns" class="registered_link"></div>
+
+The `ALL_VIEW_COLUMNS` view provides information on all columns in all user-defined views.
+
+| Name             | Type                | Description                                                                                                              |
+| ---------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `owner`          | `CHARACTER VARYING` | User name of the view’s owner.                                                                                           |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the view belongs.                                                                            |
+| `view_name`      | `CHARACTER VARYING` | Name of the view.                                                                                                        |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                      |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                 |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                  |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                       |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                               |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the view.                                                                         |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/31_all_views.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/31_all_views.mdx
new file mode 100644
index 00000000000..95a8b2dd4d1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/31_all_views.mdx
@@ -0,0 +1,21 @@
+---
+title: "ALL_VIEWS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.133.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.248.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.194.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/31_all_views/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="all_views" class="registered_link"></div>
+
+The `ALL_VIEWS` view provides information about all user-defined views.
+
+| Name          | Type   | Description                                   |
+| ------------- | ------ | --------------------------------------------- |
+| `owner`       | `TEXT` | User name of the view’s owner.                |
+| `schema_name` | `TEXT` | Name of the schema in which the view belongs. |
+| `view_name`   | `TEXT` | Name of the view.                             |
+| `text`        | `TEXT` | The `SELECT` statement that defines the view. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/32_dba_all_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/32_dba_all_tables.mdx
new file mode 100644
index 00000000000..62a8ef7cc38
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/32_dba_all_tables.mdx
@@ -0,0 +1,24 @@
+---
+title: "DBA_ALL_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.134.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.249.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.195.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/32_dba_all_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_all_tables" class="registered_link"></div>
+
+The `DBA_ALL_TABLES` view provides information about all tables in the database.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the table owner.                                                                                                   |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                                |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING(5)`  | Included only for compatibility. Always set to `VALID`.                                                                           |
+| `temporary`       | `TEXT`                  | `Y` if the table is temporary, `N` if the table is permanent.                                                                     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/33_dba_cons_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/33_dba_cons_columns.mdx
new file mode 100644
index 00000000000..576e1014105
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/33_dba_cons_columns.mdx
@@ -0,0 +1,24 @@
+---
+title: "DBA_CONS_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.135.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.250.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.196.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/33_dba_cons_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_cons_columns" class="registered_link"></div>
+
+The `DBA_CONS_COLUMNS` view provides information about all columns that are included in constraints that are specified on all tables in the database.
+
+| Name              | Type       | Description                                              |
+| ----------------- | ---------- | -------------------------------------------------------- |
+| `owner`           | `TEXT`     | User name of the constraint’s owner.                     |
+| `schema_name`     | `TEXT`     | Name of the schema in which the constraint belongs.      |
+| `constraint_name` | `TEXT`     | Name of the constraint.                              |
+| `table_name`      | `TEXT`     | Name of the table to which the constraint belongs.   |
+| `column_name`     | `TEXT`     | Name of the column referenced in the constraint.     |
+| `position`        | `SMALLINT` | Position of the column in the object definition. |
+| `constraint_def`  | `TEXT`     | Definition of the constraint.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/34_dba_constraints.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/34_dba_constraints.mdx
new file mode 100644
index 00000000000..aa5d6ed2065
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/34_dba_constraints.mdx
@@ -0,0 +1,31 @@
+---
+title: "DBA_CONSTRAINTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.136.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.251.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.197.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/34_dba_constraints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_constraints" class="registered_link"></div>
+
+The `DBA_CONSTRAINTS` view provides information about all constraints on tables in the database.
+
+| Name                | Type      | Description                                                                                                                                                                                                                                                    |
+| ------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`             | `TEXT`    | User name of the constraint’s owner.                                                                                                                                                                                                                           |
+| `schema_name`       | `TEXT`    | Name of the schema in which the constraint belongs.                                                                                                                                                                                                            |
+| `constraint_name`   | `TEXT`    | Name of the constraint.                                                                                                                                                                                                                                    |
+| `constraint_type`   | `TEXT`    | The constraint type. Possible values are: `C` – check constraint; `F` – foreign key constraint; `P` – primary key constraint; `U` – unique key constraint; `R` – referential integrity constraint; `V` – constraint on a view; `O` – with read-only, on a view. |
+| `table_name`        | `TEXT`    | Name of the table to which the constraint belongs.                                                                                                                                                                                                             |
+| `search_condition`  | `TEXT`    | Search condition that applies to a check constraint.                                                                                                                                                                                                           |
+| `r_owner`           | `TEXT`    | Owner of a table referenced by a referential constraint.                                                                                                                                                                                                       |
+| `r_constraint_name` | `TEXT`    | Name of the constraint definition for a referenced table.                                                                                                                                                                                                      |
+| `delete_rule`       | `TEXT`    | The delete rule for a referential constraint. Possible values are: `C` – cascade; `R` - restrict; `N` – no action.                                                                                                                                              |
+| `deferrable`        | `BOOLEAN` | Specified if the constraint is deferrable (`T` or `F`).                                                                                                                                                                                                        |
+| `deferred`          | `BOOLEAN` | Specifies if the constraint has been deferred (`T` or `F`).                                                                                                                                                                                                    |
+| `index_owner`       | `TEXT`    | User name of the index owner.                                                                                                                                                                                                                                  |
+| `index_name`        | `TEXT`    | Name of the index.                                                                                                                                                                                                                                         |
+| `constraint_def`    | `TEXT`    | The definition of the constraint.                                                                                                                                                                                                                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/35_dba_col_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/35_dba_col_privs.mdx
new file mode 100644
index 00000000000..f77766127dc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/35_dba_col_privs.mdx
@@ -0,0 +1,22 @@
+---
+title: "DBA_COL_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/35_dba_col_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_col_privs" class="registered_link"></div>
+
+The `DBA_COL_PRIVS` view provides a listing of the object privileges granted on columns for all the database users.
+
+| Name          | Type                     | Description                                                                                                                                                                                                                                                         |
+| ------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantee`     | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `owner`       | `CHARACTER VARYING(128)` | Object owner.                                                                                                                                                                                                                                                       |
+| `schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`  | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `column_name` | `CHARACTER VARYING(128)` | Column name.                                                                                                                                                                                                                                                        |
+| `grantor`     | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `privilege`   | `CHARACTER VARYING(40)`  | Privilege on the column.                                                                                                                                                                                                                                            |
+| `grantable`   | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the `GRANTEE` (recipient of the privilege) can grant the privilege to others. The value can be `YES` if the grantee has administrator privileges. |
+| `common`      | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
+| `inherited`   | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/36_dba_db_links.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/36_dba_db_links.mdx
new file mode 100644
index 00000000000..177dffd875a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/36_dba_db_links.mdx
@@ -0,0 +1,22 @@
+---
+title: "DBA_DB_LINKS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.137.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.252.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.198.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/36_dba_db_links/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_db_links" class="registered_link"></div>
+
+The `DBA_DB_LINKS` view provides information about all database links in the database.
+
+| Name       | Type                | Description                                                     |
+| ---------- | ------------------- | --------------------------------------------------------------- |
+| `owner`    | `TEXT`              | User name of the database link’s owner.                         |
+| `db_link`  | `TEXT`              | Name of the database link.                                  |
+| `type`     | `CHARACTER VARYING` | Type of remote server. Value is `REDWOOD` or `EDB`.      |
+| `username` | `TEXT`              | User name of the user logging in.                               |
+| `host`     | `TEXT`              | Name or IP address of the remote server.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx
new file mode 100644
index 00000000000..08ee8ec9c39
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/37_dba_directories.mdx
@@ -0,0 +1,19 @@
+---
+title: "DBA_DIRECTORIES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.138.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/37_dba_directories/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/37_dba_directories/
+---
+
+<div id="dba_directories" class="registered_link"></div>
+
+The `DBA_DIRECTORIES` view provides information about all directories created with the `CREATE DIRECTORY` command.
+
+| Name             | Type                      | Description                               |
+| ---------------- | ------------------------- | ----------------------------------------- |
+| `owner`          | `CHARACTER VARYING(30)`   | User name of the directory’s owner.       |
+| `directory_name` | `CHARACTER VARYING(30)`   | Alias name assigned to the directory. |
+| `directory_path` | `CHARACTER VARYING(4000)` | Path to the directory.                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/38_dba_dependencies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/38_dba_dependencies.mdx
new file mode 100644
index 00000000000..928bd6858f6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/38_dba_dependencies.mdx
@@ -0,0 +1,22 @@
+---
+title: "DBA_DEPENDENCIES"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/38_dba_dependencies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_dependencies" class="registered_link"></div>
+
+The `DBA_DEPENDENCIES` view provides information about the dependencies between all objects in the database except for synonyms.
+
+| Name                     | Type                     | Description                                                |
+| ------------------------ | ------------------------ | ---------------------------------------------------------- |
+| `owner`                  | `CHARACTER VARYING(128)` | Owner of the dependent object.                             |
+| `schema_name`            | `CHARACTER VARYING(128)` | Name of the schema in which the dependent object resides.  |
+| `name`                   | `CHARACTER VARYING(128)` | Name of the dependent object.                              |
+| `type`                   | `CHARACTER VARYING(18)`  | Type of the dependent object.                              |
+| `referenced_owner`       | `CHARACTER VARYING(128)` | Owner of the referenced object.                            |
+| `referenced_schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the referenced object resides. |
+| `referenced_name`        | `CHARACTER VARYING(128)` | Name of the referenced object.                             |
+| `referenced_type`        | `CHARACTER VARYING(18)`  | Type of the referenced object.                             |
+| `referenced_link_name`   | `CHARACTER VARYING(128)` | Included only for compatibility. Always `NULL`.            |
+| `dependency_type`        | `CHARACTER VARYING(4)`   | Included only for compatibility. Always set to `HARD`.     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/39_dba_ind_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/39_dba_ind_columns.mdx
new file mode 100644
index 00000000000..10d5498f18f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/39_dba_ind_columns.mdx
@@ -0,0 +1,27 @@
+---
+title: "DBA_IND_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.139.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.253.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.199.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/39_dba_ind_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_ind_columns" class="registered_link"></div>
+
+The `DBA_IND_COLUMNS` view provides information about all columns included in indexes on all tables in the database.
+
+| Name              | Type           | Description                                                      |
+| ----------------- | -------------- | ---------------------------------------------------------------- |
+| `index_owner`     | `TEXT`         | User name of the index owner.                                  |
+| `schema_name`     | `TEXT`         | Name of the schema in which the index belongs.                   |
+| `index_name`      | `TEXT`         | Name of the index.                                               |
+| `table_owner`     | `TEXT`         | User name of the table owner.                                  |
+| `table_name`      | `TEXT`         | Name of the table in which the index belongs.                    |
+| `column_name`     | `TEXT`         | Name of column or attribute of object column.                    |
+| `column_position` | `SMALLINT`     | Position of the column in the index.                         |
+| `column_length`   | `SMALLINT`     | Length of the column in bytes.                             |
+| `char_length`     | `NUMERIC`      | Length of the column in characters.                        |
+| `descend`         | `CHARACTER(1)` | Included only for compatibility. Always set to `Y` (descending). |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/40_dba_indexes.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/40_dba_indexes.mdx
new file mode 100644
index 00000000000..a02cf85a54e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/40_dba_indexes.mdx
@@ -0,0 +1,35 @@
+---
+title: "DBA_INDEXES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.140.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.254.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.200.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/40_dba_indexes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_indexes" class="registered_link"></div>
+
+The `DBA_INDEXES` view provides information about all indexes in the database.
+
+| Name              | Type                    | Description                                                                             |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the index owner.                                                         |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the index resides.                                          |
+| `index_name`      | `TEXT`                  | Name of the index.                                                                  |
+| `index_type`      | `TEXT`                  | The index type is always `BTREE`. Included only for compatibility.                      |
+| `table_owner`     | `TEXT`                  | User name of the owner of the indexed table.                                            |
+| `table_name`      | `TEXT`                  | Name of the indexed table.                                                          |
+| `table_type`      | `TEXT`                  | Included only for compatibility. Always set to `TABLE`.                                 |
+| `uniqueness`      | `TEXT`                  | Indicates if the index is `UNIQUE` or `NONUNIQUE`.                                      |
+| `compression`     | `CHARACTER(1)`          | Included only for compatibility. Always set to `N` (not compressed).                    |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides if other than the default tablespace. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan the index.                                       |
+| `logging`         | `TEXT`                  | Included only for compatibility. Always set to `LOGGING`.                               |
+| `status`          | `TEXT`                  | Whether or not the state of the object is valid (`VALID` or `INVALID`).                |
+| `partitioned`     | `CHARACTER(3)`          | Indicates that the index is partitioned. Always set to `NO`.                            |
+| `temporary`       | `CHARACTER(1)`          | Indicates that an index is on a temporary table. Always set to `N`.                     |
+| `secondary`       | `CHARACTER(1)`          | Included only for compatibility. Always set to `N`.                                     |
+| `join_index`      | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                    |
+| `dropped`         | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/41_dba_jobs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/41_dba_jobs.mdx
new file mode 100644
index 00000000000..6410e09b0de
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/41_dba_jobs.mdx
@@ -0,0 +1,35 @@
+---
+title: "DBA_JOBS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.141.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.255.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.201.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/41_dba_jobs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_jobs" class="registered_link"></div>
+
+The `DBA_JOBS` view provides information about all jobs in the database.
+
+| Name          | Type                       | Description                                                                                   |
+| ------------- | -------------------------- | --------------------------------------------------------------------------------------------- |
+| `job`         | `INTEGER`                  | The identifier of the job (Job ID).                                                           |
+| `log_user`    | `TEXT`                     | Name of the user that submitted the job.                                                  |
+| `priv_user`   | `TEXT`                     | Same as `log_user`. Included only for compatibility.                                          |
+| `schema_user` | `TEXT`                     | Name of the schema used to parse the job.                                                 |
+| `last_date`   | `TIMESTAMP WITH TIME ZONE` | Last date that this job executed successfully.                                            |
+| `last_sec`    | `TEXT`                     | Same as `last_date`.                                                                          |
+| `this_date`   | `TIMESTAMP WITH TIME ZONE` | Date that the job began executing.                                                        |
+| `this_sec`    | `TEXT`                     | Same as `this_date`.                                                                          |
+| `next_date`   | `TIMESTAMP WITH TIME ZONE` | Next date that for the job to execute.                                                     |
+| `next_sec`    | `TEXT`                     | Same as `next_date`.                                                                          |
+| `total_time`  | `INTERVAL`                 | The execution time of this job in seconds.                                                  |
+| `broken`      | `TEXT`                     | If `Y`, no attempt is made to run this job. If `N`, this job attempts to execute.             |
+| `interval`    | `TEXT`                     | Determines how often the job repeats.                                                         |
+| `failures`    | `BIGINT`                   | Number of times that the job failed to complete since its last successful execution. |
+| `what`        | `TEXT`                     | The job definition (PL/SQL code block) that runs when the job executes.                       |
+| `nls_env`     | `CHARACTER VARYING(4000)`  | Always `NULL`. Provided only for compatibility.                                               |
+| `misc_env`    | `BYTEA`                    | Always `NULL`. Provided only for compatibility.                                               |
+| `instance`    | `NUMERIC`                  | Always `0`. Provided only for compatibility.                                                  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/42_dba_objects.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/42_dba_objects.mdx
new file mode 100644
index 00000000000..5ee52d85d01
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/42_dba_objects.mdx
@@ -0,0 +1,25 @@
+---
+title: "DBA_OBJECTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.142.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.256.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.202.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/42_dba_objects/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_objects" class="registered_link"></div>
+
+The `DBA_OBJECTS` view provides information about all objects in the database.
+
+| Name            | Type                | Description                                                                                                                                                   |
+| --------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`         | `TEXT`              | User name of the object’s owner.                                                                                                                              |
+| `schema_name`   | `TEXT`              | Name of the schema in which the object belongs.                                                                                                               |
+| `object_name`   | `TEXT`              | Name of the object.                                                                                                                                           |
+| `object_type`   | `TEXT`              | Type of the object. Possible values are: `INDEX`, `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, `SEQUENCE`, `SYNONYM`, `TABLE`, `TRIGGER`, and `VIEW`.  |
+| `created`       | `DATE`              | Timestamp for when the object was created.                                                                                                                      |
+| `last_ddl_time` | `DATE `             | Timestamp for the last modification of an object resulting from a DDL statement including grants and revokes.                                                 |
+| `status`        | `CHARACTER VARYING` | Included only for compatibility. Always set to `VALID`.                                                                                                       |
+| `temporary`     | `TEXT`              | `Y` if the table is temporary, `N` if the table is permanent.                                                                                                 |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/43_dba_part_key_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/43_dba_part_key_columns.mdx
new file mode 100644
index 00000000000..1847699e405
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/43_dba_part_key_columns.mdx
@@ -0,0 +1,24 @@
+---
+title: "DBA_PART_KEY_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.143.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.257.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.203.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/43_dba_part_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/43_dba_part_key_columns/
+---
+
+<div id="dba_part_key_columns" class="registered_link"></div>
+
+The `DBA_PART_KEY_COLUMNS` view provides information about the key columns of the partitioned tables that reside in the database.
+
+| Name              | Type           | Description                                               |
+| ----------------- | -------------- | --------------------------------------------------------- |
+| `owner`           | `TEXT`         | Owner of the table.                                   |
+| `schema_name`     | `TEXT`         | Name of the schema in which the table resides.        |
+| `name`            | `TEXT`         | Name of the table in which the column resides.        |
+| `object_type`     | `CHARACTER(5)` | Only for compatibility. Always `TABLE`.                   |
+| `column_name`     | `TEXT`         | Name of the column on which the key is defined.       |
+| `column_position` | `INTEGER`      | `1` for the first column, `2` for the second column, and so on. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/44_dba_part_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/44_dba_part_tables.mdx
new file mode 100644
index 00000000000..42ca6bd21a5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/44_dba_part_tables.mdx
@@ -0,0 +1,44 @@
+---
+title: "DBA_PART_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.144.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.258.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.204.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/44_dba_part_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_part_tables" class="registered_link"></div>
+
+The `DBA_PART_TABLES` view provides information about all of the partitioned tables in the database.
+
+| Name                        | Type                      | Description                                                  |
+| --------------------------- | ------------------------- | ------------------------------------------------------------ |
+| `owner`                     | `TEXT`                    | Owner of the partitioned table.                          |
+| `schema_name`               | `TEXT`                    | Schema in which the table resides.                       |
+| `table_name`                | `TEXT`                    | Name of the table.                                       |
+| `partitioning_type`         | `TEXT`                    | Type used to define table partitions.                    |
+| `subpartitioning_type`      | `TEXT`                    | Subpartitioning type used to define table subpartitions. |
+| `partition_count`           | `BIGINT`                  | Number of partitions in the table.                       |
+| `def_subpartition_count`    | `INTEGER`                 | Number of subpartitions in the table.                    |
+| `partitioning_key_count`    | `INTEGER`                 | Number of partitioning keys specified.                   |
+| `subpartitioning_key_count` | `INTEGER`                 | Number of subpartitioning keys specified.                |
+| `status`                    | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `VALID`.             |
+| `def_tablespace_name`       | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_free`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_used`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_ini_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_max_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_initial_extent`        | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_next_extent`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_min_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_max_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_increase`          | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_freelists`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_freelist_groups`       | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_logging`               | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `YES`.               |
+| `def_compression`           | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `NONE`.              |
+| `def_buffer_pool`           | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `DEFAULT`.           |
+| `ref_ptn_constraint_name`   | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `interval`                  | `CHARACTER VARYING(1000)` | Provided only for compatibility. Always `NULL`.              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45_dba_policies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45_dba_policies.mdx
new file mode 100644
index 00000000000..e1b670231b5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45_dba_policies.mdx
@@ -0,0 +1,35 @@
+---
+title: "DBA_POLICIES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.145.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.259.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.205.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/45_dba_policies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_policies" class="registered_link"></div>
+
+The `DBA_POLICIES` view provides information on all policies in the database. This view is accessible only to superusers.
+
+| Name             | Type   | Description                                                                                                                |
+| ---------------- | ------ | -------------------------------------------------------------------------------------------------------------------------- |
+| `object_owner`   | `TEXT` | Name of the owner of the object.                                                                                           |
+| `schema_name`    | `TEXT` | Name of the schema in which the object resides.                                                                        |
+| `object_name`    | `TEXT` | Name of the object to which the policy applies.                                                                            |
+| `policy_group`   | `TEXT` | Name of the policy group. Included only for compatibility. Always set to an empty string.                                  |
+| `policy_name`    | `TEXT` | Name of the policy.                                                                                                        |
+| `pf_owner`       | `TEXT` | Name of the schema containing the policy function or the schema containing the package that contains the policy function. |
+| `package`        | `TEXT` | Name of the package containing the policy function if the function belongs to a package.                                 |
+| `function`       | `TEXT` | Name of the policy function.                                                                                               |
+| `sel`            | `TEXT` | Whether or not the policy applies to `SELECT` commands. Possible values are `YES` or `NO`.                                 |
+| `ins`            | `TEXT` | Whether or not the policy applies to `INSERT` commands. Possible values are `YES` or `NO`.                                 |
+| `upd`            | `TEXT` | Whether or not the policy applies to `UPDATE` commands. Possible values are `YES` or `NO`.                                 |
+| `del`            | `TEXT` | Whether or not the policy applies to `DELETE` commands. Possible values are `YES` or `NO`.                                 |
+| `idx`            | `TEXT` | Whether or not the policy applies to index maintenance. Possible values are `YES` or `NO`.                                 |
+| `chk_option`     | `TEXT` | Whether or not the check option is in force for `INSERT` and `UPDATE` commands. Possible values are `YES` or `NO`.         |
+| `enable`         | `TEXT` | Whether or not the policy is enabled on the object. Possible values are `YES` or `NO`.                                     |
+| `static_policy`  | `TEXT` | Included only for compatibility. Always set to `NO`.                                                                       |
+| `policy_type`    | `TEXT` | Included only for compatibility. Always set to `UNKNOWN`.                                                                  |
+| `long_predicate` | `TEXT` | Included only for compatibility. Always set to `YES`.                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45a_dba_privs_capture.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45a_dba_privs_capture.mdx
new file mode 100644
index 00000000000..b4e7a44f5bd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/45a_dba_privs_capture.mdx
@@ -0,0 +1,18 @@
+---
+title: "DBA_PRIVS_CAPTURE"
+---
+
+The `DBA_PRIVS_CAPTURE` view provides information about all the used privileges. The used privileges are populated by the `DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT` procedure.
+
+Superuser or the user with `CAPTURE_ADMIN` role can access this view.
+
+
+|     Name      |    Type     |                                                      Description                                                      |
+| ------------- | ----------- | --------------------------------------------------------------------------------------------------------------------- |
+| `name`        | `NAME`      | Name of the capture policy for privilege analysis.                                                                    |
+| `description` | `TEXT`      | Description of the capture policy for privilege analysis.                                                             |
+| `type`        | `TEXT`      | Type of the privilege analysis policy. Possible values are `G_DATABASE`, `G_ROLE`, `G_CONTEXT`, `G_ROLE_AND_CONTEXT`. |
+| `enabled`     | `BOOLEAN`   | Whether or not the policy is enabled on the object. Possible values are `YES` or `NO`.                                |
+| `roles`       | `REGROLE[]` | Name of the roles whose privileges are to be analyzed, if the `type` is `G_ROLE` or `G_ROLE_AND_CONTEXT`.             |
+| `context`     | `TEXT`      | Condition if the privilege analysis type is `G_CONTEXT` or `G_ROLE_AND_CONTEXT`.                                      |
+| `run_name`    | `NAME`      | Name of the run for which privileges are analyzed.                                                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/46_dba_profiles.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/46_dba_profiles.mdx
new file mode 100644
index 00000000000..8ec161b6baf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/46_dba_profiles.mdx
@@ -0,0 +1,22 @@
+---
+title: "DBA_PROFILES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.146.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.260.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.206.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/46_dba_profiles/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_profiles" class="registered_link"></div>
+
+The `DBA_PROFILES` view provides information about existing profiles. The table includes a row for each profile/resource combination.
+
+| Name            | Type                     | Description                                                                                     |
+| --------------- | ------------------------ | ----------------------------------------------------------------------------------------------- |
+| `profile`       | `CHARACTER VARYING(128)` | Name of the profile.                                                                        |
+| `resource_name` | `CHARACTER VARYING(32)`  | Name of the resource associated with the profile.                                           |
+| `resource_type` | `CHARACTER VARYING(8)`   | Type of resource governed by the profile. `PASSWORD` for all supported resources. |
+| `limit`         | `CHARACTER VARYING(128)` | The limit values of the resource.                                                               |
+| `common`        | `CHARACTER VARYING(3)`   | `YES` for a user-created profile, `NO` for a system-defined profile.                            |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/47_dba_queues.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/47_dba_queues.mdx
new file mode 100644
index 00000000000..8aacab47120
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/47_dba_queues.mdx
@@ -0,0 +1,28 @@
+---
+title: "DBA_QUEUES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.147.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/47_dba_queues/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_queues" class="registered_link"></div>
+
+The `DBA_QUEUES` view provides information about any currently defined queues.
+
+| Name              | Type                | Description                                                                          |
+| ----------------- | ------------------- | ------------------------------------------------------------------------------------ |
+| `owner`           | `TEXT`              | User name of the queue owner.                                                        |
+| `name`            | `TEXT`              | Name of the queue.                                                               |
+| `queue_table`     | `TEXT`              | Name of the queue table in which the queue resides.                              |
+| `qid`             | `OID`               | System-assigned object ID of the queue.                                          |
+| `queue_type`      | `CHARACTER VARYING` | Queue type. Possible values are `EXCEPTION_QUEUE`, `NON_PERSISTENT_QUEUE`, or `NORMAL_QUEUE`. |
+| `max_retries`     | `NUMERIC`           | Maximum number of dequeue attempts.                                              |
+| `retrydelay`      | `NUMERIC`           | Maximum time allowed between retries.                                            |
+| `enqueue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows enqueuing, `NO` if the queue does not.                     |
+| `dequeue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows dequeuing, `NO` if the queue does not.                     |
+| `retention`       | `CHARACTER VARYING` | Number of seconds that a processed message is retained in the queue.             |
+| `user_comment`    | `CHARACTER VARYING` | User-specified comment.                                                            |
+| `network_name`    | `CHARACTER VARYING` | Name of the network on which the queue resides.                                  |
+| `sharded`         | `CHARACTER VARYING` | `YES` if the queue resides on a sharded network, `NO` if the queue does not.         |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/48_dba_queue_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/48_dba_queue_tables.mdx
new file mode 100644
index 00000000000..e85516db565
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/48_dba_queue_tables.mdx
@@ -0,0 +1,28 @@
+---
+title: "DBA_QUEUE_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.148.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/48_dba_queue_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_queue_tables" class="registered_link"></div>
+
+The `DBA_QUEUE_TABLES` view provides information about all of the queue tables in the database.
+
+| Name                 | Type                | Description                                                                                  |
+| -------------------- | ------------------- | -------------------------------------------------------------------------------------------- |
+| `owner`              | `TEXT`              | Role name of the owner of the queue table.                                                   |
+| `queue_table`        | `TEXT`              | User-specified name of the queue table.                                                  |
+| `type`               | `CHARACTER VARYING` | Type of data stored in the queue table.                                                  |
+| `object_type`        | `TEXT`              | User-defined payload type.                                                               |
+| `sort_order`         | `CHARACTER VARYING` | Order in which the queue table is sorted.                                                |
+| `recipients`         | `CHARACTER VARYING` | Always `SINGLE`.                                                                             |
+| `message_grouping`   | `CHARACTER VARYING` | Always `NONE`.                                                                               |
+| `compatible`         | `CHARACTER VARYING` | Release number of the EDB Postgres Advanced Server release with which this queue table is compatible. |
+| `primary_instance`   | `NUMERIC`           | Always `0`.                                                                                  |
+| `secondary_instance` | `NUMERIC`           | Always `0`.                                                                                  |
+| `owner_instance`     | `NUMERIC`           | Instance number of the instance that owns the queue table.                               |
+| `user_comment`       | `CHARACTER VARYING` | User comment provided when the table was created.                                        |
+| `secure`             | `CHARACTER VARYING` | `YES` indicates that the queue table is secure. `NO` indicates that it isn't.               |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/49_dba_role_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/49_dba_role_privs.mdx
new file mode 100644
index 00000000000..f363aa56080
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/49_dba_role_privs.mdx
@@ -0,0 +1,21 @@
+---
+title: "DBA_ROLE_PRIVS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.149.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.261.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.207.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/49_dba_role_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_role_privs" class="registered_link"></div>
+
+The `DBA_ROLE_PRIVS` view provides information on all roles that were granted to users. A row is created for each role to which a user was granted.
+
+| Name           | Type   | Description                                                          |
+| -------------- | ------ | -------------------------------------------------------------------- |
+| `grantee`      | `TEXT` | User name to whom the role was granted.                              |
+| `granted_role` | `TEXT` | Name of the role granted to the grantee.                             |
+| `admin_option` | `TEXT` | `YES` if the role was granted with the admin option. `NO` otherwise. |
+| `default_role` | `TEXT` | `YES` if the role is enabled when the grantee creates a session.     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/50_dba_roles.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/50_dba_roles.mdx
new file mode 100644
index 00000000000..64b63288991
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/50_dba_roles.mdx
@@ -0,0 +1,19 @@
+---
+title: "DBA_ROLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.150.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.262.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.208.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/50_dba_roles/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_roles" class="registered_link"></div>
+
+The `DBA_ROLES` view provides information on all roles with the `NOLOGIN` attribute (groups).
+
+| Name                | Type   | Description                                                    |
+| ------------------- | ------ | -------------------------------------------------------------- |
+| `role`              | `TEXT` | Name of a role having the `NOLOGIN` attribute, that is, a group. |
+| `password_required` | `TEXT` | Included only for compatibility. Always `N`.                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/51_dba_sequences.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/51_dba_sequences.mdx
new file mode 100644
index 00000000000..eff4e25bd0d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/51_dba_sequences.mdx
@@ -0,0 +1,27 @@
+---
+title: "DBA_SEQUENCES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.151.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.263.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.209.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/51_dba_sequences/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_sequences" class="registered_link"></div>
+
+The `DBA_SEQUENCES` view provides information about all user-defined sequences.
+
+| Name             | Type                | Description                                                                       |
+| ---------------- | ------------------- | --------------------------------------------------------------------------------- |
+| `sequence_owner` | `TEXT`              | User name of the sequence's owner.                                                |
+| `schema_name`    | `TEXT`              | Name of the schema in which the sequence resides.                             |
+| `sequence_name`  | `TEXT`              | Name of the sequence.                                                             |
+| `min_value`      | `NUMERIC`           | Lowest value that the server assigns to the sequence.                         |
+| `max_value`      | `NUMERIC`           | Highest value that the server assigns to the sequence.                        |
+| `increment_by`   | `NUMERIC`           | Value added to the current sequence number to create the next sequent number. |
+| `cycle_flag`     | `CHARACTER VARYING` | Specifies whether the sequence wraps when it reaches `min_value` or `max_value`. |
+| `order_flag`     | `CHARACTER VARYING` | Always returns `Y`.                                                                |
+| `cache_size`     | `NUMERIC`           | The number of preallocated sequence numbers stored in memory.                    |
+| `last_number`    | `NUMERIC`           | The value of the last sequence number saved to disk.                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/52_dba_source.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/52_dba_source.mdx
new file mode 100644
index 00000000000..05925169a52
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/52_dba_source.mdx
@@ -0,0 +1,23 @@
+---
+title: "DBA_SOURCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.152.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.264.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.210.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/52_dba_source/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_source" class="registered_link"></div>
+
+The `DBA_SOURCE` view provides the source code listing of all objects in the database.
+
+| Name          | Type      | Description                                                                                              |
+| ------------- | --------- | -------------------------------------------------------------------------------------------------------- |
+| `owner`       | `TEXT`    | User name of the program owner.                                                                        |
+| `schema_name` | `TEXT`    | Name of the schema in which the program belongs.                                                         |
+| `name`        | `TEXT`    | Name of the program.                                                                                     |
+| `type`        | `TEXT`    | Type of program. Possible values are: `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, and `TRIGGER`. |
+| `line`        | `INTEGER` | Source code line number relative to a given program.                                                     |
+| `text`        | `TEXT`    | Line of source code text.                                                                                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/53_dba_subpart_key_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/53_dba_subpart_key_columns.mdx
new file mode 100644
index 00000000000..edf11843e75
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/53_dba_subpart_key_columns.mdx
@@ -0,0 +1,23 @@
+---
+title: "DBA_SUBPART_KEY_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.153.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.265.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.211.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/53_dba_subpart_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_subpart_key_columns" class="registered_link"></div>
+
+The `DBA_SUBPART_KEY_COLUMNS` view provides information about the key columns of those partitioned tables that are subpartitioned that reside in the database.
+
+| Name              | Type           | Description                                               |
+| ----------------- | -------------- | --------------------------------------------------------- |
+| `owner`           | `TEXT`         | Owner of the table.                                   |
+| `schema_name`     | `TEXT`         | Name of the schema in which the table resides.        |
+| `name`            | `TEXT`         | Name of the table in which the column resides.        |
+| `object_type`     | `CHARACTER(5)` | Only for compatibility. Always `TABLE`.                   |
+| `column_name`     | `TEXT`         | Name of the column on which the key is defined.       |
+| `column_position` | `INTEGER`      | `1` for the first column, `2` for the second column, and so on. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/54_dba_synonyms.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/54_dba_synonyms.mdx
new file mode 100644
index 00000000000..21e67bff511
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/54_dba_synonyms.mdx
@@ -0,0 +1,24 @@
+---
+title: "DBA_SYNONYMS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.154.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.266.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.212.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/54_dba_synonyms/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_synonyms" class="registered_link"></div>
+
+The `DBA_SYNONYM` view provides information about all synonyms in the database.
+
+| Name                | Type   | Description                                                     |
+| ------------------- | ------ | --------------------------------------------------------------- |
+| `owner`             | `TEXT` | User name of the synonym owner.                               |
+| `schema_name`       | `TEXT` | Name of the schema in which the synonym belongs.                |
+| `synonym_name`      | `TEXT` | Name of the synonym.                                            |
+| `table_owner`       | `TEXT` | User name of the owner of the table on which the synonym is defined. |
+| `table_schema_name` | `TEXT` | Name of the schema in which the table resides.              |
+| `table_name`        | `TEXT` | Name of the table on which the synonym is defined.              |
+| `db_link`           | `TEXT` | Name of any associated database link.                           |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/55_dba_tab_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/55_dba_tab_columns.mdx
new file mode 100644
index 00000000000..36a04909c1a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/55_dba_tab_columns.mdx
@@ -0,0 +1,28 @@
+---
+title: "DBA_TAB_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.155.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.267.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.213.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/55_dba_tab_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_tab_columns" class="registered_link"></div>
+
+The `DBA_TAB_COLUMNS` view provides information about all columns in the database.
+
+| Name             | Type                | Description                                                                                                             |
+| ---------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `owner`          | `CHARACTER VARYING` | User name of the owner of the table or view in which the column resides.                                                |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the table or view resides.                                                                  |
+| `table_name`     | `CHARACTER VARYING` | Name of the table or view in which the column resides.                                                                  |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                     |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                 |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                      |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                              |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the table or view.                                                               |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/56_dba_tab_partitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/56_dba_tab_partitions.mdx
new file mode 100644
index 00000000000..811f30c7b03
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/56_dba_tab_partitions.mdx
@@ -0,0 +1,52 @@
+---
+title: "DBA_TAB_PARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.156.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.268.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.214.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/56_dba_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_tab_partitions" class="registered_link"></div>
+
+The `DBA_TAB_PARTITIONS` view provides information about all of the partitions that reside in the database.
+
+| Name                 | Type                          | Description                                                                                                                               |
+| -------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `table_owner`        | `TEXT`                        | Owner of the table in which the partition resides.                                                                                    |
+| `schema_name`        | `TEXT`                        | Name of the schema in which the table resides.                                                                                        |
+| `table_name`         | `TEXT`                        | Name of the table.                                                                                                                    |
+| `composite`          | `TEXT`                        | `YES` if the table is subpartitioned, NO if the table isn't subpartitioned.                                                              |
+| `partition_name`     | `TEXT`                        | Name of the partition.                                                                                                                |
+| `subpartition_count` | `BIGINT`                      | Number of subpartitions in the partition.                                                                                             |
+| `high_value`         | `TEXT`                        | High-partitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`  | `INTEGER`                     | Length of high-partitioning value.                                                                                                    |
+| `partition_position` | `INTEGER`                     | Ordinal position of this partition.                                                                                                   |
+| `tablespace_name`    | `TEXT`                        | Name of the tablespace in which the partition resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `pct_free`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_used`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `ini_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `initial_extent`     | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `next_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `min_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_increase`       | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `freelists`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`                                                                                            |
+| `freelist_groups`    | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `logging`            | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `compression`        | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                           |
+| `num_rows`           | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                             |
+| `blocks`             | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                              |
+| `empty_blocks`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_space`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `chain_cnt`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_row_len`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `sample_size`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `last_analyzed`      | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                           |
+| `buffer_pool`        | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                           |
+| `global_stats`       | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `user_stats`         | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                             |
+| `backing_table`      | `REGCLASS`                    | Name of the partition backing table.                                                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/57_dba_tab_subpartitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/57_dba_tab_subpartitions.mdx
new file mode 100644
index 00000000000..e84e0cd61cd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/57_dba_tab_subpartitions.mdx
@@ -0,0 +1,51 @@
+---
+title: "DBA_TAB_SUBPARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.157.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.269.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.215.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/57_dba_tab_subpartitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_tab_subpartitions" class="registered_link"></div>
+
+The `DBA_TAB_SUBPARTITIONS` view provides information about all of the subpartitions that reside in the database.
+
+| Name                    | Type                          | Description                                                                                                                                  |
+| ----------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `table_owner`           | `TEXT`                        | Owner of the table in which the subpartition resides.                                                                                    |
+| `schema_name`           | `TEXT`                        | Name of the schema in which the table resides.                                                                                           |
+| `table_name`            | `TEXT`                        | Name of the table.                                                                                                                       |
+| `partition_name`        | `TEXT`                        | Name of the partition.                                                                                                                   |
+| `subpartition_name`     | `TEXT`                        | Name of the subpartition.                                                                                                                |
+| `high_value`            | `TEXT`                        | High-subpartitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`     | `INTEGER`                     | Length of high-partitioning value.                                                                                                       |
+| `subpartition_position` | `INTEGER`                     | Ordinal position of this subpartition.                                                                                                   |
+| `tablespace_name`       | `TEXT`                        | Name of the tablespace in which the subpartition resides. If the tablespace name isn't specified, the default tablespace ia `PG_DEFAULT`. |
+| `pct_free`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_used`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `ini_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `initial_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `next_extent`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `min_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_increase`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `freelists`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `freelist_groups`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `logging`               | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `compression`           | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                              |
+| `num_rows`              | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                                |
+| `blocks`                | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                                 |
+| `empty_blocks`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_space`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `chain_cnt`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_row_len`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `sample_size`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `last_analyzed`         | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                              |
+| `buffer_pool`           | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                              |
+| `global_stats`          | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `user_stats`            | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                                |
+| `backing_table`         | `REGCLASS`                    | Name of the subpartition backing table.                                                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/58_dba_tab_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/58_dba_tab_privs.mdx
new file mode 100644
index 00000000000..913883d088d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/58_dba_tab_privs.mdx
@@ -0,0 +1,23 @@
+---
+title: "DBA_TAB_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/58_dba_tab_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_tab_privs" class="registered_link"></div>
+
+The `DBA_TAB_PRIVS` view provides a listing of the access privileges granted to database users and to `PUBLIC`.
+
+| Name          | Type                     | Description                                                                                                                                                                                                                                                         |
+| ------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantee`     | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `owner`       | `CHARACTER VARYING(128)` | Object owner.                                                                                                                                                                                                                                                       |
+| `schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`  | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `grantor`     | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `privilege`   | `CHARACTER VARYING(40)`  | Privilege name.                                                                                                                                                                                                                                                     |
+| `grantable`   | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the `GRANTEE` (recipient of the privilege) can grant the privilege to others. The value can be `YES` if the grantee has administrator privileges. |
+| `hierarchy`   | `CHARACTER VARYING(3)`   | The value can be `YES` or `NO`. The value can be `YES` if the privilege is `SELECT`.                                                                                                                                                                       |
+| `common`      | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
+| `type`        | `CHARACTER VARYING(24)`  | Type of object.                                                                                                                                                                                                                                                     |
+| `inherited`   | `CHARACTER VARYING(3)`   | Included only for compatibility. Aalways `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/59_dba_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/59_dba_tables.mdx
new file mode 100644
index 00000000000..5e53287ab10
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/59_dba_tables.mdx
@@ -0,0 +1,24 @@
+---
+title: "DBA_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.158.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.270.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.216.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/59_dba_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_tables" class="registered_link"></div>
+
+The `DBA_TABLES` view provides information about all tables in the database.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`           | `TEXT`                  | User name of the table owner.                                                                                                   |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                                |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING(5)`  | Included only for compatibility. Always set to `VALID`.                                                                           |
+| `temporary`       | `CHARACTER(1)`          | `Y` if the table is temporary. `N` if the table is permanent.                                                                     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/60_dba_triggers.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/60_dba_triggers.mdx
new file mode 100644
index 00000000000..8efb3b504c1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/60_dba_triggers.mdx
@@ -0,0 +1,30 @@
+---
+title: "DBA_TRIGGERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.159.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.271.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.217.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/60_dba_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_triggers" class="registered_link"></div>
+
+The `DBA_TRIGGERS` view provides information about all triggers in the database.
+
+| Name                | Type   | Description                                                                                                    |
+| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------- |
+| `owner`             | `TEXT` | User name of the trigger owner.                                                                              |
+| `schema_name`       | `TEXT` | Name of the schema in which the trigger resides.                                                           |
+| `trigger_name`      | `TEXT` | Name of the trigger.                                                                                       |
+| `trigger_type`      | `TEXT` | Type of the trigger. Possible values are: `BEFORE ROW`, `BEFORE STATEMENT`, `AFTER ROW`, `AFTER STATEMENT`. |
+| `triggering_event`  | `TEXT` | Event that fires the trigger.                                                                              |
+| `table_owner`       | `TEXT` | User name of the owner of the table on which the trigger is defined.                                       |
+| `base_object_type`  | `TEXT` | Included only for compatibility. Value is always `TABLE`.                                                      |
+| `table_name`        | `TEXT` | Name of the table on which the trigger is defined.                                                         |
+| `referencing_names` | `TEXT` | Included only for compatibility. Value is always `REFERENCING NEW AS NEW OLD AS OLD`.                          |
+| `status`            | `TEXT` | Status indicates if the trigger is enabled `(VALID)` or disabled `(NOTVALID)`.                                 |
+| `description`       | `TEXT` | Included onky for compatibility.                                                                               |
+| `trigger_body`      | `TEXT` | The body of the trigger.                                                                                       |
+| `action_statement`  | `TEXT` | The SQL command that executes when the trigger fires.                                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/61_dba_types.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/61_dba_types.mdx
new file mode 100644
index 00000000000..1c18ca8a475
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/61_dba_types.mdx
@@ -0,0 +1,23 @@
+---
+title: "DBA_TYPES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.160.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.272.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.218.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/61_dba_types/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_types" class="registered_link"></div>
+
+The `DBA_TYPES` view provides information about all object types in the database.
+
+| Name          | Type      | Description                                                                    |
+| ------------- | --------- | ------------------------------------------------------------------------------ |
+| `owner`       | `TEXT`    | Owner of the object type.                                                  |
+| `schema_name` | `TEXT`    | Name of the schema in which the type is defined.                           |
+| `type_name`   | `TEXT`    | Name of the type.                                                          |
+| `type_oid`    | `OID`     | Oject identifier (OID) of the type.                                       |
+| `typecode`    | `TEXT`    | Typecode of the type. Possible values are: `OBJECT`, `COLLECTION`, `OTHER`. |
+| `attributes`  | `INTEGER` | Number of attributes in the type.                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62_dba_users.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62_dba_users.mdx
new file mode 100644
index 00000000000..1d415c0c497
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62_dba_users.mdx
@@ -0,0 +1,30 @@
+---
+title: "DBA_USERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.161.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.273.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.219.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/62_dba_users/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_users" class="registered_link"></div>
+
+The `DBA_USERS` view provides information about all users of the database.
+
+| Name                          | Type                          | Description                                                                                                                                                                                                                                                                                                                   |
+| ----------------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `username`                    | `TEXT`                        | User name of the user.                                                                                                                                                                                                                                                                                                        |
+| `user_id`                     | `OID`                         | ID number of the user.                                                                                                                                                                                                                                                                                                        |
+| `password`                    | `CHARACTER VARYING(30)`       | Encrypted password of the user.                                                                                                                                                                                                                                                                                         |
+| `account_status`              | `CHARACTER VARYING(32)`       | Current status of the account. Possible values are: `OPEN`, `EXPIRED`, `EXPIRED(GRACE)`, `EXPIRED & LOCKED`, `EXPIRED & LOCKED(TIMED)`, `EXPIRED(GRACE) & LOCKED`, `EXPIRED(GRACE) & LOCKED(TIMED)`, `LOCKED`, `LOCKED(TIMED)`. Use the `edb_get_role_status(role_id)` function to get the current status of the account. |
+| `lock_date`                   | `TIMESTAMP WITHOUT TIME ZONE` | If the account status is `LOCKED`, `lock_date` displays the date and time the account was locked.                                                                                                                                                                                                                             |
+| `expiry_date`                 | `TIMESTAMP WITHOUT TIME ZONE` | The expiration date of the password. Use the `edb_get_password_expiry_date(role_id)` function to get the current password expiration date.                                                                                                                                                                                    |
+| `default_tablespace`          | `TEXT`                        | Default tablespace associated with the account.                                                                                                                                                                                                                                                                           |
+| `temporary_tablespace`        | `CHARACTER VARYING(30)`       | Included only for compatibility. The value is always '' (an empty string).                                                                                                                                                                                                                                                    |
+| `created`                     | `DATE`                        | Timestamp for when the object was created.                                                                                                                                                                                                                                                                                      |
+| `last_ddl_time`               | `DATE`                        | Timestamp for the last modification of an object resulting from a DDL statement including grants and revokes.                                                                                                                                                                                                                 |
+| `profile`                     | `CHARACTER VARYING(30)`       | The profile associated with the user.                                                                                                                                                                                                                                                                                         |
+| `initial_rsrc_consumer_group` | `CHARACTER VARYING(30)`       | Included only for compatibility. The value is always `NULL`.                                                                                                                                                                                                                                                                  |
+| `external_name`               | `CHARACTER VARYING(4000)`     | Included only for compatibility. The value is always `NULL`.                                                                                                                                                                                                                                                                  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62a_dba_used_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62a_dba_used_privs.mdx
new file mode 100644
index 00000000000..4866846f837
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62a_dba_used_privs.mdx
@@ -0,0 +1,19 @@
+---
+title: "DBA_USED_PRIVS"
+---
+
+The `DBA_USED_PRIVS` view provides information about all the used privileges. The used privileges are populated by the `DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT` procedure.
+
+Superuser or the user with `CAPTURE_ADMIN` role can access this view.
+
+
+|       Name       |  Type  |                                                                  Description                                                                  |  
+| ---------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------- | 
+| `policy_name`    | `NAME` | Name of the privilege analysis policy.                                                                                                        | 
+| `run_name`       | `NAME` | Name of the run for which privileges are analyzed.                                                                                            |
+| `object_class`   | `TEXT` | Name of the database object like table, function, procedure, and so on.                                                                       |
+| `object_name`    | `TEXT` | Name of the object for which used privilege are recorded.                                                                                     | 
+| `column_name`    | `TEXT` | Name of the column for the used object privilege.                                                                                             |
+| `application`    | `TEXT` | Name of the application through which queries are run. For eg: psql.                                                                          |
+| `role_name`      | `NAME` | Name of the role whose privilege usage is analyzed and recorded.                                                                              |
+| `privilege_type` | `TEXT` | Name of the used privilege recorded during analysis. Possible values are `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, `REFERENCES`,... |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62b_dba_unused_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62b_dba_unused_privs.mdx
new file mode 100644
index 00000000000..4f5cc2c308c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/62b_dba_unused_privs.mdx
@@ -0,0 +1,19 @@
+---
+title: "DBA_UNUSED_PRIVS"
+---
+
+The `DBA_UNUSED_PRIVS` view provides information about all the unused privileges. The unused privileges are populated by the `DBMS_PRIVILEGE_CAPTURE.GENERATE_RESULT` procedure.
+
+Superuser or the user with `CAPTURE_ADMIN` role can access this view.
+
+
+|       Name       |  Type  |                               Description                                |
+| ---------------- | ------ | ------------------------------------------------------------------------ |
+| `policy_name`    | `NAME` | Name of the privilege analysis policy.                                   |
+| `run_name`       | `NAME` | Name of the run for which privileges are analyzed.                       |
+| `object_class`   | `TEXT` | Name of the database object like table, function, procedure, and so on.. |
+| `object_name`    | `TEXT` | Name of the object for which unused privilege are recorded.              |
+| `column_name`    | `TEXT` | Name of the column for the unused object privilege.                      |
+| `application`    | `TEXT` | Name of the application through which queries are run. For eg: psql.     |
+| `role_name`      | `NAME` | Name of the role whose privilege usage is analyzed and recorded.         |
+| `privilege_type` | `TEXT` | Name of the unused privilege recorded during analysis.                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/63_dba_view_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/63_dba_view_columns.mdx
new file mode 100644
index 00000000000..89e4327a322
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/63_dba_view_columns.mdx
@@ -0,0 +1,28 @@
+---
+title: "DBA_VIEW_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.162.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.274.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.220.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/63_dba_view_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_view_columns" class="registered_link"></div>
+
+The `DBA_VIEW_COLUMNS` view provides information on all columns in the database.
+
+| Name             | Type                | Description                                                                                                             |
+| ---------------- | ------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `owner`          | `CHARACTER VARYING` | User name of the view owner.                                                                                          |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the view belongs.                                                                           |
+| `view_name`      | `CHARACTER VARYING` | Name of the view.                                                                                                       |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                     |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                 |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                      |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                              |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the view.                                                                        |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/64_dba_views.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/64_dba_views.mdx
new file mode 100644
index 00000000000..414d24bd3af
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/64_dba_views.mdx
@@ -0,0 +1,21 @@
+---
+title: "DBA_VIEWS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.163.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.275.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.221.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/64_dba_views/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="dba_views" class="registered_link"></div>
+
+The `DBA_VIEWS` view provides information about all views in the database.
+
+| Name          | Type   | Description                                               |
+| ------------- | ------ | --------------------------------------------------------- |
+| `owner`       | `TEXT` | User name of the view owner.                            |
+| `schema_name` | `TEXT` | Name of the schema in which the view belongs.             |
+| `view_name`   | `TEXT` | Name of the view.                                         |
+| `text`        | `TEXT` | Text of the `SELECT` statement that defines the view. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/65_user_all_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/65_user_all_tables.mdx
new file mode 100644
index 00000000000..ff0afb77eca
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/65_user_all_tables.mdx
@@ -0,0 +1,23 @@
+---
+title: "USER_ALL_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.164.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.276.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.222.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/65_user_all_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_all_tables" class="registered_link"></div>
+
+The `USER_ALL_TABLES` view provides information about all tables owned by the current user.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                                |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING(5)`  | Included only for compatibility. Always set to `VALID`.                                                                           |
+| `temporary`       | `TEXT`                  | `Y` if the table is temporary; `N` if the table is permanent.                                                                     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/66_user_cons_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/66_user_cons_columns.mdx
new file mode 100644
index 00000000000..b3f9f882d37
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/66_user_cons_columns.mdx
@@ -0,0 +1,24 @@
+---
+title: "USER_CONS_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.165.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.277.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.223.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/66_user_cons_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_cons_columns" class="registered_link"></div>
+
+The `USER_CONS_COLUMNS` view provides information about all columns that are included in constraints in tables that are owned by the current user.
+
+| Name              | Type       | Description                                              |
+| ----------------- | ---------- | -------------------------------------------------------- |
+| `owner`           | `TEXT`     | User name of the constraint owner.                     |
+| `schema_name`     | `TEXT`     | Name of the schema in which the constraint belongs.      |
+| `constraint_name` | `TEXT`     | Name of the constraint.                              |
+| `table_name`      | `TEXT`     | Name of the table to which the constraint belongs.   |
+| `column_name`     | `TEXT`     | Name of the column referenced in the constraint.     |
+| `position`        | `SMALLINT` | Position of the column in the object definition. |
+| `constraint_def`  | `TEXT`     | Definition of the constraint.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/67_user_constraints.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/67_user_constraints.mdx
new file mode 100644
index 00000000000..c865fb603df
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/67_user_constraints.mdx
@@ -0,0 +1,31 @@
+---
+title: "USER_CONSTRAINTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.166.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.278.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.224.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/67_user_constraints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_constraints" class="registered_link"></div>
+
+The `USER_CONSTRAINTS` view provides information about all constraints placed on tables that are owned by the current user.
+
+| Name                | Type      | Description                                                                                                                                                                                                                                                    |
+| ------------------- | --------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `owner`             | `TEXT`    | Name of the owner of the constraint.                                                                                                                                                                                                                       |
+| `schema_name`       | `TEXT`    | Name of the schema in which the constraint belongs.                                                                                                                                                                                                            |
+| `constraint_name`   | `TEXT`    | Name of the constraint.                                                                                                                                                                                                                                    |
+| `constraint_type`   | `TEXT`    | The constraint type. Possible values are: `C` – check constraint; `F` – foreign key constraint; `P` – primary key constraint; `U` – unique key constraint; `R` – referential integrity constraint; `V` – constraint on a view; `O` – with read-only, on a view. |
+| `table_name`        | `TEXT`    | Name of the table to which the constraint belongs.                                                                                                                                                                                                             |
+| `search_condition`  | `TEXT`    | Search condition that applies to a check constraint.                                                                                                                                                                                                           |
+| `r_owner`           | `TEXT`    | Owner of a table referenced by a referential constraint.                                                                                                                                                                                                       |
+| `r_constraint_name` | `TEXT`    | Name of the constraint definition for a referenced table.                                                                                                                                                                                                      |
+| `delete_rule`       | `TEXT`    | The delete rule for a referential constraint. Possible values are: `C` – cascade; `R` - restrict; `N` – no action.                                                                                                                                              |
+| `deferrable`        | `BOOLEAN` | Specified if the constraint is deferrable (`T` or `F`).                                                                                                                                                                                                        |
+| `deferred`          | `BOOLEAN` | Specifies if the constraint was deferred (`T` or `F`).                                                                                                                                                                                                    |
+| `index_owner`       | `TEXT`    | User name of the index owner.                                                                                                                                                                                                                                  |
+| `index_name`        | `TEXT`    | Name of the index.                                                                                                                                                                                                                                         |
+| `constraint_def`    | `TEXT`    | Definition of the constraint.                                                                                                                                                                                                                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/68_user_col_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/68_user_col_privs.mdx
new file mode 100644
index 00000000000..23c4d34058a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/68_user_col_privs.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_COL_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/68_user_col_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_col_privs" class="registered_link"></div>
+
+The `USER_COL_PRIVS` view provides a listing of the object privileges granted on a column for which a current user is either an object owner, grantor, or grantee.
+
+| Name          | Type                     | Description                                                                                                                                                                                                                                                         |
+| ------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantee`     | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `owner`       | `CHARACTER VARYING(128)` | Object owner.                                                                                                                                                                                                                                                       |
+| `schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`  | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `column_name` | `CHARACTER VARYING(128)` | Column name.                                                                                                                                                                                                                                                        |
+| `grantor`     | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `privilege`   | `CHARACTER VARYING(40)`  | Privilege on the column.                                                                                                                                                                                                                                            |
+| `grantable`   | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the `GRANTEE` (recipient of the privilege) can grant the privilege to others. The value can be `YES` if the grantee has the administrator privileges. |
+| `common`      | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
+| `inherited`   | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/69_user_db_links.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/69_user_db_links.mdx
new file mode 100644
index 00000000000..429cc23c6c5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/69_user_db_links.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_DB_LINKS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.167.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.279.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.225.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/69_user_db_links/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_db_links" class="registered_link"></div>
+
+The `USER_DB_LINKS` view provides information about all database links that are owned by the current user.
+
+| Name       | Type                | Description                                                     |
+| ---------- | ------------------- | --------------------------------------------------------------- |
+| `db_link`  | `TEXT`              | Name of the database link.                                  |
+| `type`     | `CHARACTER VARYING` | Type of remote server. Value is either `REDWOOD` or `EDB`.      |
+| `username` | `TEXT`              | User name of the user logging in.                               |
+| `password` | `TEXT`              | Password used to authenticate on the remote server.             |
+| `host`     | `TEXT`              | Name or IP address of the remote server.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/70_user_dependencies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/70_user_dependencies.mdx
new file mode 100644
index 00000000000..e10f23c58bf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/70_user_dependencies.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_DEPENDENCIES"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/70_user_dependencies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_dependencies" class="registered_link"></div>
+
+The `USER_DEPENDENCIES` view provides information about dependencies between objects owned by a current user, with the exception of synonyms.
+
+| Name                     | Type                     | Description                                                |
+| ------------------------ | ------------------------ | ---------------------------------------------------------- |
+| `schema_name`            | `CHARACTER VARYING(128)` | Name of the schema in which the dependent object resides.  |
+| `name`                   | `CHARACTER VARYING(128)` | Name of the dependent object.                              |
+| `type`                   | `CHARACTER VARYING(18)`  | Type of the dependent object.                              |
+| `referenced_owner`       | `CHARACTER VARYING(128)` | Owner of the referenced object.                            |
+| `referenced_schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the referenced object resides. |
+| `referenced_name`        | `CHARACTER VARYING(128)` | Name of the referenced object.                             |
+| `referenced_type`        | `CHARACTER VARYING(18)`  | Type of the referenced object.                             |
+| `referenced_link_name`   | `CHARACTER VARYING(128)` | Included only for compatibility. Always `NULL`.            |
+| `schemaid`               | `NUMERIC`                | ID of the current schema.                                  |
+| `dependency_type`        | `CHARACTER VARYING(4)`   | Included only for compatibility. Always set to `HARD`.     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/71_user_indexes.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/71_user_indexes.mdx
new file mode 100644
index 00000000000..1e5907516a0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/71_user_indexes.mdx
@@ -0,0 +1,34 @@
+---
+title: "USER_INDEXES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.169.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.281.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.227.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/71_user_indexes/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_indexes" class="registered_link"></div>
+
+The `USER_INDEXES` view provides information about all indexes on tables that are owned by the current user.
+
+| Name              | Type                    | Description                                                                             |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------- |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the index belongs.                                          |
+| `index_name`      | `TEXT`                  | Name of the index.                                                                  |
+| `index_type`      | `TEXT`                  | Included only for compatibility. The index type is always `BTREE`.                      |
+| `table_owner`     | `TEXT`                  | User name of the owner of the indexed table.                                            |
+| `table_name`      | `TEXT`                  | Name of the indexed table.                                                          |
+| `table_type`      | `TEXT`                  | Included only for compatibility. Always set to `TABLE`.                                 |
+| `uniqueness`      | `TEXT`                  | Indicates if the index is `UNIQUE` or `NONUNIQUE`.                                      |
+| `compression`     | `CHARACTER(1)`          | Included only for compatibility. Always set to `N` (not compressed).                    |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides if other than the default tablespace. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan the index.                                       |
+| `logging`         | `TEXT`                  | Included only for compatibility. Always set to `LOGGING`.                               |
+| `status`          | `TEXT`                  | Whether or not the state of the object is valid. (`VALID` or `INVALID`).                |
+| `partitioned`     | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                    |
+| `temporary`       | `CHARACTER(1)`          | Included only for compatibility. Always set to `N`.                                     |
+| `secondary`       | `CHARACTER(1)`          | Included only for compatibility. Always set to `N`.                                     |
+| `join_index`      | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                    |
+| `dropped`         | `CHARACTER(3)`          | Included only for compatibility. Always set to `NO`.                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx
new file mode 100644
index 00000000000..f4e6c7d14cd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/72_user_jobs.mdx
@@ -0,0 +1,36 @@
+---
+title: "USER_JOBS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.170.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.282.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.228.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/72_user_jobs/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/72_user_jobs/
+---
+
+<div id="user_jobs" class="registered_link"></div>
+
+The `USER_JOBS` view provides information about all jobs owned by the current user.
+
+| Name          | Type                       | Description                                                                                   |
+| ------------- | -------------------------- | --------------------------------------------------------------------------------------------- |
+| `job`         | `INTEGER`                  | Identifier of the job (Job ID).                                                           |
+| `log_user`    | `TEXT`                     | Name of the user that submitted the job.                                                  |
+| `priv_user`   | `TEXT`                     | Same as `log_user`. Included only for compatibility.                                          |
+| `schema_user` | `TEXT`                     | Name of the schema used to parse the job.                                                 |
+| `last_date`   | `TIMESTAMP WITH TIME ZONE` | Last date that this job executed successfully.                                            |
+| `last_sec`    | `TEXT`                     | Same as `last_date`.                                                                          |
+| `this_date`   | `TIMESTAMP WITH TIME ZONE` | Date that the job began executing.                                                        |
+| `this_sec`    | `TEXT`                     | Same as `this_date`.                                                                          |
+| `next_date`   | `TIMESTAMP WITH TIME ZONE` | Next date that this job will execute.                                                     |
+| `next_sec`    | `TEXT`                     | Same as `next_date`.                                                                          |
+| `total_time`  | `INTERVAL`                 | Execution time of this job (in seconds).                                                  |
+| `broken`      | `TEXT`                     | If `Y`, no attempt is made to run this job. If `N`, this job attempts to execute.             |
+| `interval`    | `TEXT`                     | Determines how often the job repeats.                                                         |
+| `failures`    | `BIGINT`                   | Number of times that the job has failed to complete since it’s last successful execution. |
+| `what`        | `TEXT`                     | Job definition (PL/SQL code block) that runs when the job executes.                       |
+| `nls_env`     | `CHARACTER VARYING(4000)`  | Always `NULL`. Provided only for compatibility.                                               |
+| `misc_env`    | `BYTEA`                    | Always `NULL`. Provided only for compatibility.                                               |
+| `instance`    | `NUMERIC`                  | Always `0`. Provided only for compatibility.                                                  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/73_user_objects.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/73_user_objects.mdx
new file mode 100644
index 00000000000..451c4caaa17
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/73_user_objects.mdx
@@ -0,0 +1,24 @@
+---
+title: "USER_OBJECTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.171.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.283.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.229.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/73_user_objects/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_objects" class="registered_link"></div>
+
+The `USER_OBJECTS` view provides information about all objects that are owned by the current user.
+
+| Name            | Type                | Description                                                                                                                                                    |
+| --------------- | ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`   | `TEXT`              | Name of the schema in which the object belongs.                                                                                                                |
+| `object_name`   | `TEXT`              | Name of the object.                                                                                                                                            |
+| `object_type`   | `TEXT`              | Type of the object. Possible values are: `INDEX`, `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, `SEQUENCE`, `SYNONYM`, `TABLE`, `TRIGGER`, and `VIEW`.   |
+| `created`       | `DATE`              | Timestamp for the creation of an object.                                                                                                                       |
+| `last_ddl_time` | `DATE`              | Timestamp for the last modification of an object resulting from a DDL statement including grants and revokes.                                                  |
+| `status`        | `CHARACTER VARYING` | Included only for compatibility. Always set to `VALID`.                                                                                                        |
+| `temporary`     | `TEXT`              | `Y` if the object is temporary; `N` if the object isn't temporary.                                                                                            |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/74_user_part_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/74_user_part_tables.mdx
new file mode 100644
index 00000000000..997349a115d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/74_user_part_tables.mdx
@@ -0,0 +1,42 @@
+---
+title: "USER_PART_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.173.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.285.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.231.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/74_user_part_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_part_tables" class="registered_link"></div>
+
+The `USER_PART_TABLES` view provides information about all of the partitioned tables in the database that are owned by the current user.
+
+| Name                        | Type                      | Description                                                  |
+| --------------------------- | ------------------------- | ------------------------------------------------------------ |
+| `schema_name`               | `TEXT`                    | Name of the schema in which the table resides.           |
+| `table_name`                | `TEXT`                    | Name of the table.                                       |
+| `partitioning_type`         | `TEXT`                    | Partitioning type used to define table partitions.       |
+| `subpartitioning_type`      | `TEXT`                    | Subpartitioning type used to define table subpartitions. |
+| `partition_count`           | `BIGINT`                  | Number of partitions in the table.                       |
+| `def_subpartition_count`    | `INTEGER`                 | Number of subpartitions in the table.                    |
+| `partitioning_key_count`    | `INTEGER`                 | Number of partitioning keys specified.                   |
+| `subpartitioning_key_count` | `INTEGER`                 | Number of subpartitioning keys specified.                |
+| `status`                    | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `VALID`.             |
+| `def_tablespace_name`       | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_free`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_used`              | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_ini_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_max_trans`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_initial_extent`        | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_min_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_max_extents`           | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_pct_increase`          | `CHARACTER VARYING(40)`   | Provided only for compatibility. Always `NULL`.              |
+| `def_freelists`             | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_freelist_groups`       | `NUMERIC`                 | Provided only for compatibility. Always `NULL`.              |
+| `def_logging`               | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `YES`.               |
+| `def_compression`           | `CHARACTER VARYING(8)`    | Provided only for compatibility. Always `NONE`.              |
+| `def_buffer_pool`           | `CHARACTER VARYING(7)`    | Provided only for compatibility. Always `DEFAULT`.           |
+| `ref_ptn_constraint_name`   | `CHARACTER VARYING(30)`   | Provided only for compatibility. Always `NULL`.              |
+| `interval`                  | `CHARACTER VARYING(1000)` | Provided only for compatibility. Always `NULL`.              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/75_user_policies.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/75_user_policies.mdx
new file mode 100644
index 00000000000..0c86de4be39
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/75_user_policies.mdx
@@ -0,0 +1,34 @@
+---
+title: "USER_POLICIES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.174.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.286.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.232.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/75_user_policies/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_policies" class="registered_link"></div>
+
+The `USER_POLICIES` view provides information on policies where the schema containing the object on which the policy applies has the same name as the current session user. This view is accessible only to superusers.
+
+| Name             | Type   | Description                                                                                                                |
+| ---------------- | ------ | -------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`    | `TEXT` | Name of the schema in which the object resides.                                                                        |
+| `object_name`    | `TEXT` | Name of the object on which the policy applies.                                                                            |
+| `policy_group`   | `TEXT` | Name of the policy group. Included only for compatibility. Always set to an empty string.                                  |
+| `policy_name`    | `TEXT` | Name of the policy.                                                                                                        |
+| `pf_owner`       | `TEXT` | Name of the schema containing the policy function or the schema containing the package that contains the policy function. |
+| `package`        | `TEXT` | Name of the package containing the policy function if the function belongs to a package.                                 |
+| `function`       | `TEXT` | Name of the policy function.                                                                                               |
+| `sel`            | `TEXT` | Whether or not the policy applies to `SELECT` commands. Possible values are `YES` or `NO`.                                 |
+| `ins`            | `TEXT` | Whether or not the policy applies to `INSERT` commands. Possible values are `YES` or `NO`.                                 |
+| `upd`            | `TEXT` | Whether or not the policy applies to `UPDATE` commands. Possible values are `YES` or `NO`.                                 |
+| `del`            | `TEXT` | Whether or not the policy applies to `DELETE` commands. Possible values are `YES` or `NO`.                                 |
+| `idx`            | `TEXT` | Whether or not the policy applies to index maintenance. Possible values are `YES` or `NO`.                                 |
+| `chk_option`     | `TEXT` | Whether or not the check option is in force for `INSERT` and `UPDATE` commands. Possible values are `YES` or `NO`.         |
+| `enable`         | `TEXT` | Whether or not the policy is enabled on the object. Possible values are `YES` or `NO`.                                     |
+| `static_policy`  | `TEXT` | Whether or not the policy is static. Included only for compatibility. Always set to `NO`.                                  |
+| `policy_type`    | `TEXT` | Policy type. Included only for compatibility. Always set to `UNKNOWN`.                                                     |
+| `long_predicate` | `TEXT` | Included only for compatibility. Always set to `YES`.                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/76_user_queues.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/76_user_queues.mdx
new file mode 100644
index 00000000000..6952a75a77e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/76_user_queues.mdx
@@ -0,0 +1,27 @@
+---
+title: "USER_QUEUES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.175.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/76_user_queues/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_queues" class="registered_link"></div>
+
+The `USER_QUEUES` view provides information about any queue on which the current user has usage privileges.
+
+| Name              | Type                | Description                                                                          |
+| ----------------- | ------------------- | ------------------------------------------------------------------------------------ |
+| `name`            | `TEXT`              | Name of the queue.                                                               |
+| `queue_table`     | `TEXT`              | Name of the queue table in which the queue resides.                              |
+| `qid`             | `OID`               | The system-assigned object ID of the queue.                                          |
+| `queue_type`      | `CHARACTER VARYING` | The queue type. Can be `EXCEPTION_QUEUE`, `NON_PERSISTENT_QUEUE`, or `NORMAL_QUEUE`. |
+| `max_retries`     | `NUMERIC`           | The maximum number of dequeue attempts.                                              |
+| `retrydelay`      | `NUMERIC`           | The maximum time allowed between retries.                                            |
+| `enqueue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows enqueuing, `NO` if the queue does not.                     |
+| `dequeue_enabled` | `CHARACTER VARYING` | `YES` if the queue allows dequeuing, `NO` if the queue does not.                     |
+| `retention`       | `CHARACTER VARYING` | Number of seconds that a processed message is retained in the queue.             |
+| `user_comment`    | `CHARACTER VARYING` | A user-specified comment.                                                            |
+| `network_name`    | `CHARACTER VARYING` | Name of the network on which the queue resides.                                  |
+| `sharded`         | `CHARACTER VARYING` | `YES` if the queue resides on a sharded network, `NO` if the queue does not.         |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/77_user_queue_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/77_user_queue_tables.mdx
new file mode 100644
index 00000000000..853ed3c13ed
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/77_user_queue_tables.mdx
@@ -0,0 +1,27 @@
+---
+title: "USER_QUEUE_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.176.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/77_user_queue_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_queue_tables" class="registered_link"></div>
+
+The `USER_QUEUE_TABLES` view provides information about all of the queue tables the current user can access.
+
+| Name                 | Type                | Description                                                                                  |
+| -------------------- | ------------------- | -------------------------------------------------------------------------------------------- |
+| `queue_table`        | `TEXT`              | User-specified name of the queue table.                                                  |
+| `type`               | `CHARACTER VARYING` | Type of data stored in the queue table.                                                  |
+| `object_type`        | `TEXT`              | User-defined payload type.                                                               |
+| `sort_order`         | `CHARACTER VARYING` | Order in which the queue table is sorted.                                                |
+| `recipients`         | `CHARACTER VARYING` | Always `SINGLE`.                                                                             |
+| `message_grouping`   | `CHARACTER VARYING` | Always `NONE`.                                                                               |
+| `compatible`         | `CHARACTER VARYING` | Release number of the EDB Postgres Advanced Server release with which this queue table is compatible. |
+| `primary_instance`   | `NUMERIC`           | Always `0`.                                                                                  |
+| `secondary_instance` | `NUMERIC`           | Always `0`.                                                                                  |
+| `owner_instance`     | `NUMERIC`           | Instance number of the instance that owns the queue table.                               |
+| `user_comment`       | `CHARACTER VARYING` | User comment provided when the table was created.                                        |
+| `secure`             | `CHARACTER VARYING` | `YES` indicates that the queue table is secure. `NO` indicates that it is not.               |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/78_user_role_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/78_user_role_privs.mdx
new file mode 100644
index 00000000000..8e00af1ad0f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/78_user_role_privs.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_ROLE_PRIVS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.177.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.287.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.233.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/78_user_role_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_role_privs" class="registered_link"></div>
+
+The `USER_ROLE_PRIVS` view provides information about the privileges that were granted to the current user. A row is created for each role to which a user has been granted.
+
+| Name           | Type                   | Description                                                          |
+| -------------- | ---------------------- | -------------------------------------------------------------------- |
+| `username`     | `TEXT`                 | Name of the user to which the role was granted.                  |
+| `granted_role` | `TEXT`                 | Name of the role granted to the grantee.                             |
+| `admin_option` | `TEXT`                 | `YES` if the role was granted with the admin option, `NO` otherwise. |
+| `default_role` | `TEXT`                 | `YES` if the role is enabled when the grantee creates a session.     |
+| `os_granted`   | `CHARACTER VARYING(3)` | Included only for compatibility. Always `NO`.                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/79_user_sequences.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/79_user_sequences.mdx
new file mode 100644
index 00000000000..0e4906da0df
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/79_user_sequences.mdx
@@ -0,0 +1,26 @@
+---
+title: "USER_SEQUENCES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.178.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.288.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.234.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/79_user_sequences/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_sequences" class="registered_link"></div>
+
+The `USER_SEQUENCES` view provides information about all user-defined sequences that belong to the current user.
+
+| Name            | Type                | Description                                                                       |
+| --------------- | ------------------- | --------------------------------------------------------------------------------- |
+| `schema_name`   | `TEXT`              | Name of the schema in which the sequence resides.                             |
+| `sequence_name` | `TEXT`              | Name of the sequence.                                                             |
+| `min_value`     | `NUMERIC`           | Lowest value for the server to assign to the sequence.                        |
+| `max_value`     | `NUMERIC`           | Highest value for the server to assign to the sequence.                       |
+| `increment_by`  | `NUMERIC`           | Value added to the current sequence number to create the next sequent number. |
+| `cycle_flag`    | `CHARACTER VARYING` | Specifies whether the sequence wraps when it reaches `min_value` or `max_value`. |
+| `order_flag`    | `CHARACTER VARYING` | Included only for compatibility. Always `Y`.                                      |
+| `cache_size`    | `NUMERIC`           | Number of preallocated sequence numbers in memory.                           |
+| `last_number`   | `NUMERIC`           | The value of the last sequence number saved to disk.                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/80_user_source.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/80_user_source.mdx
new file mode 100644
index 00000000000..f238b876b3e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/80_user_source.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_SOURCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.179.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.289.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.235.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/80_user_source/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_source" class="registered_link"></div>
+
+The `USER_SOURCE` view provides information about all programs owned by the current user.
+
+| Name          | Type      | Description                                                                                              |
+| ------------- | --------- | -------------------------------------------------------------------------------------------------------- |
+| `schema_name` | `TEXT`    | Name of the schema in which the program belongs.                                                         |
+| `name`        | `TEXT`    | Name of the program.                                                                                     |
+| `type`        | `TEXT`    | Type of program. Possible values are: `FUNCTION`, `PACKAGE`, `PACKAGE BODY`, `PROCEDURE`, and `TRIGGER`. |
+| `line`        | `INTEGER` | Source code line number relative to a given program.                                                     |
+| `text`        | `TEXT`    | Line of source code text.                                                                                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/81_user_subpart_key_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/81_user_subpart_key_columns.mdx
new file mode 100644
index 00000000000..8f5c027b909
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/81_user_subpart_key_columns.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_SUBPART_KEY_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.180.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.290.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.236.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/81_user_subpart_key_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_subpart_key_columns" class="registered_link"></div>
+
+The `USER_SUBPART_KEY_COLUMNS` view provides information about the key columns of partitioned tables that are subpartitioned that belong to the current user.
+
+| Name              | Type           | Description                                               |
+| ----------------- | -------------- | --------------------------------------------------------- |
+| `schema_name`     | `TEXT`         | Name of the schema in which the table resides.        |
+| `name`            | `TEXT`         | Name of the table in which the column resides.        |
+| `object_type`     | `CHARACTER(5)` | For compatibility only. Always `TABLE`.                   |
+| `column_name`     | `TEXT`         | Name of the column on which the key is defined.       |
+| `column_position` | `INTEGER`      | `1` for the first column, `2` for the second column, and so on. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx
new file mode 100644
index 00000000000..a2ee6eb3e6a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms.mdx
@@ -0,0 +1,24 @@
+---
+title: "USER_SYNONYMS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.181.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.291.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.237.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/82_user_synonyms/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/82_user_synonyms/
+---
+
+<div id="user_synonyms" class="registered_link"></div>
+
+The `USER_SYNONYMS` view provides information about all synonyms owned by the current user.
+
+| Name                | Type   | Description                                                     |
+| ------------------- | ------ | --------------------------------------------------------------- |
+| `schema_name`       | `TEXT` | Name of the schema in which the synonym resides.            |
+| `synonym_name`      | `TEXT` | Name of the synonym.                                            |
+| `table_owner`       | `TEXT` | User name of the owner of the table on which the synonym is defined. |
+| `table_schema_name` | `TEXT` | Name of the schema in which the table resides.              |
+| `table_name`        | `TEXT` | Name of the table on which the synonym is defined.              |
+| `db_link`           | `TEXT` | Name of any associated database link.                           |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/83_user_tab_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/83_user_tab_columns.mdx
new file mode 100644
index 00000000000..da40bb8eb02
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/83_user_tab_columns.mdx
@@ -0,0 +1,27 @@
+---
+title: "USER_TAB_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.182.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.292.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.238.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/83_user_tab_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_tab_columns" class="registered_link"></div>
+
+The `USER_TAB_COLUMNS` view displays information about all columns in tables and views owned by the current user.
+
+| Name             | Type                | Description                                                                                                              |
+| ---------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the table or view resides.                                                                   |
+| `table_name`     | `CHARACTER VARYING` | Name of the table or view in which the column resides.                                                                   |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                      |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                 |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                  |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                       |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                               |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the table.                                                                        |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx
new file mode 100644
index 00000000000..368dff07edf
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions.mdx
@@ -0,0 +1,52 @@
+---
+title: "USER_TAB_PARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.183.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.293.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.239.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/84_user_tab_partitions/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_cat_views/84_user_tab_partitions/
+---
+
+<div id="user_tab_partitions" class="registered_link"></div>
+
+The `USER_TAB_PARTITIONS` view provides information about all of the partitions that are owned by the current user.
+
+| Name                 | Type                          | Description                                                                                                                               |
+| -------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`        | `TEXT`                        | Name of the schema in which the table resides.                                                                                        |
+| `table_name`         | `TEXT`                        | Name of the table.                                                                                                                    |
+| `composite`          | `TEXT`                        | `YES` if the table is subpartitioned, `NO` if the table isn't subpartitioned.                                                            |
+| `partition_name`     | `TEXT`                        | Name of the partition.                                                                                                                |
+| `subpartition_count` | `BIGINT`                      | Number of subpartitions in the partition.                                                                                             |
+| `high_value`         | `TEXT`                        | High-partitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`  | `INTEGER`                     | Length of high-partitioning value.                                                                                                    |
+| `partition_position` | `INTEGER`                     | The ordinal position of this partition.                                                                                                   |
+| `tablespace_name`    | `TEXT`                        | Name of the tablespace in which the partition resides. If the tablespace name isn't specified, then default tablespace is `PG_DEFAULT`. |
+| `pct_free`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_used`           | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `ini_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_trans`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `initial_extent`     | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `next_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `min_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `max_extent`         | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `pct_increase`       | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                              |
+| `freelists`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `freelist_groups`    | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `logging`            | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `compression`        | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                           |
+| `num_rows`           | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                             |
+| `blocks`             | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                              |
+| `empty_blocks`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_space`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `chain_cnt`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `avg_row_len`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `sample_size`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                           |
+| `last_analyzed`      | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                           |
+| `buffer_pool`        | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                           |
+| `global_stats`       | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                            |
+| `user_stats`         | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                             |
+| `backing_table`      | `REGCLASS`                    | Name of the partition backing table.                                                                                                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/85_user_tab_subpartitions.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/85_user_tab_subpartitions.mdx
new file mode 100644
index 00000000000..7b7d01a71c4
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/85_user_tab_subpartitions.mdx
@@ -0,0 +1,50 @@
+---
+title: "USER_TAB_SUBPARTITIONS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.184.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.294.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.240.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/85_user_tab_subpartitions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_tab_subpartitions" class="registered_link"></div>
+
+The `USER_TAB_SUBPARTITIONS` view provides information about all of the subpartitions owned by the current user.
+
+| Name                    | Type                          | Description                                                                                                                                  |
+| ----------------------- | ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`           | `TEXT`                        | Name of the schema in which the table resides.                                                                                           |
+| `table_name`            | `TEXT`                        | Name of the table.                                                                                                                       |
+| `partition_name`        | `TEXT`                        | Name of the partition.                                                                                                                   |
+| `subpartition_name`     | `TEXT`                        | Name of the subpartition.                                                                                                                |
+| `high_value`            | `TEXT`                        | High-subpartitioning value specified in the `CREATE TABLE` statement.                                                                    |
+| `high_value_length`     | `INTEGER`                     | Length of high-partitioning value.                                                                                                       |
+| `subpartition_position` | `INTEGER`                     | Ordinal position of this subpartition.                                                                                                   |
+| `tablespace_name`       | `TEXT`                        | Name of the tablespace in which the subpartition resides. If the tablespace name is not specified, then default tablespace `PG_DEFAULT`. |
+| `pct_free`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_used`              | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `ini_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_trans`             | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `initial_extent`        | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `next_extent`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `min_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `max_extent`            | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `pct_increase`          | `NUMERIC`                     | Included only for compatibility. Always `0`.                                                                                                 |
+| `freelists`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `freelist_groups`       | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `logging`               | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `compression`           | `CHARACTER VARYING(8)`        | Included only for compatibility. Always `NONE`.                                                                                              |
+| `num_rows`              | `NUMERIC`                     | Same as `pg_class.reltuples`.                                                                                                                |
+| `blocks`                | `INTEGER`                     | Same as `pg_class.relpages`.                                                                                                                 |
+| `empty_blocks`          | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_space`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `chain_cnt`             | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `avg_row_len`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `sample_size`           | `NUMERIC`                     | Included only for compatibility. Always `NULL`.                                                                                              |
+| `last_analyzed`         | `TIMESTAMP WITHOUT TIME ZONE` | Included only for compatibility. Always `NULL`.                                                                                              |
+| `buffer_pool`           | `CHARACTER VARYING(7)`        | Included only for compatibility. Always `NULL`.                                                                                              |
+| `global_stats`          | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `YES`.                                                                                               |
+| `user_stats`            | `CHARACTER VARYING(3)`        | Included only for compatibility. Always `NO`.                                                                                                |
+| `backing_table`         | `REGCLASS`                    | Name of the partition backing table.                                                                                                         |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/86_user_tab_privs.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/86_user_tab_privs.mdx
new file mode 100644
index 00000000000..1651feb8580
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/86_user_tab_privs.mdx
@@ -0,0 +1,23 @@
+---
+title: "USER_TAB_PRIVS"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/86_user_tab_privs/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_tab_privs" class="registered_link"></div>
+
+The `USER_TAB_PRIVS` view provides a listing of the object privileges for which a current user is either an object owner, grantor, or grantee.
+
+| Name          | Type                     | Description                                                                                                                                                                                                                                                         |
+| ------------- | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `grantee`     | `CHARACTER VARYING(128)` | Name of the user with the privilege.                                                                                                                                                                                                                                |
+| `owner`       | `CHARACTER VARYING(128)` | Object owner.                                                                                                                                                                                                                                                       |
+| `schema_name` | `CHARACTER VARYING(128)` | Name of the schema in which the object resides.                                                                                                                                                                                                                     |
+| `table_name`  | `CHARACTER VARYING(128)` | Object name.                                                                                                                                                                                                                                                        |
+| `grantor`     | `CHARACTER VARYING(128)` | Name of the user who granted the privilege.                                                                                                                                                                                                                         |
+| `privilege`   | `CHARACTER VARYING(40)`  | Privilege name.                                                                                                                                                                                                                                                     |
+| `grantable`   | `CHARACTER VARYING(3)`   | Indicates whether the privilege was granted with the grant option `YES` or `NO`. `YES` indicates that the grantee (recipient of the privilege) can grant the privilege to others. The value can be `YES` if the grantee has administrator privileges. |
+| `hierarchy`   | `CHARACTER VARYING(3)`   | The value can be `YES` or `NO`. The value can be `YES` if the privilege is `SELECT`. Otherwise the value is `NO`.                                                                                                                                                                      |
+| `common`      | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
+| `type`        | `CHARACTER VARYING(24)`  | Type of object.                                                                                                                                                                                                                                                     |
+| `inherited`   | `CHARACTER VARYING(3)`   | Included only for compatibility. Always `NO`.                                                                                                                                                                                                                       |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/87_user_tables.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/87_user_tables.mdx
new file mode 100644
index 00000000000..a69c13c3ad0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/87_user_tables.mdx
@@ -0,0 +1,23 @@
+---
+title: "USER_TABLES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.185.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.295.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.241.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/87_user_tables/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_tables" class="registered_link"></div>
+
+The `USER_TABLES` view displays information about all tables owned by the current user.
+
+| Name              | Type                    | Description                                                                                                                       |
+| ----------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------- |
+| `schema_name`     | `TEXT`                  | Name of the schema in which the table belongs.                                                                                    |
+| `table_name`      | `TEXT`                  | Name of the table.                                                                                                                |
+| `tablespace_name` | `TEXT`                  | Name of the tablespace in which the table resides. If the tablespace name isn't specified, the default tablespace is `PG_DEFAULT`. |
+| `degree`          | `CHARACTER VARYING(10)` | Number of threads per instance to scan a table, or `DEFAULT`.                                                                     |
+| `status`          | `CHARACTER VARYING(5)`  | Included only for compatibility. Always set to `VALID`.                                                                           |
+| `temporary`       | `CHARACTER(1)`          | `Y` if the table is temporary, `N` if the table isn't temporary.                                                                 |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/88_user_triggers.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/88_user_triggers.mdx
new file mode 100644
index 00000000000..66eee33a4be
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/88_user_triggers.mdx
@@ -0,0 +1,29 @@
+---
+title: "USER_TRIGGERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.186.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.296.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.242.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/88_user_triggers/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_triggers" class="registered_link"></div>
+
+The `USER_TRIGGERS` view displays information about all triggers on tables owned by the current user.
+
+| Name                | Type   | Description                                                                                                    |
+| ------------------- | ------ | -------------------------------------------------------------------------------------------------------------- |
+| `schema_name`       | `TEXT` | Name of the schema in which the trigger resides.                                                           |
+| `trigger_name`      | `TEXT` | Name of the trigger.                                                                                       |
+| `trigger_type`      | `TEXT` | The type of the trigger. Possible values are: `BEFORE ROW`, `BEFORE STATEMENT`, `AFTER ROW`, `AFTER STATEMENT`. |
+| `triggering_event`  | `TEXT` | The event that fires the trigger.                                                                              |
+| `table_owner`       | `TEXT` | The user name of the owner of the table on which the trigger is defined.                                       |
+| `base_object_type`  | `TEXT` | Included only for compatibility. Value is always  `TABLE`.                                                     |
+| `table_name`        | `TEXT` | Name of the table on which the trigger is defined.                                                         |
+| `referencing_names` | `TEXT` | Included only for compatibility. Value is always `REFERENCING NEW AS NEW OLD AS OLD`.                             |
+| `status`            | `TEXT` | Status indicates if the trigger is enabled (`VALID`) or disabled (`NOTVALID`).                                 |
+| `description`       | `TEXT` | Included only for compatibility.                                                                               |
+| `trigger_body`      | `TEXT` | The body of the trigger.                                                                                       |
+| `action_statement`  | `TEXT` | The SQL command that executes when the trigger fires.                                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/89_user_types.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/89_user_types.mdx
new file mode 100644
index 00000000000..24804388ec2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/89_user_types.mdx
@@ -0,0 +1,22 @@
+---
+title: "USER_TYPES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.187.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.297.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.243.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/89_user_types/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_types" class="registered_link"></div>
+
+The `USER_TYPES` view provides information about all object types owned by the current user.
+
+| Name          | Type      | Description                                                                    |
+| ------------- | --------- | ------------------------------------------------------------------------------ |
+| `schema_name` | `TEXT`    | Name of the schema in which the type is defined.                           |
+| `type_name`   | `TEXT`    | Name of the type.                                                          |
+| `type_oid`    | `OID`     | The object identifier (OID) of the type.                                       |
+| `typecode`    | `TEXT`    | The typecode of the type. Possible values are: `OBJECT`, `COLLECTION`, `OTHER`. |
+| `attributes`  | `INTEGER` | Number of attributes in the type.                                          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/90_user_users.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/90_user_users.mdx
new file mode 100644
index 00000000000..20c7abfc90e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/90_user_users.mdx
@@ -0,0 +1,28 @@
+---
+title: "USER_USERS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.188.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.298.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.244.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/90_user_users/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_users" class="registered_link"></div>
+
+The `USER_USERS` view provides information about the current user.
+
+| Name                          | Type                          | Description                                                                                                                                                                                                                                                                                                                   |
+| ----------------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `username`                    | `TEXT`                        | User name of the user.                                                                                                                                                                                                                                                                                                        |
+| `user_id`                     | `OID`                         | ID number of the user.                                                                                                                                                                                                                                                                                                        |
+| `account_status`              | `CHARACTER VARYING(32)`       | The current status of the account. Possible values are: `OPEN`, `EXPIRED`, `EXPIRED(GRACE)`, `EXPIRED & LOCKED`, `EXPIRED & LOCKED(TIMED)`, `EXPIRED(GRACE) & LOCKED`, `EXPIRED(GRACE) & LOCKED(TIMED)`, `LOCKED`, `LOCKED(TIMED)`. Use the `edb_get_role_status(role_id)` function to get the current status of the account. |
+| `lock_date`                   | `TIMESTAMP WITHOUT TIME ZONE` | If the account status is `LOCKED`, `lock_date` displays the date and time the account was locked.                                                                                                                                                                                                                             |
+| `expiry_date`                 | `TIMESTAMP WITHOUT TIME ZONE` | The expiration date of the account.                                                                                                                                                                                                                                                                                           |
+| `default_tablespace`          | `TEXT`                        | The default tablespace associated with the account.                                                                                                                                                                                                                                                                           |
+| `temporary_tablespace`        | `CHARACTER VARYING(30)`       | Included only for compatibility. The value is always '' (an empty string).                                                                                                                                                                                                                                                    |
+| `created`                     | `DATE`                        | Timestamp for the creation of an object.                                                                                                                                                                                                                                                                                      |
+| `last_ddl_time`               | `DATE`                        | Timestamp for the last modification of an object resulting from a DDL statement including grants and revokes.                                                                                                                                                                                                                 |
+| `initial_rsrc_consumer_group` | `CHARACTER VARYING(30)`       | Included only for compatibility. The value is always `NULL`.                                                                                                                                                                                                                                                                  |
+| `external_name`               | `CHARACTER VARYING(4000)`     | Included only for compatibility. Always set to `NULL`.                                                                                                                                                                                                                                                                        |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/91_user_view_columns.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/91_user_view_columns.mdx
new file mode 100644
index 00000000000..4e616341d45
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/91_user_view_columns.mdx
@@ -0,0 +1,27 @@
+---
+title: "USER_VIEW_COLUMNS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.189.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.299.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.245.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/91_user_view_columns/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_view_columns" class="registered_link"></div>
+
+The `USER_VIEW_COLUMNS` view provides information about all columns in views owned by the current user.
+
+| Name             | Type                | Description                                                                                                              |
+| ---------------- | ------------------- | ------------------------------------------------------------------------------------------------------------------------ |
+| `schema_name`    | `CHARACTER VARYING` | Name of the schema in which the view belongs.                                                                            |
+| `view_name`      | `CHARACTER VARYING` | Name of the view.                                                                                                        |
+| `column_name`    | `CHARACTER VARYING` | Name of the column.                                                                                                      |
+| `data_type`      | `CHARACTER VARYING` | Data type of the column.                                                                                                 |
+| `data_length`    | `NUMERIC`           | Length of text columns.                                                                                                  |
+| `data_precision` | `NUMERIC`           | Precision (number of digits) for `NUMBER` columns.                                                                       |
+| `data_scale`     | `NUMERIC`           | Scale of `NUMBER` columns.                                                                                               |
+| `nullable`       | `CHARACTER(1)`      | Whether or not the column is nullable. Possible values are: `Y` – column is nullable; `N` – column does not allow null. |
+| `column_id`      | `NUMERIC`           | Relative position of the column in the view.                                                                         |
+| `data_default`   | `CHARACTER VARYING` | Default value assigned to the column.                                                                                    |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/92_user_views.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/92_user_views.mdx
new file mode 100644
index 00000000000..81d8d343191
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/92_user_views.mdx
@@ -0,0 +1,20 @@
+---
+title: "USER_VIEWS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.190.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.300.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.246.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/92_user_views/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="user_views" class="registered_link"></div>
+
+The `USER_VIEWS` view provides information about all views owned by the current user.
+
+| Name          | Type   | Description                                   |
+| ------------- | ------ | --------------------------------------------- |
+| `schema_name` | `TEXT` | Name of the schema in which the view resides. |
+| `view_name`   | `TEXT` | Name of the view.                             |
+| `text`        | `TEXT` | The `SELECT` statement that defines the view. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/93_v_version.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/93_v_version.mdx
new file mode 100644
index 00000000000..c0277a9fcf6
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/93_v_version.mdx
@@ -0,0 +1,18 @@
+---
+title: "V$VERSION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.191.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.301.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.247.html"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/93_v_version/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="v_version" class="registered_link"></div>
+
+The `V$VERSION` view provides information about product compatibility.
+
+| Name     | Type   | Description                                 |
+| -------- | ------ | ------------------------------------------- |
+| `banner` | `TEXT` | Displays product compatibility information. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/94_product_component_version.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/94_product_component_version.mdx
new file mode 100644
index 00000000000..1b461ea0a95
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/94_product_component_version.mdx
@@ -0,0 +1,15 @@
+---
+title: "PRODUCT_COMPONENT_VERSION"
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/94_product_component_version/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="product_component_version" class="registered_link"></div>
+
+The `PRODUCT_COMPONENT_VERSION` view provides version information about product version compatibility.
+
+| Name      | Type                    | Description                                     |
+| --------- | ----------------------- | ----------------------------------------------- |
+| `product` | `CHARACTER VARYING(74)` | Name of the product.                            |
+| `version` | `CHARACTER VARYING(74)` | Version number of the product.                  |
+| `status`  | `CHARACTER VARYING(74)` | Included for compatibility. Always `Available`. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/index.mdx
new file mode 100644
index 00000000000..09c8ff5a0fd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/oracle_compatible_views/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Oracle catalog views"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_cat_views/oracle_compatible_views/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../../epas_compat_ora_dev_guide/11_system_catalog_tables/
+---
+
+Oracle catalog views provide information about database objects in a manner compatible with Oracle data dictionary views.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/index.mdx
new file mode 100644
index 00000000000..5db7e33c110
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/index.mdx
@@ -0,0 +1,10 @@
+---
+title: "System catalog views"
+indexCards: simple
+redirects:
+  - /epas/latest/epas_compat_cat_views/pg_views/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+System catalog views are present in PostgreSQL. They might have extra information when accessed in EDB Postgres Advanced Server. The [`PG_USER`](pg_user) view is an example of a system catalog view that provides additional information specific to EDB Postgres Advanced Server.         
+
+For the complete list of the system catalogs, see [System Catalogs](https://www.postgresql.org/docs/current/catalogs.html) in the PostgreSQL documentation. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_attribute.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_attribute.mdx
new file mode 100644
index 00000000000..3f626e66f9c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_attribute.mdx
@@ -0,0 +1,11 @@
+---
+title: "PG_ATTRIBUTE"
+---
+
+The `PG_ATTRIBUTE` view provides information about table columns. There's one `PG_ATTRIBUTE` row for every column in every table in the database. 
+
+In addition to the information in the [PostgreSQL pg_attribute description](https://www.postgresql.org/docs/current/catalog-pg-attribute.html), EDB Postgres Advanced Server provides the following information.
+
+| Name              | Type      | Description                                                                            |
+| ----------------- | --------- | -------------------------------------------------------------------------------------- |
+| attishidden       | Boolean   | Column included in SELECT * expansion                                                  |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_authid.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_authid.mdx
new file mode 100644
index 00000000000..9899416edeb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_authid.mdx
@@ -0,0 +1,16 @@
+---
+title: "PG_AUTHID"
+---
+
+The `PG_AUTHID` view provides information about database authorization identifiers (that is, roles). A role includes users and groups. 
+
+In addition to the information in the [PostgreSQL pg_authid description](https://www.postgresql.org/docs/current/catalog-pg-authid.html), EDB Postgres Advanced Server provides the following information.
+
+| Name                  | Type                     | Description                                                           |
+| --------------------- | ------------------------ | --------------------------------------------------------------------- |
+| rolaccountstatus      | smallint                 | Account status of the role                                            |
+| rolcreatedblink       | Boolean                  | Specifies whether the role is allowed to create databases link        |
+| rolcreatepublicdblink | Boolean                  | Specifies whether the role is allowed to create public databases link |
+| roldroppublicdblink   | Boolean                  | Specifies whether the role is allowed to drop public databases links  |
+| rolpolicyexempt       | Boolean                  | Specifies whether the role is allowed to bypass VPD policies          |
+| rolprofile            | oid                      | Object identifier for the role's profile                              |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_class.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_class.mdx
new file mode 100644
index 00000000000..ecbd8ae4014
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_class.mdx
@@ -0,0 +1,13 @@
+---
+title: "PG_CLASS"
+---
+
+The `PG_CLASS` view provides information about tables and other objects that have columns or are similar to a table in other ways. This information includes indexes, sequences, views, and other objects. In the context of this table, *objects* refers to *relations*.
+
+In addition to the information in the [PostgreSQL pg_class description](https://www.postgresql.org/docs/current/catalog-pg-class.html), EDB Postgres Advanced Server provides the following information.
+
+| Name                  | Type    | Description                                                                                           |
+| --------------------- | ------- | ----------------------------------------------------------------------------------------------------- |
+| relbackingtable       | "char"  | Identifies whether a table is backing relation for any other object. The default value is `d` for a normal object and `q` for queue tables. The relbackingtable is stored as `q` for all the backing objects of QUEUE TABLE (backing table, index, toast table, and so forth). |
+| relhasredactionpolicy | Boolean | Specifies whether object has a redaction policy.  |
+| relpartname           | text    | Partition name. |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_collation.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_collation.mdx
new file mode 100644
index 00000000000..e4027608b34
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_collation.mdx
@@ -0,0 +1,12 @@
+---
+title: "PG_COLLATION"
+---
+
+The `PG_COLLATION` view describes the available collations, which map SQL names to operating system locale categories. 
+
+In addition to the information in the [PostgreSQL pg_collation description](https://www.postgresql.org/docs/current/catalog-pg-collation.html), EDB Postgres Advanced Server provides the following information.
+
+| Name         | Type | Description                        |
+| ------------ | ---- | ---------------------------------- |
+| collicu      | name | An ICU short-form string or empty. An ICU short form is a method of specifying collation attributes. |
+| collicurules | text | ICU collation rules.                |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_database.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_database.mdx
new file mode 100644
index 00000000000..59c7b0465fc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_database.mdx
@@ -0,0 +1,13 @@
+---
+title: "PG_DATABASE"
+---
+
+The `PG_DATABASE` view provides information about the available databases. 
+
+In addition to the information in the [PostgreSQL pg_database description](https://www.postgresql.org/docs/current/catalog-pg-database.html), EDB Postgres Advanced Server provides the following information.
+
+| Name           | Type    | Description                                                                                           |
+| -------------- | ------- | ----------------------------------------------------------------------------------------------------- |
+| datacu         | name    | An ICU short-form string or empty. An ICU short form is a method of specifying collation attributes. |
+| datacurules    | text    | ICU collation rules.                                                                                   |
+| datredwoodlike | Boolean | Disables backslash-escape in LIKE patterns.                                                             |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_namespace.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_namespace.mdx
new file mode 100644
index 00000000000..c426e5dc705
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_namespace.mdx
@@ -0,0 +1,18 @@
+---
+title: "PG_NAMESPACE"
+---
+
+The `PG_NAMESPACE` view describes namespaces, which are the structures underlying SQL schemas. Each namespace can have a separate collection of relations, types, and so forth without name conflicts. 
+
+In addition to the information in the [PostgreSQL pg_namespace description](https://www.postgresql.org/docs/current/catalog-pg-namespace.html), EDB Postgres Advanced Server provides the following information.
+
+| Name               | Type    | Description                                                                         |
+| ------------------ | ------- | ----------------------------------------------------------------------------------- |
+| nspbodysrc         | text    | The object identifier of the parent table                                           |
+| nspcompoundtrigger | Boolean | Specifies whether this a compound trigger's package                                 |
+| nspforeignserver   | oid     | Object identifier of the foreign server where the foreign namespace resides         |
+| nspheadsrc         | text    | Header for the package                                                              |
+| nspobjecttype      | oid     | Object identifier of the type to which this package belongs                         |
+| nspparent          | oid     | Object identifier of the schema (namespace) of the package (0 for a regular schema) |
+| nspremoteschema    | text    | Name of the foreign namespace                                                       |
+| nspsecdef          | Boolean | Specifies whether the namespace (package) is a security definer                     |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_partitioned_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_partitioned_table.mdx
new file mode 100644
index 00000000000..a718502b0fc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_partitioned_table.mdx
@@ -0,0 +1,13 @@
+---
+title: "PG_PARTITIONED_TABLE"
+---
+
+The `PG_PARTITIONED_TABLE` view provides information about how tables are partitioned. 
+
+In addition to the information in the [PostgreSQL pg_partitioned_table description](https://www.postgresql.org/docs/current/catalog-pg-partitioned-table.html), EDB Postgres Advanced Server provides the following information.
+
+| Name                | Type         | Description                                |
+| ------------------- | ------------ | ------------------------------------------ |
+| partdynamicspec     | pg_node_tree | The dynamic partitioning specification     |
+| partnullorder       | smallint     | Null ordering for range-partitioned tables |
+| partsubparttemplate | pg_node_tree | Subpartition number specification          |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_proc.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_proc.mdx
new file mode 100644
index 00000000000..bb770c5fb76
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_proc.mdx
@@ -0,0 +1,15 @@
+---
+title: "PG_PROC"
+---
+
+The `PG_PROC` view provides information about functions, procedures, aggregate functions, and window functions (collectively also known as routines). 
+
+In addition to the information in the [PostgreSQL pg_proc description](https://www.postgresql.org/docs/current/catalog-pg-proc.html), EDB Postgres Advanced Server provides the following information.
+
+| Name                | Type     | Description                                                           |
+| ------------------- | -------- | --------------------------------------------------------------------- |
+| proaccess           | "char"   | Determines PUBLIC/PRIVATE; used only when `pronamespace` is a package |
+| proargdeclaredmodes | "char"[] | Parameter modes; NULL if the same as `proargmodes`                    |
+| prolineno           | integer  | Line number relative to the package body                              |
+| promemberattrs      | text     | Object method attributes, such as final, overriding, or instantiable  |
+| protype             | "char"   | Type of procedure, such as function or procedure                      |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_subscription.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_subscription.mdx
new file mode 100644
index 00000000000..0e9abebef7f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_subscription.mdx
@@ -0,0 +1,12 @@
+---
+title: "PG_SUBSCRIPTION"
+---
+
+The `PG_SUBSCRIPTION` view provides information about all existing logical replication subscriptions. 
+
+In addition to the information in the [PostgreSQL pg_subscription description](https://www.postgresql.org/docs/current/catalog-pg-subscription.html), EDB Postgres Advanced Server provides the following information.
+
+| Name                | Type    | Description                                                 |
+| ------------------- | ------- | ----------------------------------------------------------- |
+| subpasswordrequired | Boolean | Specifies whether the connection requires a password        |
+| subrunasowner       | Boolean | Specifies whether replication runs as the subscription owner |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_synonym.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_synonym.mdx
new file mode 100644
index 00000000000..fe8fd9d8be8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_synonym.mdx
@@ -0,0 +1,15 @@
+---
+title: "PG_SYNONYM"
+---
+
+The `PG_SYNONYM` view defines system synonym relations (pg_synonym) along with the relation's initial contents, if any. PostgreSQL doesn't provide a system catalog for `PG_SYNONYM`.
+
+| Name         | Type | Description                                             |
+| ------------ | ---- | ------------------------------------------------------- |
+| oid          | oid  |                                                          |
+| synlink      | text | Name of the database link or an empty string           |                 
+| synname      | name | Name of the synonym                                     |
+| synnamespace | oid  | Namespace where the synonym resides                     |
+| synobjname   | text | Name of the base object referenced by the synonym       |
+| synobjschema | text | Name of the schema where the base object resides        |
+| synowner     | oid  | Object identifier of the owner (creator) of the synonym |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_trigger.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_trigger.mdx
new file mode 100644
index 00000000000..3d4a93cbb8c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_trigger.mdx
@@ -0,0 +1,12 @@
+---
+title: "PG_TRIGGER"
+---
+
+The `PG_TRIGGER` view provides information about triggers on tables and views. 
+
+In addition to the information in the [PostgreSQL pg_trigger description](https://www.postgresql.org/docs/current/catalog-pg-trigger.html), EDB Postgres Advanced Server provides the following information.
+
+| Name         | Type     | Description                                                                |
+| ------------ | -------- | -------------------------------------------------------------------------- |
+| tgctype      | smallint | Compound trigger events                                                    |
+| tgpackageoid | oid      | Object identifier of the package created implicitly for a compound trigger |
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_type.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_type.mdx
new file mode 100644
index 00000000000..700ec97d2ef
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_type.mdx
@@ -0,0 +1,12 @@
+---
+title: "PG_TYPE"
+---
+
+The `PG_TYPE` view provides information about data types. 
+
+In addition to the information in the [PostgreSQL pg_type description](https://www.postgresql.org/docs/current/catalog-pg-type.html), EDB Postgres Advanced Server provides the following information.
+
+| Name      | Type   | Description                                   |
+| --------- | ------ | --------------------------------------------- |
+| typaccess | "char" | Specifies whether types contained in packages have PUBLIC or PRIVATE access. This field matters only when there's a packageId in `typnamespace`. |
+| typattrs  | text   | Type modifiers, such as FINAL or INSTANTIABLE. |                                                                                   |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_user.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_user.mdx
new file mode 100644
index 00000000000..b34662a75ca
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_cat_views/pg_views/pg_user.mdx
@@ -0,0 +1,13 @@
+---
+title: "PG_USER"
+redirects:
+  - /epas/latest/epas_compat_cat_views/pg_views/pg_user/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The `PG_USER` view provides information about the database users. It provides information specific to EDB Postgres Advanced Server in addition to the information provided in the [PostgreSQL pg_user view](https://www.postgresql.org/docs/current/view-pg-user.html).
+
+| Name              | Type      | Description                                                                            |
+| ----------------- | --------- | -------------------------------------------------------------------------------------- |
+| uselockdate       | date      | The time when the account was last locked; null if the account was never locked before |
+| useaccountstatus  | integer   | Bit mask identifying user account status                                              |
+| usepasswordexpire | date      | The time after which a password change is forced at the next login               |
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/01_alter_capture_privilege.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/01_alter_capture_privilege.mdx
new file mode 100644
index 00000000000..6ebca185730
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/01_alter_capture_privilege.mdx
@@ -0,0 +1,67 @@
+---
+title: "ALTER CAPTURE PRIVILEGE POLICY"
+---
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle with the `ALTER CAPTURE PRIVILEGES POLICY` SQL command. 
+
+## Name
+
+`ALTER CAPTURE PRIVILEGES POLICY` &mdash; Allows a superuser or a user with `CAPTURE_ADMIN` role to modify the attributes of the capture privilege poilicy.
+
+## Synopsis
+
+This command is available in five forms.
+
+```sql
+ALTER CAPTURE PRIVILEGES POLICY <name> SET WHERE ( <expression> )
+
+ALTER CAPTURE PRIVILEGES POLICY <name> DROP WHERE
+
+ALTER CAPTURE PRIVILEGES POLICY <name> SET { ROLE | USER } <role_names>
+
+ALTER CAPTURE PRIVILEGES POLICY <name> DROP { ROLE | USER }
+
+ALTER CAPTURE PRIVILEGES POLICY <name> { ENABLE | DISABLE } [ <run_name> ]
+```
+
+## Description
+
+The `ALTER CAPTURE PRIVILEGES POLICY` command allows a database superuser or any user with the system-defined `CAPTURE_ADMIN` privilege to a policy in the database.
+
+Use `DROP CAPTURE PRIVILEGES POLICY` to remove a capture policy.
+
+## Parameters
+
+`name`
+
+ The name optionally schema-qualified of the capture privilege policy to alter.
+
+`expression`
+
+Boolean expression containing up to 4000 characters.
+
+`role_names`
+
+The roles whose privileges are to be analyzed.
+
+`run_name`
+
+Name of the capture run.
+
+## Examples
+
+This command alters the attributes of a capture privilege policy:
+
+```sql
+## Enable and disable policy on the database
+ALTER CAPTURE PRIVILEGES POLICY sampledb_p1 ENABLE sampledb_run1;
+ALTER CAPTURE PRIVILEGES POLICY sampledb_p1 DISABLE;
+
+## Enable and disable policy on the role
+ALTER CAPTURE PRIVILEGES POLICY sampledb_p2 ENABLE sampledb_role_run1;
+ALTER CAPTURE PRIVILEGES POLICY sampledb_p2 DISABLE sampledb_role_run1;
+```
+
+## See also
+
+[CREATE CAPTURE PRIVILEGE POLICY](19a_create_capture_privilege), [DROP CAPTURE PRIVILEGE POLICY](44a_drop_capture_privilege)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/02_alter_directory.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/02_alter_directory.mdx
new file mode 100644
index 00000000000..eb995019e80
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/02_alter_directory.mdx
@@ -0,0 +1,64 @@
+---
+title: "ALTER DIRECTORY"
+redirects:
+  - /epas/latest/epas_compat_sql/02_alter_directory/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_directory" class="registered_link"></div>
+
+## Name
+
+`ALTER DIRECTORY` &mdash; Change the owner of a directory created using the [CREATE DIRECTORY](22_create_directory/#create_directory) command.
+
+## Synopsis
+
+```sql
+ALTER DIRECTORY <name> OWNER TO <rolename>
+```
+
+## Description
+
+The `ALTER DIRECTORY ...OWNER TO` command changes the owner of a directory. You must have the superuser privilege to execute this command. The new owner of the directory must also have the superuser privilege.
+
+## Parameters
+
+`name`
+
+ The name of the directory to alter.
+
+`rolename`
+
+ The name of an owner of the directory.
+
+## Examples
+
+These examples change ownership. `bob` and `carol` are superusers. `bob` is a current owner of the directory `EMPDIR`.
+
+```sql
+SELECT * FROM all_directories where directory_name = 'EMPDIR' order
+by 1,2,3;
+__OUTPUT__
+ owner | directory_name | directory_path
+-------+----------------+----------------
+ bob   | EMPDIR         | /path
+(1 row)
+```
+
+To change the ownership of directory `EMPDIR` to `carol`:
+
+```sql
+ALTER DIRECTORY EMPDIR OWNER TO carol;
+ALTER DIRECTORY
+
+SELECT * FROM all_directories where directory_name = 'EMPDIR' order by
+1,2,3;
+__OUTPUT__
+ owner | directory_name | directory_path
+-------+----------------+----------------
+ carol | EMPDIR         | /path
+(1 row)
+```
+
+## See also
+
+[CREATE DIRECTORY](22_create_directory/#create_directory), [DROP DIRECTORY](46_drop_directory/#drop_directory)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/03_alter_index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/03_alter_index.mdx
new file mode 100644
index 00000000000..2ecb9e76a21
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/03_alter_index.mdx
@@ -0,0 +1,93 @@
+---
+title: "ALTER INDEX"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.018.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.050.html"
+redirects:
+  - /epas/latest/epas_compat_sql/03_alter_index/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_index" class="registered_link"></div>
+
+## Name
+
+`ALTER INDEX` &mdash; Modify an existing index.
+
+## Synopsis
+
+EDB Postgres Advanced Server supports three variations of the `ALTER INDEX` command compatible with Oracle databases. Use the first variation to rename an index:
+
+```sql
+ALTER INDEX <name> RENAME TO <new_name>
+```
+
+Use the second variation of the `ALTER INDEX` command to rebuild an index:
+
+```sql
+ALTER INDEX <name> REBUILD
+```
+
+Use the third variation of the `ALTER INDEX` command to set the `PARALLEL` or `NOPARALLEL` clause:
+
+```sql
+ALTER INDEX <name> { NOPARALLEL | PARALLEL [ <integer> ] }
+```
+
+## Description
+
+`ALTER INDEX` changes the definition of an existing index. The `RENAME` clause changes the name of the index. The `REBUILD` clause reconstructs an index, replacing the old copy of the index with an updated version based on the index's table.
+
+The `REBUILD` clause invokes the PostgreSQL `REINDEX` command. For more information about using the `REBUILD` clause, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-reindex.html).
+
+The `PARALLEL` clause sets the degree of parallelism for an index that can be used to parallelize rebuilding an index.
+
+The `NOPARALLEL` clause resets parallelism to use default values. `reloptions` shows the `parallel_workers` parameter as `0`.
+
+`ALTER INDEX` has no effect on stored data.
+
+## Parameters
+
+`name`
+
+ The name (possibly schema-qualified) of an existing index.
+
+`new_name`
+
+ New name for the index.
+
+`PARALLEL`
+
+ Include the `PARALLEL` clause to specify a degree of parallelism. Set the `parallel_workers` parameter equal to the degree of parallelism for rebuilding an index. If you specify `PARALLEL` but don't provide a degree of parallelism, the default parallelism is used.
+
+`NOPARALLEL`
+
+ Specify `NOPARALLEL` to reset parallelism to default values.
+
+`integer`
+
+ The `integer` indicates the degree of parallelism, that is, the number of `parallel_workers` used when rebuilding an index.
+
+## Examples
+
+To change the name of an index from `name_idx` to `empname_idx`:
+
+```sql
+ALTER INDEX name_idx RENAME TO empname_idx;
+```
+
+To rebuild an index named `empname_idx`:
+
+```sql
+ALTER INDEX empname_idx REBUILD;
+```
+
+This example sets the degree of parallelism on an `empname_idx` index to 7:
+
+```sql
+ALTER INDEX empname_idx PARALLEL 7;
+```
+
+## See also
+
+[CREATE INDEX](24_create_index), [DROP INDEX](48_drop_index)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/04_alter_procedure.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/04_alter_procedure.mdx
new file mode 100644
index 00000000000..26c639b544e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/04_alter_procedure.mdx
@@ -0,0 +1,55 @@
+---
+title: "ALTER PROCEDURE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.019.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.051.html"
+redirects:
+  - /epas/latest/epas_compat_sql/04_alter_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_procedure" class="registered_link"></div>
+
+## Name
+
+`ALTER PROCEDURE` &mdash; Modify an existing procedure.
+
+## Synopsis
+
+```sql
+ALTER PROCEDURE <procedure_name> <options> [RESTRICT]
+```
+
+## Description
+
+Use the `ALTER PROCEDURE` statement to specify that a procedure is a `SECURITY INVOKER` or `SECURITY DEFINER`.
+
+## Parameters
+
+`procedure_name`
+
+ The (possibly schema-qualified) name of a stored procedure.
+
+`options` can be:
+
+-   `[EXTERNAL] SECURITY DEFINER`
+
+    Specify `SECURITY DEFINER` to execute the procedure with the privileges of the user that created the procedure. The `EXTERNAL` keyword is accepted for compatibility but ignored.
+
+-   `[EXTERNAL] SECURITY INVOKER`
+
+    Specify `SECURITY INVOKER` to execute the procedure with the privileges of the user that's invoking the procedure. The `EXTERNAL` keyword is accepted for compatibility but ignored.
+
+The `RESTRICT` keyword is accepted for compatibility but ignored.
+
+## Examples
+
+This command specifies for the `update_balance` to execute with the privileges of the user invoking the procedure:
+
+```sql
+ALTER PROCEDURE update_balance SECURITY INVOKER;
+```
+
+## See also
+
+[CREATE PROCEDURE](28_create_procedure/#create_procedure), [DROP PROCEDURE](50_drop_procedure/#drop_procedure)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/05_alter_profile.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/05_alter_profile.mdx
new file mode 100644
index 00000000000..d5f44c08a8a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/05_alter_profile.mdx
@@ -0,0 +1,124 @@
+---
+title: "ALTER PROFILE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.020.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.052.html"
+redirects:
+  - /epas/latest/epas_compat_sql/05_alter_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_profile" class="registered_link"></div>
+
+## Name
+
+`ALTER PROFILE` &mdash; Alter an existing profile.
+
+## Synopsis
+
+```sql
+ALTER PROFILE <profile_name> RENAME TO <new_name>;
+
+ALTER PROFILE <profile_name>
+      LIMIT {<parameter value>}[...];
+```
+
+## Description
+
+Use the `ALTER PROFILE` command to modify a user-defined profile. EDB Postgres Advanced Server supports two forms of the command:
+
+-   Use `ALTER PROFILE…RENAME TO` to change the name of a profile.
+-   Use `ALTER PROFILE…LIMIT` to modify the limits associated with a profile.
+
+Include the `LIMIT` clause and one or more space-delimited `parameter/value` pairs to specify the rules enforced by EDB Postgres Advanced Server. Use `ALTER PROFILE…RENAME TO` to change the name of a profile.
+
+## Parameters
+
+`profile_name`
+
+ The name of the profile.
+
+`new_name`
+
+ The new name of the profile.
+
+`parameter`
+
+ The attribute limited by the profile.
+
+`value`
+
+ The parameter limit.
+
+EDB Postgres Advanced Server supports these values for each parameter:
+
+`FAILED_LOGIN_ATTEMPTS` specifies the number of failed login attempts that a user can make before the server locks them out of their account for the length of time specified by `PASSWORD_LOCK_TIME`. Supported values are:
+
+-   An `INTEGER` value greater than `0`.
+-   `DEFAULT` &mdash; The value of `FAILED_LOGIN_ATTEMPTS` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The connecting user can make an unlimited number of failed login attempts.
+
+`PASSWORD_LOCK_TIME` specifies the length of time that must pass before the server unlocks an account that was locked because of `FAILED_LOGIN_ATTEMPTS`. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LOCK_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The account is locked until manually unlocked by a database superuser.
+
+`PASSWORD_LIFE_TIME` specifies the number of days to use the current password before the user is prompted to provide a new password. Include the `PASSWORD_GRACE_TIME` clause when using the `PASSWORD_LIFE_TIME` clause to specify the number of days after the password expires before connections by the role are rejected. If you don't specify `PASSWORD_GRACE_TIME`, the password expires on the day specified by the default value of `PASSWORD_GRACE_TIME`. The user can't execute any command until they provide a new password. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LIFE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password doesn't have an expiration date.
+
+`PASSWORD_GRACE_TIME` specifies the length of the grace period after a password expires until the user is forced to change their password. When the grace period expires, a user is allowed to connect but isn't allowed to execute any command until they update their expired password. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_GRACE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The grace period is infinite.
+
+`PASSWORD_REUSE_TIME` specifies the number of days a user must wait before reusing a password. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED`, there are no restrictions on password reuse. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_REUSE_MAX` specifies the number of password changes that must occur before a password can be reused. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED`, there are no restrictions on password reuse. Supported values are:
+
+-   An `INTEGER` value of `0` or greater.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_MAX` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_VERIFY_FUNCTION` specifies password complexity. Supported values are:
+
+-   The name of a PL/SQL function.
+-   `DEFAULT` &mdash; The value of `PASSWORD_VERIFY_FUNCTION` specified in the `DEFAULT` profile.
+-   `NULL`
+
+`PASSWORD_ALLOW_HASHED` specifies whether an encrypted password is allowed. If you specify the value as `TRUE`, the system allows a user to change the password by specifying a hash-computed encrypted password on the client side. However, if you specify the value as `FALSE`, then a password must be specified in a plain-text form to validate without error. Supported values are:
+
+-   A `BOOLEAN` value `TRUE/ON/YES/1` or `FALSE/OFF/NO/0`.
+-   `DEFAULT` &mdash; The value of `PASSWORD_ALLOW_HASHED` specified in the `DEFAULT` profile.
+
+!!! Note
+    The `PASSWORD_ALLOW_HASHED` isn't compatible with Oracle.
+
+## Examples
+
+This example modifies a profile named `acctg_profile`:
+
+```sql
+ALTER PROFILE acctg_profile
+       LIMIT FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LOCK_TIME 1;
+```
+
+`acctg_profile` counts failed connection attempts when a login role attempts to connect to the server. The profile specifies that if a user doesn't authenticate with the correct password in three attempts, the account is locked for one day.
+
+This example changes the name of `acctg_profile` to `payables_profile`:
+
+```sql
+ALTER PROFILE acctg_profile RENAME TO payables_profile;
+```
+
+## See also
+
+[CREATE PROFILE](29_create_profile/#create_profile), [DROP PROFILE](51_drop_profile/#drop_profile)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/06_alter_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/06_alter_queue.mdx
new file mode 100644
index 00000000000..2367faf8493
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/06_alter_queue.mdx
@@ -0,0 +1,149 @@
+---
+title: "ALTER QUEUE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.021.html"
+redirects:
+  - /epas/latest/epas_compat_sql/06_alter_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_queue" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes an extra syntax not offered by Oracle with the `ALTER QUEUE SQL` command. You can use this syntax with the `DBMS_AQADM` package.
+
+## Name
+
+`ALTER QUEUE` &mdash; Allows a superuser or a user with the `aq_administrator_role` privilege to modify the attributes of a queue.
+
+## Synopsis
+
+This command is available in four forms. 
+
+## Parameters for the first form
+
+The first form of this command changes the name of a queue:
+
+```sql
+ALTER QUEUE <queue_name> RENAME TO <new_name>
+```
+
+`queue_name`
+
+ The name (optionally schema-qualified) of an existing queue.
+
+`RENAME TO`
+
+ To rename the queue, include the `RENAME TO` clause and a new name for the queue.
+
+`new_name`
+
+ New name for the queue.
+
+
+## Parameters for the second form
+
+The second form of the `ALTER QUEUE` command modifies the attributes of the queue:
+
+```sql
+ALTER QUEUE <queue_name> SET [ ( { <option_name option_value> ) } [,SET <option_name> ] ]
+```
+
+`queue_name`
+
+ The name (optionally schema-qualified) of an existing queue.
+
+ Include the `SET` clause and `option_name/option_value` pairs to modify the attributes of the queue.
+
+`option_name option_value`
+
+ The name of an option to associate with the new queue and the corresponding value of the option. If you provide duplicate option names, the server returns an error.
+
+-   If `option_name` is `retries`, provide an integer that represents the number of times to attempt a dequeue.
+-   If `option_name` is `retrydelay`, provide a double-precision value that represents the delay in seconds.
+-   If `option_name` is `retention`, provide a double-precision value that represents the retention time in seconds.
+
+## Parameters for the third form
+
+Use the third form of the `ALTER QUEUE` command to enable or disable enqueuing or dequeuing on a queue:
+
+```sql
+ALTER QUEUE <queue_name> ACCESS { START | STOP } [ FOR { enqueue | dequeue } ] [ NOWAIT ]
+```
+
+`queue_name`
+
+ The name (optionally schema-qualified) of an existing queue.
+
+`ACCESS`
+
+ Include the `ACCESS` keyword to enable or disable enqueuing or dequeuing on a queue.
+
+`START | STOP`
+
+ Use the `START` and `STOP` keywords to indicate the desired state of the queue.
+
+`FOR enqueue|dequeue`
+
+ Use the `FOR` clause to indicate if you are specifying the state of enqueueing or dequeueing activity on the specified queue.
+
+`NOWAIT`
+
+ Include the `NOWAIT` keyword to specify for the server not to wait for the completion of outstanding transactions before changing the state of the queue. You can use the `NOWAIT` keyword only when specifying an `ACCESS` value of `STOP`. The server returns an error if `NOWAIT` is specified with an `ACCESS` value of `START`.
+
+## Parameters for the fourth form
+
+Use the fourth form to `ADD` or `DROP` callback details for a queue.
+
+```sql
+ALTER QUEUE <queue_name> { ADD | DROP } CALL TO <location_name> [ WITH <callback_option> ]
+```
+
+`queue_name`
+
+ The name (optionally schema-qualified) of an existing queue.
+
+`ADD | DROP`
+
+ Include the `ADD` or `DROP` keywords to enable add or remove callback details for a queue.
+
+`location_name`
+
+ Specifies the name of the callback procedure.
+
+`callback_option`
+
+ Can be `context`. Specify a `RAW` value when including this clause.
+
+## Examples
+
+This example changes the name of a queue from `work_queue_east` to `work_order`:
+
+```sql
+ALTER QUEUE work_queue_east RENAME TO work_order;
+```
+
+This example modifies a queue named `work_order`. It sets the number of retries to 100, the delay between retries to 2 seconds, and the length of time that the queue retains dequeued messages to 10 seconds:
+
+```sql
+ALTER QUEUE work_order SET (retries 100, retrydelay 2, retention 10);
+```
+
+These commands enable enqueueing and dequeueing in a queue named `work_order`:
+
+```sql
+ALTER QUEUE work_order ACCESS START;
+ALTER QUEUE work_order ACCESS START FOR enqueue;
+ALTER QUEUE work_order ACCESS START FOR dequeue;
+```
+
+These commands disable enqueueing and dequeueing in a queue named `work_order`:
+
+```sql
+ALTER QUEUE work_order ACCESS STOP NOWAIT;
+ALTER QUEUE work_order ACCESS STOP FOR enqueue;
+ALTER QUEUE work_order ACCESS STOP FOR dequeue;
+```
+
+## See also
+
+[CREATE QUEUE](30_create_queue/#create_queue), [DROP QUEUE](52_drop_queue/#drop_queue)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/07_alter_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/07_alter_queue_table.mdx
new file mode 100644
index 00000000000..e9bcc234d23
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/07_alter_queue_table.mdx
@@ -0,0 +1,50 @@
+---
+title: "ALTER QUEUE TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.022.html"
+redirects:
+  - /epas/latest/epas_compat_sql/07_alter_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_queue_table" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle with the `ALTER QUEUE SQL` command. You can use this syntax with the `DBMS_AQADM` package.
+
+## Name
+
+`ALTER QUEUE TABLE` &mdash; Modify an existing queue table.
+
+## Synopsis
+
+Use `ALTER QUEUE TABLE` to change the name of an existing queue table:
+
+```sql
+ALTER QUEUE TABLE <name> RENAME TO <new_name>
+```
+
+## Description
+
+`ALTER QUEUE TABLE` allows a superuser or a user with the `aq_administrator_role` privilege to change the name of an existing queue table.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of an existing queue table.
+
+`new_name`
+
+ New name for the queue table.
+
+## Examples
+
+This example changes the name of a queue table from `wo_table_east` to `work_order_table`:
+
+```sql
+ALTER QUEUE TABLE wo_queue_east RENAME TO work_order_table;
+```
+
+## See also
+
+[CREATE QUEUE TABLE](31_create_queue_table/#create_queue_table), [DROP QUEUE TABLE](53_drop_queue_table/#drop_queue_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/08_alter_role_identified_by.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/08_alter_role_identified_by.mdx
new file mode 100644
index 00000000000..86dacd8951b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/08_alter_role_identified_by.mdx
@@ -0,0 +1,52 @@
+---
+title: "ALTER ROLE… IDENTIFIED BY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.023.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.053.html"
+redirects:
+  - /epas/latest/epas_compat_sql/08_alter_role_identified_by/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_role_identified_by" class="registered_link"></div>
+
+## Name
+
+`ALTER ROLE` &mdash; Change the password associated with a database role.
+
+## Synopsis
+
+```sql
+ALTER ROLE <role_name> IDENTIFIED BY <password>
+          [REPLACE <prev_password>]
+```
+
+## Description
+
+A role without the `CREATEROLE` privilege can use this command to change their own password. An unprivileged role must include the `REPLACE` clause and their previous password if `PASSWORD_VERIFY_FUNCTION` isn't `NULL` in their profile. When a non-superuser uses the `REPLACE` clause, the server compares the password provided to the existing password and raises an error if the passwords don't match.
+
+A database superuser can use this command to change the password associated with any role. If a superuser includes the `REPLACE` clause, the clause is ignored. A non-matching value for the previous password doesn't throw an error.
+
+If the role whose password is being changed has the `SUPERUSER` attribute, then a superuser must issue this command. A role with the `CREATEROLE` attribute can use this command to change the password associated with a role that isn't a superuser.
+
+## Parameters
+
+`role_name`
+
+ The name of the role whose password to alter.
+
+`password`
+
+ The role’s new password.
+
+`prev_password`
+
+ The role’s previous password.
+
+## Examples
+
+This example changes a role’s password:
+
+```sql
+ALTER ROLE john IDENTIFIED BY xyRP35z REPLACE 23PJ74a;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/09_alter_role_managing_database_link_and_dbms_rls_privileges.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/09_alter_role_managing_database_link_and_dbms_rls_privileges.mdx
new file mode 100644
index 00000000000..995c2597b4c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/09_alter_role_managing_database_link_and_dbms_rls_privileges.mdx
@@ -0,0 +1,117 @@
+---
+title: "ALTER ROLE: Managing database link and DBMS_RLS privileges"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.024.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.054.html"
+redirects:
+  - /epas/latest/epas_compat_sql/09_alter_role_managing_database_link_and_dbms_rls_privileges/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_role_managing_database_link_and_dbms_rls_privileges" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle for the `ALTER ROLE` command. This syntax can be useful when assigning privileges related to creating and dropping database links compatible with Oracle databases and fine-grained access control using `DBMS_RLS`.
+
+## CREATE DATABASE LINK
+
+A user who holds the `CREATE DATABASE LINK` privilege can create a private database link. The following `ALTER ROLE` command grants privileges to an EDB Postgres Advanced Server role that allow the specified role to create a private database link:
+
+```sql
+ALTER ROLE role_name
+    WITH [CREATEDBLINK | CREATE DATABASE LINK]
+```
+
+This command is the functional equivalent of:
+
+```sql
+GRANT CREATE DATABASE LINK to role_name
+```
+
+Use the following command to revoke the privilege:
+
+```sql
+ALTER ROLE role_name
+  WITH [NOCREATEDBLINK | NO CREATE DATABASE LINK]
+```
+
+!!! Note
+    The `CREATEDBLINK` and `NOCREATEDBLINK` keywords are deprecated syntaxes. We recommend using the `CREATE DATABASE LINK` and `NO CREATE DATABASE LINK` syntax options.
+
+## CREATE PUBLIC DATABASE LINK
+
+A user who holds the `CREATE PUBLIC DATABASE LINK` privilege can create a public database link. The following `ALTER ROLE` command grants privileges to an EDB Postgres Advanced Server role that allow the specified role to create a public database link:
+
+```sql
+ALTER ROLE role_name
+  WITH [CREATEPUBLICDBLINK | CREATE PUBLIC DATABASE LINK]
+```
+
+This command is the functional equivalent of:
+
+```sql
+GRANT CREATE PUBLIC DATABASE LINK to role_name
+```
+
+Use the following command to revoke the privilege:
+
+```sql
+ALTER ROLE role_name
+  WITH [NOCREATEPUBLICDBLINK | NO CREATE PUBLIC DATABASE LINK]
+```
+
+!!! Note
+    The `CREATEPUBLICDBLINK` and `NOCREATEPUBLICDBLINK` keywords are deprecated syntaxes. We recommend using the `CREATE PUBLIC DATABASE LINK` and `NO CREATE PUBLIC DATABASE LINK` syntax options.
+
+## DROP PUBLIC DATABASE LINK
+
+A user who holds the `DROP PUBLIC DATABASE LINK` privilege can drop a public database link. The following `ALTER ROLE` command grants privileges to an EDB Postgres Advanced Server role that allow the specified role to drop a public database link:
+
+```sql
+ALTER ROLE role_name
+  WITH [DROPPUBLICDBLINK | DROP PUBLIC DATABASE LINK]
+```
+
+This command is the functional equivalent of:
+
+```sql
+GRANT DROP PUBLIC DATABASE LINK to role_name
+```
+
+Use the following command to revoke the privilege:
+
+```sql
+ALTER ROLE role_name
+  WITH [NODROPPUBLICDBLINK | NO DROP PUBLIC DATABASE LINK]
+```
+
+!!! Note
+    The `DROPPUBLICDBLINK` and `NODROPPUBLICDBLINK` keywords are deprecated syntaxes. We recommend using the `DROP PUBLIC DATABASE LINK` and `NO DROP PUBLIC DATABASE LINK` syntax options.
+
+## EXEMPT ACCESS POLICY
+
+A user who holds the `EXEMPT ACCESS POLICY` privilege is exempt from fine-grained access control (`DBMS_RLS`) policies. A user who holds these privileges can view or modify any row in a table constrained by a `DBMS_RLS` policy. The following `ALTER ROLE` command grants privileges to an EDB Postgres Advanced Server role that exempt the specified role from any defined `DBMS_RLS` policies:
+
+```sql
+ALTER ROLE role_name
+    WITH [POLICYEXEMPT | EXEMPT ACCESS POLICY]
+```
+
+This command is the functional equivalent of:
+
+```sql
+GRANT EXEMPT ACCESS POLICY TO role_name
+```
+
+Use the following command to revoke the privilege:
+
+```sql
+ALTER ROLE role_name
+  WITH [NOPOLICYEXEMPT | NO EXEMPT ACCESS POLICY]
+```
+
+!!! Note
+    The `POLICYEXEMPT` and `NOPOLICYEXEMPT` keywords are deprecated syntaxes. We recommend using the `EXEMPT ACCESS POLICY` and `NO EXEMPT ACCESS POLICY` syntax options.
+
+## See also
+
+[CREATE ROLE](32_create_role/#create_role), [DROP ROLE](55_drop_role/#drop_role), [GRANT](64_grant/#grant), [REVOKE](67_revoke/#revoke), [SET ROLE](73_set_role/#set_role)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/10_alter_sequence.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/10_alter_sequence.mdx
new file mode 100644
index 00000000000..ec2ce00092d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/10_alter_sequence.mdx
@@ -0,0 +1,71 @@
+---
+title: "ALTER SEQUENCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.025.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.055.html"
+redirects:
+  - /epas/latest/epas_compat_sql/10_alter_sequence/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_sequence" class="registered_link"></div>
+
+## Name
+
+`ALTER SEQUENCE` &mdash; Change the definition of a sequence generator.
+
+## Synopsis
+
+```sql
+ALTER SEQUENCE <name> [ INCREMENT BY <increment> ]
+  [ MINVALUE <minvalue> ] [ MAXVALUE <maxvalue> ]
+  [ CACHE <cache> | NOCACHE ] [ CYCLE ]
+```
+
+## Description
+
+`ALTER SEQUENCE` changes the parameters of an existing sequence generator. Any parameter not specifically set in the `ALTER SEQUENCE` command retains its prior setting.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of a sequence to alter.
+
+`increment`
+
+ The clause `INCREMENT BY increment` is optional. A positive value makes an ascending sequence, a negative one a descending sequence. If unspecified, the old increment value is maintained.
+
+`minvalue`
+
+ The optional clause `MINVALUE minvalue` determines the minimum value a sequence can generate. If not specified, the current minimum value is maintained. You can use the keywords `NO MINVALUE` to set this behavior back to the defaults of 1 and -2<sup>63</sup>-1 for ascending and descending sequences, respectively. However, this term isn't compatible with Oracle databases.
+
+`maxvalue`
+
+ The optional clause `MAXVALUE maxvalue` determines the maximum value for the sequence. If not specified, the current maximum value is maintained. You can use the keywords `NO MAXVALUE` to set this behavior back to the defaults of 2<sup>63</sup>-1 and -1 for ascending and descending sequences, respectively. However, this term isn't compatible with Oracle databases.
+
+`cache`
+
+ The optional clause `CACHE cache` specifies how many sequence numbers to preallocate and store in memory for faster access. The minimum value is `1`. Only one value can be generated at a time, i.e., `NOCACHE`. If unspecified, the old cache value is maintained.
+
+`CYCLE`
+
+ The `CYCLE` option allows the sequence to wrap around when the `maxvalue` or `minvalue` is reached by an ascending or descending sequence. If the limit is reached, the next number generated is the `minvalue` or `maxvalue`. If not specified, the old cycle behavior is maintained. You can use the keywords `NO CYCLE` to alter the sequence so that it doesn't recycle. However, this term isn't compatible with Oracle databases.
+
+## Notes
+
+To avoid blocking concurrent transactions that obtain numbers from the same sequence, `ALTER SEQUENCE` is never rolled back. The changes take effect immediately and aren't reversible.
+
+`ALTER SEQUENCE` doesn't immediately affect `NEXTVAL` results in backends, other than the current one, that have preallocated (cached) sequence values. They use up all cached values prior to noticing the changed sequence parameters. The current backend is affected immediately.
+
+## Examples
+
+Change the increment and cache values of the sequence `serial`:
+
+```sql
+ALTER SEQUENCE serial INCREMENT BY 2 CACHE 5;
+```
+
+## See also
+
+[CREATE SEQUENCE](34_create_sequence/#create_sequence), [DROP SEQUENCE](56_drop_sequence/#drop_sequence)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11_alter_session.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11_alter_session.mdx
new file mode 100644
index 00000000000..b63d7fd7c01
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11_alter_session.mdx
@@ -0,0 +1,77 @@
+---
+title: "ALTER SESSION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+redirects:
+  - /epas/latest/epas_compat_sql/11_alter_session/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_session" class="registered_link"></div>
+
+## Name
+
+`ALTER SESSION` &mdash; Change a runtime parameter.
+
+## Synopsis
+
+```sql
+ALTER SESSION SET <name> = <value>
+```
+
+## Description
+
+The `ALTER SESSION` command changes runtime configuration parameters. `ALTER SESSION` affects only the value used by the current session. Some of these parameters are provided solely for compatibility with Oracle syntax and have no effect on the runtime behavior of EDB Postgres Advanced Server. Others alter a corresponding EDB Postgres Advanced Server database server runtime configuration parameter.
+
+## Parameters
+
+`name`
+
+ Name of a settable runtime parameter.
+
+`value`
+
+ New value of parameter.
+
+## Configuration parameters
+
+You can modify the following configuration parameters using the `ALTER SESSION` command:
+
+-   `NLS_DATE_FORMAT (string)`
+
+    Sets the display format for date and time values as well as the rules for interpreting ambiguous date input values. Has the same effect as setting the EDB Postgres Advanced Server `datestyle` runtime configuration parameter.
+
+-   `NLS_LANGUAGE (string)`
+
+    Sets the message-display language. Has the same effect as setting the EDB Postgres Advanced Server `lc_messages` runtime configuration parameter.
+
+-   `NLS_LENGTH_SEMANTICS (string)`
+
+    Valid values are `BYTE` and `CHAR`. The default is `BYTE`. This parameter is provided only for syntax compatibility and has no effect in the EDB Postgres Advanced Server.
+
+-   `OPTIMIZER_MODE (string)`
+
+    Sets the default optimization mode for queries. Valid values are `ALL_ROWS`, `CHOOSE`, `FIRST_ROWS`, `FIRST_ROWS_10`, `FIRST_ROWS_100`, and `FIRST_ROWS_1000`. The default is `CHOOSE`. This parameter is implemented in EDB Postgres Advanced Server.
+
+-   `QUERY_REWRITE_ENABLED (string)`
+
+    Valid values are `TRUE`, `FALSE`, and `FORCE`. The default is `FALSE`. This parameter is provided only for syntax compatibility and has no effect in EDB Postgres Advanced Server.
+
+-   `QUERY_REWRITE_INTEGRITY (string)`
+
+    Valid values are `ENFORCED`, `TRUSTED`, and `STALE_TOLERATED`. The default is `ENFORCED`. This parameter is provided only for syntax compatibility and has no effect in EDB Postgres Advanced Server.
+
+## Examples
+
+Set the language to U.S. English in UTF-8 encoding. In this example, the value `en_US.UTF-8` is in the format for EDB Postgres Advanced Server. This form isn't compatible with Oracle databases.
+
+```sql
+ALTER SESSION SET NLS_LANGUAGE = 'en_US.UTF-8';
+```
+
+Set the date display format:
+
+```sql
+ALTER SESSION SET NLS_DATE_FORMAT = 'dd/mm/yyyy';
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11a_alter_synonym.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11a_alter_synonym.mdx
new file mode 100644
index 00000000000..58528a02564
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/11a_alter_synonym.mdx
@@ -0,0 +1,67 @@
+---
+title: "ALTER SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.026.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.056.html"
+redirects:
+  - /epas/latest/epas_compat_sql/11a_alter_synonym/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+## Name
+
+`ALTER SYNONYM` &mdash; Change ownership of a synonym object. 
+
+## Synopsis
+
+```text
+ALTER SYNONYM <syn_name> OWNER TO <new_owner>
+```
+
+## Description
+
+The `ALTER SYNONYM` command changes the owner of the synonym. 
+
+
+## Examples
+
+```text
+-- create user t1 and t2
+edb=# create user t1;
+CREATE ROLE
+edb=# create user t2;
+CREATE ROLE
+
+-- grant all the privileges to user t1 and t2 on public schema
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t1;
+GRANT
+edb=# GRANT ALL PRIVILEGES ON SCHEMA public TO GROUP t2;
+GRANT
+
+-- connect to the database as user t1 and create the table
+edb=# \c - t1
+You are now connected to database "edb" as user "t1".
+edb=> create table t(n int); 
+CREATE TABLE
+
+-- create a synonym for table t
+edb=> create public synonym x for  t;
+CREATE SYNONYM
+
+-- check the owner of the synonym x is t1
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T1    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          | 
+
+-- connect the database as user edb and change the owner of the synonym x to user t2
+edb=> \c - edb
+You are now connected to database "edb" as user "edb".
+edb=# alter synonym x owner to t2;
+
+-- check the owner of the synonym x is changed to t2
+edb=# select * from all_synonyms;
+ owner | schema_name | objid | synonym_name | table_owner | table_schema_name | table_name | db_link 
+-------+-------------+-------+--------------+-------------+-------------------+------------+---------
+ T2    | PUBLIC      | 16390 | X            | T1          | PUBLIC            | T          |          
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/12_alter_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/12_alter_table.mdx
new file mode 100644
index 00000000000..c710d2d1696
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/12_alter_table.mdx
@@ -0,0 +1,205 @@
+---
+title: "ALTER TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.027.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.057.html"
+redirects:
+  - /epas/latest/epas_compat_sql/12_alter_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_table" class="registered_link"></div>
+
+## Name
+
+`ALTER TABLE` &mdash; Change the definition of a table.
+
+## Synopsis
+
+```sql
+ALTER TABLE <name>
+  action [, ...]
+ALTER TABLE <name>
+  RENAME COLUMN <column> TO <new_column>
+ALTER TABLE <name>
+  RENAME TO <new_name>
+ALTER TABLE <name>
+  { NOPARALLEL | PARALLEL [ <integer> ] }
+```
+
+`action` is one of:
+
+```sql
+ADD <column type> [ <column_constraint> [ ... ] ]
+DROP COLUMN <column>
+ADD <table_constraint>
+DROP CONSTRAINT <constraint_name> [ CASCADE ]
+```
+
+## Description
+
+`ALTER TABLE` changes the definition of an existing table. There are several subforms:
+
+-   `ADD column type`
+
+    This form adds a column to the table using the same syntax as `CREATE TABLE`.
+
+-   `DROP COLUMN`
+
+    This form drops a column from a table. Indexes and table constraints involving the column are dropped as well.
+
+-   `ADD table_constraint`
+
+    This form adds a constraint to a table. For details, see [CREATE TABLE](36_create_table/#create_table).
+
+-   `DROP CONSTRAINT`
+
+    This form drops constraints on a table. Currently, constraints on tables don't need unique names, so there might be more than one constraint matching the specified name. All matching constraints are dropped.
+
+`RENAME`
+
+ The `RENAME` forms change the name of a table (or an index, sequence, or view) or the name of a column in a table. There is no effect on the stored data.
+
+The `PARALLEL` clause sets the degree of parallelism for a table. The `NOPARALLEL` clause resets the values to their defaults. `reloptions` shows the `parallel_workers` parameter as `0`.
+
+A superuser has permission to create a trigger on any user's table, but a user can create a trigger only on the table they own. However, when the ownership of a table is changed, the ownership of the trigger's implicit objects is updated when they're matched with a table owner owning a trigger.
+
+You can use the `ALTER TRIGGER ...ON AUTHORIZATION` command to alter a trigger's implicit object owner. For information, see [ALTER TRIGGER](13_alter_trigger/#alter_trigger).
+
+You must own the table to use `ALTER TABLE`.
+
+## Parameters
+
+`name`
+
+ The name (possibly schema-qualified) of an existing table to alter.
+
+`column`
+
+ Name of a new or existing column.
+
+`new_column`
+
+ New name for an existing column.
+
+`new_name`
+
+ New name for the table.
+
+`type`
+
+ Data type of the new column.
+
+`table_constraint`
+
+ New table constraint for the table.
+
+`constraint_name`
+
+ Name of an existing constraint to drop.
+
+`CASCADE`
+
+ Automatically drop objects that depend on the dropped constraint.
+
+`PARALLEL`
+
+ Specify `PARALLEL` to select a degree of parallelism. You can also specify the degree of parallelism by setting the `parallel_workers` parameter when performing a parallel scan on a table. If you specify `PARALLEL` without including a degree of parallelism, the index uses default parallelism.
+
+`NOPARALLEL`
+
+ Specify `NOPARALLEL` to reset parallelism to default values.
+
+`integer`
+
+ The `integer` indicates the degree of parallelism, which is the number of `parallel_workers` used in the parallel operation to perform a parallel scan on a table.
+
+## Notes
+
+When you invoke `ADD COLUMN`, all existing rows in the table are initialized with the column’s default value (null if no `DEFAULT` clause is specified). Adding a column with a non-null default requires rewriting the entire table. This can take a long time for a large table, and it temporarily requires double the disk space. Adding a `CHECK` or `NOT NULL` constraint requires scanning the table to verify that existing rows meet the constraint.
+
+The `DROP COLUMN` form doesn't physically remove the column but makes it invisible to SQL operations. Subsequent insert and update operations in the table store a null value for the column. Thus, dropping a column is quick, but it doesn't immediately reduce the on-disk size of your table since the space occupied by the dropped column isn't reclaimed. The space is reclaimed over time as existing rows are updated.
+
+Changing any part of a system catalog table isn't permitted. Refer to [CREATE TABLE](36_create_table/#create_table) for a further description of valid parameters.
+
+## Examples
+
+To add a column of type `VARCHAR2` to a table:
+
+```sql
+ALTER TABLE emp ADD address VARCHAR2(30);
+```
+
+To drop a column from a table:
+
+```sql
+ALTER TABLE emp DROP COLUMN address;
+```
+
+To rename an existing column:
+
+```sql
+ALTER TABLE emp RENAME COLUMN address TO city;
+```
+
+To rename an existing table:
+
+```sql
+ALTER TABLE emp RENAME TO employee;
+```
+
+To add a check constraint to a table:
+
+```sql
+ALTER TABLE emp ADD CONSTRAINT sal_chk CHECK (sal > 500);
+```
+
+To remove a check constraint from a table:
+
+```sql
+ALTER TABLE emp DROP CONSTRAINT sal_chk;
+```
+
+To reset the degree of parallelism to 0 on the `emp` table:
+
+```sql
+ALTER TABLE emp NOPARALLEL;
+```
+
+This example creates a table named `dept` and then alters the `dept` table to define and enable a unique key on the `dname` column. The constraint `dept_dname_uq` identifies the `dname` column as a unique key. The `USING_INDEX` clause creates an index on a table `dept` with the index statement specified to enable the unique constraint.
+
+```sql
+CREATE TABLE dept (
+   deptno          NUMBER(2),
+   dname           VARCHAR2(14),
+   loc             VARCHAR2(13)
+);
+```
+
+```sql
+ALTER TABLE dept
+  ADD CONSTRAINT dept_dname_uq UNIQUE(dname)
+     USING INDEX (CREATE UNIQUE INDEX idx_dept_dname_uq ON dept (dname));
+```
+
+This example creates a table named `emp` and then alters the `emp` table to define and enable a primary key on the `ename` column. The `emp_ename_pk` constraint identifies the column `ename` as a primary key of the `emp` table. The `USING_INDEX` clause creates an index on a table `emp` with the index statement specified to enable the primary constraint.
+
+```sql
+CREATE TABLE emp (
+   empno           NUMBER(4) NOT NULL,
+   ename           VARCHAR2(10),
+   job             VARCHAR2(9),
+   sal             NUMBER(7,2),
+   deptno          NUMBER(2)
+);
+```
+
+```sql
+ALTER TABLE emp
+  ADD CONSTRAINT emp_ename_pk PRIMARY KEY (ename)
+     USING INDEX (CREATE INDEX idx_emp_ename_pk ON emp (ename));
+```
+
+## See also
+
+[CREATE TABLE](36_create_table/#create_table), [DROP TABLE](57_drop_table/#drop_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/13_alter_trigger.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/13_alter_trigger.mdx
new file mode 100644
index 00000000000..f382eb9a7f1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/13_alter_trigger.mdx
@@ -0,0 +1,111 @@
+---
+title: "ALTER TRIGGER"
+redirects:
+  - /epas/latest/epas_compat_sql/13_alter_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_trigger" class="registered_link"></div>
+
+## Name
+
+`ALTER TRIGGER` &mdash; Change the definition of a trigger.
+
+## Synopsis
+
+EDB Postgres Advanced Server supports three variations of the `ALTER TRIGGER` command. Use the first variation to change the name of a given trigger without changing the trigger definition:
+
+```sql
+ALTER TRIGGER <name> ON <table_name> RENAME TO <new_name>
+```
+
+Use the second variation of the `ALTER TRIGGER` command if the trigger depends on an extension. If the extension is dropped, the trigger is dropped as well.
+
+```sql
+ALTER TRIGGER <name> ON <table_name> DEPENDS ON EXTENSION <extension_name>
+```
+
+Use the third variation of the `ALTER TRIGGER` command to change the ownership of a trigger's object:
+
+```sql
+ALTER TRIGGER <name> ON <table_name> AUTHORIZATION <rolespec>
+```
+
+For information about using non-compatible implementations of the `ALTER TRIGGER` command that are supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-altertrigger.html).
+
+## Description
+
+`ALTER TRIGGER` changes the properties of an existing trigger. You must own the table the trigger acts on to change its properties.
+
+To alter an owner of the trigger's implicit object, you can use the `ALTER TRIGGER ...ON AUTHORIZATION` command. You must have the privilege to execute `ALTER TRIGGER ...ON AUTHORIZATION` command to assign the trigger's implicit object ownership to a user after authorization.
+
+## Parameters
+
+`name`
+
+ The name of the trigger to alter.
+
+`table_name`
+
+ The name of a table on which trigger acts.
+
+`rolespec`
+
+ Determines an owner of trigger objects.
+
+## Examples
+
+This example includes the users `bob` and `carol` as superusers. The user `bob` owns a table `emp`. The user `carol` owns a trigger named `emp_sal_trig`, which is created on table `emp`:
+
+```sql
+SELECT relname, relowner::regrole FROM pg_class WHERE relname = 'emp';
+__OUTPUT__
+ relname | relowner
+---------+----------
+ emp     | bob
+(1 row)
+```
+
+```sql
+SELECT proname, proowner::regrole FROM pg_proc WHERE oid = (SELECT tgfoid
+FROM pg_trigger WHERE tgname = 'emp_sal_trig') ORDER BY oid;
+__OUTPUT__
+ proname           | proowner
+-------------------+----------
+ emp_sal_trig_emp  | carol
+(1 row)
+```
+
+To alter the ownership of table `emp` from user `bob` to a new owner `edb`:
+
+```sql
+ALTER TABLE emp OWNER TO edb;
+ALTER TABLE
+
+SELECT relname, relowner::regrole FROM pg_class WHERE relname = 'emp';
+__OUTPUT__
+ relname | relowner
+---------+----------
+ emp     | edb
+(1 row)
+```
+
+The table ownership is changed from the user `bob` to an owner `edb`, but the trigger ownership of `emp_sal_trig` isn't altered and is owned by user `carol`. Alter the trigger `emp_sal_trig` on table `emp`, and grant authorization to an owner `edb`:
+
+```sql
+ALTER TRIGGER emp_sal_trig ON emp AUTHORIZATION edb;
+ALTER TRIGGER
+
+SELECT proname, proowner::regrole FROM pg_proc WHERE oid = (SELECT tgfoid
+FROM pg_trigger WHERE tgname = 'emp_sal_trig') ORDER BY oid;
+__OUTPUT__
+ proname          | proowner
+------------------+----------
+ emp_sal_trig_emp | edb
+(1 row)
+```
+
+The trigger ownership `emp_sal_trig` on table `emp` is altered and granted to an owner `edb`.
+
+## See also
+
+[CREATE TRIGGER](38_create_trigger/#create_trigger), [DROP TRIGGER](59_drop_trigger/#drop_trigger)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/14_alter_tablespace.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/14_alter_tablespace.mdx
new file mode 100644
index 00000000000..1351a3910f7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/14_alter_tablespace.mdx
@@ -0,0 +1,47 @@
+---
+title: "ALTER TABLESPACE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.028.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.058.html"
+redirects:
+  - /epas/latest/epas_compat_sql/14_alter_tablespace/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_tablespace" class="registered_link"></div>
+
+## Name
+
+`ALTER TABLESPACE` &mdash; Change the definition of a tablespace.
+
+## Synopsis
+
+```sql
+ALTER TABLESPACE <name> RENAME TO <newname>
+```
+
+## Description
+
+`ALTER TABLESPACE` changes the definition of a tablespace.
+
+## Parameters
+
+`name`
+
+ The name of an existing tablespace.
+
+`newname`
+
+ The new name of the tablespace. The new name can't begin with `pg_`. These names are reserved for system tablespaces.
+
+## Examples
+
+Rename tablespace `empspace` to `employee_space`:
+
+```sql
+ALTER TABLESPACE empspace RENAME TO employee_space;
+```
+
+## See also
+
+[DROP TABLESPACE](58_drop_tablespace/#drop_tablespace)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/15_alter_user_identified_by.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/15_alter_user_identified_by.mdx
new file mode 100644
index 00000000000..5e2e020e0ae
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/15_alter_user_identified_by.mdx
@@ -0,0 +1,55 @@
+---
+title: "ALTER USER… IDENTIFIED BY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.029.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.059.html"
+redirects:
+  - /epas/latest/epas_compat_sql/15_alter_user_identified_by/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_user_identified_by" class="registered_link"></div>
+
+## Name
+
+`ALTER USER` &mdash; Change a database user account.
+
+## Synopsis
+
+```sql
+ALTER USER <role_name> IDENTIFIED BY <password> REPLACE <prev_password>
+```
+
+## Description
+
+A role without the `CREATEROLE` privilege can use this command to change their own password. An unprivileged role must include the `REPLACE` clause and their previous password if `PASSWORD_VERIFY_FUNCTION` isn't `NULL` in their profile. When a non-superuser uses the `REPLACE` clause, the server compares the password provided to the existing password and raises an error if the passwords don't match.
+
+A database superuser can use this command to change the password associated with any role. If a superuser includes the `REPLACE` clause, the clause is ignored. A non-matching value for the previous password doesn't throw an error.
+
+If the role for which the password is being changed has the `SUPERUSER` attribute, then a superuser must issue this command. A role with the `CREATEROLE` attribute can use this command to change the password associated with a role that isn't a superuser.
+
+## Parameters
+
+`role_name`
+
+ The name of the role whose password to alter.
+
+`password`
+
+ The role’s new password.
+
+`prev_password`
+
+ The role’s previous password.
+
+## Examples
+
+Change a user password:
+
+```sql
+ALTER USER john IDENTIFIED BY xyRP35z REPLACE 23PJ74a;
+```
+
+## See also
+
+[CREATE USER](41_create_user/#create_user), [DROP USER](61_drop_user/#drop_user)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/16_alter_user_role_profile_management_clauses.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/16_alter_user_role_profile_management_clauses.mdx
new file mode 100644
index 00000000000..2aff61cb006
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/16_alter_user_role_profile_management_clauses.mdx
@@ -0,0 +1,95 @@
+---
+title: "ALTER USER|ROLE… PROFILE MANAGEMENT CLAUSES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.030.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.060.html"
+redirects:
+  - /epas/latest/epas_compat_sql/16_alter_user_role_profile_management_clauses/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="alter_user_role_profile_management_clauses" class="registered_link"></div>
+
+## Name
+
+`ALTER USER|ROLE`
+
+## Synopsis
+
+```sql
+ALTER USER|ROLE <name> [[WITH] option[…]
+```
+
+`option` can be the following compatible clauses:
+
+```sql
+  PROFILE <profile_name>
+| ACCOUNT {LOCK|UNLOCK}
+| PASSWORD EXPIRE [AT '<timestamp>']
+```
+
+`option` can be the following non-compatible clauses:
+
+```sql
+| PASSWORD SET AT '<timestamp>'
+| LOCK TIME '<timestamp>'
+| STORE PRIOR PASSWORD {'<password>' '<timestamp>} [, ...]
+```
+
+For information about the administrative clauses of the `ALTER USER` or `ALTER ROLE` command that are supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+Only a database superuser can use the `ALTER USER|ROLE` clauses that enforce profile management. The clauses enforce the following behaviors:
+
+-   Include the `PROFILE` clause and a `profile_name` to associate a predefined profile with a role or to change the predefined profile associated with a user.
+
+-   Include the `ACCOUNT` clause and the `LOCK` or `UNLOCK` keyword to place the user account in a locked or unlocked state.
+
+-   Include the `LOCK TIME 'timestamp'` clause and a date/time value to lock the role at the specified time and unlock the role at the time indicated by the `PASSWORD_LOCK_TIME` parameter of the profile assigned to this role. If `LOCK TIME` is used with the `ACCOUNT LOCK` clause, only a database superuser can unlock the role with the `ACCOUNT UNLOCK` clause.
+
+-   Include the `PASSWORD EXPIRE` clause with the `AT 'timestamp'` keywords to specify a date/time for the password associated with the role to expire. If you omit the `AT 'timestamp'` keywords, the password expires immediately.
+
+-   Include the `PASSWORD SET AT 'timestamp'` keywords to set the password modification date to the time specified.
+
+-   Include the `STORE PRIOR PASSWORD {'password' 'timestamp} [, ...]` clause to modify the password history, adding the new password and the time the password was set.
+
+Each login role can have only one profile. To discover the profile that's currently associated with a login role, query the `profile` column of the `DBA_USERS` view.
+
+## Parameters
+
+`name`
+
+ The name of the role to associate with the specified profile.
+
+`password`
+
+ The password associated with the role.
+
+`profile_name`
+
+ The name of the profile to associate with the role.
+
+`timestamp`
+
+ The date and time when the clause is enforced. When specifying a value for `timestamp`, enclose the value in single quotes.
+
+## Notes
+
+For information about the Postgres-compatible clauses of the `ALTER USER` or `ALTER ROLE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-alterrole.html).
+
+## Examples
+
+This example uses the `ALTER USER… PROFILE` command to associate a profile named `acctg` with a user named `john`:
+
+```sql
+ALTER USER john PROFILE acctg_profile;
+```
+
+This example uses the `ALTER ROLE… PROFILE` command to associate a profile named `acctg` with a user named `john`:
+
+```sql
+ALTER ROLE john PROFILE acctg_profile;
+```
+
+## See also
+
+[CREATE USER|ROLE… PROFILE MANAGEMENT CLAUSES](42_create_user_role_profile_management_clauses/#create_user_role_profile_management_clauses)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/17_call.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/17_call.mdx
new file mode 100644
index 00000000000..2b85cdcf146
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/17_call.mdx
@@ -0,0 +1,43 @@
+---
+title: "CALL"
+redirects:
+  - /epas/latest/epas_compat_sql/17_call/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="call" class="registered_link"></div>
+
+## Name
+
+`CALL` &mdash; Invoke a procedure.
+
+## Synopsis
+
+```sql
+CALL <procedure_name> '('[<argument_list>]')'
+```
+
+## Description
+
+Use the `CALL` statement to invoke a procedure. To use the `CALL` statement, you must have `EXECUTE` privileges on the procedure that the `CALL` statement invokes.
+
+## Parameters
+
+`procedure_name`
+
+ The (optionally schema-qualified) procedure name.
+
+`argument_list`
+
+ Specifies a comma-separated list of arguments required by the procedure. Each member of `argument_list` corresponds to a formal argument expected by the procedure. Each formal argument can be an `IN` parameter, an `OUT` parameter, or an `INOUT` parameter.
+
+ !!!! Note
+    You must specify an `OUT` parameter in the `CALL` statement when calling a package function. The `OUT` parameter acts as an `INOUT` parameter during package overloading.
+
+## Examples
+
+The `CALL` statement can take several forms, depending on the arguments required by the procedure:
+
+```sql
+CALL update_balance();
+CALL update_balance(1,2,3);
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/18_comment.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/18_comment.mdx
new file mode 100644
index 00000000000..4a4acacfa13
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/18_comment.mdx
@@ -0,0 +1,64 @@
+---
+title: "COMMENT"
+redirects:
+  - /epas/latest/epas_compat_sql/18_comment/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="comment" class="registered_link"></div>
+
+## Name
+
+`COMMENT` &mdash; Define or change the comment of an object.
+
+## Synopsis
+
+```sql
+COMMENT ON
+{
+  TABLE <table_name> |
+  COLUMN <table_name.column_name>
+} IS '<text>'
+```
+
+## Description
+
+`COMMENT` stores a comment about a database object. To modify a comment, issue a new `COMMENT` command for the same object. Only one comment string is stored for each object. To remove a comment, specify an empty string (two consecutive single quotes with no intervening space) for `text`. Comments are dropped when the object is dropped.
+
+## Parameters
+
+`table_name`
+
+ The name of the table (optionally schema-qualified) to comment. 
+
+`table_name.column_name`
+
+ The name of a column (optionally schema-qualified) in `table_name` to comment. 
+
+`text`
+
+ The new comment.
+
+## Notes
+
+There is currently no security mechanism for comments. Any user connected to a database can see all the comments for objects in that database, although only superusers can change comments for objects that they don’t own. Don't put security-critical information in a comment.
+
+## Examples
+
+Attach a comment to the table `emp`:
+
+```sql
+COMMENT ON TABLE emp IS 'Current employee information';
+```
+
+Attach a comment to the `empno` column of the `emp` table:
+
+```sql
+COMMENT ON COLUMN emp.empno IS 'Employee identification number';
+```
+
+Remove these comments:
+
+```sql
+COMMENT ON TABLE emp IS '';
+COMMENT ON COLUMN emp.empno IS '';
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19_commit.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19_commit.mdx
new file mode 100644
index 00000000000..bc81ee044a7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19_commit.mdx
@@ -0,0 +1,46 @@
+---
+title: "COMMIT"
+redirects:
+  - /epas/latest/epas_compat_sql/19_commit/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="commit" class="registered_link"></div>
+
+## Name
+
+`COMMIT` &mdash; Commit the current transaction.
+
+## Synopsis
+
+```sql
+COMMIT [ WORK ]
+```
+
+## Description
+
+`COMMIT` commits the current transaction. All changes made by the transaction become visible to others and are guaranteed to be durable if a crash occurs.
+
+## Parameters
+
+`WORK`
+
+ Optional keyword that has no effect.
+
+## Notes
+
+Use `ROLLBACK` to abort a transaction. Issuing `COMMIT` when not inside a transaction does no harm.
+
+!!! Note
+    Executing a `COMMIT` in a plpgsql procedure throws an error if there's an Oracle-style SPL procedure on the runtime stack.
+
+## Examples
+
+To commit the current transaction and make all changes permanent:
+
+```sql
+COMMIT;
+```
+
+## See also
+
+[ROLLBACK](68_rollback/#rollback), [ROLLBACK TO SAVEPOINT](69_rollback_to_savepoint/#rollback_to_savepoint)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19a_create_capture_privilege.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19a_create_capture_privilege.mdx
new file mode 100644
index 00000000000..64faa8fe76c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/19a_create_capture_privilege.mdx
@@ -0,0 +1,61 @@
+---
+title: "CREATE CAPTURE PRIVILEGES POLICY"
+---
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle with the `CREATE CAPTURE PRIVILEGES POLICY` SQL command. 
+
+## Name
+
+`CREATE CAPTURE PRIVILEGES POLICY` &mdash; Create a new capture privilege policy.
+
+## Synopsis
+
+Use `CREATE CAPTURE PRIVILEGES POLICY` to define a new policy to capture privileges:
+
+```sql
+## Create a policy on database
+CREATE CAPTURE PRIVILEGES POLICY <name> [ WHERE ( <expression> ) ];
+
+## Create a policy on a ROLE/USER
+CREATE CAPTURE PRIVILEGES POLICY <name> ON { ROLE | USER } <role_names> [ WHERE ( <expression> ) ];
+```
+
+## Description
+
+The `CREATE CAPTURE PRIVILEGES POLICY` command allows a database superuser or any user with the system-defined `CAPTURE_ADMIN` privilege to create a policy in the database.
+
+If the name of the policy is schema-qualified, the policy is created in the specified schema. If the `CREATE CAPTURE PRIVILEGES POLICY` command doesn't include a schema, the policy is created in the current schema. 
+
+Use `DROP CAPTURE PRIVILEGES POLICY` to remove a capture policy.
+
+## Parameters
+
+`name`
+
+ The name optionally schema-qualified of the capture privilege policy to create.
+
+`expression`
+
+ Boolean expression containing up to 4000 characters.  
+
+`role_names`
+
+ The roles whose privileges are to be analyzed.
+
+## Examples
+
+This command creates a capture privilege policy named `sampledb_p1` on the database:
+
+```sql
+CREATE CAPTURE PRIVILEGES POLICY sampledb_p1;
+```
+
+This command creates a capture privilege policy named `sampledb_p2` on role `sampledb_role1` and `sampledb_user1`:
+
+```sql
+CREATE CAPTURE PRIVILEGES POLICY sampledb_p2 ON ROLE sampledb_role1,sampledb_user1;
+```
+
+## See also
+
+[ALTER CAPTURE PRIVILEGE POLICY](01_alter_capture_privilege), [DROP CAPTURE PRIVILEGE POLICY](44a_drop_capture_privilege)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/20_create_database.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/20_create_database.mdx
new file mode 100644
index 00000000000..2781f1d991a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/20_create_database.mdx
@@ -0,0 +1,49 @@
+---
+title: "CREATE DATABASE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.034.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.064.html"
+redirects:
+  - /epas/latest/epas_compat_sql/20_create_database/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_database" class="registered_link"></div>
+
+## Name
+
+`CREATE DATABASE` &mdash; Create a database.
+
+## Synopsis
+
+```sql
+CREATE DATABASE <name>
+```
+
+## Description
+
+`CREATE DATABASE` creates a database.
+
+To create a database, you must be a superuser or have the `CREATEDB` privilege. Normally, the creator becomes the owner of the new database. Non-superusers with the `CREATEDB` privilege can create only databases they own.
+
+The new database is a clone of the standard system database `template1`.
+
+## Parameters
+
+`name`
+
+ The name of the database to create.
+
+## Notes
+
+You can't execute `CREATE DATABASE` inside a transaction block.
+
+Errors along the line of “could not initialize database directory” are most likely related to insufficient permissions on the data directory, a full disk, or other file system problems.
+
+## Examples
+
+To create a database:
+
+```sql
+CREATE DATABASE employees;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx
new file mode 100644
index 00000000000..e1db1a6e95f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/21_create_public_database_link.mdx
@@ -0,0 +1,613 @@
+---
+title: "CREATE PUBLIC DATABASE LINK"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.035.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.065.html"
+redirects:
+  - /epas/latest/epas_compat_sql/21_create_public_database_link/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_public_database_link" class="registered_link"></div>
+
+## Name
+
+`CREATE [PUBLIC] DATABASE LINK` &mdash; Create a database link.
+
+## Synopsis
+
+```sql
+CREATE [ PUBLIC ] DATABASE LINK <name>
+  CONNECT TO { CURRENT_USER |
+               <username> IDENTIFIED BY '<password>'}
+  USING { postgres_fdw '<fdw_connection_string>' |
+        [ oci ] '<oracle_connection_string>' }
+```
+
+## Description
+
+`CREATE DATABASE LINK` creates a database link. A database link is an object that allows a reference to a table or view in a remote database in a `DELETE`, `INSERT`, `SELECT` or `UPDATE` command. Reference a database link by appending `@dblink` to the table or view name referenced in the SQL command, where `dblink` is the name of the database link.
+
+Database links can be *public* or *private*. A public database link is one that any user can use. Only the database link's owner can use a private database link. Specify the `PUBLIC` option to create a public database link. Otherwise, a private database link is created.
+
+When you use the `CREATE DATABASE LINK` command, the database link name and the given connection attributes are stored in the EDB Postgres Advanced Server system table named `pg_catalog.edb_dblink`. When using a given database link, the database containing the `edb_dblink` entry defining this database link is called the *local database*. The server and database whose connection attributes are defined in the `edb_dblink` entry is called the *remote database*. You can use `edb_dblink_oci` to access remote Oracle tables and views using any `SELECT`, `INSERT`, `UPDATE`, or `DELETE` statement.
+ 
+You must be connected to the local database when you issue a SQL command containing a reference to a database link. When the SQL command executes, the appropriate authentication and connection is made to the remote database to access the table or view to which the `@dblink` reference is appended.
+
+!!!note "Oracle compatibility"
+-  For EDB Postgres Advanced Server 16, the CREATE DATABASE LINK command has been tested and certified with all the minor versions for use with Oracle versions 10g Release 2, 11g Release 2, 12c Release 1, 18c Release 1, 19c, 21c, and 23.
+!!!
+    
+!!!note
+- You can't use a database link to access a remote database in a standby database server. Standby database servers are for high availability, load balancing, and replication.
+  
+  For information about high availability, load balancing, and replication for Postgres database servers, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/high-availability.html).
+-  You can set the `edb_dblink_oci.rescans` GUC to `SCROLL` or `SERIALIZABLE` at the server level in the `postgresql.conf` file. You can also set it at the session level using the `SET` command. However, the setting isn't applied to existing dblink connections due to dblink connection caching.
+-  When executing `SELECT` on LOB data of more than 4000 characters, we recommend using `edb_dblink_oci.rescans=serializable` to free up the temporary PGA memory and avoid exceeding `PGA_AGGREGATE_LIMIT`.
+!!!
+    
+The `edb_dblink_oci` supports both types of rescans: `SCROLL` and `SERIALIZABLE`. By default it's set to `SERIALIZABLE`. When set to `SERIALIZABLE`, `edb_dblink_oci` uses the `SERIALIZABLE` transaction isolation level on the Oracle side, which corresponds to PostgreSQL’s `REPEATABLE READ`. This is necessary because a single PostgreSQL statement can lead to multiple Oracle queries. It thereby uses a serializable isolation level to provide consistent results.
+
+A serialization failure can occur when modifying a table concurrent with long-running DML transactions, for example, `ADD`, `UPDATE`, or `DELETE` statements. If such a failure occurs, the OCI reports `ORA-08177: can't serialize access for this transaction`, and the application must retry the transaction.
+
+A `SCROLL` rescan is quick, but each iteration resets the current row position to `1`. A `SERIALIZABLE` rescan has performance benefits over a `SCROLL` rescan.
+
+## Parameters
+
+`PUBLIC`
+
+ Create a public database link that any user can use. If you omit this parameter, then the database link is private and only the database link’s owner can use it.
+
+`name`
+
+ The name of the database link.
+
+`username`
+
+ The username to use for connecting to the remote database.
+
+`CURRENT_USER`
+
+ Include `CURRENT_USER` to use the user mapping associated with the role that's using the link when establishing a connection to the remote server.
+
+`password`
+
+ The password for `username`.
+
+`postgres_fdw`
+
+ Specifies foreign data wrapper `postgres_fdw` as the connection to a remote EDB Postgres Advanced Server database. If `postgres_fdw` isn't installed on the database, use the `CREATE EXTENSION` command to install `postgres_fdw`. For more information, see the `CREATE EXTENSION` command in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createextension.html).
+
+`fdw_connection_string`
+
+ Specifies the connection information for the `postgres_fdw` foreign data wrapper.
+
+`oci`
+
+ Specifies a connection to a remote Oracle database. This is the default behavior.
+
+`oracle_connection_string`
+
+ Specifies the connection information for an oci connection.
+
+!!! Note
+
+    To create a non-public database link, you need the `CREATE DATABASE LINK` privilege. To create a public database link, you need the `CREATE PUBLIC DATABASE LINK` privilege.
+
+## Setting up an Oracle instant client for OCI database link
+
+To use `edb_dblink_oci`, you must download and install an Oracle instant client on the host running the EDB Postgres Advanced Server database in which you want to create the database link.
+
+You can download an instant client [here](http://www.oracle.com/technetwork/database/features/instant-client/index-097480.html).
+
+### Oracle instant client for Linux
+
+These instructions apply to Linux hosts running EDB Postgres Advanced Server.
+
+Be sure the `libaio` library (the Linux-native asynchronous I/O facility) is installed on the Linux host running EDB Postgres Advanced Server.
+
+You can install the `libaio` library with the following command:
+
+```shell
+yum install libaio
+```
+
+If the Oracle instant client that you downloaded doesn't include the file named `libclntsh.so` without a version number suffix, create a symbolic link named `libclntsh.so` that points to the downloaded version of the library file. To do so, navigate to the instant client directory and execute the following command:
+
+```shell
+ln -s libclntsh.so.<version> libclntsh.so
+```
+
+Where `version` is the version number of the `libclntsh.so` library. For example:
+
+```shell
+ln -s libclntsh.so.12.1 libclntsh.so
+```
+
+When executing a SQL command that references a database link to a remote Oracle database, EDB Postgres Advanced Server must know where the Oracle instant client library resides on the EDB Postgres Advanced Server host.
+
+The `LD_LIBRARY_PATH` environment variable must include the path to the Oracle client installation directory containing the `libclntsh.so` file. For example, if the installation directory containing `libclntsh.so` is `/tmp/instantclient`, use:
+
+```shell
+export LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH
+```
+
+Alternatively, you can set the value of the `oracle_home` configuration parameter in the
+`postgresql.conf` file. The `oracle_home` configuration parameter is an alternative to the
+`LD_LIBRARY_PATH` environment variable. For more details on the `oracle_home` configuration
+parameter, see [configuration parameters](../../database_administrator_reference/01_introduction/05_oracle_home/).
+
+The `ORACLE_HOME` environment variable must be set and include the path to the Oracle home directory. For example, 
+
+```text
+export ORACLE_HOME=/opt/product/version/dbhomeXE
+```
+
+!!! Note
+    You must set either the `LD_LIBRARY_PATH` or the `oracle_home` configuration parameter and the `ORACLE_HOME` environment variable before executing the `pg_ctl` utility to start or restart EDB Postgres Advanced Server.
+
+If you're running the current session as the user account (for example, `enterprisedb`) that directly invokes `pg_ctl` to start or restart EDB Postgres Advanced Server, then set either the `LD_LIBRARY_PATH` environment variable or the `oracle_home` configuration parameter and the `ORACLE_HOME` environment variable before invoking `pg_ctl`.
+
+You can set the `LD_LIBRARY_PATH` and the `ORACLE_HOME` environment variable in the `.bash_profile` file under the home directory of the `enterprisedb` user account. That is, set `LD_LIBRARY_PATH` and `ORACLE_HOME` in the file `~enterprisedb/.bash_profile`. This setting ensures that `LD_LIBRARY_PATH` and `ORACLE_HOME` are set when you log in as `enterprisedb`.
+
+If you're using a Linux service script with the `systemctl` or `service` command to start or restart EDB Postgres Advanced Server, you must set `LD_LIBRARY_PATH` and `ORACLE_HOME` so it's in effect when the script invokes the `pg_ctl` utility.
+
+For example, to set an environment variable for EDB Postgres Advanced Server, you can create a file named `/etc/systemd/system/edb-as-14.service`. Include `/lib/systemd/system/edb-as-14.service` in the file.
+
+If the `LD_LIBRARY_PATH=/tmp/instantclient`, include the environment variable by specifying:
+
+```shell
+[Service]
+Environment=LD_LIBRARY_PATH=/tmp/instantclient:$LD_LIBRARY_PATH
+Environment=ORACLE_HOME=/tmp/instantclient
+```
+
+Reload systemd:
+
+```shell
+systemctl daemon-reload
+```
+
+Restart the EDB Postgres Advanced Server service:
+
+```shell
+systemctl restart edb-as-14
+```
+
+The script file that you need to modify to include the `LD_LIBRARY_PATH` setting depends on the EDB Postgres Advanced Server version and the Linux system on which it was installed.
+
+
+### Oracle instant client for Windows
+
+These instructions apply to Windows hosts running EDB Postgres Advanced Server.
+
+When you're executing a SQL command that references a database link to a remote Oracle database, EDB Postgres Advanced Server must know where the Oracle instant client library resides on the EDB Postgres Advanced Server host.
+
+Set the Windows `PATH` system environment variable to include the Oracle client installation directory that contains the `oci.dll` file.
+
+Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The value specified in the `oracle_home` configuration parameter overrides the Windows `PATH` environment variable.
+
+To set the `oracle_home` configuration parameter in the `postgresql.conf` file, add the following line:
+
+```ini
+oracle_home = 'lib_directory'
+```
+
+Substitute the name of the Windows directory that contains `oci.dll` for `lib_directory`. For example:
+
+```ini
+oracle_home = 'C:/tmp/instantclient_10_2'
+```
+
+After setting the `PATH` environment variable or the `oracle_home` configuration parameter, you must restart the server for the changes to take effect. Restart the server from the Windows Services console.
+
+!!! Note
+    If `tnsnames.ora` is configured in failover mode, and a client:server failure occurs, the client connection is established with a secondary server (usually a backup server). Later, when the primary server resumes, the client retains its connection to a secondary server until a new session is established. The new client connections is automatically established with the primary server. If the primary and secondary servers are out of sync, then the clients that established a connection to the secondary server and the clients that later connected to the primary server might see a different database view.
+
+## Examples
+
+### Creating an OCI database link
+
+This example uses the `CREATE DATABASE LINK` command to create a database link named `chicago` that connects an instance of EDB Postgres Advanced Server to an Oracle server using an `edb_dblink_oci` connection. The connection information tells EDB Postgres Advanced Server to log in to Oracle as the user `admin` whose password is `mypassword`. Including the `oci` option tells EDB Postgres Advanced Server that this is an `edb_dblink_oci` connection. The connection string `'//127.0.0.1/acctg'` specifies the server address and name of the database.
+
+```sql
+CREATE DATABASE LINK chicago
+  CONNECT TO admin IDENTIFIED BY 'mypassword'
+  USING oci '//127.0.0.1/acctg';
+```
+
+!!! Note
+    You can specify a hostname in the connection string in place of an IP address.
+
+### Creating a postgres_fdw database link
+
+This example uses the `CREATE DATABASE LINK` command to create a database link named `bedford`. The database link connects an instance of EDB Postgres Advanced Server to another EDB Postgres Advanced Server instance by way of a `postgres_fdw` foreign data wrapper connection. The connection information tells EDB Postgres Advanced Server to log in as the user `admin` with the password `mypassword`. Including the `postgres_fdw` option tells EDB Postgres Advanced Server that this is a `postgres_fdw` connection. The connection string, `'host=127.0.0.1 port=5444 dbname=marketing'` specifies the server address and name of the database.
+
+```sql
+CREATE DATABASE LINK bedford
+  CONNECT TO admin IDENTIFIED BY 'mypassword'
+  USING postgres_fdw 'host=127.0.0.1 port=5444 dbname=marketing';
+```
+
+!!! Note
+    You can specify a hostname in the connection string in place of an IP address.
+
+## Using a database link
+
+These examples use a database link with EDB Postgres Advanced Server to connect to an Oracle database. The examples assume that a copy of the EDB Postgres Advanced Server sample application’s `emp` table was created in an Oracle database. A second EDB Postgres Advanced Server database cluster with the sample application is accepting connections at port `5443`.
+
+Create a public database link, named `oralink`, to an Oracle database named `xe` located at `127.0.0.1` on port `1521`. Connect to the Oracle database with the username `edb` and password `password`.
+
+```sql
+CREATE PUBLIC DATABASE LINK oralink CONNECT TO edb IDENTIFIED BY 'password'
+USING '//127.0.0.1:1521/xe';
+```
+
+Issue a `SELECT` command on the `emp` table in the Oracle database using the database link `oralink`.
+
+```sql
+SELECT * FROM emp@oralink;
+__OUTPUT__
+ empno | ename  |    job    | mgr  |      hiredate      | sal  | comm | deptno
+-------+--------+-----------+------+--------------------+------+------+--------
+  7369 | SMITH  | CLERK     | 7902 | 17-DEC-80 00:00:00 |  800 |      |     20
+  7499 | ALLEN  | SALESMAN  | 7698 | 20-FEB-81 00:00:00 | 1600 |  300 |     30
+  7521 | WARD   | SALESMAN  | 7698 | 22-FEB-81 00:00:00 | 1250 |  500 |     30
+  7566 | JONES  | MANAGER   | 7839 | 02-APR-81 00:00:00 | 2975 |      |     20
+  7654 | MARTIN | SALESMAN  | 7698 | 28-SEP-81 00:00:00 | 1250 | 1400 |     30
+  7698 | BLAKE  | MANAGER   | 7839 | 01-MAY-81 00:00:00 | 2850 |      |     30
+  7782 | CLARK  | MANAGER   | 7839 | 09-JUN-81 00:00:00 | 2450 |      |     10
+  7788 | SCOTT  | ANALYST   | 7566 | 19-APR-87 00:00:00 | 3000 |      |     20
+  7839 | KING   | PRESIDENT |      | 17-NOV-81 00:00:00 | 5000 |      |     10
+  7844 | TURNER | SALESMAN  | 7698 | 08-SEP-81 00:00:00 | 1500 |    0 |     30
+  7876 | ADAMS  | CLERK     | 7788 | 23-MAY-87 00:00:00 | 1100 |      |     20
+  7900 | JAMES  | CLERK     | 7698 | 03-DEC-81 00:00:00 |  950 |      |     30
+  7902 | FORD   | ANALYST   | 7566 | 03-DEC-81 00:00:00 | 3000 |      |     20
+  7934 | MILLER | CLERK     | 7782 | 23-JAN-82 00:00:00 | 1300 |      |     10
+(14 rows)
+```
+
+Create a private database link, named `fdwlink`, to the EDB Postgres Advanced Server database named `edb` located on host `192.168.2.22` running on port `5444`. Connect to the EDB Postgres Advanced Server database with the username `enterprisedb` and password `password`.
+
+```sql
+CREATE DATABASE LINK fdwlink CONNECT TO enterprisedb IDENTIFIED BY
+'password' USING postgres_fdw 'host=192.168.2.22 port=5444 dbname=edb';
+```
+
+Display attributes of database links `oralink` and `fdwlink` from the local `edb_dblink` system table:
+
+```sql
+SELECT lnkname, lnkuser, lnkconnstr FROM pg_catalog.edb_dblink;
+__OUTPUT__
+ lnkname |   lnkuser    |               lnkconnstr
+---------+--------------+----------------------------------------
+ oralink | edb          | //127.0.0.1:1521/xe
+ fdwlink | enterprisedb |
+(2 rows)
+```
+
+Perform a join of the `emp` table from the Oracle database with the `dept` table from the EDB Postgres Advanced Server database:
+
+```sql
+SELECT d.deptno, d.dname, e.empno, e.ename, e.job, e.sal, e.comm FROM
+emp@oralink e, dept@fdwlink d WHERE e.deptno = d.deptno ORDER BY 1, 3;
+__OUTPUT__
+ deptno |   dname    | empno | ename  |    job    | sal  | comm
+--------+------------+-------+--------+-----------+------+------
+     10 | ACCOUNTING |  7782 | CLARK  | MANAGER   | 2450 |
+     10 | ACCOUNTING |  7839 | KING   | PRESIDENT | 5000 |
+     10 | ACCOUNTING |  7934 | MILLER | CLERK     | 1300 |
+     20 | RESEARCH   |  7369 | SMITH  | CLERK     |  800 |
+     20 | RESEARCH   |  7566 | JONES  | MANAGER   | 2975 |
+     20 | RESEARCH   |  7788 | SCOTT  | ANALYST   | 3000 |
+     20 | RESEARCH   |  7876 | ADAMS  | CLERK     | 1100 |
+     20 | RESEARCH   |  7902 | FORD   | ANALYST   | 3000 |
+     30 | SALES      |  7499 | ALLEN  | SALESMAN  | 1600 |  300
+     30 | SALES      |  7521 | WARD   | SALESMAN  | 1250 |  500
+     30 | SALES      |  7654 | MARTIN | SALESMAN  | 1250 | 1400
+     30 | SALES      |  7698 | BLAKE  | MANAGER   | 2850 |
+     30 | SALES      |  7844 | TURNER | SALESMAN  | 1500 |    0
+     30 | SALES      |  7900 | JAMES  | CLERK     |  950 |
+(14 rows)
+```
+
+## Push down for an OCI database link
+
+When the OCI database link is used to execute SQL statements on a remote Oracle database, sometimes the *pushdown* of the processing occurs on the foreign server.
+
+Push down refers to the occurrence of processing on the foreign that is, remote server instead of the local client where the SQL statement was issued. Push down can result in performance improvement since the data is processed on the remote server before being returned to the local client.
+
+OCI database link supports push down for
+- WHERE clause 
+- JOIN operations
+- AGGREGATE functions
+- ORDER BY clause
+
+For push down to occur, some basic conditions must be met. The tables involved in the join operation must belong to the same foreign server and use the identical connection information to the foreign server. This connection information is the same database link defined with the `CREATE DATABASE LINK` command.
+
+To determine whether to use push down for a SQL statement, display the execution plan by using the `EXPLAIN` command. For information about the `EXPLAIN` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-explain.html).
+
+You can restrict the push downs using the `edb_dbLink_oci_pushdown.config` configuration file. You can define the list of functions and operators in this file that can push down to the remote server. You can easily add or modify the list as per the requirements.
+
+This file lists the objects as aggregates, functions, and operators allowed to push down to the remote server. Put each entry on a single line. Each entry must have two columns:
+-   Object type that can be ROUTINE (functions, aggregates, and procedures) or OPERATOR.
+-   The second column is schema-qualified object names with their arguments.
+
+You can format the second column using the following query:
+
+For ROUTINES:
+
+```sql
+SELECT pronamespace::regnamespace || '.' || oid::regprocedure FROM pg_proc
+WHERE proname = '<routine_name>'
+```
+
+For OPERATORS:
+
+```sql
+SELECT oprnamespace::regnamespace || '.' || oid::regoperator FROM pg_operator
+WHERE oprname = '<operator_name>'
+```
+
+Example of `edb_dbLink_oci_pushdown.config` file:
+
+```shell
+ROUTINE pg_catalog.sum(bigint)
+ROUTINE pg_catalog.sum(smallint)
+ROUTINE pg_catalog.to_number(text)
+ROUTINE pg_catalog.to_number(text,text)
+OPERATOR pg_catalog.=(integer,integer)
+OPERATOR pg_catalog.=(text,text)
+OPERATOR pg_catalog.=(smallint,integer)
+OPERATOR pg_catalog.=(bigint,integer)
+OPERATOR pg_catalog.=(numeric,numeric)
+```
+
+To find out whether pushdown is used for a SQL statement, display the execution plan by using the `EXPLAIN` command.
+
+These examples use the following database link:
+
+```sql
+CREATE PUBLIC DATABASE LINK oralink CONNECT TO edb IDENTIFIED BY 'password'
+USING '//192.168.2.23:1521/xe';
+```
+
+This example shows the execution plan of an inner join:
+
+```sql
+EXPLAIN (verbose,costs off) SELECT d.deptno, d.dname, e.empno, e.ename FROM
+dept@oralink d, emp@oralink e WHERE d.deptno = e.deptno ORDER BY 1, 3;
+
+                                        QUERY PLAN
+--------------------------------------------------------------------------------
+ Foreign Scan
+   Output: d.deptno, d.dname, e.empno, e.ename
+   Relations: (_dblink_dept_1 d) INNER JOIN (_dblink_emp_2 e)
+   Remote Query: SELECT r1.deptno, r1.dname, r2.empno, r2.ename FROM (dept r1 INNER 
+JOIN emp r2 ON ((r1.deptno = r2.deptno))) ORDER BY r1.deptno ASC NULLS LAST, r2.empno ASC NULLS LAST
+(4 rows)
+# The `INNER JOIN` operation occurs under the Foreign Scan section. The output of this join is the following:
+__OUTPUT__
+deptno |   dname    | empno | ename
+-------+------------+-------+--------
+    10 | ACCOUNTING |  7782 | CLARK
+    10 | ACCOUNTING |  7839 | KING
+    10 | ACCOUNTING |  7934 | MILLER
+    20 | RESEARCH   |  7369 | SMITH
+    20 | RESEARCH   |  7566 | JONES
+    20 | RESEARCH   |  7788 | SCOTT
+    20 | RESEARCH   |  7876 | ADAMS
+    20 | RESEARCH   |  7902 | FORD
+    30 | SALES      |  7499 | ALLEN
+    30 | SALES      |  7521 | WARD
+    30 | SALES      |  7654 | MARTIN
+    30 | SALES      |  7698 | BLAKE
+    30 | SALES      |  7844 | TURNER
+    30 | SALES      |  7900 | JAMES
+(14 rows)
+```
+
+This example shows the execution plan of an left outer join:
+
+```sql
+EXPLAIN (verbose,costs off) SELECT d.deptno, d.dname, e.empno, e.ename FROM
+dept@oralink d LEFT OUTER JOIN emp@oralink e ON d.deptno = e.deptno ORDER BY 1, 3;
+
+                                        QUERY PLAN
+--------------------------------------------------------------------------------
+ Foreign Scan
+   Output: d.deptno, d.dname, e.empno, e.ename
+   Relations: (_dblink_dept_1 d) LEFT JOIN (_dblink_emp_2 e)
+   Remote Query: SELECT r1.deptno, r1.dname, r2.empno, r2.ename FROM (dept r1 LEFT JOIN 
+emp r2 ON ((r1.deptno = r2.deptno))) ORDER BY r1.deptno ASC NULLS LAST, r2.empno ASC NULLS LAST
+(4 rows)
+# The output of this join is the following:
+__OUTPUT__
+deptno |   dname    | empno | ename
+-------+------------+-------+--------
+    10 | ACCOUNTING |  7782 | CLARK
+    10 | ACCOUNTING |  7839 | KING
+    10 | ACCOUNTING |  7934 | MILLER
+    20 | RESEARCH   |  7369 | SMITH
+    20 | RESEARCH   |  7566 | JONES
+    20 | RESEARCH   |  7788 | SCOTT
+    20 | RESEARCH   |  7876 | ADAMS
+    20 | RESEARCH   |  7902 | FORD
+    30 | SALES      |  7499 | ALLEN
+    30 | SALES      |  7521 | WARD
+    30 | SALES      |  7654 | MARTIN
+    30 | SALES      |  7698 | BLAKE
+    30 | SALES      |  7844 | TURNER
+    30 | SALES      |  7900 | JAMES
+    40 | OPERATIONS |       |
+(15 rows)
+```
+
+This example shows the execution plan of ORDER BY clause:
+
+```sql
+EXPLAIN (verbose, costs off)
+ SELECT department_id, COUNT(*), SUM(salary), AVG(salary), MIN(salary), MAX(salary), ROUND(STDDEV(salary)), SUM(salary) * aggpd_pkg.pkgvar as sum2 
+ FROM employees@oralink
+ WHERE department_id < 50 
+ GROUP BY department_id 
+ ORDER BY 1;    
+                                              QUERY PLAN                                                                                                           
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
+ Foreign Scan
+   Output: department_id, (count(*)), (sum(salary)), (avg(salary)), (min(salary)), (max(salary)), (round(stddev(salary), 0)), ((sum(salary)) * (public.aggpd_pkg.pkgvar)::numeric)
+   Relations: Aggregate on (_dblink_employees_1 employees)
+   Remote Query: SELECT department_id, count(*), sum(salary), avg(salary), min(salary), max(salary), round(stddev(salary), 0) FROM employees WHERE (department_id < 50) GROUP BY department_id ORDER BY department_id ASC NULLS LAST
+(4 rows)
+```
+
+This example shows a case where the entire processing isn't pushed down because the `emp` joined table resides locally instead of on the same foreign server:
+
+```sql
+EXPLAIN (verbose,costs off) SELECT d.deptno, d.dname, e.empno, e.ename FROM
+dept@oralink d LEFT OUTER JOIN emp e ON d.deptno = e.deptno ORDER BY 1, 3;
+
+                            QUERY PLAN
+------------------------------------------------------------------
+ Sort
+   Output: d.deptno, d.dname, e.empno, e.ename
+   Sort Key: d.deptno, e.empno
+   ->  Hash Left Join
+         Output: d.deptno, d.dname, e.empno, e.ename
+         Hash Cond: (d.deptno = e.deptno)
+         ->  Foreign Scan on _dblink_dept_1 d
+               Output: d.deptno, d.dname, d.loc
+               Remote Query: SELECT deptno, dname, NULL FROM dept
+         ->  Hash
+               Output: e.empno, e.ename, e.deptno
+               ->  Seq Scan on public.emp e
+                     Output: e.empno, e.ename, e.deptno
+(13 rows)
+```
+
+The output of this join is the same as the previous left-outer-join example.
+
+## Creating a foreign table from a database link
+
+!!! Note
+    This procedure isn't compatible with Oracle databases.
+
+After you create a database link, you can create a foreign table based on this database link. You can then use the foreign table to access the remote table, referencing it with the foreign table name instead of using the database link syntax. Using the database link requires appending `@dblink` to the table or view name referenced in the SQL command, where `dblink` is the name of the database link.
+
+You can use this technique for either an oci-dblink connection for remote Oracle access or a `postgres_fdw` connection for remote Postgres access.
+
+This example creates a foreign table to access a remote Oracle table.
+
+The following creates a database link named `oralink` for connecting to the Oracle database:
+
+```sql
+CREATE PUBLIC DATABASE LINK oralink CONNECT TO edb IDENTIFIED BY 'password'
+USING '//127.0.0.1:1521/xe';
+```
+
+The following query shows the database link:
+
+```sql
+SELECT lnkname, lnkuser, lnkconnstr FROM pg_catalog.edb_dblink;
+__OUTPUT__
+ lnkname | lnkuser |     lnkconnstr
+---------+---------+---------------------
+ oralink | edb     | //127.0.0.1:1521/xe
+(1 row)
+```
+
+When you create the database link, EDB Postgres Advanced Server creates a corresponding foreign server. The following query displays the foreign server:
+
+```sql
+SELECT srvname, srvowner, srvfdw, srvtype, srvoptions FROM
+pg_foreign_server;
+__OUTPUT__
+ srvname | srvowner | srvfdw | srvtype |          srvoptions
+---------+----------+--------+---------+-------------------------------
+ oralink |       10 |  14005 |         | {connstr=//127.0.0.1:1521/xe}
+(1 row)
+```
+
+For more information about foreign servers, see the `CREATE SERVER` command in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createserver.html).
+
+Create the foreign table:
+
+```sql
+CREATE FOREIGN TABLE emp_ora (
+    empno           NUMERIC(4),
+    ename           VARCHAR(10),
+    job             VARCHAR(9),
+    mgr             NUMERIC(4),
+    hiredate        TIMESTAMP WITHOUT TIME ZONE,
+    sal             NUMERIC(7,2),
+    comm            NUMERIC(7,2),
+    deptno          NUMERIC(2)
+)
+  SERVER oralink
+  OPTIONS (table_name 'emp', schema_name 'edb'
+);
+```
+
+Note the following in the `CREATE FOREIGN TABLE` command:
+
+-   The name specified in the `SERVER` clause at the end of the `CREATE FOREIGN TABLE` command is the name of the foreign server, which is `oralink` in this example. You can see this name in the `srvname` column from the query on `pg_foreign_server`.
+-   The table name and schema name are specified in the `OPTIONS` clause by the `table` and `schema` options.
+-   The column names specified in the `CREATE FOREIGN TABLE` command must match the column names in the remote table.
+-   Generally, `CONSTRAINT` clauses can't be accepted or enforced on the foreign table. They are assumed to have been defined on the remote table.
+
+For more information about the `CREATE FOREIGN TABLE` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createforeigntable.html).
+
+The following is a query on the foreign table:
+
+```sql
+SELECT * FROM emp_ora;
+__OUTPUT__
+ empno | ename  |    job    | mgr  |      hiredate      |   sal   |  comm   | deptno
+-------+--------+-----------+------+--------------------+---------+---------+--------
+  7369 | SMITH  | CLERK     | 7902 | 17-DEC-80 00:00:00 |  800.00 |         |     20
+  7499 | ALLEN  | SALESMAN  | 7698 | 20-FEB-81 00:00:00 | 1600.00 |  300.00 |     30
+  7521 | WARD   | SALESMAN  | 7698 | 22-FEB-81 00:00:00 | 1250.00 |  500.00 |     30
+  7566 | JONES  | MANAGER   | 7839 | 02-APR-81 00:00:00 | 2975.00 |         |     20
+  7654 | MARTIN | SALESMAN  | 7698 | 28-SEP-81 00:00:00 | 1250.00 | 1400.00 |     30
+  7698 | BLAKE  | MANAGER   | 7839 | 01-MAY-81 00:00:00 | 2850.00 |         |     30
+  7782 | CLARK  | MANAGER   | 7839 | 09-JUN-81 00:00:00 | 2450.00 |         |     10
+  7788 | SCOTT  | ANALYST   | 7566 | 19-APR-87 00:00:00 | 3000.00 |         |     20
+  7839 | KING   | PRESIDENT |      | 17-NOV-81 00:00:00 | 5000.00 |         |     10
+  7844 | TURNER | SALESMAN  | 7698 | 08-SEP-81 00:00:00 | 1500.00 |    0.00 |     30
+  7876 | ADAMS  | CLERK     | 7788 | 23-MAY-87 00:00:00 | 1100.00 |         |     20
+  7900 | JAMES  | CLERK     | 7698 | 03-DEC-81 00:00:00 |  950.00 |         |     30
+  7902 | FORD   | ANALYST   | 7566 | 03-DEC-81 00:00:00 | 3000.00 |         |     20
+  7934 | MILLER | CLERK     | 7782 | 23-JAN-82 00:00:00 | 1300.00 |         |     10
+(14 rows)
+```
+
+In contrast, the following is a query on the same remote table but using the database link instead of the foreign table:
+
+```sql
+SELECT * FROM emp@oralink;
+__OUTPUT__
+ empno | ename  |    job    | mgr  |      hiredate      | sal  | comm | deptno
+-------+--------+-----------+------+--------------------+------+------+--------
+  7369 | SMITH  | CLERK     | 7902 | 17-DEC-80 00:00:00 |  800 |      |     20
+  7499 | ALLEN  | SALESMAN  | 7698 | 20-FEB-81 00:00:00 | 1600 |  300 |     30
+  7521 | WARD   | SALESMAN  | 7698 | 22-FEB-81 00:00:00 | 1250 |  500 |     30
+  7566 | JONES  | MANAGER   | 7839 | 02-APR-81 00:00:00 | 2975 |      |     20
+  7654 | MARTIN | SALESMAN  | 7698 | 28-SEP-81 00:00:00 | 1250 | 1400 |     30
+  7698 | BLAKE  | MANAGER   | 7839 | 01-MAY-81 00:00:00 | 2850 |      |     30
+  7782 | CLARK  | MANAGER   | 7839 | 09-JUN-81 00:00:00 | 2450 |      |     10
+  7788 | SCOTT  | ANALYST   | 7566 | 19-APR-87 00:00:00 | 3000 |      |     20
+  7839 | KING   | PRESIDENT |      | 17-NOV-81 00:00:00 | 5000 |      |     10
+  7844 | TURNER | SALESMAN  | 7698 | 08-SEP-81 00:00:00 | 1500 |    0 |     30
+  7876 | ADAMS  | CLERK     | 7788 | 23-MAY-87 00:00:00 | 1100 |      |     20
+  7900 | JAMES  | CLERK     | 7698 | 03-DEC-81 00:00:00 |  950 |      |     30
+  7902 | FORD   | ANALYST   | 7566 | 03-DEC-81 00:00:00 | 3000 |      |     20
+  7934 | MILLER | CLERK     | 7782 | 23-JAN-82 00:00:00 | 1300 |      |     10
+(14 rows)
+```
+
+!!! Note
+    For backward compatibility, you can still write `USING libpq` instead of `USING postgres_fdw`. However, the `libpq` connector is missing important optimizations that the `postgres_fdw` connector has. Therefore, use the `postgres_fdw` connector when possible. The `libpq` option is deprecated and might be removed in a future EDB Postgres Advanced Server release.
+
+## See also
+
+[DROP DATABASE LINK](45_drop_public_database_link/#drop_public_database_link)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/22_create_directory.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/22_create_directory.mdx
new file mode 100644
index 00000000000..ddc24f244c5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/22_create_directory.mdx
@@ -0,0 +1,95 @@
+---
+title: "CREATE DIRECTORY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.036.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.066.html"
+redirects:
+  - /epas/latest/epas_compat_sql/22_create_directory/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_directory" class="registered_link"></div>
+
+## Name
+
+`CREATE DIRECTORY` &mdash; Create an alias for a file system directory path.
+
+## Synopsis
+
+```sql
+CREATE DIRECTORY <name> AS '<pathname>'
+```
+
+## Description
+
+The `CREATE DIRECTORY` command creates an alias for a file system directory pathname. You must be a database superuser to use this command.
+
+When you specify the alias as the appropriate parameter to the programs of the `UTL_FILE` package, the operating system files are created in or accessed from the directory corresponding to the alias.
+
+## Parameters
+
+`name`
+
+ The directory alias name.
+
+`pathname`
+
+ The fully qualified directory path represented by the alias name. The `CREATE DIRECTORY` command doesn't create the operating system directory. The physical directory must be created independently using operating system commands.
+
+## Notes
+
+The operating system user id `enterprisedb` must have the appropriate read and write privileges on the directory if you want to use the `UTL_FILE` package to create or read files using the directory.
+
+The directory alias is stored in the `pg_catalog.edb_dir` system catalog table. 
+
+!!!Note
+The `edb_dir` table isn't compatible with Oracle databases.
+!!!
+
+You can also view the directory alias from the Oracle catalog views `SYS.ALL_DIRECTORIES` and `SYS.DBA_DIRECTORIES`. These views are compatible with Oracle databases.
+
+Use the `DROP DIRECTORY` command to delete the directory alias. Deleting a directory alias doesn't affect the corresponding physical file system directory. Delete the file system directory using operating system commands.
+
+In a Linux system, the directory name separator is a forward slash `(/)`.
+
+In a Windows system, you can specify the directory name separator as a forward slash `(/)` or two consecutive backslashes `(\\)`.
+
+## Examples
+
+Create an alias named `empdir` for the directory `/tmp/empdir` on Linux:
+
+```sql
+CREATE DIRECTORY empdir AS '/tmp/empdir';
+```
+
+Create an alias named `empdir` for the directory `C:\TEMP\EMPDIR` on Windows:
+
+```sql
+CREATE DIRECTORY empdir AS 'C:/TEMP/EMPDIR';
+```
+
+View all of the directory aliases:
+
+```sql
+SELECT * FROM pg_catalog.edb_dir;
+__OUTPUT__
+dirname | dirowner |    dirpath     | diracl
+--------+----------+----------------+--------
+ empdir |       10 | C:/TEMP/EMPDIR |
+(1 row)
+```
+
+View the directory aliases using a view compatible with Oracle databases:
+
+```sql
+SELECT * FROM SYS.ALL_DIRECTORIES;
+__OUTPUT__
+    owner     | directory_name | directory_path
+--------------+----------------+----------------
+ ENTERPRISEDB | EMPDIR         | C:/TEMP/EMPDIR
+(1 row)
+```
+
+## See also
+
+[ALTER DIRECTORY](02_alter_directory/#alter_directory), [DROP DIRECTORY](46_drop_directory/#drop_directory)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/23_create_function.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/23_create_function.mdx
new file mode 100644
index 00000000000..ee56e201c79
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/23_create_function.mdx
@@ -0,0 +1,259 @@
+---
+title: "CREATE FUNCTION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.037.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.067.html"
+redirects:
+  - /epas/latest/epas_compat_sql/23_create_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_function" class="registered_link"></div>
+
+## Name
+
+`CREATE FUNCTION` &mdash; Define a new function.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] FUNCTION <name> [ (<parameters>) ]
+  RETURN <data_type>
+   [
+          IMMUTABLE
+        | STABLE
+        | VOLATILE
+        | DETERMINISTIC
+        | [ NOT ] LEAKPROOF
+        | CALLED ON NULL INPUT
+        | RETURNS NULL ON NULL INPUT
+        | STRICT
+        | [ EXTERNAL ] SECURITY INVOKER
+        | [ EXTERNAL ] SECURITY DEFINER
+        | AUTHID DEFINER
+        | AUTHID CURRENT_USER
+        | PARALLEL { UNSAFE | RESTRICTED | SAFE }
+        | COST <execution_cost>
+        | ROWS <result_rows>
+        | SET configuration_parameter
+          { TO <value> | = <value> | FROM CURRENT }
+   ...]
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+## Description
+
+`CREATE FUNCTION` defines a new function. `CREATE OR REPLACE FUNCTION` either creates a new function or replaces an existing definition.
+
+If you include a schema name, then the function is created in the specified schema. Otherwise it's created in the current schema. The name of the new function can't match any existing function with the same input argument types in the same schema. However, functions of different input argument types can share a name. This is called *overloading*. 
+
+!!!Note
+Overloading functions is an EDB Postgres Advanced Server feature. Overloading stored, standalone functions isn't compatible with Oracle databases.
+!!!
+
+To update the definition of an existing function, use `CREATE OR REPLACE FUNCTION`. You can't change the name or argument types of a function this way. (That syntax instead creates a new function.) `CREATE OR REPLACE FUNCTION` also doesn't let you change the return type of an existing function. To do that, you must drop the function and create it again. Also, you can change the types of any `OUT` parameters only by dropping the function first.
+
+The user that creates the function becomes the owner of the function.
+
+## Parameters
+
+`name`
+
+ The identifier of the function.
+
+`parameters`
+
+ A list of formal parameters.
+
+`data_type`
+
+ The data type of the value returned by the function’s `RETURN` statement.
+
+`declarations`
+
+ Variable, cursor, type, or subprogram declarations. To include subprogram declarations, declare them after all other variable, cursor, and type declarations.
+
+`statements`
+
+ SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+`IMMUTABLE`
+
+`STABLE`
+
+`VOLATILE`
+
+ These attributes inform the query optimizer about the behavior of the function. You can specify only one of these attributes. 
+
+-   Use `IMMUTABLE` to indicate that the function can't modify the database and must always reach the same result when given the same argument values. This attribute doesn't perform database lookups and uses only information present in its argument list. If you include this clause, you can immediately replace any call of the function with all-constant arguments with the function value.
+
+-   Use `STABLE` to indicate that the function can't modify the database and that, in a single table scan, it consistently returns the same result for the same argument values. However, its result might change across SQL statements. Use this selection for functions that depend on database lookups, parameter variables (such as the current time zone), and so on.
+
+-   Use `VOLATILE` (the default) to indicate that the function value can change even in a single table scan, so no optimizations can be made. Classify any function that has side effects as volatile, even if its result is predictable. This setting prevent calls from being optimized away.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` function can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups and uses only information directly present in its argument list. If you include this clause, you can immediately replace any call of the function with all-constant arguments with the function value.
+
+`[ NOT ] LEAKPROOF`
+
+ A `LEAKPROOF` function has no side effects and reveals no information about the values used to call the function.
+
+`CALLED ON NULL INPUT`
+
+`RETURNS NULL ON NULL INPUT`
+
+`STRICT`
+
+-   Use `CALLED ON NULL INPUT` (the default) to call the procedure normally when some of its arguments are `NULL`. Check for `NULL` values, if necessary, and respond appropriately.
+
+-   Use `RETURNS NULL ON NULL INPUT` or `STRICT` to indicate that the procedure always returns `NULL` when any of its arguments are `NULL`. If you use these clauses, the procedure doesn't execute when there are `NULL` arguments. Instead, a `NULL` result is assumed.
+
+`[ EXTERNAL ] SECURITY DEFINER`
+
+ `SECURITY DEFINER` (the default) specifies for the function to execute with the privileges of the user that created it. The optional keyword `EXTERNAL` is allowed for SQL conformance.
+
+`[ EXTERNAL ] SECURITY INVOKER`
+
+ Use the `SECURITY INVOKER` clause to execute the function with the privileges of the user that calls it. The optional keyword `EXTERNAL` is allowed for SQL conformance.
+
+`AUTHID DEFINER`
+
+`AUTHID CURRENT_USER`
+
+-   The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If you omit the `AUTHID` clause or specify `AUTHID DEFINER`, the rights of the function owner determine access privileges to database objects.
+
+-   The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If you specify `AUTHID CURRENT_USER`, the rights of the current user executing the function determine access privileges.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query, in contrast to a serial sequential scan.
+
+-   When set to `UNSAFE` (the default), the function can't execute in parallel mode. The presence of such a function in a SQL statement forces a serial execution plan. 
+
+-   When set to `RESTRICTED`, the function can execute in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that is parallel restricted, that relation isn't chosen for parallelism.
+
+-   When set to `SAFE`, the function can execute in parallel mode with no restriction.
+
+`COST execution_cost`
+
+ `execution_cost` is a positive number giving the estimated execution cost for the function, in units of `cpu_operator_cost`. If the function returns a set, this is the cost per returned row. Larger values cause the planner to try to avoid evaluating the function more often than needed.
+
+`ROWS result_rows`
+
+ `result_rows` is a positive number giving the estimated number of rows for the planner to expect the function to return. This option is allowed only when the function is declared to return a set. The default assumption is `1000` rows.
+
+`SET configuration_parameter { TO value | = value | FROM CURRENT }`
+
+ The `SET` clause causes the specified configuration parameter to be set to the specified value when the function is entered and then restored to its prior value when the function exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the function is entered.
+
+ If a `SET` clause is attached to a function, then the effects of a `SET LOCAL` command executed inside the function for the same variable are restricted to the function. The configuration parameter's prior value is restored at function exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, similar to a previous `SET LOCAL` command. The effects of such a command persist after procedure exit unless the current transaction is rolled back.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the function as an autonomous transaction.
+
+!!! Note
+    The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle.
+
+## Notes
+
+EDB Postgres Advanced Server allows function overloading. That is, you can use the same name for several different functions. However, they must have discrete input (`IN`, `IN OUT`) argument data types.
+
+## Examples
+
+The function `emp_comp` takes two numbers as input and returns a computed value. The `SELECT` command shows the use of the function.
+
+```sql
+CREATE OR REPLACE FUNCTION emp_comp (
+    p_sal           NUMBER,
+    p_comm          NUMBER
+) RETURN NUMBER
+IS
+BEGIN
+    RETURN (p_sal + NVL(p_comm, 0)) * 24;
+END;
+```
+
+```sql
+SELECT ename "Name", sal "Salary", comm "Commission", emp_comp(sal, comm)
+    "Total Compensation"  FROM emp;
+__OUTPUT__
+  Name  | Salary  | Commission | Total Compensation
+--------+---------+------------+--------------------
+ SMITH  |  800.00 |            |           19200.00
+ ALLEN  | 1600.00 |     300.00 |           45600.00
+ WARD   | 1250.00 |     500.00 |           42000.00
+ JONES  | 2975.00 |            |           71400.00
+ MARTIN | 1250.00 |    1400.00 |           63600.00
+ BLAKE  | 2850.00 |            |           68400.00
+ CLARK  | 2450.00 |            |           58800.00
+ SCOTT  | 3000.00 |            |           72000.00
+ KING   | 5000.00 |            |          120000.00
+ TURNER | 1500.00 |       0.00 |           36000.00
+ ADAMS  | 1100.00 |            |           26400.00
+ JAMES  |  950.00 |            |           22800.00
+ FORD   | 3000.00 |            |           72000.00
+ MILLER | 1300.00 |            |           31200.00
+(14 rows)
+```
+
+The function `sal_range` returns a count of the number of employees whose salary falls in the specified range. The following anonymous block calls the function a number of times using the argument's default values for the first two calls:
+
+```sql
+CREATE OR REPLACE FUNCTION sal_range (
+    p_sal_min       NUMBER DEFAULT 0,
+    p_sal_max       NUMBER DEFAULT 10000
+) RETURN INTEGER
+IS
+    v_count         INTEGER;
+BEGIN
+    SELECT COUNT(*) INTO v_count FROM emp
+        WHERE sal BETWEEN p_sal_min AND p_sal_max;
+    RETURN v_count;
+END;
+
+BEGIN
+    DBMS_OUTPUT.PUT_LINE('Number of employees with a salary: ' ||
+        sal_range);
+    DBMS_OUTPUT.PUT_LINE('Number of employees with a salary of at least '
+        || '$2000.00: ' || sal_range(2000.00));
+    DBMS_OUTPUT.PUT_LINE('Number of employees with a salary between '
+        || '$2000.00 and $3000.00: ' || sal_range(2000.00, 3000.00));
+
+END;
+
+Number of employees with a salary: 14
+Number of employees with a salary of at least $2000.00: 6
+Number of employees with a salary between $2000.00 and $3000.00: 5
+```
+
+This example uses the `AUTHID CURRENT_USER` clause and `STRICT` keyword in a function declaration:
+
+```sql
+CREATE OR REPLACE FUNCTION dept_salaries(dept_id int) RETURN NUMBER
+  STRICT
+  AUTHID CURRENT_USER
+BEGIN
+  RETURN QUERY (SELECT sum(salary) FROM emp WHERE deptno = id);
+END;
+```
+
+Include the `STRICT` keyword to return `NULL` if any input parameter passed is `NULL`. If a `NULL` value is passed, the function doesn't execute.
+
+The `dept_salaries` function executes with the privileges of the role that's calling the function. If the current user doesn't have privileges to perform the `SELECT` statement querying the `emp` table (to display employee salaries), the function reports an error. To use the privileges associated with the role that defined the function, replace the `AUTHID CURRENT_USER` clause with the `AUTHID DEFINER` clause.
+
+## Other Pragmas (declared in a package specification)
+
+`PRAGMA RESTRICT_REFERENCES`
+
+ EDB Postgres Advanced Server accepts but ignores syntax referencing `PRAGMA RESTRICT_REFERENCES`.
+
+## See also
+
+[DROP FUNCTION](47_drop_function/#drop_function)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/24_create_index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/24_create_index.mdx
new file mode 100644
index 00000000000..b9ff78d8b6e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/24_create_index.mdx
@@ -0,0 +1,123 @@
+---
+title: "CREATE INDEX"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.038.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.068.html"
+redirects:
+  - /epas/latest/epas_compat_sql/24_create_index/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_index" class="registered_link"></div>
+
+## Name
+
+`CREATE INDEX` &mdash; Define a new index.
+
+## Synopsis
+
+```sql
+CREATE [ UNIQUE ] INDEX <name> ON <table>
+  ( { <column> | ( <expression> ) | <constant> } )
+  [ TABLESPACE <tablespace> ]
+  ( { NOPARALLEL | PARALLEL [ <integer> ] } )
+```
+
+## Description
+
+`CREATE INDEX` constructs an index, `name`, on the specified table. Indexes are primarily used to enhance database performance. However, inappropriate use results in slower performance.
+
+The key fields for the index are specified as column names, constants, or as expressions written in parentheses. You can specify multiple fields to create multicolumn indexes.
+
+An index field can be an expression computed from the values of one or more columns of the table row. You can use this feature to get fast access to data based on some transformation of the basic data. For example, an index computed on `UPPER(col)` allows the clause `WHERE UPPER(col) = 'JIM'` to use an index.
+
+EDB Postgres Advanced Server provides the B-tree index method. The B-tree index method is an implementation of Lehman-Yao high-concurrency B-trees.
+
+By default, indexes aren't used for `IS NULL` clauses.
+
+All functions and operators used in an index definition must be immutable. That is, their results must depend only on their arguments and never on any outside influence, such as the contents of another table or the current time. This restriction ensures that the behavior of the index is well-defined. To use a user-defined function in an index expression, mark the function immutable when you create it.
+
+If you create an index on a partitioned table, the `CREATE INDEX` command propagates indexes to the table’s subpartitions.
+
+The `PARALLEL` clause specifies the degree of parallelism used while creating an index. The `NOPARALLEL` clause resets the parallelism to the default value. `reloptions` shows the `parallel_workers` parameter as `0`.
+
+!!! Note
+    If you use the `CREATE INDEX... PARALLEL` command to create an index on a table whose definition included the `PARALLEL` clause at creation, the server uses the `PARALLEL` clause provided with the `CREATE INDEX` command when building a parallel index.
+
+## Parameters
+
+`UNIQUE`
+
+ Causes the system to check for duplicate values in the table when the index is created, if data already exists, and each time data is added. Attempts to insert or update data that would result in duplicate entries generates an error.
+
+`name`
+
+ The name of the index to create. You can't create a schema name here. The index is always created in the same schema as its parent table.
+
+`table`
+
+ The name (possibly schema-qualified) of the table to index.
+
+`column`
+
+ The name of a column in the table.
+
+`expression`
+
+ An expression based on one or more columns of the table. Usually, you must write the expression surrounded by parentheses, as shown in the syntax. However, you can omit the parentheses if the expression has the form of a function call.
+
+`constant`
+
+ A constant value that you can use as an index key.
+
+ Normally, a row where all indexed columns are `NULL` isn't included in an index. That means that the optimizer can't use that index for certain queries. To overcome this limitation, you can add a constant to the index, which forces the index to never contain a row where all index columns are `NULL`.
+
+`tablespace`
+
+ The tablespace in which to create the index. If not specified, `default_tablespace` is used, or the database’s default tablespace if `default_tablespace` is an empty string.
+
+`PARALLEL`
+
+ Specify `PARALLEL` to select a degree of parallelism. Set `parallel_workers` parameter equal to the degree of parallelism to create a parallelized index. Alternatively, if you specify `PARALLEL` but don't list the degree of parallelism, an index accepts default parallelism.
+
+`NOPARALLEL`
+
+ Specify `NOPARALLEL` for default execution.
+
+`integer`
+
+ The `integer` indicates the degree of parallelism, which is a number of `parallel_workers` used in the parallel operation to perform a parallel scan on an index.
+
+## Notes
+
+You can specify up to 32 fields in a multicolumn index.
+
+## Examples
+
+To create a B-tree index on the column `ename` in the table `emp`:
+
+```sql
+CREATE INDEX name_idx ON emp (ename);
+```
+
+To create the same index but have it reside in the `index_tblspc` tablespace:
+
+```sql
+CREATE INDEX name_idx ON emp (ename) TABLESPACE index_tblspc;
+```
+
+You can include a constant value in the index definition (`1`) to create an index that never contains a row where all of the indexed columns are `NULL`:
+
+```sql
+CREATE INDEX emp_dob_idx on emp (emp_dob, 1);
+```
+
+To create an index on `name_idx` in the table `emp` with degree of parallelism set to 7:
+
+```sql
+CREATE UNIQUE INDEX name_idx ON emp (ename) PARALLEL 7;
+```
+
+## See also
+
+[ALTER INDEX](03_alter_index), [DROP INDEX](48_drop_index)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/25_create_materialized_view.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/25_create_materialized_view.mdx
new file mode 100644
index 00000000000..dd2736eef09
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/25_create_materialized_view.mdx
@@ -0,0 +1,79 @@
+---
+title: "CREATE MATERIALIZED VIEW"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.039.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.069.html"
+redirects:
+  - /epas/latest/epas_compat_sql/25_create_materialized_view/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_materialized_view" class="registered_link"></div>
+
+## Name
+
+`CREATE MATERIALIZED VIEW` &mdash; Define a new materialized view.
+
+## Synopsis
+
+```sql
+CREATE MATERIALIZED VIEW <name>
+   [<build_clause>][<create_mv_refresh>] AS subquery
+
+      Where <build_clause> is:
+
+      BUILD {IMMEDIATE | DEFERRED}
+
+      Where <create_mv_refresh> is:
+
+      REFRESH [COMPLETE] [ON DEMAND]
+```
+
+## Description
+
+`CREATE MATERIALIZED VIEW` defines a view of a query that isn't updated each time the view is referenced in a query. By default, the view is populated when the view is created. You can include the `BUILD DEFERRED` keywords to delay populating the view.
+
+A materialized view can be schema-qualified. If you specify a schema name when invoking the `CREATE MATERIALIZED VIEW` command, the view is created in the specified schema. The view name must be different from the name of any other view, table, sequence, or index in the same schema.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of a view to create.
+
+`subquery`
+
+ A `SELECT` statement that specifies the contents of the view.
+
+`build_clause`
+
+ Include a `build_clause` to specify when to populate the view. Specify `BUILD IMMEDIATE` or `BUILD DEFERRED`:
+
+-   `BUILD IMMEDIATE` (the default) populates the view immediately. 
+-   `BUILD DEFERRED` populates the view later, during a `REFRESH` operation.
+
+`create_mv_refresh`
+
+ Include the `create_mv_refresh` clause to specify when to update the contents of a materialized view. The clause contains the `REFRESH` keyword followed by optional `COMPLETE` and `ON DEMAND` keywords, where:
+
+-   `COMPLETE` discards the current content and reloads the materialized view by executing the view's defining query when refreshing the materialized view.
+
+-   `ON DEMAND` (the default) refreshes the materialized view on demand by calling the `DBMS_MVIEW` package or by calling the Postgres `REFRESH MATERIALIZED VIEW` statement.
+
+## Notes
+
+Materialized views are read-only. The server doesn't allow an `INSERT`, `UPDATE`, or `DELETE` on a view.
+
+Permissions of the view owner determine access to tables referenced in the view. The user of a view must have permissions to call all functions the view uses.
+
+For more information about the Postgres `REFRESH MATERIALIZED VIEW` command, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-refreshmaterializedview.html).
+
+## Examples
+
+This statement creates a materialized view named `dept_30`:
+
+```sql
+CREATE MATERIALIZED VIEW dept_30 BUILD IMMEDIATE AS SELECT * FROM emp WHERE deptno = 30;
+```
+
+The view contains information retrieved from the `emp` table about any employee that works in department `30`.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/26_create_package.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/26_create_package.mdx
new file mode 100644
index 00000000000..f67b655f4f9
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/26_create_package.mdx
@@ -0,0 +1,117 @@
+---
+title: "CREATE PACKAGE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.040.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.070.html"
+redirects:
+  - /epas/latest/epas_compat_sql/26_create_package/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_package" class="registered_link"></div>
+
+## Name
+
+`CREATE PACKAGE` &mdash; Define a new package specification.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] PACKAGE <name>
+[ AUTHID { DEFINER | CURRENT_USER } ]
+{ IS | AS }
+  [ <declaration>; ] [, ...]
+  [ { PROCEDURE <proc_name>
+      [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ]
+        [, ...]) ];
+      [ PRAGMA RESTRICT_REFERENCES(<name>,
+        { RNDS | RNPS | TRUST | WNDS | WNPS } [, ... ] ); ]
+    |
+      FUNCTION <func_name>
+      [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ]
+        [, ...]) ]
+      RETURN <rettype> [ DETERMINISTIC ];
+      [ PRAGMA RESTRICT_REFERENCES(<name>,
+        { RNDS | RNPS | TRUST | WNDS | WNPS } [, ... ] ); ]
+    }
+  ] [, ...]
+  END [ <name> ]
+```
+
+## Description
+
+`CREATE PACKAGE` defines a new package specification. `CREATE OR REPLACE PACKAGE` either creates a new package specification or replaces an existing specification.
+
+If you include a schema name, then the package is created in the specified schema. Otherwise it's created in the current schema. The name of the new package can't match any existing package in the same schema unless you want to update the definition of an existing package. In that case, use `CREATE OR REPLACE PACKAGE`.
+
+The user that creates the procedure becomes the owner of the package.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the package to create.
+
+`DEFINER | CURRENT_USER`
+
+ Specifies whether to use the privileges of the package owner (`DEFINER`) or the privileges of the current user executing a program in the package (`CURRENT_USER`) to determine whether access is allowed to database objects referenced in the package. `DEFINER` is the default.
+
+`declaration`
+
+ A public variable, type, cursor, or `REF CURSOR` declaration.
+
+`proc_name`
+
+ The name of a public procedure.
+
+`argname`
+
+ The name of an argument.
+
+`IN | IN OUT | OUT`
+
+ The argument mode.
+
+`argtype`
+
+ The data types of the program’s arguments.
+
+`DEFAULT value`
+
+ Default value of an input argument.
+
+`func_name`
+
+ The name of a public function.
+
+`rettype`
+
+ The return data type.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups and uses only information directly present in its argument list. If you include this clause, you can immediately replace any call of the procedure with all-constant arguments with the procedure value.
+
+`RNDS | RNPS | TRUST | WNDS | WNPS`
+
+ The keywords are accepted for compatibility and ignored.
+
+## Examples
+
+The package specification `empinfo` contains three public components: a public variable, a public procedure, and a public function:
+
+```sql
+CREATE OR REPLACE PACKAGE empinfo
+IS
+    emp_name        VARCHAR2(10);
+    PROCEDURE get_name (
+        p_empno     NUMBER
+    );
+    FUNCTION display_counter
+    RETURN INTEGER;
+END;
+```
+
+## See also
+
+[DROP PACKAGE](49_drop_package/#drop_package)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/27_create_package_body.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/27_create_package_body.mdx
new file mode 100644
index 00000000000..460b3a731ab
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/27_create_package_body.mdx
@@ -0,0 +1,279 @@
+---
+title: "CREATE PACKAGE BODY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.041.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.071.html"
+redirects:
+  - /epas/latest/epas_compat_sql/27_create_package_body/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_package_body" class="registered_link"></div>
+
+## Name
+
+`CREATE PACKAGE BODY` &mdash; Define a new package body.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] PACKAGE BODY <name>
+{ IS | AS }
+  [ declaration; ] | [ forward_declaration ] [, ...]
+  [ { PROCEDURE <proc_name>
+      [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ] [, ...]) ]
+      [ STRICT ]
+      [ LEAKPROOF ]
+      [ PARALLEL { UNSAFE | RESTRICTED | SAFE } ]
+      [ COST <execution_cost> ]
+      [ ROWS <result_rows> ]
+      [ SET <config_param> { TO <value> | = <value> | FROM CURRENT } ]
+    { IS | AS }
+        <program_body>
+      END [ <proc_name> ];
+    |
+      FUNCTION <func_name>
+      [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ] [, ...]) ]
+      RETURN <rettype> [ DETERMINISTIC ]
+      [ STRICT ]
+      [ LEAKPROOF ]
+      [ PARALLEL { UNSAFE | RESTRICTED | SAFE } ]
+      [ COST <execution_cost> ]
+      [ ROWS <result_rows> ]
+      [ SET <config_param> { TO <value> | = <value> | FROM CURRENT } ]
+    { IS | AS }
+        <program_body>
+      END [ <func_name> ];
+    }
+  ] [, ...]
+  [ BEGIN
+      <statement>; [, ...] ]
+  END [ <name> ]
+
+Where forward_declaration:=
+
+[ { PROCEDURE <proc_name>
+  [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ] [, ...])
+  ] ; ]
+|
+[ { FUNCTION <func_name>
+  [ (<argname> [ IN | IN OUT | OUT ] <argtype> [ DEFAULT <value> ] [, ...])
+  ]
+  RETURN <rettype> [ DETERMINISTIC ]; ]
+```
+
+## Description
+
+`CREATE PACKAGE BODY` defines a new package body. `CREATE OR REPLACE PACKAGE BODY` either creates a new package body or replaces an existing body.
+
+If you include a schema name, then the package body is created in the specified schema. Otherwise it's created in the current schema. The name of the new package body must match an existing package specification in the same schema. The new package body name can't match any existing package body in the same schema unless you want to update the definition of an existing package body. In that case, use `CREATE OR REPLACE PACKAGE BODY`.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the package body to create.
+
+`declaration`
+
+ A private variable, type, cursor, or `REF CURSOR` declaration.
+
+`forward_declaration`
+
+ The forward declaration of a procedure or function appears in a package body and is declared in advance of the actual body definition. In a block, you can create multiple subprograms. If they invoke each other, each one requires a forward declaration. You must declare a subprogram before you can invoke it. You can use a forward declaration to declare a subprogram without defining it. The forward declaration and its corresponding definition must reside in the same block.
+
+`proc_name`
+
+ The name of a public or private procedure. If `proc_name` exists in the package specification with an identical signature, then it's public. Otherwise, it's private.
+
+`argname`
+
+ The name of an argument.
+
+`IN | IN OUT | OUT`
+
+ The argument mode.
+
+`argtype`
+
+ The data types of the program’s arguments.
+
+`DEFAULT value`
+
+ Default value of an input argument.
+
+`STRICT`
+
+ Use the `STRICT` keyword to specify for the function not to execute if called with a `NULL` argument. Instead the function returns `NULL`.
+
+`LEAKPROOF`
+
+ Use the `LEAKPROOF` keyword to specify for the function not to reveal any information about arguments other than through a return value.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query, in contrast to a serial sequential scan.
+
+-   When set to `UNSAFE` (the default), the procedure or function can't execute in parallel mode. The presence of such a procedure or function forces a serial execution plan.
+
+-   When set to `RESTRICTED`, the procedure or function can execute in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that's parallel restricted, that relation isn't chosen for parallelism.
+
+-   When set to `SAFE`, the procedure or function can execute in parallel mode with no restriction.
+
+`execution_cost`
+
+ `execution_cost` specifies a positive number giving the estimated execution cost for the function, in units of `cpu_operator_cost`. If the function returns a set, this is the cost per returned row. The default is `0.0025`.
+
+`result_rows`
+
+ `result_rows` is the estimated number of rows for the query planner to expect the function to return. The default is `1000`.
+
+`SET`
+
+ Use the `SET` clause to specify a parameter value for the duration of the function:
+
+-   `config_param` specifies the parameter name.
+
+-   `value` specifies the parameter value.
+
+-   `FROM CURRENT` guarantees that the parameter value is restored when the function ends.
+
+`program_body`
+
+ The pragma, declarations, and SPL statements that comprise the body of the function or procedure.
+
+ The pragma can be `PRAGMA AUTONOMOUS_TRANSACTION` to set the function or procedure as an autonomous transaction.
+
+ The declarations can include variable, type, `REF CURSOR`, or subprogram declarations. If you include subprogram declarations, declare them after all other variable, type, and `REF CURSOR` declarations.
+
+`func_name`
+
+ The name of a public or private function. If `func_name` exists in the package specification with an identical signature, then it's public. Otherwise it's private.
+
+`rettype`
+
+ The return data type.
+
+`DETERMINISTIC`
+
+ Include `DETERMINISTIC` to specify for the function to always return the same result when given the same argument values. A `DETERMINISTIC` function must not modify the database.
+
+ !!! Note
+  The `DETERMINISTIC` keyword is equivalent to the PostgreSQL `IMMUTABLE` option. If you specify `DETERMINISTIC` for a public function in the package body, you must also specify it for the function declaration in the package specification. For private functions, there's no function declaration in the package specification.
+
+`statement`
+
+ An SPL program statement. Statements in the package initialization section execute once per session the first time the package is referenced.
+
+!!! Note
+    The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle.
+
+## Examples
+
+The following is the package body for the `empinfo` package:
+
+```sql
+CREATE OR REPLACE PACKAGE BODY empinfo
+IS
+    v_counter       INTEGER;
+    PROCEDURE get_name (
+        p_empno     NUMBER
+    )
+    IS
+    BEGIN
+        SELECT ename INTO emp_name FROM emp WHERE empno = p_empno;
+        v_counter := v_counter + 1;
+    END;
+    FUNCTION display_counter
+    RETURN INTEGER
+    IS
+    BEGIN
+        RETURN v_counter;
+    END;
+BEGIN
+    v_counter := 0;
+    DBMS_OUTPUT.PUT_LINE('Initialized counter');
+END;
+```
+
+The following two anonymous blocks execute the procedure and function in the `empinfo` package and display the public variable:
+
+```sql
+BEGIN
+    empinfo.get_name(7369);
+    DBMS_OUTPUT.PUT_LINE('Employee Name    : ' || empinfo.emp_name);
+    DBMS_OUTPUT.PUT_LINE('Number of queries: ' || empinfo.display_counter);
+END;
+
+Initialized counter
+Employee Name    : SMITH
+Number of queries: 1
+
+BEGIN
+    empinfo.get_name(7900);
+    DBMS_OUTPUT.PUT_LINE('Employee Name    : ' || empinfo.emp_name);
+    DBMS_OUTPUT.PUT_LINE('Number of queries: ' || empinfo.display_counter);
+END;
+
+Employee Name    : JAMES
+Number of queries: 2
+```
+
+This example uses a forward declaration in a package body. The example displays the name and number of employees whose salary falls in the specified range.
+
+```sql
+CREATE OR REPLACE PACKAGE empinfo IS
+  FUNCTION emp_comp (p_sal_range INTEGER) RETURN INTEGER;
+END empinfo;
+
+CREATE OR REPLACE PACKAGE BODY empinfo IS
+  FUNCTION sal_range (p_sal_range INTEGER) RETURN INTEGER;
+  PROCEDURE list_emp (p_sal_range INTEGER);
+
+  FUNCTION emp_comp (p_sal_range INTEGER) RETURN INTEGER IS
+  BEGIN
+    dbms_output.put_line ('Employee details');
+    return sal_range(p_sal_range);
+  END;
+
+  FUNCTION sal_range (p_sal_range INTEGER) RETURN INTEGER IS
+    emp_cnt INTEGER;
+  BEGIN
+    select count(*) into emp_cnt from emp where sal <= p_sal_range;
+    dbms_output.put_line('Number of employees in the salary range ' ||
+p_sal_range|| ' is :'|| emp_cnt);
+    list_emp(p_sal_range);
+    return emp_cnt;
+  END;
+
+  PROCEDURE list_emp (p_sal_range IN INTEGER) IS
+  BEGIN
+    FOR i IN select ename from emp where sal <= p_sal_range
+    LOOP
+       dbms_output.put_line (i);
+    END LOOP;
+  END;
+
+END empinfo;
+
+
+SELECT empinfo.emp_comp(1500);
+__OUTPUT__
+Employee details
+Number of employees in the salary range 1500 is :7
+(SMITH)
+(WARD)
+(MARTIN)
+(TURNER)
+(ADAMS)
+(JAMES)
+(MILLER)
+emp_comp
+----------
+        7
+(1 row)
+```
+
+## See also
+
+[CREATE PACKAGE](26_create_package/#create_package), [DROP PACKAGE](49_drop_package/#drop_package)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/28_create_procedure.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/28_create_procedure.mdx
new file mode 100644
index 00000000000..4282507af73
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/28_create_procedure.mdx
@@ -0,0 +1,272 @@
+---
+title: "CREATE PROCEDURE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.042.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.072.html"
+redirects:
+  - /epas/latest/epas_compat_sql/28_create_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_procedure" class="registered_link"></div>
+
+## Name
+
+`CREATE PROCEDURE` &mdash; Define a new stored procedure.
+
+## Synopsis
+
+```sql
+CREATE [OR REPLACE] PROCEDURE <name> [ (<parameters>) ]
+   [
+          IMMUTABLE
+        | STABLE
+        | VOLATILE
+        | DETERMINISTIC
+        | [ NOT ] LEAKPROOF
+        | CALLED ON NULL INPUT
+        | RETURNS NULL ON NULL INPUT
+        | STRICT
+        | [ EXTERNAL ] SECURITY INVOKER
+        | [ EXTERNAL ] SECURITY DEFINER
+        | AUTHID DEFINER
+        | AUTHID CURRENT_USER
+        | PARALLEL { UNSAFE | RESTRICTED | SAFE }
+        | COST <execution_cost>
+        | ROWS <result_rows>
+        | SET <configuration_parameter>
+          { TO <value> | = <value> | FROM CURRENT }
+   ...]
+{ IS | AS }
+    [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+    [ <declarations> ]
+  BEGIN
+    <statements>
+  END [ <name> ];
+```
+
+## Description
+
+`CREATE PROCEDURE` defines a new stored procedure. `CREATE OR REPLACE PROCEDURE` either creates a new procedure or replaces an existing definition.
+
+If you include a schema name, then the procedure is created in the specified schema. Otherwise it's created in the current schema. The name of the new procedure can't match any existing procedure with the same input argument types in the same schema. However, procedures of different input argument types can share a name. This is called *overloading*. 
+
+!!! Note
+    Overloading procedures is an EDB Postgres Advanced Server feature. Overloading stored, standalone procedures isn't compatible with Oracle databases.
+
+To update the definition of an existing procedure, use `CREATE OR REPLACE PROCEDURE`. You can't change the name or argument types of a procedure this way. That syntax creates a new, distinct procedure. When using `OUT` parameters, you can't change the types of any `OUT` parameters except by dropping the procedure.
+
+## Parameters
+
+`name`
+
+ The identifier of the procedure.
+
+`parameters`
+
+ A list of formal parameters.
+
+`declarations`
+
+ Variable, cursor, type, or subprogram declarations. If you include subprogram declarations, declare them after all other variable, cursor, and type declarations.
+
+`statements`
+
+ SPL program statements. The `BEGIN - END` block can contain an `EXCEPTION` section.
+
+`IMMUTABLE`
+
+`STABLE`
+
+`VOLATILE`
+
+ These attributes inform the query optimizer about the behavior of the procedure. You can specify only one of these attributes. 
+
+-   Use `IMMUTABLE` to indicate that the procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups and uses only information directly present in its argument list. If you include this clause, you can immediately replace any call of the procedure with all-constant arguments with the procedure value.
+
+-   Use `STABLE` to indicate that the procedure can't modify the database and that, in a single table scan, it consistently returns the same result for the same argument values. However, its result might change across SQL statements. Use this selection for procedures that depend on database lookups, parameter variables (such as the current time zone), and so on.
+
+-   Use `VOLATILE` (the default) to indicate that the procedure value can change even in a single table scan, so no optimizations can be made. You must classify any function that has side effects as volatile, even if its result is predictable, to prevent calls from being optimized away.
+
+`DETERMINISTIC`
+
+ `DETERMINISTIC` is a synonym for `IMMUTABLE`. A `DETERMINISTIC` procedure can't modify the database and always reaches the same result when given the same argument values. It doesn't perform database lookups and uses only information directly present in its argument list. If you include this clause, you can immediately replace any call of the procedure with all-constant arguments with the procedure value.
+
+`[ NOT ] LEAKPROOF`
+
+ A `LEAKPROOF` procedure has no side effects and reveals no information about the values used to call the procedure.
+
+`CALLED ON NULL INPUT`
+
+`RETURNS NULL ON NULL INPUT`
+
+`STRICT`
+
+-   Use `CALLED ON NULL INPUT` (the default) to call the procedure normally when some of its arguments are `NULL`. Check for `NULL` values, if needed, and respond appropriately.
+
+-   Use `RETURNS NULL ON NULL INPUT` or `STRICT` to indicate that the procedure always returns `NULL` when any of its arguments are `NULL`. If you specify these clauses, the procedure doesn't execute when there are `NULL` arguments. Instead a `NULL` result is assumed.
+
+`[ EXTERNAL ] SECURITY DEFINER`
+
+ Use `SECURITY DEFINER` (the default) to specify that the procedure executes with the privileges of the user that created it. The keyword `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`[ EXTERNAL ] SECURITY INVOKER`
+
+ Use the `SECURITY INVOKER` clause to execute the procedure with the privileges of the user that calls it. The keyword `EXTERNAL` is allowed for SQL conformance but is optional.
+
+`AUTHID DEFINER`
+
+`AUTHID CURRENT_USER`
+
+-   The `AUTHID DEFINER` clause is a synonym for `[EXTERNAL] SECURITY DEFINER`. If you omit the `AUTHID` clause or specify `AUTHID DEFINER`, the rights of the procedure owner determine access privileges to database objects.
+
+-   The `AUTHID CURRENT_USER` clause is a synonym for `[EXTERNAL] SECURITY INVOKER`. If you specify `AUTHID CURRENT_USER`, the rights of the current user executing the procedure determine access privileges.
+
+`PARALLEL { UNSAFE | RESTRICTED | SAFE }`
+
+ The `PARALLEL` clause enables the use of parallel sequential scans (parallel mode). A parallel sequential scan uses multiple workers to scan a relation in parallel during a query, in contrast to a serial sequential scan.
+
+-   When set to `UNSAFE` (the default), the procedure can't execute in parallel mode. The presence of such a procedure forces a serial execution plan. 
+
+-   When set to `RESTRICTED`, the procedure can execute in parallel mode, but the execution is restricted to the parallel group leader. If the qualification for any particular relation has anything that is parallel restricted, that relation isn't chosen for parallelism.
+
+-   When set to `SAFE`, the procedure can execute in parallel mode with no restriction.
+
+`COST execution_cost`
+
+ `execution_cost` is a positive number giving the estimated execution cost for the procedure, in units of `cpu_operator_cost`. If the procedure returns a set, this is the cost per returned row. Larger values cause the planner to try to avoid evaluating the function more often than necessary.
+
+`ROWS result_rows`
+
+ `result_rows` is a positive number giving the estimated number of rows for the planner to expect the procedure to return. This option is allowed only when the procedure is declared to return a set. The default is 1000 rows.
+
+`SET configuration_parameter { TO value | = value | FROM CURRENT }`
+
+ The `SET` clause sets the specified configuration parameter to the specified value when the procedure is entered and then restored to its prior value when the procedure exits. `SET FROM CURRENT` saves the session's current value of the parameter as the value to apply when the procedure is entered.
+
+ If a `SET` clause is attached to a procedure, then the effects of a `SET LOCAL` command executed inside the procedure for the same variable are restricted to the procedure. The configuration parameter's prior value is restored at procedure exit. An ordinary `SET` command (without `LOCAL`) overrides the `SET` clause, similar to a previous `SET LOCAL` command. The effects of such a command persist after procedure exit, unless the current transaction is rolled back.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the procedure as an autonomous transaction.
+
+!!! Note
+    -   The `STRICT`, `LEAKPROOF`, `PARALLEL`, `COST`, `ROWS` and `SET` keywords provide extended functionality for EDB Postgres Advanced Server and aren't supported by Oracle.
+    -   The `IMMUTABLE`, `STABLE`, `STRICT`, `LEAKPROOF`, `COST`, `ROWS` and `PARALLEL { UNSAFE | RESTRICTED | SAFE }` attributes are supported only for EDB SPL procedures.
+    -   By default, stored procedures are created as `SECURITY DEFINERS`. Stored procedures defined in plpgsql are created as `SECURITY INVOKERS`.
+
+## Examples
+
+This procedure lists the employees in the `emp` table:
+
+```sql
+CREATE OR REPLACE PROCEDURE list_emp
+IS
+    v_empno         NUMBER(4);
+    v_ename         VARCHAR2(10);
+    CURSOR emp_cur IS
+        SELECT empno, ename FROM emp ORDER BY empno;
+BEGIN
+    OPEN emp_cur;
+    DBMS_OUTPUT.PUT_LINE('EMPNO    ENAME');
+    DBMS_OUTPUT.PUT_LINE('-----    -------');
+    LOOP
+        FETCH emp_cur INTO v_empno, v_ename;
+        EXIT WHEN emp_cur%NOTFOUND;
+        DBMS_OUTPUT.PUT_LINE(v_empno || '     ' || v_ename);
+    END LOOP;
+    CLOSE emp_cur;
+END;
+
+EXEC list_emp;
+__OUTPUT__
+EMPNO    ENAME
+-----    -------
+7369     SMITH
+7499     ALLEN
+7521     WARD
+7566     JONES
+7654     MARTIN
+7698     BLAKE
+7782     CLARK
+7788     SCOTT
+7839     KING
+7844     TURNER
+7876     ADAMS
+7900     JAMES
+7902     FORD
+7934     MILLER
+```
+
+This procedure uses `IN OUT` and `OUT` arguments to return an employee’s number, name, and job based on a search using the given employee number. If that isn't found, then the search uses the given name. An anonymous block calls the procedure.
+
+```sql
+CREATE OR REPLACE PROCEDURE emp_job (
+    p_empno         IN OUT emp.empno%TYPE,
+    p_ename         IN OUT emp.ename%TYPE,
+    p_job           OUT    emp.job%TYPE
+)
+IS
+    v_empno         emp.empno%TYPE;
+    v_ename         emp.ename%TYPE;
+    v_job           emp.job%TYPE;
+BEGIN
+    SELECT ename, job INTO v_ename, v_job FROM emp WHERE empno = p_empno;
+    p_ename := v_ename;
+    p_job   := v_job;
+    DBMS_OUTPUT.PUT_LINE('Found employee # ' || p_empno);
+EXCEPTION
+    WHEN NO_DATA_FOUND THEN
+        BEGIN
+            SELECT empno, job INTO v_empno, v_job FROM emp
+                WHERE ename = p_ename;
+            p_empno := v_empno;
+            p_job   := v_job;
+            DBMS_OUTPUT.PUT_LINE('Found employee ' || p_ename);
+        EXCEPTION
+            WHEN NO_DATA_FOUND THEN
+                DBMS_OUTPUT.PUT_LINE('Could not find an employee with ' ||
+                    'number, ' || p_empno || ' nor name, '  || p_ename);
+                p_empno := NULL;
+                p_ename := NULL;
+                p_job   := NULL;
+        END;
+END;
+
+DECLARE
+    v_empno      emp.empno%TYPE;
+    v_ename      emp.ename%TYPE;
+    v_job        emp.job%TYPE;
+BEGIN
+    v_empno := 0;
+    v_ename := 'CLARK';
+    emp_job(v_empno, v_ename, v_job);
+    DBMS_OUTPUT.PUT_LINE('Employee No: ' || v_empno);
+    DBMS_OUTPUT.PUT_LINE('Name       : ' || v_ename);
+    DBMS_OUTPUT.PUT_LINE('Job        : ' || v_job);
+END;
+__OUTPUT__
+Found employee CLARK
+Employee No: 7782
+Name       : CLARK
+Job        : MANAGER
+```
+
+This example uses the `AUTHID DEFINER` and `SET` clauses in a procedure declaration. The `update_salary` procedure conveys the privileges of the role that defined the procedure to the role that's calling the procedure while the procedure executes.
+
+```sql
+CREATE OR REPLACE PROCEDURE update_salary(id INT, new_salary NUMBER)
+  SET SEARCH_PATH = 'public' SET WORK_MEM = '1MB'
+  AUTHID DEFINER IS
+BEGIN
+  UPDATE emp SET salary = new_salary WHERE emp_id = id;
+END;
+```
+
+Include the `SET` clause to set the procedure's search path to `public` and the work memory to `1MB`. Other procedures, functions, and objects aren't affected by these settings.
+
+In this example, the `AUTHID DEFINER` clause temporarily grants privileges to a role that otherwise might not be allowed to execute the statements in the procedure. To use the privileges associated with the role invoking the procedure, replace the `AUTHID DEFINER` clause with the `AUTHID CURRENT_USER` clause.
+
+## See also
+
+[DROP PROCEDURE](50_drop_procedure/#drop_procedure), [ALTER PROCEDURE](04_alter_procedure/#alter_procedure)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx
new file mode 100644
index 00000000000..3bc12041923
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/29_create_profile.mdx
@@ -0,0 +1,141 @@
+---
+title: "CREATE PROFILE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.043.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.073.html"
+redirects:
+  - /epas/latest/epas_compat_sql/29_create_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_profile" class="registered_link"></div>
+
+## Name
+
+`CREATE PROFILE` &mdash; Create a profile.
+
+## Synopsis
+
+```sql
+CREATE PROFILE <profile_name>
+       [LIMIT {<parameter value>} ... ];
+```
+
+## Description
+
+`CREATE PROFILE` create a profile. Include the `LIMIT` clause and one or more space-delimited `parameter/value` pairs to specify the rules enforced by EDB Postgres Advanced Server.
+
+EDB Postgres Advanced Server creates a default profile named `DEFAULT`. When you use the `CREATE ROLE` command to create a role, the new role is associated with the `DEFAULT` profile. If you upgrade from a previous version of EDB Postgres Advanced Server to EDB Postgres Advanced Server 10, the upgrade process creates the roles in the upgraded version to the `DEFAULT` profile.
+
+You must be a superuser to use `CREATE PROFILE`.
+
+Include the `LIMIT` clause and one or more space-delimited `parameter/value` pairs to specify the rules enforced by EDB Postgres Advanced Server.
+
+## Parameters
+
+`profile_name`
+
+ The name of the profile.
+
+`parameter`
+
+ The password attribute for the rule to monitor.
+
+`value`
+
+ The value the `parameter` must reach before an action is taken by the server.
+
+EDB Postgres Advanced Server supports these values for each parameter:
+
+`FAILED_LOGIN_ATTEMPTS` specifies the number of failed login attempts that a user can make before the server locks them out of their account for the length of time specified by `PASSWORD_LOCK_TIME`. Supported values are:
+
+-   An `INTEGER` value greater than `0`.
+-   `DEFAULT` &mdash; The value of `FAILED_LOGIN_ATTEMPTS` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The connecting user can make an unlimited number of failed login attempts.
+
+`PASSWORD_LOCK_TIME` specifies the length of time that must pass before the server unlocks an account that was locked because of `FAILED_LOGIN_ATTEMPTS`. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LOCK_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The account is locked until manually unlocked by a database superuser.
+
+`PASSWORD_LIFE_TIME` specifies the number of days that the current password can be used before the user is prompted to provide a new password. Include the `PASSWORD_GRACE_TIME` clause when using the `PASSWORD_LIFE_TIME` clause to specify the number of days to pass after the password expires before the user is forced to change their password. If you don't specify `PASSWORD_GRACE_TIME`, the password expires on the day specified by the default value of `PASSWORD_GRACE_TIME`, and the user isn't allowed to execute any command until a new password is provided. Supported values are:
+
+-   A `NUMERIC` value greater of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_LIFE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password doesn't have an expiration date.
+
+`PASSWORD_GRACE_TIME` specifies the length of the grace period after a password expires until the user is forced to change their password. When the grace period expires, a user is allowed to connect but isn't allowed to execute any command until they update their expired password. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_GRACE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The grace period is infinite.
+
+`PASSWORD_REUSE_TIME` specifies the number of days a user must wait before reusing a password. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED`, there are no restrictions on password reuse. Supported values are:
+
+-   A `NUMERIC` value of `0` or greater. To specify a fractional portion of a day, specify a decimal value. For example, use the value `4.5` to specify 4 days, 12 hours.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_TIME` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_REUSE_MAX` specifies the number of password changes that must occur before a password can be reused. Use the `PASSWORD_REUSE_TIME` and `PASSWORD_REUSE_MAX` parameters together. If you specify a finite value for one of these parameters while the other is `UNLIMITED`, old passwords can never be reused. If both parameters are set to `UNLIMITED` there are no restrictions on password reuse. Supported values are:
+
+-   An `INTEGER` value of `0` or greater.
+-   `DEFAULT` &mdash; The value of `PASSWORD_REUSE_MAX` specified in the `DEFAULT` profile.
+-   `UNLIMITED` &mdash; The password can be reused without restrictions.
+
+`PASSWORD_VERIFY_FUNCTION` specifies password complexity. Supported values are:
+
+-   The name of a PL/SQL function.
+-   `DEFAULT` &mdash; The value of `PASSWORD_VERIFY_FUNCTION` specified in the `DEFAULT` profile.
+-   `NULL`
+
+`PASSWORD_ALLOW_HASHED` specifies whether an encrypted password is allowed for use. If you specify `TRUE`, the system allows a user to change the password by specifying a hash computed encrypted password on the client side. However, if you specify `FALSE`, then a password must be specified in a plain-text form to be validated. Otherwise an error is thrown if a server receives an encrypted password. Supported values are:
+
+-   A `BOOLEAN` value `TRUE/ON/YES/1` or `FALSE/OFF/NO/0`.
+-   `DEFAULT` &mdash; The value of `PASSWORD_ALLOW_HASHED` specified in the `DEFAULT` profile.
+
+!!! Note
+    The `PASSWORD_ALLOW_HASHED` isn't compatible with Oracle.
+
+## Notes
+
+Use the `DROP PROFILE` command to remove the profile.
+
+## Examples
+
+This command creates a profile named `acctg`. The profile specifies that if a user hasn't authenticated with the correct password in five attempts, the account is locked for one day:
+
+```sql
+CREATE PROFILE acctg LIMIT
+       FAILED_LOGIN_ATTEMPTS 5
+       PASSWORD_LOCK_TIME 1;
+```
+
+This command creates a profile named `sales`. The profile specifies that a user must change their password every 90 days:
+
+```sql
+CREATE PROFILE sales LIMIT
+       PASSWORD_LIFE_TIME 90
+       PASSWORD_GRACE_TIME 3;
+```
+
+If the user doesn't change their password before the 90 days specified in the profile passes, they are issued a warning at login. After a grace period of three days, their account isn't allowed to invoke any commands until they change their password.
+
+This command creates a profile named `accts`. The profile specifies that a user can't reuse a password within 180 days of the last use of the password and must change their password at least five times before reusingit:
+
+```sql
+CREATE PROFILE accts LIMIT
+       PASSWORD_REUSE_TIME 180
+       PASSWORD_REUSE_MAX 5;
+```
+
+This command creates a profile named `resources`. The profile calls a user-defined function named `password_rules` that verifies that the password provided meets their standards for complexity:
+
+```sql
+CREATE PROFILE resources LIMIT
+       PASSWORD_VERIFY_FUNCTION password_rules;
+```
+
+## See also
+
+[ALTER PROFILE](05_alter_profile/#alter_profile), [DROP PROFILE](51_drop_profile/#drop_profile)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/30_create_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/30_create_queue.mdx
new file mode 100644
index 00000000000..1332ac2e655
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/30_create_queue.mdx
@@ -0,0 +1,74 @@
+---
+title: "CREATE QUEUE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.044.html"
+redirects:
+  - /epas/latest/epas_compat_sql/30_create_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_queue" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle with the `CREATE QUEUE SQL` command. You can use this syntax with `DBMS_AQADM`.
+
+## Name
+
+`CREATE QUEUE` &mdash; Create a queue.
+
+## Synopsis
+
+Use `CREATE QUEUE` to define a new queue:
+
+```sql
+CREATE QUEUE <name> QUEUE TABLE <queue_table_name> [ ( { <option_name option_value>} [, ... ] ) ]
+```
+
+Where possible values for `option_name` and the corresponding `option_value` are:
+
+```sql
+TYPE [normal_queue | exception_queue]
+RETRIES [INTEGER]
+RETRYDELAY [DOUBLE PRECISION]
+RETENTION [DOUBLE PRECISION]
+```
+
+## Description
+
+The `CREATE QUEUE` command allows a database superuser or any user with the system-defined `aq_administrator_role` privilege to create a queue in the current database.
+
+If the name of the queue is schema-qualified, the queue is created in the specified schema. If the `CREATE QUEUE` command doesn't include a schema, the queue is created in the current schema. You can create a queue only in the schema where the queue table resides. The name of the queue must be unique among queues in the same schema.
+
+Use `DROP QUEUE` to remove a queue.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the queue to create.
+
+`queue_table_name`
+
+ The name of the queue table with which this queue is associated.
+
+`option_name option_value`
+
+ The name of any options to associate with the new queue and the corresponding value for the option. If the call to `CREATE QUEUE` includes duplicate option names, the server returns an error. The following values are accepted:
+
+-   `TYPE` &mdash; Specify `normal_queue` to indicate that the queue is a normal queue or `exception_queue` for an exception queue. An exception queue accepts only dequeue operations.
+-   `RETRIES` &mdash; An integer value that specifies the maximum number of attempts to remove a message from a queue.                                                       
+-   `RETRYDELAY` &mdash; A double-precision value that specifies the number of seconds after a rollback that the server waits before retrying a message.                                                            
+-   `RETENTION` &mdash; A double-precision value that specifies the number of seconds to save a message in the queue table after dequeueing.
+
+## Examples
+
+This command creates a queue named `work_order` that's associated with a queue table named `work_order_table`:
+
+```sql
+CREATE QUEUE work_order QUEUE TABLE work_order_table (RETRIES 5, RETRYDELAY 2);
+```
+
+The server allows 5 attempts to remove a message from the queue and enforces a retry delay of 2 seconds between attempts.
+
+## See also
+
+[ALTER QUEUE](06_alter_queue/#alter_queue), [DROP QUEUE](52_drop_queue/#drop_queue)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx
new file mode 100644
index 00000000000..fd2b1563d2b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/31_create_queue_table.mdx
@@ -0,0 +1,107 @@
+---
+title: "CREATE QUEUE TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.045.html"
+redirects:
+  - /epas/latest/epas_compat_sql/31_create_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_queue_table" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes extra syntax not offered by Oracle with the `CREATE QUEUE TABLE SQL` command. You can use this syntax with `DBMS_AQADM`.
+
+## Name
+
+`CREATE QUEUE TABLE` &mdash; Create a queue table.
+
+## Synopsis
+
+Use `CREATE QUEUE TABLE` to define a queue table:
+
+```sql
+CREATE QUEUE TABLE <name> OF <type_name> [ ( { <option_name option_value> } [, ... ] ) ]
+```
+
+Possible `option_name` and corresponding `option_value` values are:
+
+-   `SORT_LIST` &mdash; Specify `option_value` as `priority`, `enq_time`.
+-   `MULTIPLE_CONSUMERS` &mdash; Specify `option_value` as`FALSE`, `TRUE`.
+-   `MESSAGE_GROUPING` &mdash; Specify `option_value` as `NONE`, `TRANSACTIONAL`.
+-   `STORAGE_CLAUSE` &mdash; Specify `option_value` as `TABLESPACE tablespace_name`, `PCTFREE integer`, `PCTUSED integer`, `INITRANS integer`, `MAXTRANS integer`, `STORAGE storage_option`. Values for `storage_option` are one or more of the following: `MINEXTENTS integer`, `MAXEXTENTS integer`, `PCTINCREASE integer`, `INITIAL size_clause`, `NEXT`, `FREELISTS integer`, `OPTIMAL size_clause`, `BUFFER_POOL {KEEP|RECYCLE|DEFAULT}`. 
+
+Only the `TABLESPACE` option is enforced. All others are accepted for compatibility and ignored. Use the `TABLESPACE` clause to specify the name of a tablespace in which to create the table.
+
+## Description
+
+`CREATE QUEUE TABLE` allows a superuser or a user with the `aq_administrator_role` privilege to create a queue table.
+
+If the call to `CREATE QUEUE TABLE` includes a schema name, the queue table is created in the specified schema. If you don't provide a schema name, the queue table is created in the current schema.
+
+The name of the queue table must be unique among queue tables in the same schema.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the new queue table.
+
+`type_name`
+
+ The name of an existing type that describes the payload of each entry in the queue table. For information about defining a type, see [CREATE TYPE](39_create_type/).
+
+`option_name option_value`
+
+ The name of any options that to associate with the new queue and the corresponding value for the option. If the call to `CREATE QUEUE` includes duplicate option names, the server returns an error. The following values are accepted:
+
+-   `SORT_LIST` &mdash; Use the `SORT_LIST` option to control the dequeueing order of the queue. Specify the names of the columns to use, in ascending order, to sort the queue. The following combinations of `enq_time` and `priority` are possible values:
+
+    `enq_time. priority`
+
+    `priority. enq_time`
+
+    `priority`
+
+    `enq_time`
+
+-   `MULTIPLE_CONSUMERS` &mdash; A `BOOLEAN` value that indicates if a message can have more than one consumer (`TRUE`) or are limited to one consumer per message (`FALSE`).
+
+-   `MESSAGE_GROUPING` &mdash; Specify `none` to dequeue each message individually or `transactional` to add messages to the queue as a result of one transaction and dequeue them as a group.
+
+-   `STORAGE_CLAUSE` &mdash; Use `STORAGE_CLAUSE` to specify table attributes. Possible values are `TABLESPACE tablespace_name`, `PCTFREE integer`, `PCTUSED integer`, `INITRANS integer`, `MAXTRANS integer`, `STORAGE storage_option`. Possible values for  `storage_option` are:
+
+    `MINEXTENTS integer` 
+
+    `MAXEXTENTS integer`
+
+    `PCTINCREASE integer` 
+
+    `INITIAL size_clause`
+
+    `NEXT` 
+
+    `FREELISTS integer` 
+
+    `OPTIMAL size_clause`
+
+    `BUFFER_POOL {KEEP|RECYCLE|DEFAULT}`
+
+Only the `TABLESPACE` option is enforced. All others are accepted for compatibility and ignored. Use the `TABLESPACE` clause to specify the name of a tablespace in which to create the table.
+
+## Examples
+
+You must create a user-defined type before creating a queue table. The type describes the columns and data types in the table. This command creates a type named `work_order`:
+
+```sql
+CREATE TYPE work_order AS (name VARCHAR2, project TEXT, completed BOOLEAN);
+```
+
+This command uses the `work_order` type to create a queue table named `work_order_table`:
+
+```sql
+CREATE QUEUE TABLE work_order_table OF work_order (sort_list (enq_time, priority));
+```
+
+## See also
+
+[ALTER QUEUE TABLE](07_alter_queue_table/#alter_queue_table), [DROP QUEUE TABLE](53_drop_queue_table/#drop_queue_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/32_create_role.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/32_create_role.mdx
new file mode 100644
index 00000000000..4d94000bc45
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/32_create_role.mdx
@@ -0,0 +1,60 @@
+---
+title: "CREATE ROLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.046.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.074.html"
+redirects:
+  - /epas/latest/epas_compat_sql/32_create_role/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_role" class="registered_link"></div>
+
+## Name
+
+`CREATE ROLE` &mdash; Define a new database role.
+
+## Synopsis
+
+```sql
+CREATE ROLE <name> [IDENTIFIED BY <password> [REPLACE old_password]]
+```
+
+## Description
+
+`CREATE ROLE` adds a role to the EDB Postgres Advanced Server database cluster. A role is an entity that can own database objects and have database privileges. A role can be considered a user, a group, or both depending on how you use it. The new role doesn't have the `LOGIN` attribute, so you can't use it to start a session. (Use the `ALTER ROLE` command to give the role `LOGIN` rights.) You must have `CREATEROLE` privilege or be a database superuser to use `CREATE ROLE`.
+
+If you specify the `IDENTIFIED BY` clause, the `CREATE ROLE` command also creates a schema owned by and with the same name as the newly created role.
+
+!!! Note
+    The roles are defined at the database cluster level, making them valid in all databases in the cluster.
+
+## Parameters
+
+`name`
+
+ The name of the new role.
+
+`IDENTIFIED BY password`
+
+ Sets the role’s password. A password is needed only for roles having the `LOGIN` attribute, but you can stil define one for roles without it. If you don't plan to use password authentication, you can omit this option.
+
+## Notes
+
+Use `ALTER ROLE` to change the attributes of a role. Use `DROP ROLE` to remove a role. You can mmodify the attributes specified by `CREATE ROLE` using `ALTER ROLE` commands.
+
+Use `GRANT` and `REVOKE` to add and remove members of roles that are being used as groups.
+
+The maximum length limit for role name and password is 63 characters.
+
+## Examples
+
+Create a role and a schema named `admins` with a password:
+
+```sql
+CREATE ROLE admins IDENTIFIED BY Rt498zb;
+```
+
+## See also
+
+[ALTER ROLE](08_alter_role_identified_by/#alter_role_identified_by), [DROP ROLE](55_drop_role/#drop_role), [GRANT](64_grant/#grant), [REVOKE](67_revoke/#revoke), [SET ROLE](73_set_role/#set_role)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/33_create_schema.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/33_create_schema.mdx
new file mode 100644
index 00000000000..59ef1a4e55d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/33_create_schema.mdx
@@ -0,0 +1,58 @@
+---
+title: "CREATE SCHEMA"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.047.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.075.html"
+redirects:
+  - /epas/latest/epas_compat_sql/33_create_schema/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_schema" class="registered_link"></div>
+
+## Name
+
+`CREATE SCHEMA` &mdash; Define a new schema.
+
+## Synopsis
+
+```sql
+CREATE SCHEMA AUTHORIZATION <username> <schema_element> [ ... ]
+```
+
+## Description
+
+This variation of the `CREATE SCHEMA` command creates a schema owned by `username` and populated with one or more objects. Creating the schema and objects occurs in a single transaction, so either all objects are created or none of them are, including the schema. If you're using an Oracle database, no new schema is created. `username`, and therefore the schema, must exist before you use the command.
+
+A schema is essentially a namespace. It contains named objects, such as tables and views, whose names might duplicate those of other objects existing in other schemas. You can access named objects either by qualifying their names with the schema name as a prefix or by setting a search path that includes the desired schemas. Unqualified objects are created in the current schema. The current scheme is the one at the front of the search path. Use the function `CURRENT_SCHEMA` to determine the value.
+
+!!! Note
+The search path concept and the `CURRENT_SCHEMA` function aren't compatible with Oracle databases.
+!!!
+
+`CREATE SCHEMA` includes subcommands to create objects in the schema. The subcommands are treated the same as separate commands issued after creating the schema. All the created objects are owned by the specified user.
+
+## Parameters
+
+`username`
+
+ The name of the user to own the new schema. The schema also gets this name. Only superusers can create schemas owned by users other than themselves. In EDB Postgres Advanced Server, the role `username` must already exist, but the schema must not exist. In Oracle, the user and schema must exist.
+
+`schema_element`
+
+ A SQL statement defining an object to create in the schema. `CREATE TABLE`, `CREATE VIEW`, and `GRANT` are accepted as clauses in `CREATE SCHEMA`. You can create other kinds of objects in separate commands after you create the schema.
+
+## Notes
+
+Nonsuperusers creating the schema must have the `CREATE` privilege for the current database. 
+
+In EDB Postgres Advanced Server, other forms of the `CREATE SCHEMA` command aren't compatible with Oracle databases.
+
+## Examples
+
+```sql
+CREATE SCHEMA AUTHORIZATION enterprisedb
+    CREATE TABLE empjobs (ename VARCHAR2(10), job VARCHAR2(9))
+    CREATE VIEW managers AS SELECT ename FROM empjobs WHERE job = 'MANAGER'
+    GRANT SELECT ON managers TO PUBLIC;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx
new file mode 100644
index 00000000000..b279bbbf0c7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/34_create_sequence.mdx
@@ -0,0 +1,116 @@
+---
+title: "CREATE SEQUENCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.048.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.076.html"
+redirects:
+  - /epas/latest/epas_compat_sql/34_create_sequence/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_sequence" class="registered_link"></div>
+
+## Name
+
+`CREATE SEQUENCE` &mdash; Define a new sequence generator.
+
+## Synopsis
+
+```sql
+CREATE SEQUENCE <name> [ INCREMENT BY <increment> ]
+  [ { NOMINVALUE | MINVALUE <minvalue> } ]
+  [ { NOMAXVALUE | MAXVALUE <maxvalue> } ]
+  [ START WITH <start> ] [ CACHE <cache> | NOCACHE ] [ CYCLE ]
+```
+
+## Description
+
+`CREATE SEQUENCE` creates a sequence number generator. This process involves creating and initializing a special single-row table with the specified name. The generator is owned by the user who created it.
+
+If you include a schema name, then the sequence is created in the specified schema. Otherwise it's created in the current schema. The sequence name differ from the name of any other sequence, table, index, or view in the same schema.
+
+After you create a sequence, use the functions `NEXTVAL` and `CURRVAL` to operate on it. These functions are documented in [SQL reference](../../sql_reference/03_functions_and_operators/09_sequence_manipulation_functions/).
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the sequence to create.
+
+`increment`
+
+ The optional clause `INCREMENT BY increment` specifies the value to add to the current sequence value to create a new value. Use a positive value to create ascending sequence and a negative value to create a descending sequence. The default value is `1`.
+
+`NOMINVALUE | MINVALUE minvalue`
+
+ The optional clause `MINVALUE minvalue` determines the minimum value a sequence can generate. The defaults are 1 for ascending and -2<sup>63</sup>-1 for descending sequences. You can use the keywords `NOMINVALUE` to set this behavior to the default.
+
+`NOMAXVALUE | MAXVALUE maxvalue`
+
+ The optional clause `MAXVALUE maxvalue` determines the maximum value for the sequence. The defaults are 2<sup>63</sup>-1 for ascending and -1 for descending sequences. You can use the keywords `NOMAXVALUE` to set this behavior to the default.
+
+`start`
+
+ The optional clause `START WITH start` allows the sequence to begin anywhere. The default starting value is `minvalue` for ascending sequences and `maxvalue` for descending ones.
+
+`cache`
+
+ The optional clause `CACHE cache` specifies how many sequence numbers to preallocate and store in memory for faster access. The minimum value is `1`, which is also the default. This setting generates only one value at a time, that is, `NOCACHE`.
+
+`CYCLE`
+
+ The `CYCLE` option allows the sequence to wrap around when the `maxvalue` or `minvalue` is reached by an ascending or descending sequence, respectively. If the limit is reached, the next number generated is `minvalue` or `maxvalue`, respectively.
+
+ If you omit `CYCLE`, any calls to `NEXTVAL` after the sequence reaches its maximum value return an error. You can use the keywords `NO CYCLE` to use the default behavior. However, this term isn't compatible with Oracle databases.
+
+## Notes
+
+Sequences are based on big integer arithmetic, so the range can't exceed the range of an eight-byte integer (-9223372036854775808 to 9223372036854775807). Some older platforms might not have compiler support for eight-byte integers. In this case, sequences use regular `INTEGER` arithmetic (range -2147483648 to +2147483647).
+
+Unexpected results can occur if you use a `cache` setting greater than `1` for a sequence object to be used concurrently by multiple sessions. Each session allocates and caches successive sequence values during one access to the sequence object and increases the sequence object’s last value accordingly. Then, the next `cache-1` that uses `NEXTVAL` in that session returns the preallocated values without touching the sequence object. So, any numbers allocated but not used in a session are lost when that session ends. "Holes" in the sequence result.
+
+Furthermore, although multiple sessions are guaranteed to allocate distinct sequence values, the values might be generated out of sequence when all the sessions are considered. For example, with a `cache` setting of `10`, session A might reserve values 1..10 and return `NEXTVAL=1`. Then session B might reserve values 11..20 and return `NEXTVAL=11` before session A generates `NEXTVAL=2`. Thus, with a `cache` setting of `1`, it's safe to assume that `NEXTVAL` values are generated sequentially. With a `cache` setting greater than `1`, assume only that the `NEXTVAL` values are all distinct, not that they are generated sequentially. Also, the last value reflects the latest value reserved by any session, whether or not it was already returned by `NEXTVAL`.
+
+## Examples
+
+Create an ascending sequence called `serial`, starting at 101:
+
+```sql
+CREATE SEQUENCE serial START WITH 101;
+```
+
+Select the next number from this sequence:
+
+```sql
+SELECT serial.NEXTVAL FROM DUAL;
+__OUTPUT__
+ nextval
+---------
+     101
+(1 row)
+```
+
+Create a sequence called `supplier_seq` with the `NOCACHE` option:
+
+```sql
+CREATE SEQUENCE supplier_seq
+    MINVALUE 1
+    START WITH 1
+    INCREMENT BY 1
+    NOCACHE;
+```
+
+Select the next number from this sequence:
+
+```sql
+SELECT supplier_seq.NEXTVAL FROM DUAL;
+__OUTPUT__
+ nextval
+---------
+       1
+(1 row)
+```
+
+## See also
+
+[ALTER SEQUENCE](10_alter_sequence/#alter_sequence), [DROP SEQUENCE](56_drop_sequence/#drop_sequence)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/35_create_synonym.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/35_create_synonym.mdx
new file mode 100644
index 00000000000..7cb97ecc27c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/35_create_synonym.mdx
@@ -0,0 +1,91 @@
+---
+title: "CREATE SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.049.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.077.html"
+redirects:
+  - /epas/latest/epas_compat_sql/35_create_synonym/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_synonym" class="registered_link"></div>
+
+## Name
+
+`CREATE SYNONYM` &mdash; Define a new synonym.
+
+## Synopsis
+
+```sql
+CREATE [OR REPLACE] [PUBLIC] SYNONYM [<schema>.]<syn_name>
+        FOR <object_schema>.<object_name>[@<dblink_name>];
+```
+
+## Description
+
+`CREATE SYNONYM` defines a synonym for certain types of database objects. EDB Postgres Advanced Server supports synonyms for:
+
+-   Tables
+-   Views
+-   Materialized views
+-   Sequences
+-   Packages
+-   Procedures
+-   Functions
+-   Types
+-   Objects that are accessible through a database link
+-   Other synonyms
+
+## Parameters
+
+`syn_name`
+
+ The name of the synonym. A synonym name must be unique in a schema.
+
+`schema`
+
+ The name of the schema where the synonym resides. If you don't specify a schema name, the synonym is created in the first existing schema in your search path.
+
+`object_name`
+
+ The name of the object.
+
+`object_schema`
+
+ The name of the schema where the referenced object resides.
+
+`dblink_name`
+
+ The name of the database link through which you access an object.
+
+Include the `REPLACE` clause to replace an existing synonym definition with a new synonym definition.
+
+Include the `PUBLIC` clause to create the synonym in the `public` schema. The `CREATE PUBLIC SYNONYM` command, compatible with Oracle databases, creates a synonym that resides in the `public` schema:
+
+```sql
+CREATE [OR REPLACE] PUBLIC SYNONYM <syn_name> FOR
+<object_schema>.<object_name>;
+```
+
+This is a shorthand way to write:
+
+```sql
+CREATE [OR REPLACE] SYNONYM public.<syn_name> FOR
+<object_schema>.<object_name>;
+```
+
+## Notes
+
+Access to the object referenced by the synonym is determined by the permissions of the current user of the synonym. The synonym user must have the appropriate permissions on the underlying database object.
+
+## Examples
+
+Create a synonym for the `emp` table in a schema named `enterprisedb`:
+
+```sql
+CREATE SYNONYM personnel FOR enterprisedb.emp;
+```
+
+## See also
+
+[DROP SYNONYM](54_drop_synonym/#drop_synonym)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx
new file mode 100644
index 00000000000..39778b4a492
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/36_create_table.mdx
@@ -0,0 +1,372 @@
+---
+title: "CREATE TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.050.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.078.html"
+redirects:
+  - /epas/latest/epas_compat_sql/36_create_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_table" class="registered_link"></div>
+
+## Name
+
+`CREATE TABLE` &mdash; Define a new table.
+
+## Synopsis
+
+```sql
+CREATE [ GLOBAL TEMPORARY | UNLOGGED ] TABLE <table_name> (
+  { <column_name> <data_type> [ DEFAULT <default_expr> ]
+  [ <column_constraint> [ ... ] ] | <table_constraint> } [, ...]
+  )
+  [ WITH ( ROWIDS [= <value> ] ) ]
+  [ ON COMMIT { PRESERVE ROWS | DELETE ROWS } ]
+  [ TABLESPACE <tablespace> ]
+  { NOPARALLEL | PARALLEL [ <integer> ] }
+```
+
+Where `column_constraint` is:
+
+```sql
+[ CONSTRAINT <constraint_name> ]
+{ NOT NULL |
+  NULL |
+  UNIQUE [ USING INDEX TABLESPACE <tablespace> ] |
+  PRIMARY KEY [ USING INDEX TABLESPACE <tablespace> ] |
+  CHECK (<expression>) |
+  REFERENCES <reftable> [ ( <refcolumn> ) ]
+    [ ON DELETE <action> ] }
+[ DEFERRABLE | NOT DEFERRABLE ] [ INITIALLY DEFERRED |
+  INITIALLY IMMEDIATE ]
+```
+
+Where `table_constraint` is:
+
+```sql
+[ CONSTRAINT <constraint_name> ]
+{ UNIQUE ( <column_name> [, ...] )
+    [ USING INDEX [ <create_index_statement> ] TABLESPACE <tablespace> ] |
+  PRIMARY KEY ( <column_name> [, ...] )
+    [ USING INDEX [ <create_index_statement> ] TABLESPACE <tablespace> ] |
+  CHECK ( <expression> ) |
+  FOREIGN KEY ( <column_name> [, ...] )
+      REFERENCES <reftable> [ ( <refcolumn> [, ...] ) ]
+    [ ON DELETE <action> ] }
+[ DEFERRABLE | NOT DEFERRABLE ]
+[ INITIALLY DEFERRED | INITIALLY IMMEDIATE ]
+```
+
+## Description
+
+`CREATE TABLE` creates an empty table in the current database. The user who creates the table owns the table.
+
+If you provide a schema name, then the table is created in the specified schema. Otherwise it's created in the current schema. Temporary tables exist in a special schema, so you can't provide a schema name when creating a temporary table. The table name must differ from the name of any table, sequence, index, or view in the same schema.
+
+`CREATE TABLE` also creates a data type that represents the composite type corresponding to one row of the table. Therefore, tables can't have the same name as any existing data type in the same schema.
+
+The `PARALLEL` clause sets the degree of parallelism for a table. If you don't specify the `PARALLEL` clause, the server determines a value based on the relation size.
+
+The `NOPARALLEL` clause resets the parallelism for default execution, and `reloptions` shows the `parallel_workers` parameter as `0`.
+
+A table can't have more than 1600 columns. In practice, the effective limit is lower because of tuple-length constraints.
+
+The optional constraint clauses specify constraints or tests that new or updated rows must satisfy for an insert or update operation to succeed. A constraint is a SQL object that helps define the set of valid values in the table in various ways.
+
+You can define table constraints and column constraints. A column constraint is part of a column definition. A table constraint definition isn't tied to a particular column, and it can encompass more than one column. You can also write every column constraint as a table constraint. A column constraint is a notational convenience only if the constraint affects only one column.
+
+!!! Note
+    EDB Postgres Advanced Server allows you to create rowids on a foreign table by specifying either the `WITH (ROWIDS)` or `WITH (ROWIDS=true)` option in the `CREATE FOREIGN TABLE` syntax. Specifying the `WITH (ROWIDS)` or `WITH (ROWIDS=true)` option adds a rowid column to a foreign table. For information about `CREATE FOREIGN TABLE`, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/sql-createforeigntable.html).
+
+## Parameters
+
+`GLOBAL TEMPORARY`
+
+ Creates the table as a temporary table. Temporary tables are dropped at the end of a session or, optionally, at the end of the current transaction. (See the `ON COMMIT` parameter.) Existing permanent tables with the same name aren't visible to the current session while the temporary table exists unless you reference them with schema-qualified names. In addition, temporary tables aren't visible outside the session in which you created them. This aspect of global temporary tables isn't compatible with Oracle databases. Any indexes created on a temporary table are also temporary.
+
+`UNLOGGED`
+
+ Creates the table as an unlogged table. The data written to unlogged tables isn't written to the write-ahead log (WAL), making them faster than an ordinary table. Indexes created on an unlogged table are unlogged. The contents of an unlogged table aren't replicated to a standby server. The unlogged table is not crash-safe. It's truncated after a crash or shutdown.
+
+`table_name`
+
+ The name (optionally schema-qualified) of the table to create.
+
+`column_name`
+
+ The name of a column to create in the new table.
+
+`data_type`
+
+ The data type of the column. This can include array specifiers. For more information on the data types included with EDB Postgres Advanced Server, see [SQL reference](../../sql_reference/02_data_types/).
+
+`DEFAULT default_expr`
+
+ The `DEFAULT` clause assigns a default data value for the column whose column definition it appears in. The value is any variable-free expression. Subqueries and cross references to other columns in the current table aren't allowed. The data type of the default expression must match the data type of the column.
+
+ The default expression is used in any insert operation that doesn't specify a value for the column. If you don't specify a default for a column, then the default is `null`.
+
+`CONSTRAINT constraint_name`
+
+ An optional name for a column or table constraint. If you don't specify one, the system generates a name.
+
+`NOT NULL`
+
+ The column can't contain null values.
+
+`NULL`
+
+ The column can contain null values. This is the default.
+
+ This clause is available only for compatibility with nonstandard SQL databases. We don't recommend using it in new applications.
+
+`UNIQUE` &mdash; Column constraint.
+
+`UNIQUE (column_name [, ...] )` &mdash; Table constraint.
+
+ The `UNIQUE` constraint specifies that a group of one or more distinct columns of a table can contain only unique values. The behavior of the unique table constraint is the same as that for column constraints. However, the unique table constraint can span multiple columns.
+
+ For the purpose of a unique constraint, null values aren't considered equal.
+
+ Each unique table constraint must name a set of columns that's different from the set of columns named by any other unique or primary key constraint defined for the table. Otherwise it's the same constraint listed twice.
+
+`PRIMARY KEY` &mdash; Column constraint.
+
+`PRIMARY KEY ( column_name [, ...] )` &mdash; Table constraint.
+
+ The primary key constraint specifies that any columns of a table can contain only unique, non-duplicated, non-null values. Technically, `PRIMARY KEY` is a combination of `UNIQUE` and `NOT NULL`. However, identifying a set of columns as primary key also provides metadata about the design of the schema. A primary key implies that other tables might rely on this set of columns as a unique identifier for rows.
+
+ You can specify only one primary key for a table, whether as a column constraint or a table constraint.
+
+ Use the primary key constraint to name a set of columns that's different from other sets of columns named by any unique constraint defined for the same table.
+
+`CHECK (expression)`
+
+ The `CHECK` clause specifies an expression producing a Boolean result that new or updated rows must satisfy for an insert or update operation to succeed. Expressions evaluating to `TRUE` or “unknown” succeed. If any row of an insert or update operation produces a `FALSE` result, an error exception is raised and the insert or update doesn't alter the database. A check constraint specified as a column constraint must reference only that column’s value. An expression appearing in a table constraint can reference multiple columns.
+
+ Currently, `CHECK` expressions can't contain subqueries or refer to variables other than columns of the current row.
+
+`REFERENCES` reftable \[ `( refcolumn`) ] \[ `ON DELETE action` ] &mdash; Column constraint.  
+
+`FOREIGN KEY ( column [, ...] ) REFERENCES reftable [ ( refcolumn  [, ...] ) ] [ ON DELETE action ]` &mdash; Table constraint.
+
+ These clauses specify a foreign-key constraint, which requires that a group of columns of the new table must contain only values that match values in the referenced columns of some row of the referenced table. If you omit `refcolumn`, the primary key of the `reftable` is used. The referenced columns must be the columns of a unique or primary key constraint in the referenced table.
+
+ In addition, when the data in the referenced columns changes, certain actions are performed on the data in this table’s columns. The `ON DELETE` clause specifies the action to perform when a referenced row in the referenced table is being deleted. You can't defer referential actions even if the constraint is deferrable. Here are the following possible actions for each clause:
+
+-   `CASCADE`
+
+    Delete any rows referencing the deleted row, or update the value of the referencing column to the new value of the referenced column.
+
+-   `SET NULL`
+
+    Set the referencing columns to `NULL`.
+
+    If the referenced columns change frequently, we recommend adding an index to the foreign key column so that referential actions associated with the foreign key column are performed more efficiently.
+
+`DEFERRABLE`
+
+`NOT DEFERRABLE`
+
+ This parameter controls whether you can defer the constraint. A constraint that isn't deferrable is checked immediately after every command. You can postpone checking constraints that are deferrable until the end of the transaction using the `SET CONSTRAINTS` command. `NOT DEFERRABLE` is the default. Only foreign key constraints currently accept this clause. All other constraint types aren't deferrable.
+
+`INITIALLY IMMEDIATE`
+
+`INITIALLY DEFERRED`
+
+ If a constraint is deferrable, this clause specifies the default time to check the constraint. If the constraint is `INITIALLY IMMEDIATE`, it's checked after each statement. This is the default. If the constraint is `INITIALLY DEFERRED`, it's checked only at the end of the transaction. You can alter the constraint check time with the `SET CONSTRAINTS` command.
+
+`WITH ( ROWIDS [= value ] )`
+
+ The `ROWIDS` option for a table includes `value` equals to `TRUE/ON/1` or `FALSE/OFF/0`. When set to `TRUE/ON/1`, a `ROWID` column is created in the new table. `ROWID` is an auto-incrementing value based on a sequence that starts with `1` and assigned to each row of a table. The default value is always `TRUE`.
+
+ By default, a unique index is created on a `ROWID` column. The `ALTER` and `DROP` operations are restricted on a `ROWID` column.
+
+`ON COMMIT`
+
+ You can control the behavior of temporary tables at the end of a transaction block using `ON COMMIT`. The options are:
+
+-   `PRESERVE ROWS`
+
+    No special action is taken at the ends of transactions. This is the default behavior. This aspect isn't compatible with Oracle databases. The Oracle default is `DELETE ROWS`.
+
+-   `DELETE ROWS`
+
+    All rows in the temporary table are deleted at the end of each transaction block. Essentially, an automatic `TRUNCATE` is done at each commit.
+
+`TABLESPACE tablespace`
+
+ The `tablespace` is the name of the tablespace where the new table is created. If not specified, `default tablespace` is used or the database’s default tablespace if `default_tablespace` is an empty string.
+
+`USING INDEX [ create_index_statement ] TABLESPACE tablespace`
+
+ This clause allows selection of the tablespace in which the index associated with a `UNIQUE` or `PRIMARY KEY` constraint is created. If not specified, `default tablespace` is used, or the database’s default tablespace if `default_tablespace` is an empty string.
+
+ If you specify the `create_index_statement` option, the database server creates an index enabling unique or primary key constraints. The columns specified in the constraint and the columns of an index must be the same, but their order of appearance might differ.
+
+`PARALLEL`
+
+ Include the `PARALLEL` clause to specify the degree of parallelism for the table. Set the `parallel_workers` parameter equal to the degree of parallelism to perform a parallel scan of a table. Alternatively, if you specify `PARALLEL` but don't include a degree of parallelism, an index uses default parallelism.
+
+`NOPARALLEL`
+
+ Specify `NOPARALLEL` for default execution.
+
+`integer`
+
+ The `integer` indicates the degree of parallelism, which is a number of `parallel_workers` used in the parallel operation to perform a parallel scan on a table.
+
+## Notes
+
+EDB Postgres Advanced Server creates an index for each unique constraint and primary key constraint to enforce the uniqueness. Thus, you don't need to create an explicit index for primary key columns. For more information, see [`CREATE INDEX`](24_create_index/).
+
+## Examples
+
+Create table `dept` and table `emp`:
+
+```sql
+CREATE TABLE dept (
+    deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+    dname           VARCHAR2(14),
+    loc             VARCHAR2(13)
+);
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    mgr             NUMBER(4),
+    hiredate        DATE,
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                        REFERENCES dept(deptno)
+);
+```
+
+Define a unique table constraint for the table `dept`. You can define unique table constraints on one or more columns of the table.
+
+```sql
+CREATE TABLE dept (
+    deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+    dname           VARCHAR2(14) CONSTRAINT dept_dname_uq UNIQUE,
+    loc             VARCHAR2(13)
+);
+```
+
+Define a check column constraint:
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    mgr             NUMBER(4),
+    hiredate        DATE,
+    sal             NUMBER(7,2) CONSTRAINT emp_sal_ck CHECK (sal > 0),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                        REFERENCES dept(deptno)
+);
+```
+
+Define a check table constraint:
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    mgr             NUMBER(4),
+    hiredate        DATE,
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                        REFERENCES dept(deptno),
+    CONSTRAINT new_emp_ck CHECK (ename IS NOT NULL AND empno > 7000)
+);
+```
+
+Define a primary key table constraint for the table `jobhist`. You can define primary key table constraints on one or more columns of the table.
+
+```sql
+CREATE TABLE jobhist (
+    empno           NUMBER(4) NOT NULL,
+    startdate       DATE NOT NULL,
+    enddate         DATE,
+    job             VARCHAR2(9),
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2),
+    chgdesc         VARCHAR2(80),
+    CONSTRAINT jobhist_pk PRIMARY KEY (empno, startdate)
+);
+```
+
+This example assigns a literal constant default value for the column `job` and makes the default value of `hiredate` the date when the row is inserted.
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL CONSTRAINT emp_pk PRIMARY KEY,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9) DEFAULT 'SALESMAN',
+    mgr             NUMBER(4),
+    hiredate        DATE DEFAULT SYSDATE,
+    sal             NUMBER(7,2),
+    comm            NUMBER(7,2),
+    deptno          NUMBER(2) CONSTRAINT emp_ref_dept_fk
+                        REFERENCES dept(deptno)
+);
+```
+
+Create table `dept` in tablespace `diskvol1`:
+
+```sql
+CREATE TABLE dept (
+    deptno          NUMBER(2) NOT NULL CONSTRAINT dept_pk PRIMARY KEY,
+    dname           VARCHAR2(14),
+    loc             VARCHAR2(13)
+) TABLESPACE diskvol1;
+```
+
+This `PARALLEL` example creates a table `sales` and sets a degree of parallelism to 6:
+
+```sql
+CREATE TABLE sales (deptno number) PARALLEL 6 WITH (FILLFACTOR=66);
+```
+
+This `NOPARALLEL` example creates a table `sales_order` and sets a degree of parallelism to 0:
+
+```sql
+CREATE TABLE sales_order (deptno number) NOPARALLEL WITH (FILLFACTOR=66);
+```
+
+This example creates a table named `dept`. The definition creates a unique key on the `dname` column. The constraint `dept_dname_uq` identifies the `dname` column as a unique key. The preceding statement includes the `USING_INDEX` clause, which explicitly creates an index on a table `dept` with the index statement enabling the unique constraint.
+
+```sql
+CREATE TABLE dept (
+    deptno          NUMBER(2) NOT NULL,
+    dname           VARCHAR2(14),
+    loc             VARCHAR2(13),
+    CONSTRAINT dept_dname_uq UNIQUE(dname)
+       USING INDEX (CREATE UNIQUE INDEX idx_dept_dname_uq ON dept(dname))
+);
+```
+
+This example creates a table named `emp`. The definition creates a primary key on the `ename` column. The `emp_ename_pk` constraint identifies the `ename` column as a primary key of the `emp` table. The preceding statement includes the `USING_INDEX` clause, which explicitly creates an index on a table `emp` with the index statement enabling the primary constraint.
+
+```sql
+CREATE TABLE emp (
+    empno           NUMBER(4) NOT NULL,
+    ename           VARCHAR2(10),
+    job             VARCHAR2(9),
+    sal             NUMBER(7,2),
+    deptno          NUMBER(2),
+    CONSTRAINT emp_ename_pk PRIMARY KEY (ename)
+        USING INDEX (CREATE INDEX idx_emp_ename_pk ON emp (ename))
+);
+```
+
+## See also
+
+[ALTER TABLE](12_alter_table/#alter_table), [DROP TABLE](57_drop_table/#drop_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx
new file mode 100644
index 00000000000..cb8a42ec106
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/37_create_table_as.mdx
@@ -0,0 +1,49 @@
+---
+title: "CREATE TABLE AS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.051.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.079.html"
+redirects:
+  - /epas/latest/epas_compat_sql/37_create_table_as/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_table_as" class="registered_link"></div>
+
+## Name
+
+`CREATE TABLE AS` &mdash; Define a new table from the results of a query.
+
+## Synopsis
+
+```sql
+CREATE [ GLOBAL TEMPORARY ] TABLE <table_name>
+  [ (<column_name> [, ...] ) ]
+  [ ON COMMIT { PRESERVE ROWS | DELETE ROWS } ]
+  [ TABLESPACE tablespace ]
+  AS <query>
+```
+
+## Description
+
+`CREATE TABLE AS` creates a table and fills it with data computed by a `SELECT` command. The table columns have the names and data types associated with the output columns of the `SELECT`. You can override the column names by providing an explicit list of new column names.
+
+`CREATE TABLE AS` is similar to creating a view. However, it differs because it creates a table and evaluates the query once to fill the new table initially. The new table doesn't track later changes to the source tables of the query. In contrast, a view reevaluates its defining `SELECT` statement whenever you query it.
+
+## Parameters
+
+`GLOBAL TEMPORARY`
+
+ Specify to create the table as a temporary table. For details, see [`CREATE TABLE`](36_create_table/).
+
+`table_name`
+
+ The name (optionally schema-qualified) of the table to create.
+
+`column_name`
+
+ The name of a column in the new table. If you don't provide column names, the names are taken from the output column names of the query.
+
+`query`
+
+ A query statement (a `SELECT` command). For a description of the allowed syntax, see [`SELECT`](71_select/).
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/38_create_trigger.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/38_create_trigger.mdx
new file mode 100644
index 00000000000..d930c07c761
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/38_create_trigger.mdx
@@ -0,0 +1,509 @@
+---
+title: "CREATE TRIGGER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.052.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.080.html"
+redirects:
+  - /epas/latest/epas_compat_sql/38_create_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_trigger" class="registered_link"></div>
+
+## Name
+
+`CREATE TRIGGER` &mdash; Define a simple trigger.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] TRIGGER <name>
+  { BEFORE | AFTER | INSTEAD OF }
+  { INSERT | UPDATE | DELETE | TRUNCATE }
+      [ OR { INSERT | UPDATE | DELETE | TRUNCATE} ] [, ...]
+    ON <table>
+  [ REFERENCING { OLD AS <old> | NEW AS <new> } ...]
+  [ FOR EACH ROW ]
+  [ WHEN <condition> ]
+  [ DECLARE
+      [ PRAGMA AUTONOMOUS_TRANSACTION; ]
+      <declaration>; [, ...] ]
+    BEGIN
+      <statement>; [, ...]
+  [ EXCEPTION
+    { WHEN <exception> [ OR <exception> ] [...] THEN
+        <statement>; [, ...] } [, ...]
+  ]
+    END
+```
+
+## Name
+
+`CREATE TRIGGER` &mdash; Define a compound trigger.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] TRIGGER <name>
+  FOR { INSERT | UPDATE | DELETE | TRUNCATE }
+        [ OR { INSERT | UPDATE | DELETE | TRUNCATE } ] [, ...]
+           ON <table>
+       [ REFERENCING { OLD AS <old> | NEW AS <new> } ...]
+       [ WHEN <condition> ]
+       COMPOUND TRIGGER
+       [ <private_declaration>; ] ...
+       [ <procedure_or_function_definition> ] ...
+       <compound_trigger_definition>
+        END
+```
+
+Where `private_declaration` is an identifier of a private variable that any procedure or function can access. There can be zero, one, or more private variables. `private_declaration` can be any of the following:
+
+-   Variable declaration
+-   Record declaration
+-   Collection declaration
+-   `REF CURSOR` and cursor variable declaration
+-   `TYPE` definitions for records, collections, and `REF CURSOR` cursors
+-   Exception
+-   Object variable declaration
+
+Where `procedure_or_function_definition` :=
+
+```text
+procedure_definition | function_definition
+```
+
+Where `procedure_definition` :=
+
+```sql
+PROCEDURE proc_name[ argument_list ]
+  [ options_list ]
+  { IS | AS }
+    procedure_body
+  END [ proc_name ];
+```
+
+Where `procedure_body` :=
+
+```sql
+[ declaration; ] [, ...]
+BEGIN
+  statement; [...]
+[ EXCEPTION
+   { WHEN exception [OR exception] [...]] THEN statement; }
+   [...]
+]
+```
+
+Where `function_definition` :=
+
+```sql
+FUNCTION func_name [ argument_list ]
+  RETURN rettype [ DETERMINISTIC ]
+  [ options_list ]
+  { IS | AS }
+    function_body
+  END [ func_name ] ;
+```
+
+Where `function_body` :=
+
+```sql
+[ declaration; ] [, ...]
+BEGIN
+  statement; [...]
+[ EXCEPTION
+  { WHEN exception [ OR exception ] [...] THEN statement; }
+  [...]
+]
+```
+
+Where `compound_trigger_definition` :=
+
+```sql
+{ compound_trigger_event } { IS | AS }
+  compound_trigger_body
+END [ compound_trigger_event ] [ ... ]
+```
+
+Where `compound_trigger_event` :=
+
+```sql
+[ BEFORE STATEMENT | BEFORE EACH ROW | AFTER EACH ROW | AFTER STATEMENT  | INSTEAD OF EACH ROW ]
+```
+
+Where `compound_trigger_body` :=
+
+```sql
+[ declaration; ] [, ...]
+BEGIN
+  statement; [...]
+[ EXCEPTION
+   { WHEN exception [OR exception] [...] THEN statement; }
+   [...]
+]
+```
+
+## Description
+
+`CREATE TRIGGER` defines a new trigger. `CREATE OR REPLACE TRIGGER` either creates a trigger or replaces an existing definition.
+
+If you're using the `CREATE TRIGGER` keywords to create a new trigger, the name of the new trigger can't match any existing trigger defined on the same table. Triggers are created in the same schema as the table where the triggering event is defined.
+
+If you're updating the definition of an existing trigger, use the `CREATE OR REPLACE TRIGGER` keywords.
+
+When you use syntax that's compatible with Oracle to create a trigger, the trigger runs as a `SECURITY DEFINER` function.
+
+## Parameters
+
+`name`
+
+ The name of the trigger to create.
+
+`BEFORE | AFTER`
+
+ Determines whether the trigger is fired before or after the triggering event.
+
+`INSTEAD OF`
+
+ Modifies an updatable view. The trigger executes to update the underlying tables appropriately. The `INSTEAD OF` trigger executes for each row of the view that's updated or modified.
+
+`INSERT | UPDATE | DELETE | TRUNCATE`
+
+ Defines the triggering event.
+
+`table`
+
+ The name of the table or view on which the triggering event occurs.
+
+`condition`
+
+ A Boolean expression that determines if the trigger executes. If `condition` evaluates to `TRUE`, the trigger fires.
+
+-   If the simple trigger definition includes the `FOR EACH ROW` keywords, the `WHEN` clause can refer to columns of the old or new row values by writing `OLD.column_name` or `NEW.column_name`. `INSERT` triggers can't refer to `OLD`, and `DELETE` triggers can't refer to `NEW`.
+
+-   If the compound trigger definition includes a statement-level trigger having a `WHEN` clause, then the trigger executes without evaluating the expression in the `WHEN` clause. Similarly, if a compound trigger definition includes a row-level trigger having a `WHEN` clause, then the trigger executes if the expression evaluates to `TRUE`.
+
+-   If the trigger includes the `INSTEAD OF` keywords, it can't include a `WHEN` clause. A `WHEN` clause can't contain subqueries.
+
+`REFERENCING { OLD AS old | NEW AS new } ...`
+
+ `REFERENCING` clause to reference old rows and new rows. This clause is restricted in that you can replace `old` only with an identifier named `old` or any equivalent that's saved in all lowercase. Examples include `REFERENCING OLD AS old`, `REFERENCING OLD AS OLD`, and `REFERENCING OLD AS "old"`. Also, you can replace `new` only with an identifier named `new` or any equivalent that's saved in all lowercase. Examples include `REFERENCING NEW AS new`, `REFERENCING NEW AS NEW`, and `REFERENCING NEW AS "new"`.
+
+ You can specify one or both phrases `OLD AS old` and `NEW AS new` in the `REFERENCING` clause, such as `REFERENCING NEW AS New OLD AS Old`.
+
+ This clause isn't compatible with Oracle databases in that you can't use identifiers other than `old` or `new`.
+
+`FOR EACH ROW`
+
+ Determines whether to fire the trigger once for every row affected by the triggering event or just once per SQL statement. If you specify this parameter, the trigger is fired once for every affected row (row-level trigger). Otherwise the trigger is a statement-level trigger.
+
+`PRAGMA AUTONOMOUS_TRANSACTION`
+
+ `PRAGMA AUTONOMOUS_TRANSACTION` is the directive that sets the trigger as an autonomous transaction.
+
+`declaration`
+
+ A variable, type, `REF CURSOR`, or subprogram declaration. If you include subprogram declarations, declare them after all other variable, type, and `REF CURSOR` declarations.
+
+`statement`
+
+ An SPL program statement. A `DECLARE - BEGIN - END` block is considered an SPL statement. Thus, the trigger body can contain nested blocks.
+
+`exception`
+
+ An exception condition name, such as `NO_DATA_FOUND` and `OTHERS`.
+
+## Examples
+
+This example shows a statement-level trigger that fires after the triggering statement (insert, update, or delete on table `emp`) executes.
+
+```sql
+CREATE OR REPLACE TRIGGER user_audit_trig
+    AFTER INSERT OR UPDATE OR DELETE ON emp
+DECLARE
+    v_action        VARCHAR2(24);
+BEGIN
+    IF INSERTING THEN
+        v_action := ' added employee(s) on ';
+    ELSIF UPDATING THEN
+        v_action := ' updated employee(s) on ';
+    ELSIF DELETING THEN
+        v_action := ' deleted employee(s) on ';
+    END IF;
+    DBMS_OUTPUT.PUT_LINE('User ' || USER || v_action ||
+        TO_CHAR(SYSDATE,'YYYY-MM-DD'));
+END;
+```
+
+This example is a row-level trigger that fires before each row is either inserted, updated, or deleted on table `emp`.
+
+```sql
+CREATE OR REPLACE TRIGGER emp_sal_trig
+    BEFORE DELETE OR INSERT OR UPDATE ON emp
+    FOR EACH ROW
+DECLARE
+    sal_diff       NUMBER;
+BEGIN
+    IF INSERTING THEN
+        DBMS_OUTPUT.PUT_LINE('Inserting employee ' || :NEW.empno);
+        DBMS_OUTPUT.PUT_LINE('..New salary: ' || :NEW.sal);
+    END IF;
+    IF UPDATING THEN
+        sal_diff := :NEW.sal - :OLD.sal;
+        DBMS_OUTPUT.PUT_LINE('Updating employee ' || :OLD.empno);
+        DBMS_OUTPUT.PUT_LINE('..Old salary: ' || :OLD.sal);
+        DBMS_OUTPUT.PUT_LINE('..New salary: ' || :NEW.sal);
+        DBMS_OUTPUT.PUT_LINE('..Raise     : ' || sal_diff);
+    END IF;
+    IF DELETING THEN
+        DBMS_OUTPUT.PUT_LINE('Deleting employee ' || :OLD.empno);
+        DBMS_OUTPUT.PUT_LINE('..Old salary: ' || :OLD.sal);
+    END IF;
+END;
+```
+
+This example shows a compound trigger that records a change to the employee salary by defining a compound trigger `hr_trigger` on table `emp`.
+
+Create a table named `emp`:
+
+```sql
+CREATE TABLE emp(EMPNO INT, ENAME TEXT, SAL INT, DEPTNO INT);
+CREATE TABLE
+```
+
+Create a compound trigger named `hr_trigger`. The trigger uses each of the four timing-points to modify the salary with an `INSERT`, `UPDATE`, or `DELETE` statement. In the global declaration section, the initial salary is declared as `10,000`.
+
+```sql
+CREATE OR REPLACE TRIGGER hr_trigger
+  FOR INSERT OR UPDATE OR DELETE ON emp
+    COMPOUND TRIGGER
+  -- Global declaration.
+  var_sal NUMBER := 10000;
+
+  BEFORE STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('Before Statement: ' || var_sal);
+  END BEFORE STATEMENT;
+
+  BEFORE EACH ROW IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('Before Each Row: ' || var_sal);
+  END BEFORE EACH ROW;
+
+  AFTER EACH ROW IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('After Each Row: ' || var_sal);
+  END AFTER EACH ROW;
+
+  AFTER STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('After Statement: ' || var_sal);
+  END AFTER STATEMENT;
+
+END hr_trigger;
+
+Output: Trigger created.
+```
+
+`INSERT` the record into table `emp`.
+
+```sql
+INSERT INTO emp (EMPNO, ENAME, SAL, DEPTNO) VALUES(1111,'SMITH', 10000, 20);
+```
+
+The `INSERT` statement produces the following output:
+
+```sql
+__OUTPUT__
+Before Statement: 11000
+Before each row: 12000
+After each row: 13000
+After statement: 14000
+INSERT 0 1
+```
+
+The `UPDATE` statement updates the employee salary record, setting the salary to `15000` for a specific employee number:
+
+```sql
+UPDATE emp SET SAL = 15000 where EMPNO = 1111;
+```
+
+The `UPDATE` statement produces the following output:
+
+sql
+__OUTPUT__
+Before Statement: 11000
+Before each row: 12000
+After each row: 13000
+After statement: 14000
+UPDATE 1
+
+SELECT * FROM emp;
+ EMPNO | ENAME |  SAL  | DEPTNO
+-------+-------+-------+--------
+  1111 | SMITH | 15000 |     20
+(1 row)
+```
+
+The `DELETE` statement deletes the employee salary record:
+
+```sql
+DELETE from emp where EMPNO = 1111;
+```
+
+The `DELETE` statement produces the following output:
+
+```sql
+Before Statement: 11000
+Before each row: 12000
+After each row: 13000
+After statement: 14000
+DELETE 1
+
+SELECT * FROM emp;
+__OUTPUT__
+ EMPNO | ENAME | SAL | DEPTNO
+-------+-------+-----+--------
+(0 rows)
+```
+
+The `TRUNCATE` statement removes all the records from the `emp` table:
+
+```sql
+CREATE OR REPLACE TRIGGER hr_trigger
+  FOR TRUNCATE ON emp
+    COMPOUND TRIGGER
+  -- Global declaration.
+  var_sal NUMBER := 10000;
+  BEFORE STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('Before Statement: ' || var_sal);
+  END BEFORE STATEMENT;
+
+  AFTER STATEMENT IS
+  BEGIN
+    var_sal := var_sal + 1000;
+    DBMS_OUTPUT.PUT_LINE('After Statement: ' || var_sal);
+  END AFTER STATEMENT;
+
+END hr_trigger;
+
+Output: Trigger created.
+```
+
+The `TRUNCATE` statement produces the following output:
+
+```sql
+TRUNCATE emp;
+__OUTPUT__
+Before Statement: 11000
+After statement: 12000
+TRUNCATE TABLE
+```
+
+!!! Note
+    You can use the `TRUNCATE` statement only at a `BEFORE STATEMENT` or `AFTER STATEMENT` timing point.
+
+This example creates a compound trigger named `hr_trigger` on the `emp` table. It is a `WHEN` condition that checks and prints employee salary whenever an `INSERT`, `UPDATE`, or `DELETE` statement affects the `emp` table. The database evaluates the `WHEN` condition for a row-level trigger, and the trigger executes once per row if the `WHEN` condition evaluates to `TRUE`. The statement-level trigger executes regardless of the `WHEN` condition.
+
+```sql
+CREATE OR REPLACE TRIGGER hr_trigger
+  FOR INSERT OR UPDATE OR DELETE ON emp
+  REFERENCING NEW AS new OLD AS old
+  WHEN (old.sal > 5000 OR new.sal < 8000)
+    COMPOUND TRIGGER
+
+  BEFORE STATEMENT IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('Before Statement');
+  END BEFORE STATEMENT;
+
+  BEFORE EACH ROW IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('Before Each Row: ' || :OLD.sal ||' ' || :NEW.sal);
+  END BEFORE EACH ROW;
+
+  AFTER EACH ROW IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('After Each Row: ' || :OLD.sal ||' ' || :NEW.sal);
+  END AFTER EACH ROW;
+
+  AFTER STATEMENT IS
+  BEGIN
+    DBMS_OUTPUT.PUT_LINE('After Statement');
+  END AFTER STATEMENT;
+
+END hr_trigger;
+```
+
+Insert the record into table `emp`:
+
+```sql
+INSERT INTO emp(EMPNO, ENAME, SAL, DEPTNO) VALUES(1111, 'SMITH', 1600, 20);
+```
+
+The `INSERT` statement produces the following output:
+
+```sql
+__OUTPUT__
+Before Statement
+Before Each Row: 1600
+After Each Row: 1600
+After Statement
+INSERT 0 1
+```
+
+The `UPDATE` statement updates the employee salary record, setting the salary to `7500`:
+
+```sql
+UPDATE emp SET SAL = 7500 where EMPNO = 1111;
+```
+
+The `UPDATE` statement produces the following output:
+
+```sql
+Before Statement
+Before Each Row: 1600 7500
+After Each Row: 1600 7500
+After Statement
+UPDATE 1
+
+SELECT * from emp;
+__OUTPUT__
+ empno | ename | sal  | deptno
+-------+-------+------+--------
+  1111 | SMITH | 7500 |     20
+(1 row)
+```
+
+The `DELETE` statement deletes the employee salary record:
+
+```sql
+DELETE from emp where EMPNO = 1111;
+```
+
+The `DELETE` statement produces the following output:
+
+```sql
+Before Statement
+Before Each Row: 7500
+After Each Row: 7500
+After Statement
+DELETE 1
+
+SELECT * from emp;
+__OUTPUT__
+ empno | ename | sal | deptno
+-------+-------+-----+--------
+(0 rows)
+```
+
+## See also
+
+[ALTER TRIGGER](13_alter_trigger/#alter_trigger), [DROP TRIGGER](59_drop_trigger/#drop_trigger)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/39_create_type.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/39_create_type.mdx
new file mode 100644
index 00000000000..791ca95b577
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/39_create_type.mdx
@@ -0,0 +1,357 @@
+---
+title: "CREATE TYPE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.053.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.081.html"
+redirects:
+  - /epas/latest/epas_compat_sql/39_create_type/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_type" class="registered_link"></div>
+
+## Name
+
+`CREATE TYPE` &mdash; Define a new user-defined type, The new type can be an object type, a collection type (a nested table type or a varray type), or a composite type.
+
+## Synopsis
+
+### Object Type
+
+```sql
+CREATE [ OR REPLACE ] TYPE <name>
+  [ AUTHID { DEFINER | CURRENT_USER } ]
+  { IS | AS } OBJECT
+( { <attribute> { <datatype> | <objtype> | <collecttype> } }
+    [, ...]
+  [ <method_spec> ] [, ...]
+) [ [ NOT ] { FINAL | INSTANTIABLE } ] ...
+```
+
+Where `method_spec` is:
+
+```sql
+[ [ NOT ] { FINAL | INSTANTIABLE } ] ...
+[ OVERRIDING ]
+  <subprogram_spec>
+```
+
+Where `subprogram_spec` is:
+
+```sql
+{ MEMBER | STATIC }
+{ PROCEDURE <proc_name>
+    [ ( [ SELF [ IN | IN OUT ] <name> ]
+        [, <argname> [ IN | IN OUT | OUT ] <argtype>
+                     [ DEFAULT <value> ]
+        ] ...)
+    ]
+|
+  FUNCTION <func_name>
+    [ ( [ SELF [ IN | IN OUT ] <name> ]
+        [, <argname> [ IN | IN OUT | OUT ] <argtype>
+                     [ DEFAULT <value> ]
+        ] ...)
+    ]
+  RETURN <rettype>
+}
+```
+
+### Nested table type
+
+```sql
+CREATE [ OR REPLACE ] TYPE <name> { IS | AS } TABLE OF
+  { <datatype> | <objtype> | <collecttype> }
+```
+
+### Varray type
+
+```sql
+CREATE [ OR REPLACE ] TYPE <name> { IS | AS }
+  { VARRAY | VARYING ARRAY } (<maxsize>) OF { <datatype> | <objtype> }
+```
+
+### Composite type
+
+```sql
+CREATE [ OR REPLACE ] TYPE <name> { IS | AS }
+( [ attribute <datatype> ][, ...]
+)
+```
+
+## Description
+
+`CREATE TYPE` defines a new data type. The types that you can create are an object type, a nested table type, a varray type, or a composite type. Nested table and varray types belong to the category of types known as *collections*.
+
+Composite types aren't compatible with Oracle databases. However, SPL programs can access composite types along with other types.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the type to create.
+
+`DEFINER | CURRENT_USER`
+
+ Specifies whether to use the privileges of the object type owner (`DEFINER`) or of the current user executing a method in the object type (`CURRENT_USER`) to determine whether access is allowed to database objects referenced in the object type. `DEFINER` is the default.
+
+`attribute`
+
+ The name of an attribute in the object type or composite type.
+
+`datatype`
+
+ The data type that defines an attribute of the object type or composite type, or the elements of the collection type that's being created.
+
+`objtype`
+
+ The name of an object type that defines an attribute of the object type or the elements of the collection type that's being created.
+
+`collecttype`
+
+ The name of a collection type that defines an attribute of the object type or the elements of the collection type that's being created.
+
+`FINAL`
+
+`NOT FINAL`
+
+ For an object type, specifies whether you can derive a subtype from the object type. `FINAL` (you can't derive a subtype from the object type) is the default.
+
+ For `method_spec`, specifies whether you can override the method in a subtype. `NOT FINAL` (you can override the method in a subtype) is the default.
+
+`INSTANTIABLE`
+
+`NOT INSTANTIABLE`
+
+ For an object type, specifies whether you can create an object instance of this object type. `INSTANTIABLE` (you can create an instance of this object type) is the default. If you specify `NOT INSTANTIABLE`, then you must specify `NOT FINAL` as well. If `method_spec` for any method in the object type contains the `NOT INSTANTIABLE` qualifier, then the object type must be defined with `NOT INSTANTIABLE` and `NOT FINAL` following the closing parenthesis of the object type specification.
+
+ For `method_spec`, specifies whether the object type definition provides an implementation for the method. `INSTANTIABLE` (the `CREATE TYPE BODY` command for the object type provides the implementation of the method) is the default. If you specify `NOT INSTANTIABLE`, then the `CREATE TYPE BODY` command for the object type can't contain the implementation of the method.
+
+`OVERRIDING`
+
+ If you spcify `OVERRIDING`, `method_spec` overrides an identically named method with the same number of identically named method arguments with the same data types, in the same order, and the same return type (if the method is a function) as defined in a supertype.
+
+`MEMBER`
+
+`STATIC`
+
+ Specify `MEMBER` if the subprogram operates on an object instance. Specify `STATIC` if the subprogram operates independently of any particular object instance.
+
+`proc_name`
+
+ The name of the procedure to create.
+
+`SELF [ IN | IN OUT ] name`
+
+ For a member method, there is an implicit, built-in parameter named `SELF` whose data type is that of the object type being defined. `SELF` refers to the object instance that's currently invoking the method. You can explicitly declare `SELF` as an `IN` or `IN OUT` parameter in the parameter list. If explicitly declared, `SELF` must be the first parameter in the parameter list. If you don't explicitly declare `SELF`, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions.
+
+`argname`
+
+ The name of an argument. The argument is referenced by this name in the method body.
+
+`argtype`
+
+ The data types of the method’s arguments. The argument types can be a base data type or a user-defined type such as a nested table or an object type. Don't specify a length for any base type. For example, specify `VARCHAR2`, not `VARCHAR2(10)`.
+
+`DEFAULT value`
+
+ Supplies a default value for an input argument if you don't supply one in the method call. You can't specify `DEFAULT` for arguments with modes `IN OUT` or `OUT`.
+
+`func_name`
+
+ The name of the function to create.
+
+`rettype`
+
+ The return data type, which can be any of the types listed for `argtype`. Don't specify a length for `rettype`.
+
+`maxsize`
+
+ The maximum number of elements permitted in the varray.
+
+## Examples
+
+### Creating an object type
+
+Create object type `addr_obj_typ`:
+
+```sql
+CREATE OR REPLACE TYPE addr_obj_typ AS OBJECT (
+    street          VARCHAR2(30),
+    city            VARCHAR2(20),
+    state           CHAR(2),
+    zip             NUMBER(5)
+);
+```
+
+Create object type `emp_obj_typ` that includes a member method `display_emp`:
+
+```sql
+CREATE OR REPLACE TYPE emp_obj_typ AS OBJECT (
+    empno           NUMBER(4),
+    ename           VARCHAR2(20),
+    addr            ADDR_OBJ_TYP,
+    MEMBER PROCEDURE display_emp (SELF IN OUT emp_obj_typ)
+);
+```
+
+Create object type `dept_obj_typ` that includes a static method `get_dname`:
+
+```sql
+CREATE OR REPLACE TYPE dept_obj_typ AS OBJECT (
+    deptno          NUMBER(2),
+    STATIC FUNCTION get_dname (p_deptno IN NUMBER) RETURN VARCHAR2,
+    MEMBER PROCEDURE display_dept
+);
+```
+
+### Creating a collection type
+
+Create a nested table type `budget_tbl_typ` of data type `NUMBER(8,2)`:
+
+```sql
+CREATE OR REPLACE TYPE budget_tbl_typ IS TABLE OF NUMBER(8,2);
+```
+
+### Creating and using a composite type
+
+This example uses a composite type accessed from an anonymous block.
+
+This example creates the composite type:
+
+```sql
+CREATE OR REPLACE TYPE emphist_typ AS (
+    empno           NUMBER(4),
+    ename           VARCHAR2(10),
+    hiredate        DATE,
+    job             VARCHAR2(9),
+    sal             NUMBER(7,2)
+);
+```
+
+This code shows the anonymous block that accesses the composite type:
+
+```sql
+DECLARE
+    v_emphist       EMPHIST_TYP;
+BEGIN
+    v_emphist.empno    := 9001;
+    v_emphist.ename    := 'SMITH';
+    v_emphist.hiredate := '01-AUG-17';
+    v_emphist.job      := 'SALESMAN';
+    v_emphist.sal      := 8000.00;
+    DBMS_OUTPUT.PUT_LINE('   EMPNO: ' || v_emphist.empno);
+    DBMS_OUTPUT.PUT_LINE('   ENAME: ' || v_emphist.ename);
+    DBMS_OUTPUT.PUT_LINE('HIREDATE: ' || v_emphist.hiredate);
+    DBMS_OUTPUT.PUT_LINE('     JOB: ' || v_emphist.job);
+    DBMS_OUTPUT.PUT_LINE('     SAL: ' || v_emphist.sal);
+END;
+
+   EMPNO: 9001
+   ENAME: SMITH
+HIREDATE: 01-AUG-17 00:00:00
+     JOB: SALESMAN
+     SAL: 8000.00
+```
+
+This example uses a composite type accessed from a user-defined record type declared in a package body.
+
+The following creates the composite type:
+
+```sql
+CREATE OR REPLACE TYPE salhist_typ AS (
+    startdate       DATE,
+    job             VARCHAR2(9),
+    sal             NUMBER(7,2)
+);
+```
+
+The following defines the package specification:
+
+```sql
+CREATE OR REPLACE PACKAGE emp_salhist
+IS
+    PROCEDURE fetch_emp (
+        p_empno     IN NUMBER
+    );
+END;
+```
+
+The following defines the package body:
+
+```sql
+CREATE OR REPLACE PACKAGE BODY emp_salhist
+IS
+    TYPE emprec_typ IS RECORD (
+        empno       NUMBER(4),
+        ename       VARCHAR(10),
+        salhist     SALHIST_TYP
+    );
+    TYPE emp_arr_typ IS TABLE OF emprec_typ INDEX BY BINARY_INTEGER;
+    emp_arr         emp_arr_typ;
+
+    PROCEDURE fetch_emp (
+        p_empno     IN NUMBER
+    )
+    IS
+        CURSOR emp_cur IS SELECT e.empno, e.ename, h.startdate, h.job, h.sal
+            FROM emp e, jobhist h
+            WHERE e.empno = p_empno
+              AND e.empno = h.empno;
+
+        i           INTEGER := 0;
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('EMPNO  ENAME    STARTDATE  JOB         ' ||
+        'SAL        ');
+        DBMS_OUTPUT.PUT_LINE('-----  -------  ---------  ---------   ' ||
+        '---------');
+
+        FOR r_emp IN emp_cur LOOP
+            i := i + 1;
+            emp_arr(i) := (r_emp.empno, r_emp.ename,
+                (r_emp.startdate, r_emp.job, r_emp.sal));
+        END LOOP;
+
+        FOR i IN 1 .. emp_arr.COUNT LOOP
+            DBMS_OUTPUT.PUT_LINE(emp_arr(i).empno || '   ' ||
+                RPAD(emp_arr(i).ename,8) || ' ' ||
+                TO_CHAR(emp_arr(i).salhist.startdate,'DD-MON-YY') || '  ' ||
+                RPAD(emp_arr(i).salhist.job,10) || ' ' ||
+                TO_CHAR(emp_arr(i).salhist.sal,'99,999.99'));
+        END LOOP;
+    END;
+END;
+```
+
+In the declaration of the `TYPE emprec_typ IS RECORD` data structure in the package body, the `salhist` field is defined with the `SALHIST_TYP` composite type created by the `CREATE TYPE salhist_typ` statement.
+
+The associative array definition `TYPE emp_arr_typ IS TABLE OF emprec_typ` references the record type data structure `emprec_typ` that includes the field `salhist` defined with the `SALHIST_TYP` composite type.
+
+This example invokes the package procedure that loads the array from a join of the `emp` and `jobhist` tables and then displays the array content:
+
+```sql
+EXEC emp_salhist.fetch_emp(7788);
+__OUTPUT__
+EMPNO  ENAME    STARTDATE  JOB         SAL
+-----  -------  ---------  ---------   ---------
+7788   SCOTT    19-APR-87  CLERK        1,000.00
+7788   SCOTT    13-APR-88  CLERK        1,040.00
+7788   SCOTT    05-MAY-90  ANALYST      3,000.00
+
+EDB-SPL Procedure successfully completed
+```
+
+## Notes
+For packages only, you can include a composite type in a user-defined record type declared with the `TYPE IS RECORD` statement in the package specification or package body. This nested structure isn't permitted in other SPL programs such as functions, procedures, and triggers.
+
+In the `CREATE TYPE` command, if you include a schema name, then the type is created in the specified schema. Otherwise it's created in the current schema. The name of the new type can't match any existing type in the same schema unless you want to update the definition of an existing type. In that case, use `CREATE OR REPLACE TYPE`.
+
+You can't use the `OR REPLACE` option to add, delete, or modify the attributes of an existing object type. Use the `DROP TYPE` command to first delete the existing object type. You can use the `OR REPLACE` option to add, delete, or modify the methods in an existing object type.
+
+You can use the PostgreSQL form of the `ALTER TYPE ALTER ATTRIBUTE` command to change the data type of an attribute in an existing object type. However, the `ALTER TYPE` command can't add or delete attributes in the object type.
+
+The user that creates the type becomes the owner of the type.
+
+## See also
+
+[CREATE TYPE BODY](40_create_type_body/#create_type_body), [DROP TYPE](60_drop_type/#drop_type)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/40_create_type_body.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/40_create_type_body.mdx
new file mode 100644
index 00000000000..179e2781f09
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/40_create_type_body.mdx
@@ -0,0 +1,156 @@
+---
+title: "CREATE TYPE BODY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.054.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.082.html"
+redirects:
+  - /epas/latest/epas_compat_sql/40_create_type_body/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_type_body" class="registered_link"></div>
+
+## Name
+
+`CREATE TYPE BODY` &mdash; Define a new object type body.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] TYPE BODY <name>
+  { IS | AS }
+  <method_spec> [...]
+END
+```
+
+Where `method_spec` is:
+
+```text
+subprogram_spec
+```
+
+Where `subprogram_spec` is:
+
+```sql
+{ MEMBER | STATIC }
+{ PROCEDURE <proc_name>
+    [ ( [ SELF [ IN | IN OUT ] <name> ]
+        [, <argname> [ IN | IN OUT | OUT ] <argtype>
+                     [ DEFAULT <value> ]
+        ] ...)
+    ]
+{ IS | AS }
+    <program_body>
+  END;
+|
+  FUNCTION <func_name>
+    [ ( [ SELF [ IN | IN OUT ] <name> ]
+        [, <argname> [ IN | IN OUT | OUT ] <argtype>
+                     [ DEFAULT <value> ]
+        ] ...)
+    ]
+  RETURN <rettype>
+{ IS |AS }
+    <program_body>
+  END;
+}
+```
+
+## Description
+
+`CREATE TYPE BODY` defines a new object type body. `CREATE OR REPLACE TYPE BODY` either creates a new object type body or replaces an existing body.
+
+If you include a schema name, then the object type body is created in the specified schema. Otherwise it's created in the current schema. The name of the new object type body must match an existing object type specification in the same schema. The new object type body name can't match any existing object type body in the same schema unless you want to update the definition of an existing object type body. In that case, use `CREATE OR REPLACE TYPE BODY`.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the object type for which to create a body.
+
+`MEMBER`
+
+`STATIC`
+
+ Specify `MEMBER` if the subprogram operates on an object instance. Specify `STATIC` if the subprogram operates independently of any particular object instance.
+
+`proc_name`
+
+ The name of the procedure to create.
+
+`SELF [ IN | IN OUT ] name`
+
+ A member method has an implicit, built-in parameter named `SELF` whose data type is the same as the object type being defined. `SELF` refers to the object instance that's currently invoking the method. You can explicitly declare `SELF` as an `IN` or `IN OUT` parameter in the parameter list. If you explicitly declare it, `SELF` must be the first parameter in the parameter list. If you don't explicitly declare `SELF`, its parameter mode defaults to `IN OUT` for member procedures and `IN` for member functions.
+
+`argname`
+
+ The name of an argument. The argument is referenced by this name in the method body.
+
+`argtype`
+
+ The data types of the method’s arguments. The argument types can be a base data type or a user-defined type such as a nested table or an object type. Don't specify a length for any base type. For example, specify `VARCHAR2`, not `VARCHAR2(10)`.
+
+`DEFAULT value`
+
+ Supplies a default value for an input argument if one isn't supplied in the method call. You can't specify `DEFAULT` for arguments with modes `IN OUT` or `OUT`.
+
+`program_body`
+
+ The pragma, declarations, and SPL statements that make up the body of the function or procedure. Use the pragma `PRAGMA AUTONOMOUS_TRANSACTION` to set the function or procedure as an autonomous transaction.
+
+`func_name`
+
+ The name of the function to create.
+
+`rettype`
+
+ The return data type, which can be any of the types listed for `argtype`. Don't specify a length for `rettype`.
+
+## Examples
+
+Create the object type body for object type `emp_obj_typ`:
+
+```sql
+CREATE OR REPLACE TYPE BODY emp_obj_typ AS
+    MEMBER PROCEDURE display_emp (SELF IN OUT emp_obj_typ)
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Employee No   : ' || empno);
+        DBMS_OUTPUT.PUT_LINE('Name          : ' || ename);
+        DBMS_OUTPUT.PUT_LINE('Street        : ' || addr.street);
+        DBMS_OUTPUT.PUT_LINE('City/State/Zip: ' || addr.city || ', ' ||
+            addr.state || ' ' || LPAD(addr.zip,5,'0'));
+    END;
+END;
+```
+
+Create the object type body for object type `dept_obj_typ`:
+
+```sql
+CREATE OR REPLACE TYPE BODY dept_obj_typ AS
+    STATIC FUNCTION get_dname (p_deptno IN NUMBER) RETURN VARCHAR2
+    IS
+        v_dname     VARCHAR2(14);
+    BEGIN
+        CASE p_deptno
+            WHEN 10 THEN v_dname := 'ACCOUNING';
+            WHEN 20 THEN v_dname := 'RESEARCH';
+            WHEN 30 THEN v_dname := 'SALES';
+            WHEN 40 THEN v_dname := 'OPERATIONS';
+            ELSE v_dname := 'UNKNOWN';
+        END CASE;
+        RETURN v_dname;
+    END;
+    MEMBER PROCEDURE display_dept
+    IS
+    BEGIN
+        DBMS_OUTPUT.PUT_LINE('Dept No    : ' || SELF.deptno);
+        DBMS_OUTPUT.PUT_LINE('Dept Name  : ' ||
+            dept_obj_typ.get_dname(SELF.deptno));
+    END;
+END;
+```
+
+## See also
+
+[CREATE TYPE](39_create_type/#create_type), [DROP TYPE](60_drop_type/#drop_type)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/41_create_user.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/41_create_user.mdx
new file mode 100644
index 00000000000..796ae3f34fb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/41_create_user.mdx
@@ -0,0 +1,53 @@
+---
+title: "CREATE USER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.055.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.083.html"
+redirects:
+  - /epas/latest/epas_compat_sql/41_create_user/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_user" class="registered_link"></div>
+
+## Name
+
+`CREATE USER` &mdash; Define a new database user account.
+
+## Synopsis
+
+```sql
+CREATE USER <name> [IDENTIFIED BY <password>]
+```
+
+## Description
+
+`CREATE USER` adds a user to an EDB Postgres Advanced Server database cluster. You must be a database superuser to use this command.
+
+When you invoke the `CREATE USER` command, a schema is created with the same name as the new user. The new schema is owned by the new user. Objects with unqualified names that this user creates are created in this schema.
+
+## Parameters
+
+`name`
+
+ The name of the user.
+
+`password`
+
+ The user’s password. You can change the password later using `ALTER USER`.
+
+## Notes
+
+The maximum length allowed for the user name and password is 63 characters.
+
+## Examples
+
+Create a user named `john`:
+
+```sql
+CREATE USER john IDENTIFIED BY abc;
+```
+
+## See also
+
+[DROP USER](61_drop_user/#drop_user)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/42_create_user_role_profile_management_clauses.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/42_create_user_role_profile_management_clauses.mdx
new file mode 100644
index 00000000000..124443e28c1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/42_create_user_role_profile_management_clauses.mdx
@@ -0,0 +1,91 @@
+---
+title: "CREATE USER|ROLE… PROFILE MANAGEMENT CLAUSES"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.056.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.084.html"
+redirects:
+  - /epas/latest/epas_compat_sql/42_create_user_role_profile_management_clauses/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_user_role_profile_management_clauses" class="registered_link"></div>
+
+## Name
+
+`CREATE USER|ROLE` &mdash; Create a user or role.
+
+## Synopsis
+
+```sql
+CREATE USER|ROLE <name> [[WITH] option […]]
+```
+
+Where `option` is any of the following compatible clauses:
+
+```sql
+   PROFILE <profile_name>
+|  ACCOUNT {LOCK|UNLOCK}
+|  PASSWORD EXPIRE [AT '<timestamp>']
+```
+
+Alternatively, `option` can be any of the following non-compatible clauses:
+
+```sql
+|  LOCK TIME  '<timestamp>'
+```
+
+For information about the administrative clauses of the `CREATE USER` or `CREATE ROLE` commands that are supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-commands.html).
+
+## Description
+
+`CREATE ROLE|USER… PROFILE` adds a role with an associated profile to an EDB Postgres Advanced Server database cluster.
+
+By default, roles created with the `CREATE USER` command are login roles and roles created with the `CREATE ROLE` command aren't login roles. To create a login account with the `CREATE ROLE` command, you must include the `LOGIN` keyword.
+
+Only a database superuser can use the `CREATE USER|ROLE` clauses that enforce profile management. These clauses enforce the following behaviors:
+
+-   Include the `PROFILE` clause and a `profile_name` to associate a predefined profile with a role or to change the predefined profile associated with a user.
+
+-   Include the `ACCOUNT` clause and the `LOCK` or `UNLOCK` keyword to place the user account in a locked or unlocked state.
+
+-   Include the `LOCK TIME 'timestamp'` clause and a date and time value to lock the role at the specified time. Unlock the role at the time indicated by the `PASSWORD_LOCK_TIME` parameter of the profile assigned to this role. If you use `LOCK TIME` with the `ACCOUNT LOCK` clause, only a database superuser can unlock the role by using the `ACCOUNT UNLOCK` clause.
+
+-   Include the `PASSWORD EXPIRE` clause with the optional `AT 'timestamp'` keywords to specify a date and time when the password associated with the role expires. If you omit the `AT 'timestamp'` keywords, the password expires immediately.
+
+Each login role can have only one profile. To find the profile that's currently associated with a login role, query the `profile` column of the `DBA_USERS` view.
+
+## Parameters
+
+`name`
+
+ The name of the role.
+
+`profile_name`
+
+ The name of the profile associated with the role.
+
+`timestamp`
+
+ The date and time when the clause is enforced. When specifying a value for `timestamp`, enclose the value in single quotes.
+
+## Examples
+
+This example uses `CREATE USER` to create a login role named `john` that is associated with the `acctg_profile` profile:
+
+```sql
+CREATE USER john PROFILE acctg_profile IDENTIFIED BY “1safepwd”;
+```
+
+`john` can log in to the server, using the password `1safepwd`.
+
+This example uses `CREATE ROLE` to create a login role named `john` that is associated with the `acctg_profile` profile:
+
+```sql
+CREATE ROLE john PROFILE acctg_profile LOGIN PASSWORD “1safepwd”;
+```
+
+`john` can log in to the server, using the password `1safepwd`.
+
+## See also
+
+[ALTER USER|ROLE… PROFILE MANAGEMENT CLAUSES](16_alter_user_role_profile_management_clauses/#alter_user_role_profile_management_clauses)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx
new file mode 100644
index 00000000000..ed876db1ec1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/43_create_view.mdx
@@ -0,0 +1,62 @@
+---
+title: "CREATE VIEW"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.057.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.085.html"
+redirects:
+  - /epas/latest/epas_compat_sql/43_create_view/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="create_view" class="registered_link"></div>
+
+## Name
+
+`CREATE VIEW` &mdash; Define a new view.
+
+## Synopsis
+
+```sql
+CREATE [ OR REPLACE ] VIEW <name> [ ( <column_name> [, ...] ) ]
+  AS <query>
+```
+
+## Description
+
+`CREATE VIEW` defines a view of a query. The view isn't physically materialized. Instead, the query runs every time a query references the view.
+
+`CREATE OR REPLACE VIEW` is similar. However, if a view of the same name exists, the command replaces it.
+
+If you provide a schema name, then the view is created in the specified schema. Otherwise it's created in the current schema. The view name must differ from the name of any other view, table, sequence, or index in the same schema.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of a view to create.
+
+`column_name`
+
+ An optional list of names to use for columns of the view. If not given, the column names are deduced from the query.
+
+`query`
+
+ A query (that is, a `SELECT` statement) that provides the columns and rows of the view. See [`SELECT`](71_select/) for information about valid queries.
+
+## Notes
+
+Currently, views are read-only. The system doesn't allow an insert, update, or delete on a view. You can get the effect of an updatable view by creating rules that rewrite inserts and the other commands on the view into appropriate actions on other tables.
+
+Permissions of the view owner determine access to tables referenced in the view. However, functions called in the view are treated the same as if they were called directly from the query using the view. Therefore, the user of a view must have permissions to call all functions the view uses.
+
+## Examples
+
+Create a view consisting of all employees in department 30:
+
+```sql
+CREATE VIEW dept_30 AS SELECT * FROM emp WHERE deptno = 30;
+```
+
+## See also
+
+[DROP VIEW](62_drop_view/#drop_view)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44_delete.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44_delete.mdx
new file mode 100644
index 00000000000..1f43b1185b2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44_delete.mdx
@@ -0,0 +1,88 @@
+---
+title: "DELETE"
+redirects:
+  - /epas/latest/epas_compat_sql/44_delete/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="delete" class="registered_link"></div>
+
+## Name
+
+`DELETE` &mdash; Delete rows of a table.
+
+## Synopsis
+
+```text
+DELETE [ <optimizer_hint> ] [ FROM ] <table>[@<dblink> ]
+  [ WHERE <condition> ]
+  [ RETURNING <return_expression> [, ...]
+      { INTO { <record> | <variable> [, ...] }
+      | BULK COLLECT INTO <collection> [, ...] } ]
+```
+
+## Description
+
+`DELETE` deletes rows that satisfy the `WHERE` clause from the specified table. Omitting the `WHERE` clause deletes all rows in the table, leaving an empty table. You need the `DELETE` privilege on the table to delete from it. You also need the `SELECT` privilege for any table whose values are read in the condition.
+
+The `FROM` keyword is optional if EDB Postgres Advanced Server is installed in Oracle-compatible mode. It's required if EDB Postgres Advanced Server is installed in Postgres mode.
+
+!!! Note
+    The `TRUNCATE` command is a faster way to remove all rows from a table.
+
+You can specify the `RETURNING INTO { record | variable [, ...] }` clause only if you use the `DELETE` command in an SPL program. The result set of the `DELETE` command can't include more than one row. If it does, an error occurs. If the result set is empty, then the contents of the target record or variables are set to null.
+
+You can specify the `RETURNING BULK COLLECT INTO collection [, ...]` clause only if you use the `DELETE` command in an SPL program. If you specify more than one `collection` as the target of the `BULK COLLECT INTO` clause, then each `collection` must consist of a single, scalar field. That is, `collection` can't be a record. 
+
+The result set of the `DELETE` command can contain zero, one, or more rows. The `return_expression` evaluated for each row of the result set becomes an element in `collection`, starting with the first element. Any existing rows in `collection` are deleted. If the result set is empty, then `collection` is empty.
+
+## Parameters
+
+`optimizer_hint`
+
+ Comment-embedded hints to the optimizer for selecting an execution plan.
+
+`table`
+
+ The name (optionally schema-qualified) of an existing table.
+
+`dblink`
+
+ Database link name identifying a remote database. For more information, see [`CREATE DATABASE LINK`](21_create_public_database_link).
+
+`condition`
+
+ A value expression that returns a value of type `BOOLEAN` that determines the rows to delete.
+
+`return_expression`
+
+ An expression that can include one or more columns from `table`. If you specify a column name from `table`  in `return_expression`, the value substituted for the column when `return_expression` is evaluated is the value from the deleted row.
+
+`record`
+
+ A record whose field to assign the evaluated `return_expression`. The first `return_expression` is assigned to the first field in `record`, the second `return_expression` is assigned to the second field in `record`, and so on. The number of fields in `record` must exactly match the number of expressions, and the fields must be type-compatible with their assigned expressions.
+
+`variable`
+
+ A variable to which to assign the evaluated `return_expression`. If you specify more than one `return_expression` and `variable`, the `first return_expression` is assigned to the first `variable`, the second `return_expression` is assigned to the second `variable`, and so on. The number of variables specified following the `INTO` keyword must exactly match the number of expressions following the `RETURNING` keyword, and the variables must be type-compatible with their assigned expressions.
+
+`collection`
+
+ A collection in which an element is created from the evaluated `return_expression`. You can have a single collection, which can be a collection of a single field or a collection of a record type. Alternatively, you can have more than one collection. In that case, each collection must consist of a single field. The number of return expressions must match in number and order the number of fields in all specified collections. Each corresponding `return_expression` and `collection` field must be type-compatible.
+
+## Examples
+
+Delete all rows for employee `7900` from the `jobhist` table:
+
+```sql
+DELETE FROM jobhist WHERE empno = 7900;
+```
+
+Clear the table `jobhist`:
+
+```sql
+DELETE FROM jobhist;
+```
+
+## See also
+
+[TRUNCATE](75_truncate/#truncate)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44a_drop_capture_privilege.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44a_drop_capture_privilege.mdx
new file mode 100644
index 00000000000..fcf59ab4114
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/44a_drop_capture_privilege.mdx
@@ -0,0 +1,40 @@
+---
+title: "DROP CAPTURE PRIVILEGES POLICY"
+---
+
+EDB Postgres Advanced Server includes syntax not offered by Oracle with the `DROP CAPTURE PRIVILEGES POLICY`  SQL command.
+
+## Name
+
+`DROP CAPTURE PRIVILEGES POLICY` &mdash; Drop an existing capture privilege policy.
+
+## Synopsis
+
+Use `DROP CAPTURE PRIVILEGES POLICY` to drop an existing policy to capture privileges:
+
+```sql
+DROP CAPTURE PRIVILEGES POLICY [ IF EXISTS ] <name> [ CASCADE | RESTRICT ]
+```
+
+## Description
+
+`DROP CAPTURE PRIVILEGES POLICY` allows a superuser or a user with the `CREATE_CAPTURE` privilege to drop an existing queue.
+
+## Parameters
+
+`name`
+
+ The name optionally schema-qualified of the capture privilege policy that's being dropped.
+
+
+## Examples
+
+This example drops a capture privilege policy named `sampledb_p2`:
+
+```sql
+DROP CAPTURE PRIVILEGES POLICY sampledb_p2;
+```
+
+## See also
+
+[CREATE CAPTURE PRIVILEGE POLICY](19a_create_capture_privilege), [ALTER CAPTURE PRIVILEGE POLICY](01_alter_capture_privilege)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/45_drop_public_database_link.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/45_drop_public_database_link.mdx
new file mode 100644
index 00000000000..ecd46994358
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/45_drop_public_database_link.mdx
@@ -0,0 +1,53 @@
+---
+title: "DROP DATABASE LINK"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.059.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.087.html"
+redirects:
+  - /epas/latest/epas_compat_sql/45_drop_public_database_link/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_public_database_link" class="registered_link"></div>
+
+## Name
+
+`DROP DATABASE LINK` &mdash; Remove a database link.
+
+## Synopsis
+
+```sql
+DROP [ PUBLIC ] DATABASE LINK <name>
+```
+
+## Description
+
+`DROP DATABASE LINK` drops existing database links. To execute this command, you must be a superuser or the owner of the database link.
+
+## Parameters
+
+`name`
+
+ The name of a database link to remove.
+
+`PUBLIC`
+
+ Indicates that `name` is a public database link.
+
+## Examples
+
+Remove the public database link named `oralink`:
+
+```sql
+DROP PUBLIC DATABASE LINK oralink;
+```
+
+Remove the private database link named `edblink`:
+
+```sql
+DROP DATABASE LINK edblink;
+```
+
+## See also
+
+[CREATE PUBLIC DATABASE LINK](21_create_public_database_link)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/46_drop_directory.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/46_drop_directory.mdx
new file mode 100644
index 00000000000..27d22c5a404
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/46_drop_directory.mdx
@@ -0,0 +1,45 @@
+---
+title: "DROP DIRECTORY"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.060.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.088.html"
+redirects:
+  - /epas/latest/epas_compat_sql/46_drop_directory/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_directory" class="registered_link"></div>
+
+## Name
+
+`DROP DIRECTORY` &mdash; Remove a directory alias for a file system directory path.
+
+## Synopsis
+
+```sql
+DROP DIRECTORY <name>
+```
+
+## Description
+
+`DROP DIRECTORY` drops an existing alias for a file system directory path that was created with the `CREATE DIRECTORY` command. To execute this command, you must be a superuser.
+
+When you delete a directory alias, the corresponding physical file system directory isn't affected. To delete the file system directory, use operating system commands.
+
+## Parameters
+
+`name`
+
+ The name of a directory alias to remove.
+
+## Examples
+
+Remove the directory alias `empdir`:
+
+```sql
+DROP DIRECTORY empdir;
+```
+
+## See also
+
+[CREATE DIRECTORY](22_create_directory/#create_directory), [ALTER DIRECTORY](02_alter_directory/#alter_directory)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/47_drop_function.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/47_drop_function.mdx
new file mode 100644
index 00000000000..ef6ad797179
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/47_drop_function.mdx
@@ -0,0 +1,83 @@
+---
+title: "DROP FUNCTION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.061.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.089.html"
+redirects:
+  - /epas/latest/epas_compat_sql/47_drop_function/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_function" class="registered_link"></div>
+
+## Name
+
+`DROP FUNCTION` &mdash; Remove a function.
+
+## Synopsis
+
+```sql
+DROP FUNCTION [ IF EXISTS ] <name>
+  [ ([ [ <argmode> ] [ <argname> ] <argtype> ] [, ...]) ]
+  [ CASCADE | RESTRICT ]
+```
+
+## Description
+
+`DROP FUNCTION` removes the definition of an existing function. To execute this command, you must be a superuser or the owner of the function. If this is an overloaded function, you must specify all input (`IN`, `IN OUT`) argument data types to the function. 
+
+!!! Note
+    This requirement isn't compatible with Oracle databases. In Oracle, you specify only the function name. EDB Postgres Advanced Server allows you to overload function names. Therefore, the function signature given by the input argument data types is required in the EDB Postgres Advanced Server `DROP FUNCTION` command of an overloaded function.
+
+The `IF EXISTS`, `CASCADE`, and `RESTRICT` parameters aren't compatible with Oracle databases. Only EDB Postgres Advanced Server uses them.
+
+## Parameters
+
+`IF EXISTS`
+
+ Specifies not to throw an error if the function doesn't exist. A notice is issued instead.
+
+`name`
+
+ The name (optionally schema-qualified) of an existing function.
+
+`argmode`
+
+ The mode of an argument: `IN`, `IN OUT`, or `OUT`. If omitted, the default is `IN`. `DROP FUNCTION` ignores `OUT` arguments, since only the input arguments are needed to determine the function’s identity. You need to list only the `IN` and `IN OUT` arguments. 
+ 
+ !!! Note
+  Specifying `argmode` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`argname`
+
+ The name of an argument. `DROP FUNCTION` ignores argument names, since only the argument data types are needed to determine the function’s identity. 
+ 
+ !!! Note
+  Specifying `argname` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`argtype`
+
+ The data type of an argument of the function. 
+ 
+ !!! Note
+  Specifying `argtype` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`CASCADE`
+
+ Drop objects that depend on the function, such as operators or triggers, and objects that depend on those objects.
+
+`RESTRICT`
+
+ Prevent dropping the function if any objects depend on it. This is the default.
+
+## Examples
+
+This example removes the `emp_comp` function:
+
+```sql
+DROP FUNCTION emp_comp(NUMBER, NUMBER);
+```
+
+## See also
+
+[CREATE FUNCTION](23_create_function/#create_function)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/48_drop_index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/48_drop_index.mdx
new file mode 100644
index 00000000000..da647cbb0e5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/48_drop_index.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP INDEX"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.062.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.090.html"
+redirects:
+  - /epas/latest/epas_compat_sql/48_drop_index/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_index" class="registered_link"></div>
+
+## Name
+
+`DROP INDEX` &mdash; Remove an index.
+
+## Synopsis
+
+```sql
+DROP INDEX <name>
+```
+
+## Description
+
+`DROP INDEX` drops an existing index from the database system. To execute this command, you must be a superuser or the owner of the index. If any objects depend on the index, an error occurs, and the index isn't dropped.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of an index to remove.
+
+## Examples
+
+This example removes the index `name_idx`:
+
+```sql
+DROP INDEX name_idx;
+```
+
+## See also
+
+[CREATE INDEX](24_create_index), [ALTER INDEX](03_alter_index)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/49_drop_package.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/49_drop_package.mdx
new file mode 100644
index 00000000000..805065031fd
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/49_drop_package.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP PACKAGE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.063.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.091.html"
+redirects:
+  - /epas/latest/epas_compat_sql/49_drop_package/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_package" class="registered_link"></div>
+
+## Name
+
+`DROP PACKAGE` &mdash; Remove a package.
+
+## Synopsis
+
+```sql
+DROP PACKAGE [ BODY ] <name>
+```
+
+## Description
+
+`DROP PACKAGE` drops an existing package. To execute this command, you must be a superuser or the owner of the package. Specify `BODY` to remove only the package body without dropping the package specification. Omit `BODY` to remove both the package specification and body.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of a package to remove.
+
+## Examples
+
+This example removes the `emp_admin` package:
+
+```sql
+DROP PACKAGE emp_admin;
+```
+
+## See also
+
+[CREATE PACKAGE](26_create_package/#create_package), [CREATE PACKAGE BODY](27_create_package_body/#create_package_body)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/50_drop_procedure.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/50_drop_procedure.mdx
new file mode 100644
index 00000000000..d5cbc1a1ca5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/50_drop_procedure.mdx
@@ -0,0 +1,84 @@
+---
+title: "DROP PROCEDURE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.064.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.092.html"
+redirects:
+  - /epas/latest/epas_compat_sql/50_drop_procedure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_procedure" class="registered_link"></div>
+
+## Name
+
+`DROP PROCEDURE` &mdash; Remove a procedure.
+
+## Synopsis
+
+```sql
+DROP PROCEDURE [ IF EXISTS ] <name>
+  [ ([ [ <argmode> ] [ <argname> ] <argtype> ] [, ...]) ]
+  [ CASCADE | RESTRICT ]
+```
+
+## Description
+
+`DROP PROCEDURE` removes the definition of an existing procedure. To execute this command, you must be a superuser or the owner of the procedure. For an overloaded procedure, you must specify all input (`IN`, `IN OUT`) argument data types to the procedure. 
+
+!!! Note 
+
+    This requirement isn't compatible with Oracle databases. In Oracle, specify only the procedure name. EDB Postgres Advanced Server allows overloading of procedure names. Therefore the procedure signature given by the input argument data types is required in the EDB Postgres Advanced Server `DROP PROCEDURE` command for an overloaded procedure.
+
+The `IF EXISTS`, `CASCADE`, and `RESTRICT` parameters aren't compatible with Oracle databases. Only EDB Postgres Advanced Server uses them.
+
+## Parameters
+
+`IF EXISTS`
+
+ Specifies not to throw an error if the procedure doesn't exist. A notice is issued instead.
+
+`name`
+
+ The name (optionally schema-qualified) of an existing procedure.
+
+`argmode`
+
+ The mode of an argument: `IN`, `IN OUT`, or `OUT`. The default is `IN`. `DROP PROCEDURE` ignores `OUT` arguments, since only the input arguments are needed to determine the procedure’s identity. List only the `IN` and `IN OUT` arguments. 
+ 
+ !!! Note
+  Specifying `argmode` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`argname`
+
+ The name of an argument. `DROP PROCEDURE` ignores argument names, since only the argument data types are needed to determine the procedure’s identity. 
+ 
+ !!! Note
+  Specifying `argname` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`argtype`
+
+ The data type of an argument of the procedure. 
+ 
+ !!! Note
+  Specifying `argtype` isn't compatible with Oracle databases. It applies only to EDB Postgres Advanced Server.
+
+`CASCADE`
+
+ Drop objects that depend on the procedure and all objects that depend on those objects.
+
+`RESTRICT`
+
+ Prevent dropping the procedure if any objects depend on it. This is the default.
+
+## Examples
+
+This example removes the `select_emp` procedure:
+
+```sql
+DROP PROCEDURE select_emp;
+```
+
+## See also
+
+[CREATE PROCEDURE](28_create_procedure/#create_procedure), [ALTER PROCEDURE](04_alter_procedure/#alter_procedure)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/51_drop_profile.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/51_drop_profile.mdx
new file mode 100644
index 00000000000..43f73988b48
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/51_drop_profile.mdx
@@ -0,0 +1,51 @@
+---
+title: "DROP PROFILE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.065.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.093.html"
+redirects:
+  - /epas/latest/epas_compat_sql/51_drop_profile/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_profile" class="registered_link"></div>
+
+## Name
+
+`DROP PROFILE` &mdash; Drop a user-defined profile.
+
+## Synopsis
+
+```sql
+DROP PROFILE [IF EXISTS] <profile_name> [CASCADE | RESTRICT];
+```
+
+## Description
+
+Include the `IF EXISTS` clause to prevent an error if the specified profile doesn't exist. Instead, issue a notice.
+
+Include the optional `CASCADE` clause to reassign any users that are currently associated with the profile to the `default` profile and then drop the profile. Include the optional `RESTRICT` clause to prevent dropping any profile that's associated with a role. This is the default behavior.
+
+## Parameters
+
+`profile_name`
+
+ The name of the profile to drop.
+
+## Examples
+
+This example drops a profile named `acctg_profile`. The command first associates any roles associated with the `acctg_profile` profile with the `default` profile and then drops the `acctg_profile` profile.
+
+```sql
+DROP PROFILE acctg_profile CASCADE;
+```
+
+This example drops a profile named `acctg_profile`. The `RESTRICT` clause prevents dropping `acctg_profile` if any roles are associated with the profile.
+
+```sql
+DROP PROFILE acctg_profile RESTRICT;
+```
+
+## See also
+
+[CREATE PROFILE](29_create_profile/#create_profile), [ALTER PROFILE](05_alter_profile/#alter_profile)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/52_drop_queue.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/52_drop_queue.mdx
new file mode 100644
index 00000000000..2d560434587
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/52_drop_queue.mdx
@@ -0,0 +1,50 @@
+---
+title: "DROP QUEUE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.066.html"
+redirects:
+  - /epas/latest/epas_compat_sql/52_drop_queue/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_queue" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes syntax not offered by Oracle with the `DROP QUEUE SQL` command. You can use this syntax with `DBMS_AQADM`.
+
+## Name
+
+`DROP QUEUE` &mdash; Drop an existing queue.
+
+## Synopsis
+
+Use `DROP QUEUE` to drop an existing queue:
+
+```sql
+DROP QUEUE [IF EXISTS] <name>
+```
+
+## Description
+
+`DROP QUEUE` allows a superuser or a user with the `aq_administrator_role` privilege to drop an existing queue.
+
+## Parameters
+
+`name`
+
+ The name (possibly schema-qualified) of the queue that's being dropped.
+
+`IF EXISTS`
+
+ Include the `IF EXISTS` clause if you don't want to return an error if the queue doesn't exist. Instead, issue a notice.
+
+## Examples
+
+This example drops a queue named `work_order`:
+
+```sql
+DROP QUEUE work_order;
+```
+
+## See also
+
+[CREATE QUEUE](30_create_queue/#create_queue), [ALTER QUEUE](06_alter_queue/#alter_queue)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/53_drop_queue_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/53_drop_queue_table.mdx
new file mode 100644
index 00000000000..7572da5bc44
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/53_drop_queue_table.mdx
@@ -0,0 +1,59 @@
+---
+title: "DROP QUEUE TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.067.html"
+redirects:
+  - /epas/latest/epas_compat_sql/53_drop_queue_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_queue_table" class="registered_link"></div>
+
+EDB Postgres Advanced Server includes syntax not offered by Oracle with the `DROP QUEUE TABLE SQL` command. You can use this syntax with `DBMS_AQADM`.
+
+## Name
+
+`DROP QUEUE TABLE` &mdash; Drop a queue table.
+
+## Synopsis
+
+Use `DROP QUEUE TABLE` to delete a queue table:
+
+```sql
+DROP QUEUE TABLE [ IF EXISTS ] <name> [, ...]
+[CASCADE | RESTRICT]
+```
+
+## Description
+
+`DROP QUEUE TABLE` allows a superuser or a user with the `aq_administrator_role` privilege to delete a queue table.
+
+## Parameters
+
+`name`
+
+ The name (possibly schema-qualified) of the queue table to delete.
+
+`IF EXISTS`
+
+ Include the `IF EXISTS` clause if you don't want to return an error if the queue table doesn't exist. Instead, issue a notice.
+
+`CASCADE`
+
+ Include the `CASCADE` keyword to delete objects that depend on the queue table.
+
+`RESTRICT`
+
+ Include the `RESTRICT` keyword to prevent deleting the queue table if any objects depend on it. This is the default.
+
+## Examples
+
+This example deletes a queue table named `work_order_table` and any objects that depend on it:
+
+```sql
+DROP QUEUE TABLE work_order_table CASCADE;
+```
+
+## See also
+
+[CREATE QUEUE TABLE](31_create_queue_table/#create_queue_table), [ALTER QUEUE TABLE](07_alter_queue_table/#alter_queue_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/54_drop_synonym.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/54_drop_synonym.mdx
new file mode 100644
index 00000000000..ca6bd09e67f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/54_drop_synonym.mdx
@@ -0,0 +1,55 @@
+---
+title: "DROP SYNONYM"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.068.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.094.html"
+redirects:
+  - /epas/latest/epas_compat_sql/54_drop_synonym/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_synonym" class="registered_link"></div>
+
+## Name
+
+`DROP SYNONYM` &mdash; Remove a synonym.
+
+## Synopsis
+
+```sql
+DROP [PUBLIC] SYNONYM [<schema>.]<syn_name>
+```
+
+## Description
+
+`DROP SYNONYM` deletes existing synonyms. To execute this command, you must be a superuser or the owner of the synonym and have `USAGE` privileges on the schema in which the synonym resides.
+
+## Parameters
+
+`syn_name`
+
+ The name of the synonym. A synonym name must be unique in a schema.
+
+`schema`
+
+ The name of the schema where the synonym resides.
+
+  Like any other object that can be schema qualified, you can have two synonyms with the same name in your search path. To specify the name of the synonym that you're dropping, include a schema name. Unless a synonym is schema qualified in the `DROP SYNONYM` command, EDB Postgres Advanced Server deletes the first instance of the synonym it finds in your search path.
+
+You can optionally include the `PUBLIC` clause to drop a synonym that resides in the `public` schema. The `DROP PUBLIC SYNONYM` command, compatible with Oracle databases, drops a synonym that resides in the `public` schema:
+
+```sql
+DROP PUBLIC SYNONYM syn_name;
+```
+
+## Examples
+
+This example drops the synonym `personnel`:
+
+```sql
+DROP SYNONYM personnel;
+```
+
+## See also
+
+[CREATE SYNONYM](35_create_synonym/#create_synonym)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/55_drop_role.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/55_drop_role.mdx
new file mode 100644
index 00000000000..67768db5641
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/55_drop_role.mdx
@@ -0,0 +1,53 @@
+---
+title: "DROP ROLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.069.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.095.html"
+redirects:
+  - /epas/latest/epas_compat_sql/55_drop_role/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_role" class="registered_link"></div>
+
+## Name
+
+`DROP ROLE` &mdash; Remove a database role.
+
+## Synopsis
+
+```sql
+DROP ROLE <name> [ CASCADE ]
+```
+
+## Description
+
+`DROP ROLE` removes the specified role. To drop a superuser role, you must be a superuser. To drop non-superuser roles, you must have the `CREATEROLE` privilege.
+
+Before dropping the role, you must drop all the objects it owns or reassign their ownership and revoke any privileges the role was granted. You can't remove a role if any database of the cluster references it. 
+
+You don't need to remove role memberships involving the role. `DROP ROLE` revokes any memberships of the target role in other roles and of other roles in the target role. The other roles aren't dropped or otherwise affected.
+
+Alternatively, if the only objects owned by the role belong in a schema that's owned by the role and has the same name as the role, you can specify the `CASCADE` option. In this case, the issuer of the `DROP ROLE name CASCADE` command must be a superuser. The named role, the schema, and all objects in the schema are deleted.
+
+## Parameters
+
+`name`
+
+ The name of the role to remove.
+
+`CASCADE`
+
+ Drops the schema owned by and with the same name as the role as long as there are no other dependencies on the role or the schema. All objects owned by the role belonging to the schema are also dropped.
+
+## Examples
+
+This example drops a role:
+
+```sql
+DROP ROLE admins;
+```
+
+## See also
+
+[CREATE ROLE](32_create_role/#create_role), [SET ROLE](73_set_role/#set_role), [GRANT](64_grant/#grant), [REVOKE](67_revoke/#revoke)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/56_drop_sequence.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/56_drop_sequence.mdx
new file mode 100644
index 00000000000..1b1a98d3121
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/56_drop_sequence.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP SEQUENCE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.070.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.096.html"
+redirects:
+  - /epas/latest/epas_compat_sql/56_drop_sequence/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_sequence" class="registered_link"></div>
+
+## Name
+
+`DROP SEQUENCE` &mdash; Remove a sequence.
+
+## Synopsis
+
+```sql
+DROP SEQUENCE <name> [, ...]
+```
+
+## Description
+
+`DROP SEQUENCE` removes sequence number generators. To execute this command, you must be a superuser or the owner of the sequence.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of a sequence.
+
+## Examples
+
+Remove the sequence `serial`:
+
+```sql
+DROP SEQUENCE serial;
+```
+
+## See also
+
+[ALTER SEQUENCE](10_alter_sequence/#alter_sequence), [CREATE SEQUENCE](34_create_sequence/#create_sequence)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/57_drop_table.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/57_drop_table.mdx
new file mode 100644
index 00000000000..4036a2f4b5b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/57_drop_table.mdx
@@ -0,0 +1,73 @@
+---
+title: "DROP TABLE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.071.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.112.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.337.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.097.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.061.html"
+redirects:
+  - /epas/latest/epas_compat_sql/57_drop_table/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_table" class="registered_link"></div>
+
+## Name
+
+`DROP TABLE` &mdash; Remove a table.
+
+## Synopsis
+
+```sql
+DROP TABLE <name> [CASCADE | RESTRICT | CASCADE CONSTRAINTS]
+```
+
+## Description
+
+`DROP TABLE` removes tables from the database. Only the owner can remove a table. To empty a table of rows without removing the table, use `DELETE`. `DROP TABLE` removes any of the target table's indexes, rules, triggers, and constraints.
+
+## Parameters
+
+`name`
+
+  The name (optionally schema-qualified) of the table to drop.
+
+`RESTRICT`
+
+  Include the `RESTRICT` keyword to prevent dropping the table if any objects depend on it. This is the default behavior. The `DROP TABLE` command reports an error if any objects depend on the table.
+
+`CASCADE`
+
+  Include the `CASCADE` clause to drop any objects that depend on the table.
+
+`CASCADE CONSTRAINTS`
+
+  Include the `CASCADE CONSTRAINTS` clause to drop any dependent constraints on the specified table, excluding other object types.
+
+## Examples
+
+This example drops a table named `emp` that has no dependencies:
+
+```sql
+DROP TABLE emp;
+```
+
+The outcome of a `DROP TABLE` command varies depending on whether the table has any dependencies. You can control the outcome by specifying a drop behavior. For example, suppose you create two tables, `orders` and `items`, where the `items` table depends on the `orders` table:
+
+```sql
+CREATE TABLE orders
+  (order_id int PRIMARY KEY, order_date date, …);
+CREATE TABLE items
+  (order_id REFERENCES orders, quantity int, …);
+```
+
+EDB Postgres Advanced Server performs one of the following actions when dropping the `orders` table, depending on the drop behavior that you specify:
+
+-   If you specify `DROP TABLE orders RESTRICT`, EDB Postgres Advanced Server reports an error.
+-   If you specify `DROP TABLE orders CASCADE`, EDB Postgres Advanced Server drops the `orders` table and the `items` table.
+-   If you specify `DROP TABLE orders CASCADE CONSTRAINTS`, EDB Postgres Advanced Server drops the `orders` table and removes the foreign key specification from the `items` table. It doesn't drop the `items` table.
+
+## See also
+
+[CREATE TABLE](36_create_table/#create_table), [ALTER TABLE](12_alter_table/#alter_table)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/58_drop_tablespace.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/58_drop_tablespace.mdx
new file mode 100644
index 00000000000..5f0bd43c0eb
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/58_drop_tablespace.mdx
@@ -0,0 +1,45 @@
+---
+title: "DROP TABLESPACE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.072.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.098.html"
+redirects:
+  - /epas/latest/epas_compat_sql/58_drop_tablespace/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_tablespace" class="registered_link"></div>
+
+## Name
+
+`DROP TABLESPACE` &mdash; Remove a tablespace.
+
+## Synopsis
+
+```sql
+DROP TABLESPACE <tablespacename>
+```
+
+## Description
+
+`DROP TABLESPACE` removes a tablespace from the system.
+
+Only a superuser or the tablespace owner can drop a tablespace. The tablespace must be empty of all database objects before you drop it. Objects in other databases might still reside in the tablespace even if no objects in the current database are using the tablespace.
+
+## Parameters
+
+`tablespacename`
+
+ The name of a tablespace.
+
+## Examples
+
+This example removes the tablespace `employee_space` from the system:
+
+```sql
+DROP TABLESPACE employee_space;
+```
+
+## See also
+
+[ALTER TABLESPACE](14_alter_tablespace/#alter_tablespace)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/59_drop_trigger.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/59_drop_trigger.mdx
new file mode 100644
index 00000000000..6e086707324
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/59_drop_trigger.mdx
@@ -0,0 +1,43 @@
+---
+title: "DROP TRIGGER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.073.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.099.html"
+redirects:
+  - /epas/latest/epas_compat_sql/59_drop_trigger/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_trigger" class="registered_link"></div>
+
+## Name
+
+`DROP TRIGGER` &mdash; Remove a trigger.
+
+## Synopsis
+
+```sql
+DROP TRIGGER <name>
+```
+
+## Description
+
+`DROP TRIGGER` removes a trigger from its associated table. A superuser or the owner of the associated table can run the command.
+
+## Parameters
+
+`name`
+
+ The name of a trigger to remove.
+
+## Examples
+
+Remove a trigger named `emp_salary_trig`:
+
+```sql
+DROP TRIGGER emp_salary_trig;
+```
+
+## See also
+
+[CREATE TRIGGER](38_create_trigger/#create_trigger), [ALTER TRIGGER](13_alter_trigger/#alter_trigger)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/60_drop_type.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/60_drop_type.mdx
new file mode 100644
index 00000000000..d133feba67e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/60_drop_type.mdx
@@ -0,0 +1,53 @@
+---
+title: "DROP TYPE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.074.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.100.html"
+redirects:
+  - /epas/latest/epas_compat_sql/60_drop_type/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_type" class="registered_link"></div>
+
+## Name
+
+`DROP TYPE` &mdash; Remove a type definition.
+
+## Synopsis
+
+```sql
+DROP TYPE [ BODY ] <name>
+```
+
+## Description
+
+`DROP TYPE` removes the type definition. To execute this command, you must be a superuser or the owner of the type.
+
+The optional `BODY` qualifier applies only to object type definitions, not to collection types or to composite types. If you specify `BODY`, only the object type body is removed and not the object type specification. If you omit `BODY`, both the object type specification and body are removed.
+
+The type isn't deleted if other database objects depend on the named type.
+
+## Parameters
+
+`name`
+
+ The name of a type definition to remove.
+
+## Examples
+
+Drop the object type named `addr_obj_typ`:
+
+```sql
+DROP TYPE addr_obj_typ;
+```
+
+Drop the nested table type named `budget_tbl_typ`:
+
+```sql
+DROP TYPE budget_tbl_typ;
+```
+
+## See also
+
+[CREATE TYPE](39_create_type/#create_type), [CREATE TYPE BODY](40_create_type_body/#create_type_body)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/61_drop_user.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/61_drop_user.mdx
new file mode 100644
index 00000000000..d5d1fcc8130
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/61_drop_user.mdx
@@ -0,0 +1,59 @@
+---
+title: "DROP USER"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.075.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.101.html"
+redirects:
+  - /epas/latest/epas_compat_sql/61_drop_user/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_user" class="registered_link"></div>
+
+## Name
+
+`DROP USER` &mdash; Remove a database user account.
+
+## Synopsis
+
+```sql
+DROP USER <name> [ CASCADE ]
+```
+
+## Description
+
+`DROP USER` removes the specified user. You must be a superuser to drop a superuser. To drop non-superusers, you need the `CREATEROLE` privilege.
+
+You can't remove a user if any database of the cluster references it. Before dropping the user, you must drop all the objects it owns or reassign their ownership and revoke any privileges the user was granted.
+
+However, you don't need to remove role memberships involving the user. `DROP USER` revokes any memberships of the target user in other roles and of other roles in the target user. The other roles aren't dropped or otherwise affected.
+
+Alternatively, if the only objects owned by the user belong in a schema that's owned by the user and has the same name as the user, you can specify the `CASCADE` option. In this case, the issuer of the `DROP USER name CASCADE` command must be a superuser. The named user, the schema, and all objects in the schema are deleted.
+
+## Parameters
+
+`name`
+
+ The name of the user to remove.
+
+`CASCADE`
+
+ If specified, drops the schema owned by and with the same name as the user as long as there are no other dependencies on the user or the schema. It also drops all objects owned by the user belonging to the schema.
+
+## Examples
+
+Drop a user account named `john` that owns no objects and doesn't have privileges on any other objects:
+
+```sql
+DROP USER john;
+```
+
+Drop the user account `john` that doesn't have privileges on any objects. The account also doesn't own any objects outside of a schema named `john` that's owned by the user `john`:
+
+```sql
+DROP USER john CASCADE;
+```
+
+## See also
+
+[CREATE USER](41_create_user/#create_user), [ALTER USER](15_alter_user_identified_by/#alter_user_identified_by)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/62_drop_view.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/62_drop_view.mdx
new file mode 100644
index 00000000000..865df7c0e32
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/62_drop_view.mdx
@@ -0,0 +1,45 @@
+---
+title: "DROP VIEW"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.076.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.102.html"
+redirects:
+  - /epas/latest/epas_compat_sql/62_drop_view/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="drop_view" class="registered_link"></div>
+
+## Name
+
+`DROP VIEW` &mdash; Remove a view.
+
+## Synopsis
+
+```sql
+DROP VIEW <name>
+```
+
+## Description
+
+`DROP VIEW` drops an existing view. To execute this command, you must be a database superuser or the owner of the view. The named view isn't deleted if other objects depend on this view, such as a view of a view.
+
+The form of the `DROP VIEW` command compatible with Oracle doesn't support a `CASCADE` clause. To drop a view and its dependencies, use the PostgreSQL-compatible form of the `DROP VIEW` command. For more information, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-dropview.html).
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the view to remove.
+
+## Examples
+
+This example removes the view named `dept_30`:
+
+```sql
+DROP VIEW dept_30;
+```
+
+## See also
+
+[CREATE VIEW](43_create_view/#create_view)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/63_exec.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/63_exec.mdx
new file mode 100644
index 00000000000..394b3eca73d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/63_exec.mdx
@@ -0,0 +1,45 @@
+---
+title: "EXEC"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.077.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.103.html"
+redirects:
+  - /epas/latest/epas_compat_sql/63_exec/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="exec" class="registered_link"></div>
+
+## Name
+
+`EXEC` &mdash; Execute a function.
+
+## Synopsis
+
+```sql
+EXEC function_name ['('[<argument_list>]')']
+```
+
+## Description
+
+`EXECUTE` 
+
+## Parameters
+
+`procedure_name`
+
+ The (optionally schema-qualified) function name.
+
+`argument_list`
+
+ A comma-separated list of arguments required by the function. Each member of `argument_list` corresponds to a formal argument expected by the function. Each formal argument can be an `IN` parameter, an `OUT` parameter, or an `INOUT` parameter.
+
+## Examples
+
+The `EXEC` statement can take one of several forms, depending on the arguments required by the function:
+
+```sql
+EXEC update_balance;
+EXEC update_balance();
+EXEC update_balance(1,2,3);
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/64_grant.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/64_grant.mdx
new file mode 100644
index 00000000000..00cf202373f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/64_grant.mdx
@@ -0,0 +1,273 @@
+---
+title: "GRANT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.078.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.079.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.080.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.081.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.107.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.104.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.105.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.106.html"
+redirects:
+  - /epas/latest/epas_compat_sql/64_grant/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="grant" class="registered_link"></div>
+
+## Name
+
+`GRANT` &mdash; Define access privileges.
+
+## Synopsis
+
+```sql
+GRANT { { SELECT | INSERT | UPDATE | DELETE | REFERENCES }
+  [,...] | ALL [ PRIVILEGES ] }
+  ON tablename
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT { { INSERT | UPDATE | REFERENCES } (column [, ...]) }
+  [, ...]
+  ON tablename
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT { SELECT | ALL [ PRIVILEGES ] }
+  ON sequencename
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT { EXECUTE | ALL [ PRIVILEGES ] }
+  ON FUNCTION progname
+    ( [ [ argmode ] [ argname ] argtype ] [, ...] )
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT { EXECUTE | ALL [ PRIVILEGES ] }
+  ON PROCEDURE progname
+    [ ( [ [ argmode ] [ argname ] argtype ] [, ...] ) ]
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT { EXECUTE | ALL [ PRIVILEGES ] }
+  ON PACKAGE packagename
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH GRANT OPTION ]
+
+GRANT role [, ...]
+  TO { username | groupname | PUBLIC } [, ...]
+  [ WITH ADMIN OPTION ]
+
+GRANT { CONNECT | RESOURCE | DBA } [, ...]
+  TO { username | groupname } [, ...]
+  [ WITH ADMIN OPTION ]
+
+GRANT CREATE [ PUBLIC ] DATABASE LINK
+  TO { username | groupname }
+
+GRANT DROP PUBLIC DATABASE LINK
+  TO { username | groupname }
+
+GRANT EXEMPT ACCESS POLICY
+  TO { username | groupname }
+```
+
+## Description
+
+The `GRANT` command has three basic variants: 
+
+-  One that grants privileges on a database object (table, view, sequence, or program) 
+-  One that grants membership in a role
+-  One that grants system privileges 
+
+In EDB Postgres Advanced Server, the concept of users and groups was unified into a single type of entity called a *role*. In this context, a *user* is a role that has the `LOGIN` attribute. The role can be used to create a session and connect to an application. A *group* is a role that doesn't have the `LOGIN` attribute. You can't use the role to create a session or connect to an application.
+
+A role can be a member of one or more other roles, so the traditional concept of users belonging to groups is still valid. However, with the generalization of users and groups, users can “belong” to users, groups can “belong” to groups, and groups can “belong” to users, forming a general multi-level hierarchy of roles. User names and group names share the same namespace. Therefore, you don't need to specify whether a grantee is a user or a group in the `GRANT` command.
+
+## GRANT on database objects
+
+This variant of the `GRANT` command gives specific privileges on a database object to a role. These privileges are added to those already granted, if any.
+
+The keyword `PUBLIC` grants the privileges to all roles, including those that you create later. `PUBLIC` is an implicitly defined group that always includes all roles. Any role has the sum of privileges granted directly to it, privileges granted to any role it is a member of, and privileges granted to `PUBLIC`.
+
+If you specify the `WITH GRANT OPTION`, the recipient of the privilege can grant it to others. Grant options aren't granted to `PUBLIC`.
+
+You don't need to grant privileges to the owner of an object (usually the user that created it), as the owner has all privileges by default. The owner can, however, revoke some of their own privileges for safety. The right to drop an object or to alter its definition isn't described by a grantable privilege. It's inherent in the owner and can't be granted or revoked. The owner implicitly has all grant options for the object as well.
+
+Depending on the type of object, the initial default privileges can include granting some privileges to `PUBLIC`. The default is no public access for tables and `EXECUTE` privilege for functions, procedures, and packages. The object owner can revoke these privileges. 
+
+!!! Note
+    For maximum security, issue the `REVOKE` in the same transaction that creates the object. This approach prevents a window from occurring in which another user can use the object.
+
+The possible privileges are:
+
+`SELECT`
+
+ Allows `SELECT` from any column of the specified table, view, or sequence. For sequences, this privilege also allows the use of the `currval` function.
+
+`INSERT`
+
+ Allows you to insert a new row into the specified table.
+
+`UPDATE`
+
+ Allows `UPDATE` of a column of the specified table. `SELECT ... FOR UPDATE` also requires this privilege in addition to the `SELECT` privilege.
+
+`DELETE`
+
+ Allows you to delete a row from the specified table.
+
+`REFERENCES`
+
+ To create a foreign key constraint, you need this privilege on both the referencing and referenced tables.
+
+`EXECUTE`
+
+ Allows the use of the specified package, procedure, or function. When applied to a package, allows the use of all of the package’s public procedures, public functions, public variables, records, cursors, and other public objects and object types. This is the only type of privilege that applies to functions, procedures, and packages.
+
+ The EDB Postgres Advanced Server syntax for granting the `EXECUTE` privilege isn't fully compatible with Oracle databases. EDB Postgres Advanced Server requires that you qualify the program name with one of the keywords `FUNCTION`, `PROCEDURE`, or `PACKAGE`. You must omit these keywords in Oracle. 
+ 
+ For functions, EDB Postgres Advanced Server requires all input (`IN`, `IN OUT`) argument data types after the function name, including an empty parenthesis if there are no function arguments. For procedures, you must specify all input argument data types if the procedure has any input arguments. In Oracle, omit function and procedure signatures. All programs share the same namespace in Oracle, whereas functions, procedures, and packages have their own namespaces in EDB Postgres Advanced Server to allow program name overloading to a certain extent.
+
+`ALL PRIVILEGES`
+
+ Grants all of the available privileges at once.
+
+<div id="grant_on_roles" class="registered_link"></div>
+
+## GRANT on roles
+
+This variant of the `GRANT` command grants membership in a role to one or more other roles. Membership in a role is significant because it conveys the privileges granted to a role to each of its members.
+
+If you specify the `WITH ADMIN OPTION`, the member can grant membership in the role to others and revoke membership in the role.
+
+Database superusers can grant or revoke membership in any role to anyone. Roles having the `CREATEROLE` privilege can grant or revoke membership in any role that isn't a superuser.
+
+There are three predefined roles.
+
+`CONNECT`
+
+ Granting the `CONNECT` role is equivalent to giving the grantee the `LOGIN` privilege. The grantor must have the `CREATEROLE` privilege.
+
+`RESOURCE`
+
+ Granting the `RESOURCE` role is equivalent to granting the `CREATE` and `USAGE` privileges on a schema that has the same name as the grantee. This schema must exist before you give the grant. The grantor must have the privilege to grant `CREATE` or `USAGE` privileges on this schema to the grantee.
+
+`DBA`
+
+ Granting the `DBA` role is equivalent to making the grantee a superuser. The grantor must be a superuser.
+
+## Notes
+
+Use the `REVOKE` command to revoke access privileges.
+
+When a non-owner of an object attempts to grant privileges on the object, the command fails if the user has no privileges on the object. As long as a privilege is available, the command proceeds, but it grants only those privileges for which the user has grant options. The `GRANT ALL PRIVILEGES` forms issue a warning if no grant options are held, while the other forms issue a warning if grant options for any of the privileges named in the command aren't held. In principle, these statements apply to the object owner as well. However, since the owner is always treated as holding all grant options, the cases can never occur.
+
+Database superusers can access all objects regardless of object privilege settings. This is comparable to the rights of `root` in a Unix system. As with `root`, only operate as a superuser when you have to.
+
+If a superuser issues a `GRANT` or `REVOKE` command, the command is performed as though it were issued by the owner of the affected object. In particular, privileges granted by such a command appear as if granted by the object owner. (For role membership, the membership appears as if granted by the containing role.)
+
+`GRANT` and `REVOKE` can also be done by:
+
+-  A role that isn't the owner of the affected object but is a member of the role that owns the object.
+-  A role that is a member of a role that holds privileges `WITH GRANT OPTION` on the object. In this case, the privileges are recorded as having been granted by the role that owns the object or holds the privileges `WITH GRANT OPTION`.
+
+For example, if table `t1` is owned by role `g1`, of which role `u1` is a member, then `u1` can grant privileges on `t1` to `u2`. However, those privileges appear as if granted directly by `g1`. Any other member of role `g1` can revoke them later.
+
+If the role executing `GRANT` holds the required privileges indirectly by way of more than one role membership path, the containing role recorded as having done the grant is unspecified. In such cases, best practice is to use `SET ROLE` to become the specific role you want to do the `GRANT` as.
+
+Currently, EDB Postgres Advanced Server doesn't support granting or revoking privileges for individual columns of a table. One workaround is to create a view having just the desired columns and then grant privileges to that view.
+
+## Examples
+
+Grant insert privilege to all users on table `emp`:
+
+```sql
+GRANT INSERT ON emp TO PUBLIC;
+```
+
+Grant all available privileges to user `mary` on view `salesemp`:
+
+```sql
+GRANT ALL PRIVILEGES ON salesemp TO mary;
+```
+
+While this example does grant all privileges if executed by a superuser or the owner of `emp`, when executed by someone else it grants only those permissions for which that user has grant options.
+
+Grant membership in role `admins` to user `joe`:
+
+```sql
+GRANT admins TO joe;
+```
+
+Grant `CONNECT` privilege to user `joe`:
+
+```sql
+GRANT CONNECT TO joe;
+```
+
+## See also
+
+[REVOKE](67_revoke/#revoke), [SET ROLE](73_set_role/#set_role)
+
+## GRANT on system privileges
+
+This variant of the `GRANT` command gives a role the ability to perform certain *system* operations in a database. System privileges relate to the ability to create or delete certain database objects that aren't necessarily in the confines of one schema. Only database superusers can grant system privileges.
+
+`CREATE [PUBLIC] DATABASE LINK`
+
+  The `CREATE [PUBLIC] DATABASE LINK` privilege allows the specified role to create a database link. Include the `PUBLIC` keyword to allow the role to create public database links. Omit the `PUBLIC` keyword to allow the specified role to create private database links.
+
+`DROP PUBLIC DATABASE LINK`
+
+  The `DROP PUBLIC DATABASE LINK` privilege allows a role to drop a public database link. You don't need system privileges to drop a private database link. The link owner or a database superuser can drop a private database link.
+
+`EXEMPT ACCESS POLICY`
+
+  The `EXEMPT ACCESS POLICY` privilege allows a role to execute a SQL command without invoking any policy function that's associated with the target database object. The role is exempt from all security policies in the database.
+
+  The `EXEMPT ACCESS POLICY` privilege can't be inherited by membership to a role that has the `EXEMPT ACCESS POLICY` privilege. For example, the following sequence of `GRANT` commands doesn't result in user `joe` obtaining the `EXEMPT ACCESS POLICY` privilege. This is true even though `joe` is granted membership to the `enterprisedb` role, which was granted the `EXEMPT ACCESS POLICY` privilege:
+
+```sql
+GRANT EXEMPT ACCESS POLICY TO enterprisedb;
+GRANT enterprisedb TO joe;
+```
+
+  The `rolpolicyexempt` column of the system catalog table `pg_authid` is set to `true` if a role has the `EXEMPT ACCESS POLICY` privilege.
+
+## Examples
+
+Grant `CREATE PUBLIC DATABASE LINK` privilege to user `joe`:
+
+```sql
+GRANT CREATE PUBLIC DATABASE LINK TO joe;
+```
+
+Grant `DROP PUBLIC DATABASE LINK` privilege to user `joe`:
+
+```sql
+GRANT DROP PUBLIC DATABASE LINK TO joe;
+```
+
+Grant the `EXEMPT ACCESS POLICY` privilege to user `joe`:
+
+```sql
+GRANT EXEMPT ACCESS POLICY TO joe;
+```
+
+## Using the ALTER ROLE command to assign system privileges
+
+The EDB Postgres Advanced Server `ALTER ROLE` command also supports syntax that you can use to assign:
+
+-   The privilege required to create a public or private database link.
+-   The privilege required to drop a public database link.
+-   The `EXEMPT ACCESS POLICY` privilege.
+
+The `ALTER ROLE` syntax is equivalent to the respective commands compatible with Oracle databases.
+
+## See also
+
+[REVOKE](67_revoke/#revoke), [ALTER ROLE](08_alter_role_identified_by/#alter_role_identified_by)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65_insert.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65_insert.mdx
new file mode 100644
index 00000000000..8bc46318089
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65_insert.mdx
@@ -0,0 +1,130 @@
+---
+title: "INSERT"
+redirects:
+  - /epas/latest/epas_compat_sql/65_insert/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="insert" class="registered_link"></div>
+
+## Name
+
+`INSERT` &mdash; Create rows in a table.
+
+## Synopsis
+
+```sql
+INSERT INTO <table>[@<dblink> | [ AS ] <alias> ] [ ( <column> [, ...] ) ]
+  { VALUES ( { <expression> | DEFAULT } [, ...] )
+    [ RETURNING <return_expression> [, ...]
+        { INTO { <record> | <variable> [, ...] }
+        | BULK COLLECT INTO <collection> [, ...] } ]
+  | <query> }
+```
+
+## Description
+
+`INSERT` allows you to insert new rows into a table. You can insert a single row or several rows as a result of a query.
+
+You can list the columns in the target list in any order. Each column not present in the target list is inserted using a default value, either its declared default value or null.
+
+If the expression for each column doesn't have the correct data type, type conversion is attempted.
+
+You can specify the `RETURNING INTO { record | variable [, ...] }` clause only when the `INSERT` command is used in an SPL program and only when the `VALUES` clause is used.
+
+You can specify the `RETURNING BULK COLLECT INTO collection [, ...]` clause only if the `INSERT` command is used in an SPL program. If you specify more than one `collection` as the target of the `BULK COLLECT INTO` clause, then each `collection` must consist of a single, scalar field. That is, `collection` can't be a record. The `return_expression` evaluated for each inserted row becomes an element in `collection`, starting with the first element. Any existing rows in `collection` are deleted. If the result set is empty, then `collection` is empty.
+
+You need `INSERT` privilege to a table to insert into it. If you use the `query` clause to insert rows from a query, you also need `SELECT` privilege on any table used in the query.
+
+## Parameters
+
+`table`
+
+ The name (optionally schema-qualified) of an existing table.
+
+`alias`
+
+ A substitute name, which is an alias for the table, view, materialized view, or a subquery to reference in a statement during query execution.
+
+`dblink`
+
+ Database link name identifying a remote database. See [`CREATE DATABASE LINK`](21_create_public_database_link) for information on database links.
+
+`column`
+
+ The name of a column in `table`.
+
+`expression`
+
+ An expression or value to assign to `column`.
+
+`DEFAULT`
+
+ This column is filled with its default value.
+
+`query`
+
+ A query (`SELECT` statement) that supplies the rows to insert. See [`SELECT`](71_select) for a description of the syntax.
+
+`return_expression`
+
+ An expression that can include one or more columns from `table`. If you specify a column name from `table` in `return_expression`, the value substituted for the column when `return_expression` is evaluated is determined as follows:
+
+  -   If the column specified in `return_expression` is assigned a value in the `INSERT` command, then the assigned value is used in the evaluation of `return_expression`.
+
+  -   If the column specified in `return_expression` isn't assigned a value in the `INSERT` command, and there's no default value for the column in the table’s column definition, then null is used in the evaluation of `return_expression`.
+
+  -   If the column specified in `return_expression` isn't assigned a value in the `INSERT` command, and there's a default value for the column in the table’s column definition, then the default value is used in the evaluation of `return_expression`.
+
+`record`
+
+ A record whose field to assign the evaluated `return_expression`. The first `return_expression` is assigned to the first field in `record`, the second `return_expression` is assigned to the second field in `record`, and so on. The number of fields in `record` must exactly match the number of expressions, and the fields must be type-compatible with their assigned expressions.
+
+`variable`
+
+ A variable to which to assign the evaluated `return_expression`. If you specify more than one `return_expression` and `variable`, the first `return_expression` is assigned to the first `variable`, the second `return_expression` is assigned to the second `variable`, and so on. The number of variables specified following the `INTO` keyword must exactly match the number of expressions following the `RETURNING` keyword. The variables must be type-compatible with their assigned expressions.
+
+`collection`
+
+ A collection in which an element is created from the evaluated `return_expression`. There can be either: 
+ 
+ -  A single collection, which can be a collection of a single field or a collection of a record type. 
+ -  More than one collection, in which case each collection must consist of a single field. 
+ 
+ The number of return expressions must match in number and order the number of fields in all specified collections. Each corresponding `return_expression` and `collection` field must be type-compatible.
+
+## Examples
+
+Insert a single row into table `emp`:
+
+```sql
+INSERT INTO emp VALUES (8021,'JOHN','SALESMAN',7698,'22-FEB-07',1250,500,30);
+```
+
+This example omits the column `comm`, which means it uses the default value of null:
+
+```sql
+INSERT INTO emp (empno, ename, job, mgr, hiredate, sal, deptno)
+    VALUES (8022,'PETERS','CLERK',7698,'03-DEC-06',950,30);
+```
+
+This example uses the `DEFAULT` clause for the `hiredate` and `comm` columns rather than specifying a value:
+
+```sql
+INSERT INTO emp VALUES (8023,'FORD','ANALYST',7566,NULL,3000,NULL,20);
+```
+
+This example creates a table for the department names and then inserts into the table by selecting from the `dname` column of the `dept` table:
+
+```sql
+CREATE TABLE deptnames (
+    deptname        VARCHAR2(14)
+);
+INSERT INTO deptnames SELECT dname FROM dept;
+```
+
+This example creates an alias `enm` for the table `emp` and inserts rows into a table:
+
+```sql
+INSERT INTO emp AS enm (enm.empno, enm.ename, enm.job, enm.mgr, enm.hiredate, enm.sal, enm.deptno)
+  VALUES (7499, 'SMITH', 'ANALYST', 7902, '03-DEC-06', 2500, 20);
+```  
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx
new file mode 100644
index 00000000000..738a4b34e0d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/65a_merge.mdx
@@ -0,0 +1,142 @@
+---
+title: "MERGE"
+redirects:
+  - /epas/latest/epas_compat_sql/65a_merge/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+## Name
+
+`MERGE` &mdash; conditionally insert, update, or delete rows of a table.
+
+## Synopsis
+
+```sql
+MERGE INTO target_table_name [ target_alias ]
+USING data_source [ source_alias ] ON ( join_condition )
+merge_update_clause merge_insert_clause
+
+-- where merge_update_clause is
+WHEN MATCHED THEN 
+   UPDATE SET column = value, ... [ WHERE where_condition ]
+   [ DELETE WHERE where_condition ]
+
+-- and merge_insert_clause is
+WHEN NOT MATCHED THEN 
+   INSERT [(col_list)] VALUES (val_list) [ WHERE where_condition ] 
+```
+
+## Description
+
+`MERGE` allows you to select rows from one or more sources for update or insertion into a table. You specify the join condition to determine whether to update or insert into the target table. You specify conditional UPDATE and INSERT statements using the WHERE clause in the MERGE statement.
+
+`MERGE` provides a single SQL statement that can conditionally INSERT, UPDATE, or DELETE rows, a task which would otherwise require multiple procedural language statements.
+
+For more information, see [MERGE statement](https://www.postgresql.org/docs/current/sql-merge.html).
+
+
+## Parameters
+
+`target_table_name`
+
+ The name (optionally schema-qualified) of the target table to merge into.
+
+`target_alias`
+
+ A substitute name for the target table. When an alias is provided, it completely hides the actual name of the table.
+
+`data_source`
+
+ The name (optionally schema-qualified) of the source table or a source query. The source table is the source table name, view name, or transition table name. The source query (SELECT or VALUES statement) supplies the rows to be merged into the target_table_name.
+
+`source_alias`
+
+ A substitute name for the data source. When an alias is provided, it completely hides the actual name of the table.
+
+`join_condition`
+
+ An expression resulting in a value of type boolean similar to a WHERE clause that specifies which rows in the data_source match rows in the target_table_name.
+
+`merge_update_clause`
+
+ Specifies the new column values of the target table. It performs this update if the join_condition of the ON clause is true. 
+
+ Specify the where_condition if you want the database to execute the update operation only if the specified condition is true. The condition can refer to either the data source or the target table. If the condition is not true, then the database skips the update operation when merging the row into the table.
+
+ Specify the DELETE where_condition to clean up data in a table while populating or updating it. The only rows affected by this clause are those rows in the target table that are updated by the merge operation. The DELETE WHERE condition evaluates the updated value, not the original value that was evaluated by the UPDATE SET ... WHERE condition. If a row of the target table meets the DELETE condition but is not included in the join defined by the ON clause, then it is not deleted. 
+
+ You can specify this clause by itself or with the merge_insert_clause. If you specify both, then they can be in either order.
+
+`merge_insert_clause`
+
+ The merge_insert_clause specifies values to insert into the column of the target table if the condition of the ON clause is false. If you omit the column list after the INSERT keyword, then the number of columns in the target table must match the number of values in the VALUES clause.
+
+ To insert all of the source rows into the table, you can use a constant filter predicate in the ON clause condition. An example of a constant filter predicate is `ON (0=1)`. It recognizes such a predicate and makes an unconditional insert of all source rows into the table. This approach is different from omitting the merge_update_clause. In that case, the database still must perform a join. With constant filter predicate, no join is performed.
+
+ Specify the where_clause if you want the database to execute the insert operation only if the specified condition is true. The condition can refer only to the data source table. Database skips the insert operation for all rows for which the condition is not true.
+
+ You can specify this clause by itself or with the merge_update_clause. If you specify both, then they can be in either order.
+ 
+
+## Examples
+
+Create tables `target` and `source`:
+
+```sql
+CREATE TABLE target (tid integer, balance integer);
+CREATE TABLE source (sid integer, delta integer);
+```
+
+Add rows to both the tables:
+
+```sql
+# Insert rows into target table
+INSERT INTO target VALUES (1, 0);
+INSERT INTO target VALUES (2, 20);
+INSERT INTO target VALUES (3, 0);
+
+# Insert rows into source table
+INSERT INTO source VALUES (1, 100);
+INSERT INTO source VALUES (2, 200);
+INSERT INTO source VALUES (3, 300);
+INSERT INTO source VALUES (4, 100);
+INSERT INTO source VALUES (5, 300);
+INSERT INTO source VALUES (6, 600);
+```
+
+This example shows how to UPDATE and INSERT rows on the target table using the MERGE statement:
+
+```sql
+MERGE INTO target t
+USING source s
+ON (t.tid = s.sid)
+WHEN MATCHED THEN
+    UPDATE SET balance = s.delta
+WHEN NOT MATCHED THEN
+    INSERT VALUES (s.sid, s.delta);
+```
+
+This example shows how to UPDATE, INSERT, and conditionally DELETE rows on the target table using MERGE statement:
+
+```sql
+MERGE INTO target t
+USING source s
+ON (t.tid = s.sid)
+WHEN MATCHED THEN
+    UPDATE SET t.balance = t.balance + 100
+    DELETE WHERE sid = 1
+WHEN NOT MATCHED THEN
+    INSERT VALUES (s.sid, s.delta);
+```
+
+This example shows how to UPDATE, INSERT, and DELETE rows on the target table conditionally using the MERGE statement:
+
+```sql
+MERGE INTO target t
+USING source s
+ON (t.tid = s.sid)
+WHEN MATCHED THEN
+    UPDATE SET balance = s.delta WHERE balance = 0
+    DELETE WHERE sid = 1
+WHEN NOT MATCHED THEN
+    INSERT VALUES (s.sid, s.delta) WHERE s.sid >= 5;
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/66_lock.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/66_lock.mdx
new file mode 100644
index 00000000000..f733e2d1421
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/66_lock.mdx
@@ -0,0 +1,67 @@
+---
+title: "LOCK"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.083.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.109.html"
+redirects:
+  - /epas/latest/epas_compat_sql/66_lock/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="lock" class="registered_link"></div>
+
+## Name
+
+`LOCK` &mdash; Lock a table.
+
+## Synopsis
+
+```sql
+LOCK TABLE <name> [, ...] IN <lockmode> MODE [ NOWAIT ]
+```
+
+Where `lockmode` is one of:
+
+```text
+ROW SHARE | ROW EXCLUSIVE | SHARE | SHARE ROW EXCLUSIVE | EXCLUSIVE
+```
+
+## Description
+
+`LOCK TABLE` obtains a table-level lock, waiting if necessary for any conflicting locks to be released. If you specify `NOWAIT`, `LOCK TABLE` doesn't wait to acquire the desired lock. If the lock can't be acquired immediately, the command is aborted and an error occurs. Once obtained, the lock is held for the remainder of the current transaction. There's no `UNLOCK TABLE` command; locks are always released at transaction end.
+
+When acquiring locks for commands that reference tables, EDB Postgres Advanced Server always uses the least restrictive lock mode possible. `LOCK TABLE` provides for cases when you might need more restrictive locking. For example, suppose an application runs a transaction at the isolation level read committed and needs to ensure that data in a table remains stable for the rest of the transaction. To achieve this, you can obtain `SHARE` lock mode over the table before querying. This approach prevents concurrent data changes and ensures subsequent reads of the table see a stable view of committed data. That's because `SHARE` lock mode conflicts with the `ROW EXCLUSIVE` lock acquired by writers, and your `LOCK TABLE` name `IN SHARE MODE` statement waits until any concurrent holders of `ROW EXCLUSIVE` mode locks commit or roll back. Thus, once you obtain the lock, there are no uncommitted writes outstanding, and none can begin until you release the lock.
+
+To achieve a similar effect when running a transaction at the isolation level serializable, you have to execute the `LOCK TABLE` statement before executing any data modification statement. A serializable transaction’s view of data is frozen when its first data modification statement begins. A later `LOCK TABLE` still prevents concurrent writes, but it won’t ensure that what the transaction reads corresponds to the latest committed values.
+
+If a transaction of this sort changes the data in the table, then use `SHARE ROW EXCLUSIVE` lock mode instead of `SHARE` mode.
+
+This approach ensures that only one transaction of this type runs at a time. Without this, a deadlock is possible: two transactions might both acquire `SHARE` mode and then be unable to also acquire `ROW EXCLUSIVE` mode to perform their updates. A transaction’s own locks never conflict, so a transaction can acquire `ROW EXCLUSIVE` mode when it holds `SHARE` mode but not if anyone else holds `SHARE` mode.
+
+To avoid deadlocks, make sure all transactions acquire locks on the same objects in the same order. If multiple lock modes are involved for a single object, then always have transactions acquire the most restrictive mode first.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of an existing table to lock.
+
+ The command `LOCK TABLE a, b;` is equivalent to `LOCK TABLE a; LOCK TABLE b`. The tables are locked one by one in the order specified in the `LOCK TABLE` command.
+
+`lockmode`
+
+ Specifies the locks this lock conflicts with.
+
+ If you don't specify a lock mode, then the server uses the most restrictive mode: `ACCESS EXCLUSIVE`. `ACCESS EXCLUSIVE` isn't compatible with Oracle databases. In EDB Postgres Advanced Server, this configuration mode ensures that no other transaction can access the locked table.
+
+`NOWAIT`
+
+ Specifies for `LOCK TABLE` not to wait for any conflicting locks to be released. If you can't immediately acquire the specified lock without waiting, the transaction is aborted.
+
+## Notes
+
+All forms of `LOCK` require `UPDATE` or `DELETE` privileges.
+
+`LOCK TABLE` is useful only inside a transaction block since the lock is dropped as soon as the transaction ends. A `LOCK TABLE` command appearing outside any transaction block forms a self-contained transaction, so the lock is dropped as soon as you obtain it.
+
+`LOCK TABLE` deals only with table-level locks, and so the mode names involving `ROW` are all misnomers. These mode names are generally read as indicating the intention of the user to acquire row-level locks in the locked table. Also, `ROW EXCLUSIVE` mode is a sharable table lock. Keep in mind that all the lock modes have identical semantics as far as `LOCK TABLE` is concerned, differing only in the rules about the modes that conflict with each other.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/67_revoke.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/67_revoke.mdx
new file mode 100644
index 00000000000..371abc59112
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/67_revoke.mdx
@@ -0,0 +1,142 @@
+---
+title: "REVOKE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.084.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.110.html"
+redirects:
+  - /epas/latest/epas_compat_sql/67_revoke/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="revoke" class="registered_link"></div>
+
+## Name
+
+`REVOKE` &mdash; Remove access privileges.
+
+## Synopsis
+
+```sql
+REVOKE { { SELECT | INSERT | UPDATE | DELETE | REFERENCES }
+  [,...] | ALL [ PRIVILEGES ] }
+  ON tablename
+  FROM { username | groupname | PUBLIC } [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE { SELECT | ALL [ PRIVILEGES ] }
+  ON sequencename
+  FROM { username | groupname | PUBLIC } [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE { EXECUTE | ALL [ PRIVILEGES ] }
+  ON FUNCTION progname
+    ( [ [ argmode ] [ argname ] argtype ] [, ...] )
+  FROM { username | groupname | PUBLIC } [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE { EXECUTE | ALL [ PRIVILEGES ] }
+  ON PROCEDURE progname
+    [ ( [ [ argmode ] [ argname ] argtype ] [, ...] ) ]
+  FROM { username | groupname | PUBLIC } [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE { EXECUTE | ALL [ PRIVILEGES ] }
+  ON PACKAGE packagename
+  FROM { username | groupname | PUBLIC } [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE role [, ...] FROM { username | groupname | PUBLIC }
+  [, ...]
+  [ CASCADE | RESTRICT ]
+
+REVOKE { CONNECT | RESOURCE | DBA } [, ...]
+  FROM { username | groupname } [, ...]
+
+REVOKE CREATE [ PUBLIC ] DATABASE LINK
+  FROM { username | groupname }
+
+REVOKE DROP PUBLIC DATABASE LINK
+  FROM { username | groupname }
+
+REVOKE EXEMPT ACCESS POLICY
+  FROM { username | groupname }
+```
+
+## Description
+
+The `REVOKE` command revokes privileges that were granted to one or more roles. The key word `PUBLIC` refers to the implicitly defined group of all roles.
+
+See [`GRANT`](64_grant) for the meaning of the privilege types.
+
+A role has the sum of:
+-  Privileges granted directly to it 
+-  Privileges granted to any role it is presently a member of
+-  Privileges granted to `PUBLIC`
+
+Thus, for example, revoking the `SELECT` privilege from `PUBLIC` doesn't necessarily mean that all roles lose `SELECT` privilege on the object. Roles that were granted the privilege directly or from another role still have it.
+
+If the privilege was granted with the grant option, the grant option for the privilege is revoked along with the privilege.
+
+If a user holds a privilege with grant option and granted it to other users, then the privileges held by those other users are called *dependent privileges*. If the privilege or the grant option held by the first user is revoked, any dependent privileges are also revoked if `CASCADE` is specified. Without the `CASCADE` option, the revoke action fails. This recursive revocation affects only privileges that were granted through a chain of users that's traceable to the subject of this `REVOKE` command. The affected users can keep the privilege if it was also granted through other users.
+
+!!! Note
+    The `CASCADE` option isn't compatible with Oracle databases. By default, Oracle always cascades dependent privileges. EDB Postgres Advanced Server requires the `CASCADE` keyword for the `REVOKE` command to succeed.
+
+When revoking membership in a role, `GRANT OPTION` is called `ADMIN OPTION`. The behavior is similar.
+
+## Notes
+
+A user can revoke only the privileges that were granted directly by that user. If, for example, user A  granted a privilege with grant option to user B, and user B granted it to user C, then user A can't revoke the privilege directly from C. Instead, user A can revoke the grant option from user B and use the `CASCADE` option to revoke the privilege from user C. For another example, if both A and B granted the same privilege to `C`, A can revoke their own grant but not B’s grant. C still has the privilege.
+
+When a non-owner of an object attempts to revoke privileges on the object, the command fails if the user doesn't have privileges on the object. As long as some privilege is available, the command proceeds, but it revokes only those privileges for which the user has grant options. The `REVOKE ALL PRIVILEGES` forms issue a warning message if no grant options are held. The other forms issue a warning if grant options for any of the privileges named in the command aren't held. In principle, these statements apply to the object owner as well. However, since the owner is always treated as holding all grant options, the cases can never occur.
+
+If a superuser issues a `GRANT` or `REVOKE` command, the command is performed as though it were issued by the owner of the affected object. Since all privileges ultimately come from the object owner (possibly indirectly by way of chains of grant options), a superuser can revoke all privileges. This might require use of `CASCADE`.
+
+A role that is not the owner of the affected object can also use `REVOKE`. That role must be a member of the role that owns the object or a member of a role that holds privileges `WITH GRANT OPTION` on the object. In this case, the command is performed as if issued by the containing role that owns the object or holds the privileges `WITH GRANT OPTION`. For example, if table t1 is owned by role g1, of which role u1 is a member, then u1 can revoke privileges on t1 that are recorded as being granted by g1. This includes grants made by u1 as well as by other members of role g1.
+
+If the role executing `REVOKE` holds privileges indirectly by more than one role membership path, the containing role that performs the command is unspecified. In such cases, best practice is to use `SET ROLE` to become the specific role you want to do the `REVOKE` as. Otherwise, you might revoke privileges other than the ones you intended or not revoke anything at all.
+
+!!! Note
+    The EDB Postgres Advanced Server `ALTER ROLE` command also supports syntax that revokes the system privileges required to create a public or private database link or exemptions from fine-grained access control policies (`DBMS_RLS`). The `ALTER ROLE` syntax is functionally equivalent to the respective `REVOKE` command, compatible with Oracle databases.
+
+## Examples
+
+Revoke insert privilege for the public on table `emp`:
+
+```sql
+REVOKE INSERT ON emp FROM PUBLIC;
+```
+
+Revoke all privileges from user `mary` on view `salesemp`. This actually means “revoke all privileges that I granted.”
+
+```sql
+REVOKE ALL PRIVILEGES ON salesemp FROM mary;
+```
+
+Revoke membership in role `admins` from user `joe`:
+
+```sql
+REVOKE admins FROM joe;
+```
+
+Revoke `CONNECT` privilege from user `joe`:
+
+```sql
+REVOKE CONNECT FROM joe;
+```
+
+Revoke `CREATE DATABASE LINK` privilege from user `joe`:
+
+```sql
+REVOKE CREATE DATABASE LINK FROM joe;
+```
+
+Revoke the `EXEMPT ACCESS POLICY` privilege from user `joe`:
+
+```sql
+REVOKE EXEMPT ACCESS POLICY FROM joe;
+```
+
+## See also
+
+[GRANT](64_grant/#grant), [SET ROLE](73_set_role/#set_role)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/68_rollback.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/68_rollback.mdx
new file mode 100644
index 00000000000..8881fbd031a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/68_rollback.mdx
@@ -0,0 +1,48 @@
+---
+title: "ROLLBACK"
+redirects:
+  - /epas/latest/epas_compat_sql/68_rollback/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="rollback" class="registered_link"></div>
+
+## Name
+
+`ROLLBACK` &mdash; Abort the current transaction.
+
+## Synopsis
+
+```sql
+ROLLBACK [ WORK ]
+```
+
+## Description
+
+`ROLLBACK` rolls back the current transaction and discards all the updates made by the transaction.
+
+## Parameters
+
+`WORK`
+
+ Optional keyword that has no effect.
+
+## Notes
+
+Use `COMMIT` to successfully terminate a transaction.
+
+Issuing `ROLLBACK` when not inside a transaction does no harm.
+
+!!! Note
+    Executing a `ROLLBACK` in a plpgsql procedure throws an error if there's an Oracle-style SPL procedure on the runtime stack.
+
+## Examples
+
+Abort all changes:
+
+```sql
+ROLLBACK;
+```
+
+## See also
+
+[COMMIT](19_commit/#commit), [ROLLBACK TO SAVEPOINT](69_rollback_to_savepoint/#rollback_to_savepoint), [SAVEPOINT](70_savepoint/#savepoint)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/69_rollback_to_savepoint.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/69_rollback_to_savepoint.mdx
new file mode 100644
index 00000000000..7c360fe2330
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/69_rollback_to_savepoint.mdx
@@ -0,0 +1,56 @@
+---
+title: "ROLLBACK TO SAVEPOINT"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.086.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.112.html"
+redirects:
+  - /epas/latest/epas_compat_sql/69_rollback_to_savepoint/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="rollback_to_savepoint" class="registered_link"></div>
+
+## Name
+
+`ROLLBACK TO SAVEPOINT` &mdash; Roll back to a savepoint.
+
+## Synopsis
+
+```sql
+ROLLBACK [ WORK ] TO [ SAVEPOINT ] <savepoint_name>
+```
+
+## Description
+
+Roll back all commands that were executed after the savepoint was set. The savepoint remains valid and you can roll back to it again if you need to.
+
+`ROLLBACK TO SAVEPOINT` destroys all savepoints that were established after the named savepoint.
+
+## Parameters
+
+`savepoint_name`
+
+ The savepoint to which to roll back.
+
+## Notes
+
+Specifying a savepoint name that wasn't established is an error.
+
+`ROLLBACK TO SAVEPOINT` isn't supported in SPL programs.
+
+## Examples
+
+Undo the effects of the commands executed from the point when savepoint `depts` was established:
+
+```sql
+\set AUTOCOMMIT off
+INSERT INTO dept VALUES (50, 'HR', 'NEW YORK');
+SAVEPOINT depts;
+INSERT INTO emp (empno, ename, deptno) VALUES (9001, 'JONES', 50);
+INSERT INTO emp (empno, ename, deptno) VALUES (9002, 'ALICE', 50);
+ROLLBACK TO SAVEPOINT depts;
+```
+
+## See also
+
+[COMMIT](19_commit/#commit), [ROLLBACK](68_rollback/#rollback), [SAVEPOINT](70_savepoint/#savepoint)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/70_savepoint.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/70_savepoint.mdx
new file mode 100644
index 00000000000..7a3bfd3f60b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/70_savepoint.mdx
@@ -0,0 +1,62 @@
+---
+title: "SAVEPOINT"
+redirects:
+  - /epas/latest/epas_compat_sql/70_savepoint/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="savepoint" class="registered_link"></div>
+
+## Name
+
+`SAVEPOINT`&mdash; Define a new savepoint in the current transaction.
+
+## Synopsis
+
+```sql
+SAVEPOINT <savepoint_name>
+```
+
+## Description
+
+`SAVEPOINT` establishes a new savepoint in the current transaction.
+
+A savepoint is a mark inside a transaction that allows all commands that are executed after it to be rolled back. This restores the transaction state to what it was at the savepoint.
+
+## Parameters
+
+`savepoint_name`
+
+ The name ofo the savepoint.
+
+## Notes
+
+Use `ROLLBACK TO SAVEPOINT` to roll back to a savepoint.
+
+You can establish savepoints only when inside a transaction block. You can define multiple savepoints in a transaction.
+
+When another savepoint is established with the same name as a previous savepoint, the old savepoint is kept. However, only the more recent one is used when rolling back.
+
+`SAVEPOINT` isn't supported in SPL programs.
+
+## Examples
+
+Establish a savepoint and then undo the effects of all commands executed after it:
+
+```sql
+\set AUTOCOMMIT off
+INSERT INTO dept VALUES (50, 'HR', 'NEW YORK');
+SAVEPOINT depts;
+INSERT INTO emp (empno, ename, deptno) VALUES (9001, 'JONES', 50);
+INSERT INTO emp (empno, ename, deptno) VALUES (9002, 'ALICE', 50);
+SAVEPOINT emps;
+INSERT INTO jobhist VALUES (9001,'17-SEP-07',NULL,'CLERK',800,NULL,50,'New Hire');
+INSERT INTO jobhist VALUES (9002,'20-SEP-07',NULL,'CLERK',700,NULL,50,'New Hire');
+ROLLBACK TO depts;
+COMMIT;
+```
+
+This transaction commits a row into the `dept` table. The inserts into the `emp` and `jobhist` tables are rolled back.
+
+## See also
+
+[COMMIT](19_commit/#commit), [ROLLBACK](68_rollback/#rollback), [ROLLBACK TO SAVEPOINT](69_rollback_to_savepoint/#rollback_to_savepoint)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/71_select.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/71_select.mdx
new file mode 100644
index 00000000000..53eac29620a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/71_select.mdx
@@ -0,0 +1,464 @@
+---
+title: "SELECT"
+redirects:
+  - /epas/latest/epas_compat_sql/71_select/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="select" class="registered_link"></div>
+
+## Name
+
+`SELECT` &mdash; Retrieve rows from a table or view.
+
+## Synopsis
+
+```sql
+SELECT [ optimizer_hint ] [ ALL | DISTINCT | UNIQUE ]
+  * | expression [ AS output_name ] [, ...]
+  FROM from_item [, ...]
+  [ WHERE condition ]
+  [ [ START WITH start_expression ]
+      CONNECT BY { PRIOR parent_expr = child_expr |
+        child_expr = PRIOR parent_expr }
+    [ ORDER SIBLINGS BY expression [ ASC | DESC ] [, ...] ] ]
+  [ GROUP BY { expression | ROLLUP ( expr_list ) |
+      CUBE ( expr_list ) | GROUPING SETS ( expr_list ) } [, ...]
+      [ LEVEL ] ]
+  [ HAVING condition [, ...] ]
+  [ { UNION [ ALL ] | INTERSECT | MINUS } select ]
+  [ ORDER BY expression [ ASC | DESC ] [, ...] ]
+  [ FOR UPDATE [WAIT n|NOWAIT|SKIP LOCKED]]
+```
+
+Where `from_item` can be one of:
+
+```sql
+table_name[@dblink ] [ alias ]
+( select ) alias
+from_item [ NATURAL ] join_type from_item
+  [ ON join_condition | USING ( join_column [, ...] ) ]
+```
+
+## Description
+
+`SELECT` retrieves rows from one or more tables. The general processing of `SELECT` is as follows:
+
+1.  All elements in the `FROM` list are computed. (Each element in the `FROM` list is a real or virtual table.) If you specify more than one element in the `FROM` list, they are cross joined. See [`FROM` clause](#from-clause).
+2.  If you specify the `WHERE` clause, all rows that don't satisfy the condition are eliminated from the output. See [`WHERE` clause](#where-clause).
+3.  If you specify the `GROUP BY` clause, the output is divided into groups of rows that match one or more values. The `HAVING` clause eliminates groups that don't satisfy the given condition. See [`GROUP BY` clause](#group-by-clause) and [`HAVING` clause](#having-clause).
+4.  Using the operators `UNION`, `INTERSECT`, and `MINUS`, you can combine the output of more than one `SELECT` statement to form a single result set. The `UNION` operator returns all rows that are in one or both of the result sets. The `INTERSECT` operator returns all rows that are strictly in both result sets. The `MINUS` operator returns the rows that are in the first result set but not in the second. In all three cases, duplicate rows are eliminated. In the case of the `UNION` operator, if you specify `ALL`, then duplicates aren't eliminated. See [`UNION` clause](#union-clause), [`INTERSECT` clause](#intersect-clause), and [`MINUS` clause](#minus-clause).
+5.  The actual output rows are computed using the `SELECT` output expressions for each selected row. See [`SELECT` list](#select-list).
+6.  The `CONNECT BY` clause is used to select data that has a hierarchical relationship. Such data has a parent-child relationship between rows. See [`CONNECT BY` clause](#connect-by-clause).
+7.  If you specify the `ORDER BY` clause, the returned rows are sorted in the specified order. Otherwise, the rows are returned in the order the system finds fastest to produce. See [`ORDER BY` clause](#order-by-clause).
+8.  `DISTINCT | UNIQUE` eliminates duplicate rows from the result. `ALL` (the default) returns all candidate rows, including duplicates. See [`DISTINCT | UNIQUE` clause](#distinct--unique-clause).
+9.  The `FOR UPDATE` clause causes the `SELECT` statement to lock the selected rows against concurrent updates. See [`FOR UPDATE` clause](#for-update-clause).
+
+You must have `SELECT` privilege on a table to read its values. The use of `FOR UPDATE` requires `UPDATE` privilege as well.
+
+## Parameters
+
+`optimizer_hint`
+
+ Comment-embedded hints to the optimizer for selecting an execution plan. See [Optimizer hints](../../../application_programming/optimizing_code/05_optimizer_hints/) for information about optimizer hints.
+
+## FROM clause
+
+The `FROM` clause specifies one or more source tables for a `SELECT` statement. The syntax is:
+
+```sql
+FROM source [, ...]
+```
+
+Where `source` can be one of following elements:
+
+`table_name[@dblink ]`
+
+ The name (optionally schema-qualified) of an existing table or view. `dblink` is a database link name identifying a remote database. See the [`CREATE DATABASE LINK`](21_create_public_database_link#create_public_database_link) command for information on database links.
+
+`alias`
+
+ A substitute name for the `FROM` item containing the alias. Use an alias for brevity or to eliminate ambiguity for self-joins where the same table is scanned multiple times. Providing an alias completely hides the name of the table or function. For example, given `FROM foo AS f`, the remainder of the `SELECT` must refer to this `FROM` item as `f`, not `foo`.
+
+`select`
+
+ A sub-`SELECT` can appear in the `FROM` clause. This acts as though its output were created as a temporary table for the duration of this single `SELECT` command. Surround the sub-`SELECT` with parentheses, and provide an alias for it.
+
+`join_type`
+
+ One of the following:
+
+ `[ INNER ] JOIN`
+
+ `LEFT [ OUTER ] JOIN`
+
+ `RIGHT [ OUTER ] JOIN`
+
+ `FULL [ OUTER ] JOIN`
+
+ `CROSS JOIN`
+
+ For the `INNER` and `OUTER` join types, you must specify a join condition, namely one of `NATURAL`, `ON join_condition`, or `USING (join_column [, ...] )`. For `CROSS JOIN`, you can't use any of these clauses.
+
+ A `JOIN` clause combines two `FROM` items. Use parentheses to determine the order of nesting. Without parentheses, `JOINs` nest left-to-right. In any case `JOIN` binds more tightly than the commas separating `FROM` items.
+
+ `CROSS JOIN` and `INNER JOIN` produce a simple Cartesian product, the same result that you get from listing the two items at the top level of `FROM` but restricted by any join condition. `CROSS JOIN` is equivalent to `INNER JOIN ON (TRUE)`, that is, no rows are removed by qualification. These join types are a notational convenience, since you can accomplish the same thing using `FROM` and `WHERE`.
+
+ `LEFT OUTER JOIN` returns all rows in the qualified Cartesian product, that is, all combined rows that pass its join condition. It also returns one copy of each row in the left-hand table for which there was no right-hand row that passed the join condition. This left-hand row is extended to the full width of the joined table by inserting null values for the right-hand columns. Only the `JOIN` clause’s own condition is considered while deciding which rows have matches. Outer conditions are applied afterwards.
+
+ Conversely, `RIGHT OUTER JOIN` returns all the joined rows plus one row for each unmatched right-hand row extended with nulls on the left. This is a notational convenience, since you can convert it to a `LEFT OUTER JOIN` by switching the left and right inputs.
+
+ `FULL OUTER JOIN` returns all the joined rows, one row for each unmatched left-hand row extended with nulls on the right, and one row for each unmatched right-hand row extended with nulls on the left.
+
+`ON join_condition`
+
+ `join_condition` is an expression resulting in a value of type `BOOLEAN` (similar to a `WHERE` clause) that specifies the rows in a join that are considered to match.
+
+`USING (join_column [, ...] )`
+
+ A clause of the form `USING (a, b, ... )` is shorthand for `ON left_table.a = right_table.a AND left_table.b = right_table.b ....` Also, `USING` implies that only one of each pair of equivalent columns is included in the join output, not both.
+
+`NATURAL`
+
+ `NATURAL` is shorthand for a `USING` list that mentions all columns in the two tables that have the same names.
+
+If you specify multiple sources, the result is the Cartesian product (cross join) of all the sources. Usually qualification conditions are added to restrict the returned rows to a small subset of the Cartesian product.
+
+### Example
+
+This example selects all of the entries from the `dept` table:
+
+```sql
+SELECT * FROM dept;
+__OUTPUT__
+deptno |  dname      |  loc
+-------+-------------+-----------
+    10 |  ACCOUNTING |  NEW YORK
+    20 |  RESEARCH   |  DALLAS
+    30 |  SALES      |  CHICAGO
+    40 | OPERATIONS  |  BOSTON
+ (4 rows)
+```
+
+## WHERE clause
+
+The optional `WHERE` clause has the form:
+
+```sql
+WHERE condition
+```
+
+where `condition` is any expression that evaluates to a result of type `BOOLEAN`. Any row that doesn't satisfy this condition is eliminated from the output. A row satisfies the condition if it returns `TRUE` when the actual row values are substituted for any variable references.
+
+### Example
+
+This example joins the contents of the `emp` and `dept` tables. The value of the `deptno` column in the `emp` table is equal to the value of the `deptno` column in the `deptno` table.
+
+```sql
+SELECT d.deptno, d.dname, e.empno, e.ename, e.mgr, e.hiredate
+    FROM emp e, dept d
+    WHERE d.deptno = e.deptno;
+__OUTPUT__
+ deptno |   dname    | empno | ename  | mgr  |      hiredate
+--------+------------+-------+--------+------+--------------------
+     10 | ACCOUNTING |  7934 | MILLER | 7782 | 23-JAN-82 00:00:00
+     10 | ACCOUNTING |  7782 | CLARK  | 7839 | 09-JUN-81 00:00:00
+     10 | ACCOUNTING |  7839 | KING   |      | 17-NOV-81 00:00:00
+     20 | RESEARCH   |  7788 | SCOTT  | 7566 | 19-APR-87 00:00:00
+     20 | RESEARCH   |  7566 | JONES  | 7839 | 02-APR-81 00:00:00
+     20 | RESEARCH   |  7369 | SMITH  | 7902 | 17-DEC-80 00:00:00
+     20 | RESEARCH   |  7876 | ADAMS  | 7788 | 23-MAY-87 00:00:00
+     20 | RESEARCH   |  7902 | FORD   | 7566 | 03-DEC-81 00:00:00
+     30 | SALES      |  7521 | WARD   | 7698 | 22-FEB-81 00:00:00
+     30 | SALES      |  7844 | TURNER | 7698 | 08-SEP-81 00:00:00
+     30 | SALES      |  7499 | ALLEN  | 7698 | 20-FEB-81 00:00:00
+     30 | SALES      |  7698 | BLAKE  | 7839 | 01-MAY-81 00:00:00
+     30 | SALES      |  7654 | MARTIN | 7698 | 28-SEP-81 00:00:00
+     30 | SALES      |  7900 | JAMES  | 7698 | 03-DEC-81 00:00:00
+(14 rows)
+```
+
+## GROUP BY clause
+
+The optional `GROUP BY` clause has the form:
+
+```sql
+GROUP BY { expression | ROLLUP ( expr_list ) |
+  CUBE ( expr_list ) | GROUPING SETS ( expr_list ) } [, ...]
+```
+
+`GROUP BY` condenses all selected rows that share the same values for the grouped expressions into a single row. `expression` can be an input column name or the name or ordinal number of an output column (`SELECT` list item). Or it can be an arbitrary expression formed from input-column values. In case of ambiguity, a `GROUP BY` name is interpreted as an input-column name rather than an output column name.
+
+`ROLLUP`, `CUBE`, and `GROUPING SETS` are extensions to the `GROUP BY` clause for supporting multidimensional analysis.
+
+Aggregate functions, if any are used, are computed across all rows making up each group, producing a separate value for each group. Without `GROUP BY`, an aggregate produces a single value computed across all the selected rows. When `GROUP BY` is present, it isn't valid for the `SELECT` list expressions to refer to ungrouped columns except in aggregate functions, since there is more than one possible value to return for an ungrouped column.
+
+### Example
+
+This example computes the sum of the `sal` column in the `emp` table, grouping the results by department number:
+
+```sql
+SELECT deptno, SUM(sal) AS total
+    FROM emp
+    GROUP BY deptno;
+__OUTPUT__
+ deptno |  total
+--------+----------
+     10 |  8750.00
+     20 | 10875.00
+     30 |  9400.00
+(3 rows)
+```
+
+## HAVING clause
+
+The optional `HAVING` clause has the form:
+
+```sql
+HAVING condition
+```
+
+Where `condition` is the same as specified for the `WHERE` clause.
+
+`HAVING` eliminates group rows that don't satisfy the specified condition. `HAVING` is different from `WHERE`. `WHERE` filters individual rows before applying `GROUP BY`, while `HAVING` filters group rows created by `GROUP BY`. Each column referenced in `condition` must unambiguously reference a grouping column, unless the reference appears in an aggregate function.
+
+### Example
+
+Sum the column `sal` of all employees, group the results by department number, and show those group totals that are less than 10000:
+
+```sql
+SELECT deptno, SUM(sal) AS total
+    FROM emp
+    GROUP BY deptno
+    HAVING SUM(sal) < 10000;
+__OUTPUT__
+ deptno |  total
+--------+---------
+     10 | 8750.00
+     30 | 9400.00
+(2 rows)
+```
+
+## SELECT List
+
+The `SELECT` list (between the keywords `SELECT` and `FROM`) specifies expressions that form the output rows of the `SELECT` statement. The expressions can refer to columns computed in the `FROM` clause, and they usually do. Using the clause `AS output_name`, you can specify another name for an output column. This name is primarily used to label the column for display. You can also use it to refer to the column’s value in `ORDER BY` and `GROUP BY` clauses but not in the `WHERE` or `HAVING` clauses. In those clauses, you must write out the expression.
+
+Instead of an expression, you can write \* in the output list as a shorthand for all the columns of the selected rows.
+
+### Example
+
+The `SELECT` list in this example specifies for the result set to include the `empno` column, the `ename` column, the `mgr` column, and the `hiredate` column:
+
+```sql
+SELECT empno, ename, mgr, hiredate FROM emp;
+__OUTPUT__
+ empno | ename  | mgr  |      hiredate
+-------+--------+------+--------------------
+  7934 | MILLER | 7782 | 23-JAN-82 00:00:00
+  7782 | CLARK  | 7839 | 09-JUN-81 00:00:00
+  7839 | KING   |      | 17-NOV-81 00:00:00
+  7788 | SCOTT  | 7566 | 19-APR-87 00:00:00
+  7566 | JONES  | 7839 | 02-APR-81 00:00:00
+  7369 | SMITH  | 7902 | 17-DEC-80 00:00:00
+  7876 | ADAMS  | 7788 | 23-MAY-87 00:00:00
+  7902 | FORD   | 7566 | 03-DEC-81 00:00:00
+  7521 | WARD   | 7698 | 22-FEB-81 00:00:00
+  7844 | TURNER | 7698 | 08-SEP-81 00:00:00
+  7499 | ALLEN  | 7698 | 20-FEB-81 00:00:00
+  7698 | BLAKE  | 7839 | 01-MAY-81 00:00:00
+  7654 | MARTIN | 7698 | 28-SEP-81 00:00:00
+  7900 | JAMES  | 7698 | 03-DEC-81 00:00:00
+(14 rows)
+```
+
+## UNION clause
+
+The `UNION` clause has the form:
+
+```sql
+select_statement UNION [ ALL ] select_statement
+```
+
+Where `select_statement` is any `SELECT` statement without an `ORDER BY` or `FOR UPDATE` clause. You can attach `ORDER BY` to a sub-expression if you enclose it in parentheses. Without parentheses, these clauses apply to the result of the `UNION`, not to its right-hand input expression.
+
+The `UNION` operator computes the set union of the rows returned by the involved `SELECT` statements. A row is in the set union of two result sets if it appears in at least one of the result sets. The two `SELECT` statements that represent the direct operands of the `UNION` must produce the same number of columns, and corresponding columns must have compatible data types.
+
+The result of `UNION` doesn't contain any duplicate rows unless you specify the `ALL` option. `ALL` prevents eliminating duplicates.
+
+Without parentheses, multiple `UNION` operators in the same `SELECT` statement are evaluated left to right.
+
+Currently, you can't specify `FOR UPDATE` either for a `UNION` result or for any input of a `UNION`.
+
+## INTERSECT clause
+
+The `INTERSECT` clause has the form:
+
+```sql
+select_statement INTERSECT select_statement
+```
+
+Where `select_statement` is any `SELECT` statement without an `ORDER BY` or `FOR UPDATE` clause.
+
+The `INTERSECT` operator computes the set intersection of the rows returned by the involved `SELECT` statements. A row is in the intersection of two result sets if it appears in both result sets.
+
+The result of `INTERSECT` doesn't contain any duplicate rows.
+
+Without parentheses, multiple `INTERSECT` operators in the same `SELECT` statement are evaluated left to right. `INTERSECT` binds more tightly than `UNION`. That is, `A UNION B INTERSECT C` is read as `A UNION (B INTERSECT C)`.
+
+## MINUS clause
+
+The `MINUS` clause has this general form:
+
+```sql
+select_statement MINUS select_statement
+```
+
+Where `select_statement` is any `SELECT` statement without an `ORDER BY` or `FOR UPDATE` clause.
+
+The `MINUS` operator computes the set of rows that are in the result of the left `SELECT` statement but not in the result of the right one.
+
+The result of `MINUS` doesn't contain any duplicate rows.
+
+Without parentheses, multiple `MINUS` operators in the same `SELECT` statement are evaluated left to right. `MINUS` binds at the same level as `UNION`.
+
+## CONNECT BY clause
+
+The `CONNECT BY` clause determines the parent-child relationship of rows when performing a hierarchical query. It has the general form:
+
+```sql
+CONNECT BY { PRIOR parent_expr = child_expr |
+  child_expr = PRIOR parent_expr }
+```
+
+Where `parent_expr` is evaluated on a candidate parent row. If `parent_expr = child_expr` results in `TRUE` for a row returned by the `FROM` clause, then this row is considered a child of the parent.
+
+You can specify the following optional clauses with the `CONNECT BY` clause.
+
+`START WITH start_expression`
+
+ The rows returned by the `FROM` clause on which `start_expression` evaluates to `TRUE` become the root nodes of the hierarchy.
+
+`ORDER SIBLINGS BY expression [ ASC | DESC ] [, ...]`
+
+ Sibling rows of the hierarchy are ordered by `expression` in the result set.
+
+!!! Note
+    EDB Postgres Advanced Server doesn't support the use of `AND` or other operators in the `CONNECT BY` clause.
+
+## ORDER BY clause
+
+The optional `ORDER BY` clause has the form:
+
+```sql
+ORDER BY expression [ ASC | DESC ] [, ...]
+```
+
+Where `expression` can be the name or ordinal number of an output column (`SELECT` list item), or it can be an arbitrary expression formed from input-column values.
+
+The `ORDER BY` clause sorts the result rows according to the specified expressions. If two rows are equal according to the left-most expression, they are compared according to the next expression, and so on. If they are equal according to all specified expressions, they are returned in an implementation-dependent order.
+
+The ordinal number refers to the ordinal (left-to-right) position of the result column. This feature makes it possible to define an ordering on the basis of a column that doesn't have a unique name. This is never required because you can always assign a name to a result column using the `AS` clause.
+
+You also can use arbitrary expressions in the `ORDER BY` clause, including columns that don't appear in the `SELECT` result list. Thus the following statement is valid:
+
+```sql
+SELECT ename FROM emp ORDER BY empno;
+```
+
+A limitation of this feature is that an `ORDER BY` clause applying to the result of a `UNION`, `INTERSECT`, or `MINUS` clause can specify only an output column name or number, not an expression.
+
+If an `ORDER BY` expression is a simple name that matches both a result column name and an input column name, `ORDER BY` interprets it as the result column name. This behavior is the opposite of the choice that `GROUP BY` makes in the same situation. This inconsistency is compatible with the SQL standard.
+
+Optionally, you can add the key word `ASC` (ascending) or `DESC` (descending) after any expression in the `ORDER BY` clause. `ASC` is the default.
+
+The null value sorts higher than any other value. In other words, with ascending sort order, null values sort at the end. With descending sort order, null values sort at the beginning.
+
+Character-string data is sorted according to the locale-specific collation order that was established when the database cluster was initialized.
+
+!!! Note
+    If you specify `SELECT DISTINCT` or if a `SELECT` statement includes the `SELECT DISTINCT ...ORDER BY` clause, then all the expressions in `ORDER BY` must be present in the select list of the `SELECT DISTINCT` query.
+
+## Examples
+
+These examples sort the individual results according to the contents of the second column (`dname`):
+
+```sql
+SELECT * FROM dept ORDER BY dname;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     40 | OPERATIONS | BOSTON
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+(4 rows)
+```
+```sql
+SELECT * FROM dept ORDER BY 2;
+__OUTPUT__
+ deptno |   dname    |   loc
+--------+------------+----------
+     10 | ACCOUNTING | NEW YORK
+     40 | OPERATIONS | BOSTON
+     20 | RESEARCH   | DALLAS
+     30 | SALES      | CHICAGO
+(4 rows)
+```
+
+This example uses the `SELECT DISTINCT ...ORDER BY` clause to fetch the `job` and `deptno` from table `emp`:
+
+```sql
+CREATE TABLE EMP(EMPNO NUMBER(4) NOT NULL,
+ENAME VARCHAR2(10),
+JOB VARCHAR2(9),
+DEPTNO NUMBER(2));
+```
+
+```sql
+INSERT INTO EMP VALUES (7369, 'SMITH', 'CLERK', 20);
+INSERT 0 1
+INSERT INTO EMP VALUES (7499, 'ALLEN', 'SALESMAN', 30);
+INSERT 0 1
+INSERT INTO EMP VALUES (7521, 'WARD', 'SALESMAN', 30);
+INSERT 0 1
+INSERT INTO EMP VALUES (7566, 'JONES', 'MANAGER', 20);
+INSERT 0 1
+```
+
+```sql
+SELECT DISTINCT e.job, e.deptno FROM emp e ORDER BY e.job, e.deptno;
+__OUTPUT__
+ job      | deptno
+----------+--------
+ CLERK    |     20
+ MANAGER  |     20
+ SALESMAN |     30
+(3 rows)
+```
+
+## DISTINCT | UNIQUE clause
+
+If a `SELECT` statement specifies `DISTINCT` or `UNIQUE`, all duplicate rows are removed from the result set. One row is kept from each group of duplicates. The `DISTINCT` or `UNIQUE` clauses are synonymous when used with a `SELECT` statement. The `ALL` keyword specifies the opposite, which is that all rows are kept (the default).
+
+Error messages resulting from the improper use of a `SELECT` statement that includes the `DISTINCT` or `UNIQUE` keywords include both the `DISTINCT | UNIQUE` keywords:
+
+```sql
+psql: ERROR: FOR UPDATE is not allowed with DISTINCT/UNIQUE clause
+```
+
+## FOR UPDATE clause
+
+The `FOR UPDATE` clause takes the form:
+
+```sql
+FOR UPDATE [WAIT n|NOWAIT|SKIP LOCKED]
+```
+
+`FOR UPDATE` causes the rows retrieved by the `SELECT` statement to be locked as though for update. This prevents a row from being modified or deleted by other transactions until the current transaction ends. Any transaction that attempts to `UPDATE`, `DELETE`, or `SELECT FOR UPDATE` a selected row is blocked until the current transaction ends. If an `UPDATE`, `DELETE`, or `SELECT FOR UPDATE` from another transaction has already locked a selected row or rows, `SELECT FOR UPDATE` waits for the first transaction to complete. It then locks and returns the updated row, or it returns no row if the row was deleted.
+
+You can't use `FOR UPDATE` in contexts where you can't clearly identify returned rows with individual table rows, for example, with aggregation.
+
+Use `FOR UPDATE` options to specify locking preferences:
+
+-   Include the `WAIT n` keywords to specify the number of seconds or fractional seconds for the `SELECT` statement to wait for a row locked by another session. Use a decimal form to specify fractional seconds. For example, `WAIT 1.5` waits one and a half seconds. Specify up to four digits to the right of the decimal.
+-   Include the `NOWAIT` keyword to report an error immediately if the current session can't lock a row.
+-   Include `SKIP LOCKED` to lock rows, if possible, and skip rows that are already locked by another session.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/72_set_constraints.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/72_set_constraints.mdx
new file mode 100644
index 00000000000..09cb7998a6b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/72_set_constraints.mdx
@@ -0,0 +1,37 @@
+---
+title: "SET CONSTRAINTS"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.089.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.115.html"
+redirects:
+  - /epas/latest/epas_compat_sql/72_set_constraints/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="set_constraints" class="registered_link"></div>
+
+## Name
+
+`SET CONSTRAINTS` &mdash; Set constraint-checking modes for the current transaction.
+
+## Synopsis
+
+```sql
+SET CONSTRAINTS { ALL | name [, ...] } { DEFERRED | IMMEDIATE }
+```
+
+## Description
+
+`SET CONSTRAINTS` sets the behavior of constraint checking in the current transaction. `IMMEDIATE` constraints are checked at the end of each statement. `DEFERRED` constraints are checked when the transaction commits. Each constraint has its own `IMMEDIATE` or `DEFERRED` mode.
+
+When you create a constraint, you give it one of three characteristics: `DEFERRABLE INITIALLY DEFERRED`, `DEFERRABLE INITIALLY IMMEDIATE`, or `NOT DEFERRABLE`. The third class is always `IMMEDIATE` and isn't affected by the `SET CONSTRAINTS` command. The first two classes start every transaction in the indicated mode, but you can change their behavior in a transaction by using `SET CONSTRAINTS`.
+
+`SET CONSTRAINTS` with a list of constraint names changes the mode of just those constraints. Those constraints must all be deferrable. If multiple constraints match any given name, all are affected. `SET CONSTRAINTS ALL` changes the mode of all deferrable constraints.
+
+When `SET CONSTRAINTS` changes the mode of a constraint from `DEFERRED` to `IMMEDIATE`, the new mode takes effect retroactively. Any outstanding data modifications that normally are checked at the end of the transaction are instead checked while `SET CONSTRAINTS` executes. If any such constraint is violated, the `SET CONSTRAINTS` fails and doesn't change the constraint mode. Thus, you can use `SET CONSTRAINTS` to force constraint checking to occur at a specific point in a transaction.
+
+Currently, only foreign key constraints are affected by this setting. Check and unique constraints are never deferrable.
+
+## Notes
+
+This command alters only the behavior of constraints in the current transaction. If you execute this command outside of a transaction block, it doesn't have any effect.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/73_set_role.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/73_set_role.mdx
new file mode 100644
index 00000000000..09bff72b456
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/73_set_role.mdx
@@ -0,0 +1,43 @@
+---
+title: "SET ROLE"
+redirects:
+  - /epas/latest/epas_compat_sql/73_set_role/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="set_role" class="registered_link"></div>
+
+## Name
+
+`SET ROLE` &mdash; Set the current user identifier of the current session.
+
+## Synopsis
+
+```sql
+SET ROLE { rolename | NONE }
+```
+
+## Description
+
+This command sets the current user identifier of the current SQL session context to `<rolename>`. After `SET ROLE`, permissions checking for SQL commands is carried out as though the named role is the one that logged in originally.
+
+The specified role name must be a role that the current session user is a member of. A superuser can select any role.
+
+`NONE` resets the current user identifier to the current session user identifier. Any user can execute these forms.
+
+## Notes
+
+You can use this command to add or restrict privileges. If the session user role has the `INHERITS` attribute, then it automatically has all the privileges of every role that it can set the role to. In this case, `SET ROLE` drops all the privileges assigned directly to the session user and to the other roles it is a member of, which leaves only the privileges available to the named role. If the session user role has the `NOINHERITS` attribute, `SET ROLE` drops the privileges assigned directly to the session user and instead acquires the privileges available to the named role. When a superuser chooses to set a role to a non-superuser role, they lose their superuser privileges.
+
+## Examples
+
+User `mary` takes on the identity of role `admins`:
+
+```sql
+SET ROLE admins;
+```
+
+User `mary` reverts back to their own identity:
+
+```sql
+SET ROLE NONE;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/74_set_transaction.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/74_set_transaction.mdx
new file mode 100644
index 00000000000..6529e0031c0
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/74_set_transaction.mdx
@@ -0,0 +1,51 @@
+---
+title: "SET TRANSACTION"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.091.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.117.html"
+redirects:
+  - /epas/latest/epas_compat_sql/74_set_transaction/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="set_transaction" class="registered_link"></div>
+
+## Name
+
+`SET TRANSACTION` &mdash; Set the characteristics of the current transaction.
+
+## Synopsis
+
+```sql
+SET TRANSACTION transaction_mode
+```
+
+Where `transaction_mode` is one of:
+
+```sql
+ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
+READ WRITE | READ ONLY
+```
+
+## Description
+
+The `SET TRANSACTION` command sets the characteristics of the current transaction. It has no effect on any later transactions. The available transaction characteristics are the transaction isolation level and the transaction access mode (read/write or read-only). The isolation level of a transaction determines the data the transaction can see when other transactions are running concurrently.
+
+`READ COMMITTED`
+
+ A statement can see only rows committed before it began. This is the default.
+
+`SERIALIZABLE`
+
+ All statements of the current transaction can see only rows committed before the first query or data-modification statement was executed in this transaction.
+
+You can't change the transaction isolation level after the first query or data-modification statement (`SELECT`, `INSERT`, `DELETE`, `UPDATE`, or `FETCH`) of a transaction is executed. The transaction access mode determines whether the transaction is read/write or read-only. Read/write is the default.
+
+When a transaction is read-only, the following SQL commands aren't allowed: 
+
+-  `INSERT`, `UPDATE`, and `DELETE` if the table they write to isn't a temporary table
+-  All `CREATE`, `ALTER`, and `DROP` commands
+-  `COMMENT`, `GRANT`, `REVOKE`, `TRUNCATE`
+-  `EXECUTE` if the command it executes is among those listed. 
+
+This is a high-level notion of read-only that doesn't prevent all writes to disk.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/75_truncate.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/75_truncate.mdx
new file mode 100644
index 00000000000..153bf12dcba
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/75_truncate.mdx
@@ -0,0 +1,51 @@
+---
+title: "TRUNCATE"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.092.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.118.html"
+redirects:
+  - /epas/latest/epas_compat_sql/75_truncate/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="truncate" class="registered_link"></div>
+
+## Name
+
+`TRUNCATE` &mdash; Empty a table.
+
+## Synopsis
+
+```sql
+TRUNCATE TABLE <name> [DROP STORAGE]
+```
+
+## Description
+
+`TRUNCATE` removes all rows from a table. It has the same effect as an unqualified `DELETE`. However, since it doesn't scan the table, it's faster. `TRUNCATE` is most useful on large tables.
+
+The `DROP STORAGE` clause is accepted for compatibility but is ignored.
+
+## Parameters
+
+`name`
+
+ The name (optionally schema-qualified) of the table to truncate.
+
+## Notes
+
+You can't use `TRUNCATE` if there are foreign-key references to the table from other tables. Checking validity in such cases requires table scans, which `TRUNCATE` aims to avoid.
+
+`TRUNCATE` doesn't run any user-defined `ON DELETE` triggers for the table.
+
+## Examples
+
+This command truncates a table named `accounts`:
+
+```sql
+TRUNCATE TABLE accounts;
+```
+
+## See also
+
+[DROP VIEW](62_drop_view/#drop_view), [DELETE](44_delete/#delete)
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/76_update.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/76_update.mdx
new file mode 100644
index 00000000000..e8e3767e5ff
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/76_update.mdx
@@ -0,0 +1,131 @@
+---
+title: "UPDATE"
+redirects:
+  - /epas/latest/epas_compat_sql/76_update/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+## Name
+
+`UPDATE` &mdash; Update rows of a table.
+
+## Synopsis
+
+```sql
+edb=# \h UPDATE 
+Command:     UPDATE
+Description: update rows of a table
+Syntax:
+[ WITH [ RECURSIVE ] with_query [, ...] ]
+UPDATE [ <optimizer_hint> ][ ONLY ] <table_name>[@<dblink> ] [ * ] [ [ AS ] alias ]
+    SET { { <column_name> = { <expression> | DEFAULT } |
+            ( <column_name> [, ...] ) = [ ROW ] ( { expression | DEFAULT } [, ...] ) |
+            ( <column_name> [, ...] ) = ( sub-SELECT )
+          } [, ...] |
+          ROW = <row_or_record_var>
+        }
+    [ FROM <from_item> [, ...] ]
+    [ WHERE <condition> | WHERE CURRENT OF <cursor_name> ]
+    [ RETURNING <return_expression> [, ...]
+      { INTO { <record> | <variable> [, ...] }
+      | BULK COLLECT INTO <collection> [, ...] } ]
+
+URL: https://www.postgresql.org/docs/15/sql-update.html
+     https://www.enterprisedb.com/docs
+```
+
+## Description
+
+`UPDATE` changes the values of the specified columns in all rows that satisfy the condition. You need to mention only the columns you want to modify in the `SET` clause. Columns not explicitly modified retain their values.
+
+`SET ROW` enables us to update a target record using a record type variable or row type objects. The record or row used, must have compatible data types with the table's columns in order.
+
+You can specify the `RETURNING INTO { record | variable [, ...] }` clause only in an SPL program. In addition, the result set of the `UPDATE` command must not return more than one row. Otherwise an exception is thrown. If the result set is empty, then the contents of the target record or variables are set to null.
+
+In an SPL program, you can specify the `RETURNING BULK COLLECT INTO collection [, ...]` clause only if you use the `UPDATE` command. If you specify more than one collection as the target of the `BULK COLLECT INTO` clause, then each collection must consist of a single scalar field. That is, `collection` can't be a record. The result set of the `UPDATE` command can contain zero or more rows. `return_expression` evaluated for each row of the result set becomes an element in `collection` starting with the first element. Any existing rows in `collection` are deleted. If the result set is empty, then `collection` is empty.
+
+You need the `UPDATE` privilege on the table to update it. You also need the `SELECT` privilege to any table whose values are read in `expression` or `condition`.
+
+## Parameters
+
+`optimizer_hint`
+
+ Comment-embedded hints to the optimizer for selecting an execution plan.
+
+`table`
+
+ The name (optionally schema-qualified) of the table to update.
+
+`dblink`
+
+ Database link name identifying a remote database. See the [`CREATE DATABASE LINK` command](21_create_public_database_link#create_public_database_link) for information on database links.
+
+`column`
+
+ The name of a column in the table.
+
+`expression`
+
+ An expression to assign to the column. The expression can use the old values of this and other columns in the table.
+
+`DEFAULT`
+
+ Set the column to its default value, which is null if you don't assign a default expression to it.
+
+`condition`
+
+ An expression that returns a value of type `BOOLEAN`. Update only rows for which this expression returns true.
+
+`return_expression`
+
+ An expression that can include one or more columns from the table. If a column name from the table is specified in `return_expression`, the value substituted for the column when `return_expression` is evaluated is determined as follows:
+
+-   If the column specified in `return_expression` is assigned a value in the `UPDATE` command, then the assigned value is used when evaluating `return_expression`.
+
+-   If the column specified in `return_expression` isn't assigned a value in the `UPDATE` command, then the column’s current value in the affected row is used when evaluating `return_expression`.
+
+`record`
+
+ A record whose field to assign the evaluated `return_expression`. The first `return_expression` is assigned to the first field in `record`, the second `return_expression` is assigned to the second field in `record`, and so on. The number of fields in `record` must exactly match the number of expressions, and the fields must be type-compatible with their assigned expressions.
+
+`variable`
+
+ A variable to which to assign the evaluated `return_expression`. If more than one `return_expression` and `variable` are specified, the first `return_expression` is assigned to the first `variable`, the second `return_expression` is assigned to the second `variable`, and so on. The number of variables specified following the `INTO` keyword must exactly match the number of expressions following the `RETURNING` keyword, and the variables must be type-compatible with their assigned expressions.
+
+`collection`
+
+ A collection in which an element is created from the evaluated `return_expression`. There can be either:
+ 
+ -  A single collection, which can be a collection of a single field or a collection of a record type
+ -  More than one collection, in which case each collection must consist of a single field 
+ 
+ The number of return expressions must match in number and order the number of fields in all specified collections. Each corresponding `return_expression` and `collection` field must be type-compatible.
+
+## Examples
+
+Change the location to `AUSTIN` for department `20` in the `dept` table:
+
+```sql
+UPDATE dept SET loc = 'AUSTIN' WHERE deptno = 20;
+```
+
+For all employees with `job = SALESMAN` in the `emp` table, update the salary by 10%, and increase the commission by 500:
+
+```sql
+UPDATE emp SET sal = sal * 1.1, comm = comm + 500 WHERE job = 'SALESMAN';
+```
+
+
+`SET ROW` example:
+
+```sql
+CREATE TABLE db1425_t1(a INT, b INT);
+INSERT INTO db1425_t1 VALUES(1,2);
+
+DECLARE   
+	TYPE rec IS RECORD (x INT, y INT);
+    	rec_var rec;    
+BEGIN    
+	rec_var = row(1000, 1000);
+	UPDATE db1425_t1 SET ROW=rec_var WHERE a = 1;   
+END;
+```
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/index.mdx
new file mode 100644
index 00000000000..6422268c5f3
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/epas_compat_sql/index.mdx
@@ -0,0 +1,16 @@
+---
+navTitle: Oracle-compatible SQL commands
+title: "Compatible SQL commands"
+indexCards: simple
+description: "Listing of SQL commands compatible with Oracle databases"
+redirects:
+  - /epas/latest/epas_compat_sql/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server supports many SQL commands compatible with Oracle databases. These SQL commands work on both an Oracle database and an EDB Postgres Advanced Server database.
+
+EDB Postgres Advanced Server supports additional commands not described here. These commands might not have an Oracle equivalent, or they might provide the similar or same functionality as an Oracle SQL command but with different syntax.
+
+The SQL commands that follow don't necessarily represent the full syntax, options, and functionality available for each command. In most cases, syntax, options, and functionality that aren't compatible with Oracle databases aren't included in the command description and syntax.
+
+Command functionality that isn't compatible with Oracle databases is noted.
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/index.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/index.mdx
new file mode 100644
index 00000000000..ca2f94ba8fe
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/index.mdx
@@ -0,0 +1,7 @@
+---
+title: "Oracle compatibility reference"
+indexCards: simple
+description: "Contains reference information applicable to organizations migrating their Oracle applications to use EDB Postgres Advanced Server"
+---
+
+This reference information applies to organizations migrating their Oracle applications to use EDB Postgres Advanced Server.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/oracle_compatibility_reference/summary_oracle_config_parameters.mdx b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/summary_oracle_config_parameters.mdx
new file mode 100644
index 00000000000..aad629cb82e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/oracle_compatibility_reference/summary_oracle_config_parameters.mdx
@@ -0,0 +1,14 @@
+---
+title: "List of Oracle compatible configuration parameters"
+description: "Descriptions of the configuration parameters used to control system behaviors to act more like PostgreSQL or more like Oracle"
+---
+
+EDB Postgres Advanced Server supports developing and running applications compatible with PostgreSQL and Oracle. You can alter some system behaviors to act in a more PostgreSQL- or in a more Oracle-compliant manner. You control these behaviors by using configuration parameters. 
+
+-   `edb_redwood_date` &mdash; Controls whether or not a time component is stored in `DATE` columns. For behavior compatible with Oracle databases, set `edb_redwood_date` to `TRUE`. 
+-   `edb_redwood_raw_names` &mdash; Controls whether database object names appear in uppercase or lowercase letters when viewed from Oracle system catalogs. For behavior compatible with Oracle databases, `edb_redwood_raw_names` is set to its default value of `FALSE`. To view database object names as they are actually stored in the PostgreSQL system catalogs, set `edb_redwood_raw_names` to `TRUE`. 
+-   `edb_redwood_strings` &mdash; Equates `NULL` to an empty string for purposes of string concatenation operations. For behavior compatible with Oracle databases, set `edb_redwood_strings` to `TRUE`. 
+-   `edb_stmt_level_tx` &mdash; Isolates automatic rollback of an aborted SQL command to statement level rollback only – the entire, current transaction is not automatically rolled back as is the case for default PostgreSQL behavior. For behavior compatible with Oracle databases, set `edb_stmt_level_tx` to `TRUE`; however, use only when absolutely necessary. 
+-   `oracle_home` &mdash; Point EDB Postgres Advanced Server to the correct Oracle installation directory. 
+
+See [Configuration parameters compatible with Oracle databases](../database_administrator_reference/01_introduction/) for access to more detailed information.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx
new file mode 100644
index 00000000000..e40a474410f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/01_lexical_structure.mdx
@@ -0,0 +1,35 @@
+---
+title: "Lexical structure"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.007.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.039.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/01_sql_syntax/01_lexical_structure/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="lexical_structure" class="registered_link"></div>
+
+The lexical structure of SQL has several aspects:
+
+- SQL input consists of a sequence of commands. 
+
+- A command is composed of a sequence of tokens, terminated by a semicolon (;). The end of the input stream also terminates a command. 
+
+- The valid tokens depend on the syntax of the command.
+
+- A token can be a key word, an identifier, a quoted identifier, a literal or constant, or a special character symbol. Tokens are normally separated by whitespace (space, tab, new line) but don't need to be if there's no ambiguity. This is generally the case only if a special character is adjacent to some other token type.
+
+- Comments can occur in SQL input. They aren't tokens. They are equivalent to whitespace.
+
+For example, the following is syntactically valid SQL input:
+
+```sql
+SELECT * FROM MY_TABLE;
+UPDATE MY_TABLE SET A = 5;
+INSERT INTO MY_TABLE VALUES (3, 'hi there');
+```
+
+This is a sequence of three commands, one per line, although that format isn't required. You can enter more than one command on a line, and commands can usually split across lines.
+
+The SQL syntax isn't very consistent regarding the tokens that identify commands and the ones that are operands or parameters. The first few tokens are generally the command name, so the example contains a `SELECT`, an `UPDATE`, and an `INSERT` command. But, for instance, the `UPDATE` command always requires a `SET` token to appear in a certain position, and this variation of `INSERT` also requires a `VALUES` token to be complete. The precise syntax rules for each command are described in [SQL reference](../../oracle_compatibility_reference/epas_compat_sql/).
diff --git a/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/02_identifiers_and_key_words.mdx b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/02_identifiers_and_key_words.mdx
new file mode 100644
index 00000000000..2465e345378
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/02_identifiers_and_key_words.mdx
@@ -0,0 +1,45 @@
+---
+title: "Identifiers and key words"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.008.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.040.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/01_sql_syntax/02_identifiers_and_key_words/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="identifiers_and_key_words" class="registered_link"></div>
+
+Tokens such as `SELECT`, `UPDATE`, or `VALUES` are examples of *key words*, that is, words that have a fixed meaning in the SQL language. The tokens `MY_TABLE` and `A` are examples of *identifiers*. They identify names of tables, columns, or other database objects, depending on the command you use them in. Therefore, they're sometimes called *names*. Key words and identifiers have the same *lexical structure*, meaning that you can't know whether a token is an identifier or a key word without knowing the language.
+
+SQL identifiers and key words must begin with a letter (`a-z` or `A-Z`). Subsequent characters in an identifier or key word can be letters, underscores, digits (`0-9`), dollar signs (`$`), or the number sign (`#`).
+
+Identifier and key word names aren't case sensitive. Therefore these two commands are equivalent:
+
+```sql
+UPDATE MY_TABLE SET A = 5;
+```
+
+The equivalent command is:
+
+```sql
+uPDaTE my_TabLE SeT a = 5;
+```
+
+A convention often used is to write key words in upper case and names in lower case, for example:
+
+```sql
+UPDATE my_table SET a = 5;
+```
+
+A second kind of identifier is the *delimited identifier* or *quoted identifier*. It's formed by enclosing an arbitrary sequence of characters in double quotes ("). A delimited identifier is always an identifier, never a key word. So you can use `"select"` to refer to a column or table named `"select"`. An unquoted `select` is taken as a key word and therefore provokes a parse error when used where a table or column name is expected. The example can be written with quoted identifiers like this:
+
+```sql
+UPDATE "my_table" SET "a" = 5;
+```
+
+Quoted identifiers can contain any character except the character with the numeric code zero.
+
+To include a double quote, use two double quotes. This allows you to construct table or column names that are otherwise not possible (such as ones containing spaces or ampersands). The length limitation still applies.
+
+Quoting an identifier also makes it case sensitive, whereas unquoted names are always folded to lower case. For example, the identifiers `FOO`, `foo`, and `"foo"` are considered the same by EDB Postgres Advanced Server, but `"Foo"` and `"FOO"` are different from these three and each other. The folding of unquoted names to lower case isn't compatible with Oracle databases. In Oracle syntax, unquoted names are folded to upper case. For example, `foo` is equivalent to `"FOO"` and not `"foo"`. If you want to write portable applications, either always quote a particular name or never quote it.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/03_constants.mdx b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/03_constants.mdx
new file mode 100644
index 00000000000..25af98b23c7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/03_constants.mdx
@@ -0,0 +1,116 @@
+---
+title: "Constants"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.009.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/01_sql_syntax/03_constants/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="constants" class="registered_link"></div>
+
+The kinds of implicitly typed constants in EDB Postgres Advanced Server are *strings* and *numbers*. You can also specify constants with explicit types, which can enable more accurate representation and more efficient handling by the system. 
+
+## String constants
+
+A *string constant* in SQL is an arbitrary sequence of characters bounded by single quotes `(')`, for example `'This is a string'`. To include a single-quote character in a string constant, include two adjacent single quotes, for example, `'Dianne''s horse'`. (The two single quotes diffe from a double-quote character `(")`.)
+
+## Numeric constants
+
+Numeric constants are accepted in these general forms:
+
+```sql
+digits
+digits.[digits][e[+-]digits]
+[digits].digits[e[+-]digits]
+digitse[+-]digits
+```
+
+Where `digits` is one or more decimal digits (0 through 9). You must enter at least one digit before or after the decimal point, if one is used. At least one digit must follow the exponent marker `(e)`, if one is present. Don't embed any spaces or other characters in the constant. Leading plus or minus signs aren't considered part of the constant. They are operators applied to the constant.
+
+These are some examples of valid numeric constants:
+
+```sql
+42
+3.5
+4.
+.001
+5e2
+1.925e-3
+```
+
+A numeric constant that doesn't contain a decimal point or an exponent is initially presumed to be type `INTEGER` if its value fits in type `INTEGER` (32 bits). Otherwise it's presumed to be type `BIGINT` if its value fits in type `BIGINT` (64 bits). If its value then doesn't fit in type `BIGINT`, it's taken to be type `NUMBER`. Constants that contain decimal points or exponents are always initially presumed to be type `NUMBER`.
+
+The initially assigned data type of a numeric constant is just a starting point for the type resolution algorithms. In most cases the constant is automatically coerced to the most appropriate type depending on context. When necessary, you can force a numeric value to be interpreted as a specific data type by casting it as described in [Constants of other types](#constants-of-other-types).
+
+## Constants of other types
+
+### CAST
+
+You can enter a constant of an arbitrary type using the following notation:
+
+```sql
+CAST('string' AS type)
+```
+
+The string constant’s text is passed to the input conversion routine for the type called `type`. The result is a constant of the indicated type. You can omit the explicit type cast if there's no ambiguity as to the type of constant (for example, when it's assigned directly to a table column), in which case it's automatically coerced.
+
+You can also use `CAST` to specify runtime type conversions of arbitrary expressions.
+
+### CAST (MULTISET)
+
+`MULTISET` is an extension to `CAST` that converts subquery results into a nested table type. The synopsis is:
+
+```sql
+CAST ( MULTISET ( < subquery > ) AS < datatype > )
+```
+
+Where `subquery` is a query returning one or more rows, and `datatype` is a nested table type.
+
+`CAST(MULTISET)` is used to store a collection of data in a table.
+
+## Example
+
+This example uses `MULTISET`:
+
+```sql
+edb=# CREATE OR REPLACE TYPE project_table_t AS TABLE OF VARCHAR2(25);
+CREATE TYPE
+edb=# CREATE TABLE projects (person_id NUMBER(10), project_name VARCHAR2(20));
+CREATE TABLE
+edb=# CREATE TABLE pers_short (person_id NUMBER(10), last_name VARCHAR2(25));
+CREATE TABLE
+```
+
+```sql
+edb=# INSERT INTO projects VALUES (1, 'Teach');
+INSERT 0 1
+edb=# INSERT INTO projects VALUES (1, 'Code');
+INSERT 0 1
+edb=# INSERT INTO projects VALUES (2, 'Code');
+INSERT 0 1
+edb=# INSERT INTO pers_short VALUES (1, 'Morgan');
+INSERT 0 1
+edb=# INSERT INTO pers_short VALUES (2, 'Kolk');
+INSERT 0 1
+edb=# INSERT INTO pers_short VALUES (3, 'Scott');
+INSERT 0 1
+edb=# COMMIT;
+COMMIT
+```
+
+```sql
+edb=# SELECT e.last_name, CAST(MULTISET(
+edb(#   SELECT p.project_name
+edb(#   FROM projects p
+edb(#   WHERE p.person_id = e.person_id
+edb(#   ORDER BY p.project_name) AS project_table_t)
+edb-# FROM pers_short e;
+__OUTPUT__
+ last_name | project_table_t
+-----------+-----------------
+ Morgan    | {Code,Teach}
+ Kolk      | {Code}
+ Scott     | {}
+(3 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/04_comments.mdx b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/04_comments.mdx
new file mode 100644
index 00000000000..ff0331095f2
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/04_comments.mdx
@@ -0,0 +1,25 @@
+---
+title: "Comments"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.010.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.042.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/01_sql_syntax/04_comments/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="comments" class="registered_link"></div>
+
+A comment is an arbitrary sequence of characters beginning with double dashes and extending to the end of the line, for example:
+
+`-- This is a standard SQL comment`
+
+Alternatively, you can use C-style block comments:
+
+```sql
+/* multiline comment
+* block
+*/
+```
+
+The comment begins with /\* and extends to the matching occurrence of \*/.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/index.mdx b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/index.mdx
new file mode 100644
index 00000000000..5857290c9fc
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/01_sql_syntax/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "SQL syntax"
+indexCards: simple
+description: "Provides basic information about the general syntax"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.006.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.038.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/01_sql_syntax/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/01_sql_syntax
+---
+
+<div id="sql_syntax" class="registered_link"></div>
+
+Understanding the general syntax of SQL forms the foundation for understanding how to apply the SQL commands to define and modify data.
+
+<div class="toctree" maxdepth="3">
+
+lexical_structure identifiers_and_key_words constants comments
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/01_numeric_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/01_numeric_types.mdx
new file mode 100644
index 00000000000..2bdd2fbde95
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/01_numeric_types.mdx
@@ -0,0 +1,167 @@
+---
+title: "Numeric types"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.012.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.044.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/01_numeric_types/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-numeric.html
+   timestamp: 2023-08-30
+---
+
+<div id="numeric_types" class="registered_link"></div>
+
+|      Data type      | Native | Alias |                                                                                                             Description                                                                                                             |
+| ------------------- | ------ | ----- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `SMALLINT`          | ✅      |       | Small-range integer, 2 bytes storage, -32768 to +32767 range                                                                                                                                                                        |
+| `INTEGER`           | ✅      |       | Usual choice for integer, 4 bytes storage, -2147483648 to +2147483647 range                                                                                                                                                         |
+| `BINARY_INTEGER`    |        | ✅     | Alias for `INTEGER`                                                                                                                                                                                                                 |
+| `BIGINT`            | ✅      |       | Large-range integer, 8 bytes storage, 	-9223372036854775808 to +9223372036854775807 range |                                                                                                                                                                                                                                     |
+| `PLS_INTEGER`       |        | ✅     | Alias for `INTEGER`                                                                                                                                                                                                                 |
+| `DECIMAL`           | ✅      |       | User-specified precision, exact; variable storage;	up to 131072 digits before the decimal point up to 16383 digits after the decimal point range                                                                                     |
+| `NUMERIC`           | ✅      |       | User-specified precision, exact; variable storage, up to 131072 digits before the decimal point; up to 16383 digits after the decimal point range                                                                                   |
+| `NUMBER`            |        | ✅     | Alias for native numeric                                                                                                                                                                                                            |
+| `NUMBER(p [, s ] )` |        | ✅     | Alias of native numeric with exact numeric of maximum precision, `p`, and optional scale, `s`; variable storage, p to 1000 digits of precision                                                                                      |
+| `REAL`              | ✅      |       | Variable-precision, inexact; 4 bytes	storage;	6 decimal digits precision range                                                                                                                                                        |
+| `DOUBLE PRECISION`  | ✅      |       | Variable-precision, inexact; 8 bytes storage; 15 decimal digits precision range                                                                                                                                                     |
+| `BINARY FLOAT`      |        | ✅     | Alias for native `DOUBLE PRECISION`                                                                                                                                                                                                 |
+| `SMALLSERIAL`       | ✅      |       | Small autoincrementing integer,  2 bytes storage,	1 to 32767 range                                                                                                                                                                   |
+| `SERIAL`            | ✅      |       | Autoincrementing integer, 4 bytes	storage,	1 to 2147483647 range                                                                                                                                                                      |
+| `BIGSERIAL`         | ✅      |       | Large autoincrementing integer, 8 bytes	storage,	1 to 9223372036854775807 range                                                                                                                                                       |
+| `ROWID`             |        |       | Custom type for emulating Oracle ROWID, signed 8 bit integer; 8 bytes storage; -9223372036854775808 to 9223372036854775807 range (see [Migration Handbook](/migrating/oracle/oracle_epas_comparison/database_features/#data-types)) |
+
+## Overview 
+
+Numeric types consist of four-byte integers, four-byte and eight-byte floating-point numbers, and fixed-precision decimals. 
+
+The syntax of constants for the numeric types is described in [Constants](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS) in the PostgreSQL documentation. The numeric types have a full set of corresponding arithmetic operators and functions. Refer to [Functions and Operators](../03_functions_and_operators) for more information. The following sections describe the types in detail.
+
+## Integer types
+
+The `BIGINT`, `BINARY_INTEGER`, `INTEGER`, `PLS_INTEGER`, `SMALLINT` and `ROWID` types store whole numbers (without fractional components) as specified in the numeric types table. Attempts to store values outside of the allowed range result in an error.
+
+The type `INTEGER` is the common choice, as it offers the best balance between range, storage size, and performance. The `SMALLINT` type is generally only used if disk space is at a premium. The `BIGINT` type is designed to be used when the range of the `INTEGER` type is insufficient.
+
+## Arbitrary precision numbers
+
+The type `NUMBER` can store an almost unlimited number of digits of precision and perform calculations exactly. We especially recommend it for storing monetary amounts and other quantities where exactness is required. However, the `NUMBER` type is very slow compared to the floating-point types described in [Floating point types](#floating-point-types).
+
+The `scale` of a `NUMBER` is the count of decimal digits in the fractional part, to the right of the decimal point. The `precision` of a `NUMBER` is the total count of significant digits in the whole number, that is, the number of digits to both sides of the decimal point. So the number 23.5141 has a precision of 6 and a scale of 4. Integers have a scale of zero.
+
+You can configure both the precision and the scale of the `NUMBER` type. To declare a column of type `NUMBER`, use the syntax:
+
+```sql
+NUMBER(precision, scale)
+```
+
+The precision must be positive, and the scale must be zero or positive. Alternatively, this syntax selects a scale of 0:
+
+```sql
+NUMBER(precision)
+```
+
+Specifying `NUMBER` without any precision or scale creates a column in which you can store numeric values of any precision and scale, up to the implementation limit on precision. A column of this kind doesn't coerce input values to any particular scale, whereas `NUMBER` columns with a declared scale coerce input values to that scale. (The SQL standard requires a default scale of 0, that is, coercion to integer precision. For maximum portability, it's best to specify the precision and scale explicitly.)
+
+If the precision or scale of a value is greater than the declared precision or scale of a column, the system attempts to round the value. If the value can't be rounded to satisfy the declared limits, an error occurs.
+
+Numeric values are physically stored without any extra leading or trailing zeroes. Thus, the declared precision and scale of a column are maximums, not fixed allocations. (In this sense the `NUMBER` type is more akin to `VARCHAR(N)` than to `CHAR(N)`.) The actual storage requirement is two bytes for each group of four decimal digits, plus three to eight bytes overhead.
+
+In addition to ordinary numeric values, the `NUMBER` type allows the special value NaN, meaning “not-a-number”. Any operation on NaN yields another NaN. When writing this value as a constant in an SQL command, you must put quotes around it, for example U`PDATE table SET x = 'NaN'`. On input, the string `NaN` is recognized in a case-insensitive manner.
+
+!!!Note
+In most implementations of the “not-a-number” concept, `NaN` is not considered equal to any other numeric value (including `NaN`). In order to allow numeric values to be sorted and used in tree-based indexes, PostgreS treats `NaN` values as equal, and greater than all non-`NaN` values.
+!!!
+
+The types `DECIMAL` and `NUMBER` are equivalent. Both types are part of the SQL standard.
+
+When rounding values, the `NUMBER` type rounds ties away from zero, while (on most machines) the `REAL` and `DOUBLE PRECISION` types round ties to the nearest even number. For example:
+
+```SQL
+SELECT x,
+  round(x::numeric) AS num_round,
+  round(x::double precision) AS dbl_round
+FROM generate_series(-3.5, 3.5, 1) as x;
+  x   | num_round | dbl_round
+------+-----------+-----------
+ -3.5 |        -4 |        -4
+ -2.5 |        -3 |        -2
+ -1.5 |        -2 |        -2
+ -0.5 |        -1 |        -0
+  0.5 |         1 |         0
+  1.5 |         2 |         2
+  2.5 |         3 |         2
+  3.5 |         4 |         4
+(8 rows)
+```
+
+## Floating-point types
+
+The data types `REAL` and `DOUBLE PRECISION` are *inexact*, variable-precision numeric types. In practice, these types are usually implementations of IEEE Standard 754 for Binary Floating-Point Arithmetic (single and double precision, respectively), to the extent that the underlying processor, operating system, and compiler support it.
+
+Inexact means that some values can't be converted exactly to the internal format and are stored as approximations, so that storing and printing back out a value might show slight discrepancies. Managing these errors and how they propagate through calculations is the subject of an entire branch of mathematics and computer science and isn't discussed further here, except for the following points:
+
+-  If you require exact storage and calculations (such as for monetary amounts), use the `NUMBER` type instead.
+
+-  If you want to do complicated calculations with these types for anything important, especially if you rely on certain behavior in boundary cases (infinity, underflow), evaluate the implementation carefully.
+
+-  Comparing two floating-point values for equality might not work as expected.
+
+On most platforms, the `REAL` type has a range of at least `1E-37` to `1E+37` with a precision of at least six decimal digits. The `DOUBLE PRECISION` type typically has a range of around `1E-307` to `1E+308` with a precision of at least 15 digits. Values that are too large or too small cause an error. Rounding might occur if the precision of an input number is too high. Numbers too close to zero that you can't represent as distinct from zero cause an underflow error.
+
+In addition to ordinary numeric values, the floating-point types have several special values:
+
+
+- `Infinity`
+- `-Infinity`
+- `NaN`
+
+These represent the IEEE 754 special values “infinity”, “negative infinity”, and “not-a-number”, respectively. (On a machine whose floating-point arithmetic does not follow IEEE 754, these values will probably not work as expected.) When writing these values as constants in an SQL command, you must put quotes around them, for example `UPDATE table SET x = '-Infinity'`. On input, these strings are recognized in a case-insensitive manner.
+
+!!!Note
+IEEE754 specifies that NaN should not compare equal to any other floating-point value (including `NaN`). In order to allow floating-point values to be sorted and used in tree-based indexes, Postgres treats `NaN` values as equal, and greater than all non-`NaN` values.
+!!!
+
+EDB Postgres Advanced Server also supports the SQL standard notations `FLOAT` and `FLOAT(p)` for specifying inexact numeric types. Here, `p` specifies the minimum acceptable precision in binary digits. EDB Postgres Advanced Server accepts `FLOAT(1)` to `FLOAT(24)` as selecting the `REAL` type and `FLOAT(25)` to `FLOAT(53)` as selecting `DOUBLE PRECISION`. Values of `p` outside the allowed range draw an error. `FLOAT` with no precision specified is taken to mean `DOUBLE PRECISION`.
+
+
+!!!Note
+The assumption that real and double precision have exactly 24 and 53 bits in the mantissa respectively is correct for IEEE-standard floating point implementations. On non-IEEE platforms it might be off a little, but for simplicity the same ranges of `p` are used on all platforms.
+!!!
+
+## Serial types
+
+!!!Note
+This section describes a PostgreSQL-specific way to create an autoincrementing column. Another way is to use the SQL-standard identity column feature, described in [CREATE TABLE](https://www.postgresql.org/docs/11/sql-createtable.html).
+!!!
+
+The data types `SMALLSERIAL`, `SERIAL` and `BIGSERIAL` are not true types, but merely a notational convenience for creating unique identifier columns (similar to the `AUTO_INCREMENT` property supported by some other databases). In the current implementation, specifying:
+
+```sql
+CREATE TABLE tablename (
+    colname SERIAL
+);
+```
+
+is equivalent to specifying:
+
+```
+CREATE SEQUENCE tablename_colname_seq AS integer;
+CREATE TABLE tablename (
+    colname integer NOT NULL DEFAULT nextval('tablename_colname_seq')
+);
+ALTER SEQUENCE tablename_colname_seq OWNED BY tablename.colname;
+```
+
+Thus, we have created an integer column and arranged for its default values to be assigned from a sequence generator. A `NOT NULL` constraint is applied to ensure that a null value cannot be inserted. (In most cases you would also want to attach a `UNIQUE` or `PRIMARY KEY` constraint to prevent duplicate values from being inserted by accident, but this is not automatic.) Lastly, the sequence is marked as “owned by” the column, so that it will be dropped if the column or table is dropped.
+
+!!!Note
+Because `SMALLSERIAL`, `SERIAL` and `BIGSERIAL` are implemented using sequences, there may be "holes" or gaps in the sequence of values which appears in the column, even if no rows are ever deleted. A value allocated from the sequence is still "used up" even if a row containing that value is never successfully inserted into the table column. This may happen, for example, if the inserting transaction rolls back. See [`nextval()`](https://www.postgresql.org/docs/11/functions-sequence.html) for details.
+!!!
+
+To insert the next value of the sequence into the serial column, specify that the serial column should be assigned its default value. This can be done either by excluding the column from the list of columns in the INSERT statement, or through the use of the `DEFAULT` key word.
+
+The type names `SERIAL` and `SERIAL4` are equivalent: both create integer columns. The type names `BIGSERIAL` and `SERIAL8` work the same way, except that they create a bigint column. `BIGSERIAL` should be used if you anticipate the use of more than 2147483648 identifiers (2 to the 31st power)over the lifetime of the table. The type names `SMALLSERIAL` and `SERIAL2` also work the same way, except that they create a `SMALLINT` column.
+
+The sequence created for a `SERIAL` column is automatically dropped when the owning column is dropped. You can drop the sequence without dropping the column, but this will force removal of the column default expression.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/02_character_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/02_character_types.mdx
new file mode 100644
index 00000000000..0fec7533eec
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/02_character_types.mdx
@@ -0,0 +1,95 @@
+---
+title: "Character types"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/02_character_types/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-numeric.html
+   timestamp: 2023-09-07
+---
+
+<div id="character_types" class="registered_link"></div>
+
+| Name                     | Native    | Alias  | Description                                                                                           |
+| ------------------------ | --------- | ------ | ----------------------------------------------------------------------------------------------------- |
+| `CHAR[(n)]`              | ✅        |        | Fixed-length character string, blank-padded to the size specified by `n`                              |
+| `CHARACTER[(n)]`         | ✅        |        | Fixed-length character string, blank-padded to the size specified by `n`                              |
+| `CHARACTER VARYING[(n)]` | ✅        |        | Variable-length character string, with limit                                                          |
+| `CLOB`                   |           |        | Custom type for emulating Oracle CLOB, large variable-length up to 1 GB (see [Migration Handbook](/migrating/oracle/oracle_epas_comparison/database_features/#data-types))                           |
+| `LONG`                   |           | ✅     | Alias for `TEXT`                                                                                      |
+| `NCHAR[(n)]`             |           | ✅     | Alias for `CHARACTER`                                                                                 |
+| `NVARCHAR[(n)]`          |           | ✅     | Alias for `CHARACTER VARYING`                                                                         |
+| `NVARCHAR2[(n)]`         |           | ✅     | Alias for `CHARACTER VARYING`                                                                         |
+| `STRING`                 |           | ✅     | Alias for `VARCHAR2`                                                                                  |
+| `TEXT`                   | ✅        |        | Variable-length character string, unlimited                                                           |
+| `VARCHAR[(n)]`           | ✅        |        | Variable-length character string, with limit (considered deprecated, but supported for compatibility) |
+| `VARCHAR2[(n)]`          |           | ✅     | Alias for `CHARACTER VARYING`                                                                         |
+
+
+## Overview
+
+SQL defines two primary character types: `CHARACTER VARYING(n)` and `CHARACTER(n)`, where `n` is a positive integer. These types can store strings up to `n` characters in length. If you don't specify a value for `n`, `n` defaults to `1`. Assigning a value that exceeds the length of `n` results in an error unless the excess characters are all spaces. In this case, the string is truncated to the maximum length. If the string to be stored is shorter than `n`, values of type `CHARACTER` are space-padded to the specified width (`n`) and are stored and displayed that way; values of type `CHARACTER VARYING` simply store the shorter string.
+
+If you explicitly cast a value to `CHARACTER VARYING(n)` or `CHARACTER(n)`, an over-length value is truncated to n characters without raising an error.
+
+The notations `VARCHAR(n)` and `CHAR(n)` are aliases for `CHARACTER VARYING(n)` and `CHARACTER(n)`, respectively. If specified, the length must be greater than zero and cannot exceed 10485760. `CHARACTER` without a length specifier is equivalent to `CHARACTER(1)`. If `CHARACTER VARYING` is used without a length specifier, the type accepts strings of any size. The latter is a PostgreSQL extension.
+
+In addition, PostgreSQL provides the `TEXT` type, which stores strings of any length. Although the type T$XT is not in the SQL standard, several other SQL database management systems have it as well.
+
+Values of type `CHARACTER` are physically padded with spaces to the specified width n, and are stored and displayed that way. However, trailing spaces are treated as semantically insignificant and disregarded when comparing two values of type `CHARACTER`. In collations where whitespace is significant, this behavior can produce unexpected results; for example `SELECT 'a '::CHAR(2) collate "C" < E'a\n'::CHAR(2)` returns true, even though C locale would consider a space to be greater than a newline. Trailing spaces are removed when converting a `CHARACTER` value to one of the other string types. Note that trailing spaces are semantically significant in `CHARACTER VARYING` and `TEXT` values, and when using pattern matching, that is `LIKE` and regular expressions.
+
+The characters that can be stored in any of these data types are determined by the database character set, which is selected when the database is created. Regardless of the specific character set, the character with code zero (sometimes called `NUL`) can't be stored. For more information refer to [Character Set Support](https://www.postgresql.org/docs/current/multibyte.html).
+
+The storage requirement for a short string (up to 126 bytes) is 1 byte plus the actual string, which includes the space padding in the case of `CHARACTER`. Longer strings have 4 bytes of overhead instead of 1. Long strings are compressed by the system automatically, so the physical requirement on disk might be less. Very long values are also stored in background tables so that they do not interfere with rapid access to shorter column values. In any case, the longest possible character string that can be stored is about 1 GB. (The maximum value that is allowed for n in the data type declaration is less than that. It wouldn't be useful to change this because with multibyte character encodings the number of characters and bytes can be quite different. If you desire to store long strings with no specific upper limit, use `TEXT` or `CHARACTER VARYING` without a length specifier, rather than making up an arbitrary length limit.)
+
+!!!Tip
+There is no performance difference among these three types, apart from increased storage space when using the blank-padded type, and a few extra CPU cycles to check the length when storing into a length-constrained column. While `CHARACTER(n)` has performance advantages in some other database systems, there is no such advantage in PostgreSQL; in fact CHARACTER(n) is usually the slowest of the three because of its additional storage costs. In most situations `TEXT` or `CHARACTER VARYING` should be used instead.
+
+Refer to the [Postgres documentation on string constances](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-STRINGS) for information about the syntax of string literals and [functions and operators](https://www.postgresql.org/docs/current/functions.html) for information about available operators and functions.
+!!!
+
+Example: Using the character types
+
+```sql
+CREATE TABLE test1 (a character(4));
+INSERT INTO test1 VALUES ('ok');
+SELECT a, char_length(a) FROM test1; -- (1)
+
+  a   | char_length
+------+-------------
+ ok   |           2
+
+
+CREATE TABLE test2 (b varchar(5));
+INSERT INTO test2 VALUES ('ok');
+INSERT INTO test2 VALUES ('good      ');
+INSERT INTO test2 VALUES ('too long');
+ERROR:  value too long for type character varying(5)
+INSERT INTO test2 VALUES ('too long'::varchar(5)); -- explicit truncation
+SELECT b, char_length(b) FROM test2;
+
+   b   | char_length
+-------+-------------
+ ok    |           2
+ good  |           5
+ too l |           5
+```
+
+There are two other fixed-length character types in PostgreSQL, shown in the following table. These are not intended for general-purpose use, only for use in the internal system catalogs. The `NAME` type is used to store identifiers. Its length is currently defined as 64 bytes (63 usable characters plus terminator) but should be referenced using the constant NAMEDATALEN in C source code. The length is set at compile time (and is therefore adjustable for special uses); the default maximum length might change in a future release. The type "CHAR" (note the quotes) is different from `CHAR(1)` in that it only uses one byte of storage, and therefore can store only a single ASCII character. It is used in the system catalogs as a simplistic enumeration type.
+
+## Special Character Types
+
+| Name   | Storage Size | Description |
+| ------ | ------------ | ----------- |
+| "CHAR" | 1 byte	      | single-byte  internal type |
+| `NAME` | 64 bytes     |	internal type for object names |
+
+ You can store a large character string in a `CLOB` type. `CLOB` is semantically equivalent to `VARCHAR2` except no length limit is specified. Generally, use a `CLOB` type if you don't know the maximum string length.
+
+ The longest possible character string that you can store in a `CLOB` type is about 1 GB.
+
+!!!Note 
+   The `CLOB` data type is actually a `DOMAIN` based on the PostgreSQL `TEXT` data type. For information on a `DOMAIN`, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/sql-createdomain.html).
+
+ Thus, use of the `CLOB` type is limited by what can be done for `TEXT`, such as a maximum size of approximately 1 GB.
+
+ For larger amounts of data, instead of using the `CLOB` data type, use the PostgreSQL *large objects* feature that relies on the `pg_largeobject` system catalog. For information on large objects, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/largeobjects.html).
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/03_binary_data.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/03_binary_data.mdx
new file mode 100644
index 00000000000..575b115eb74
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/03_binary_data.mdx
@@ -0,0 +1,86 @@
+---
+title: "Binary data"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.013.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.045.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/03_binary_data/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-binary.html
+   timestamp: 2023-07-11
+---
+
+<div id="binary_data" class="registered_link"></div>
+
+| Name        | Native | Alias | Description                                                                                                                              | 
+| ----------- | ------ | ----- | ------------------------------------------------------------------------------------------------------------------------------------------ | 
+| `BYTEA`     | ✅     |        | Variable-length binary string, 1 or 4 bytes plus the actual binary string. 
+| `BINARY`    |        | ✅     | Alias for `BYTEA`. Fixed-length binary string, with a length between 1 and 8300.                                                                                                          | 
+| `BLOB`      |        | ✅     | Alias for `BYTEA`. Variable-length binary string, with a maximum size of 1 GB. The actual binary string plus 1 byte if the binary string is less than 127 bytes, or 4 bytes if the binary string is 127 bytes or greater |
+| `VARBINARY` |        | ✅     | Alias for `BYTEA`. Variable-length binary string, with a length between 1 and 8300.                                                                                                            |
+
+## Overview
+
+A binary string is a sequence of octets (or bytes). Binary strings are distinguished from characters strings by two characteristics: 
+
+-  Binary strings specifically allow storing octets of value zero and other "non-printable" octets (defined as octets outside the range 32 to 126). 
+-  Operations on binary strings process the actual bytes, whereas the encoding and processing of character strings depends on locale settings.
+
+The `BYTEA` type supports two formats for input and output: “hex” format and “escape” format. Both of these are always accepted on input. The output format depends on the configuration parameter bytea_output; the default is hex. 
+
+### Hex format
+
+The hex format encodes binary data as two hexadecimal digits per byte, most significant nibble first. The entire string is preceded by the sequence \x (to distinguish it from the escape format). In some contexts, the initial backslash may need to be escaped by doubling it. For input, the hexadecimal digits can be either upper or lower case, and whitespace is permitted between digit pairs (but not within a digit pair or in the starting \x sequence). The hex format is compatible with a wide range of external applications and protocols, and it tends to be faster to convert than the escape format, so its use is preferred.
+
+Example:
+
+```
+SET bytea_output = 'hex';
+
+SELECT '\xDEADBEEF'::bytea;
+   bytea
+------------
+ \xdeadbeef
+```
+
+### Escape format
+
+The “escape” format is the traditional PostgreSQL format for the bytea type. It takes the approach of representing a binary string as a sequence of ASCII characters, while converting those bytes that cannot be represented as an ASCII character into special escape sequences. If, from the point of view of the application, representing bytes as characters makes sense, then this representation can be convenient. But in practice it is usually confusing because it blurs the distinction between binary strings and character strings. Also, the escape mechanism can be unwieldy. Therefore, this format should probably be avoided for most new applications.
+
+When entering `BYTEA` values in escape format, octets of certain values *must* be escaped, while all octet values *can* be escaped. In general, to escape an octet, convert it into its three-digit octal value and precede it by a backslash. A backslash itself (octet decimal value 92) can alternatively be represented by double backslashes. The following table shows the characters that must be escaped, and gives the alternative escape sequences where applicable.
+
+| Decimal octet value    | Description            | Escaped input representation | Example        | Hex representation |
+| ---------------------- | ---------------------- | ---------------------------- | --------------- | ------------------ |
+|  0                     | zero octet             | `'\000'`                     | `'\000'::bytea` | \x00               |
+| 39                     | single quote           | `''''` or `'\047'`           | `''''::bytea`   | \x27               |
+| 92                     | backslash              | `'\\'` or `'\134'`           | `'\\'::bytea`   | \x5c               |
+| 0 to 31 and 127 to 255 | “non-printable” octets | `'\xxx'` (octal value)       | `'\001'::bytea` | \x01               |
+
+The requirement to escape non-printable octets varies depending on locale settings. In some instances you can leave them unescaped.
+
+The reason that single quotes must be doubled is that this is true for any string literal in an SQL command. The generic string-literal parser consumes the outermost single quotes and reduces any pair of single quotes to one data character. What the `BYTEA` input function sees is just one single quote, which it treats as a plain data character. However, the `BYTEA` input function treats backslashes as special, and the other behaviors shown in the table are implemented by that function.
+
+In some contexts, backslashes must be doubled compared to what is shown above, because the generic string-literal parser will also reduce pairs of backslashes to one data character.
+
+`BYTEA` octets are output in hex format by default. If you change bytea_output to escape, “non-printable” octets are converted to their equivalent three-digit octal value and preceded by one backslash. Most “printable” octets are output by their standard representation in the client character set, as shown in the following example:
+
+```
+SET bytea_output = 'escape';
+
+SELECT 'abc \153\154\155 \052\251\124'::bytea;
+     bytea
+----------------
+ abc klm *\251T
+```
+
+The octet with decimal value 92 (backslash) is doubled in the output. The following table provides details:
+
+| Decimal octet value    | Description            | Escaped input representation        | Example         | Output result |
+| ---------------------- | ---------------------- | ----------------------------------- | --------------- | ------------- |
+| 92                     | backslash              | `\\`                                | `'\134'::bytea` | `\\`          |
+| 0 to 31 and 127 to 255 | “non-printable” octets | `'\xxx'` (octal value)              | `'\001'::bytea` | `\001`        |
+| 32 to 126              | “printable” octets     | client character set representation | `'\176'::bytea` | ~             |
+
+Depending on the front end to PostgreSQL you use, you might have additional work in terms of escaping and unescaping `BYTEA` strings. For example, you might also have to escape line feeds and carriage returns if your interface automatically translates these.
+
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/04_date_time_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/04_date_time_types.mdx
new file mode 100644
index 00000000000..e68d39329ef
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/04_date_time_types.mdx
@@ -0,0 +1,327 @@
+---
+title: "Date/time types"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.014.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.046.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/04_date_time_types/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-datetime.html
+   timestamp: 2023-09-20
+---
+
+<div id="date_time_types" class="registered_link"></div>
+
+
+| Name                             | Native | Alias | Description                                                                                   |
+| -------------------------------- | -------| ----- | ---------------------------------------------------------------------------------------------- |
+| `DATE`                           | ✅      |      | Date and time, 8 bytes storage, 4713 BC to 5874897 AD range, and resolution 1 second.              | 
+| `INTERVAL DAY TO SECOND [(p)]`   | ✅      |      | Period of time, 12 bytes storage,  -178000000 years to 178000000 years range, and resolution 1 microsecond / 14 digits |
+| `INTERVAL YEAR TO MONTH`         | ✅      |      | Period of time, 12 bytes storage, -178000000 years to 178000000 years range, and resolution 1 microsecond / 14 digits. |
+| `TIMESTAMP [(p)]`                | ✅      |      | Date and time, 8 bytes storage, 4713 BC to 5874897 AD range, and resolution 1 microsecond. |
+| `TIMESTAMP [(p)] WITH TIME ZONE` | ✅      |      | Date and time with time zone, 8 bytes storage, 4713 BC to 5874897 AD range, and resolution 1 microsecond.  |
+
+## Overview
+
+The following discussion of the date/time types assumes that the configuration parameter `edb_redwood_date` is set to `TRUE` whenever a table is created or altered.
+
+When `DATE` appears as the data type of a column in the data definition language (DDL) commands `CREATE TABLE` or `ALTER TABLE`, it's translated to `TIMESTAMP` at the time the table definition is stored in the database. Thus, a time component is also stored in the column along with the date.
+
+`DATE` can appear as a data type of:
+
+-  A variable in an SPL declaration section 
+-  The data type of a formal parameter in an SPL procedure or an SPL function
+-  The return type of an SPL function 
+
+In these cases, it's always translated to `TIMESTAMP` and thus can handle a time component if present.
+
+`TIMESTAMP` accepts an optional precision value `p` that specifies the number of fractional digits retained in the seconds field. The allowed range of `p` is from 0 to 6. The default is `6`.
+
+When `TIMESTAMP` values are stored as double-precision floating-point numbers (the default), the effective limit of precision might be less than 6. `TIMESTAMP` values are stored as seconds before or after midnight 2000-01-01. Microsecond precision is achieved for dates within a few years of 2000-01-01, but the precision degrades for dates further away. When `TIMESTAMP` values are stored as 8-byte integers (a compile-time option), microsecond precision is available over the full range of values. However, 8-byte integer timestamps have a more limited range of dates than shown in the table: from 4713 BC up to 294276 AD.
+
+`TIMESTAMP (p) WITH TIME ZONE` is similar to `TIMESTAMP (p)` but includes the time zone as well.
+
+## INTERVAL types
+
+`INTERVAL` values specify a period of time. Values of `INTERVAL` type are composed of fields that describe the value of the data. The following table lists the fields allowed in an `INTERVAL` type.
+
+| Field name | INTERVAL values allowed                                             |
+| ---------- | ------------------------------------------------------------------- |
+| `YEAR`     | Integer value (positive or negative)                                |
+| `MONTH`    | 0 through 11                                                        |
+| `DAY`      | Integer value (positive or negative)                                |
+| `HOUR`     | 0 through 23                                                        |
+| `MINUTE`   | 0 through 59                                                        |
+| `SECOND`   | 0 through 59.9(p) where 9(p) is the precision of fractional seconds |
+
+The fields must be presented in descending order, from `YEARS` to `MONTHS` and from `DAYS` to `HOURS`, `MINUTES`, and then `SECONDS`.
+
+EDB Postgres Advanced Server supports two `INTERVAL` types compatible with Oracle databases.
+
+The first variation supported by EDB Postgres Advanced Server is `INTERVAL DAY TO SECOND [(p)]`. `INTERVAL DAY TO SECOND [(p)]` stores a time interval in days, hours, minutes, and seconds.
+
+ `p` specifies the precision of the `second` field.
+
+EDB Postgres Advanced Server interprets the following value as as 1 day, 2 hours, 34 minutes, 5 seconds and 678 thousandths of a second:
+
+ `INTERVAL '1 2:34:5.678' DAY TO SECOND(3)`
+
+EDB Postgres Advanced Server interprets the following value as 1 day and 23 hours:
+
+ `INTERVAL '1 23' DAY TO HOUR`
+
+EDB Postgres Advanced Server interprets the following value as 2 hours and 34 minutes:
+
+ `INTERVAL '2:34' HOUR TO MINUTE`
+
+EDB Postgres Advanced Server interprets the following value as 2 hours, 34 minutes, 56 seconds and 13 thousandths of a second. The fractional second is rounded up to 13 because of the specified precision.
+
+ `INTERVAL '2:34:56.129' HOUR TO SECOND(2)`
+
+The second variation supported by EDB Postgres Advanced Server that's compatible with Oracle databases is `INTERVAL YEAR TO MONTH`. This variation stores a time interval in years and months.
+
+EDB Postgres Advanced Server interprets the following value as 12 years and 3 months:
+
+ `INTERVAL '12-3' YEAR TO MONTH`
+
+EDB Postgres Advanced Server interprets the following value as 12 years and 3 months:
+
+ `INTERVAL '456' YEAR(2)`
+
+EDB Postgres Advanced Server interprets the following value as 25 years:
+
+ `INTERVAL '300' MONTH`
+
+
+## Date/time input
+
+Date and time input is accepted in ISO 8601 SQL-compatible format, the Oracle default `dd-MON-yy` format, as well as a number of other formats provided that there's no ambiguity as to which component is the year, month, and day. However, we strongly recommend using the `TO_DATE` function to avoid ambiguities.
+
+Enclose any date or time literal input in single quotes, like text strings. The following SQL standard syntax is also accepted:
+
+```sql
+type 'value'
+```
+
+`type` is either `DATE` or `TIMESTAMP`.
+
+`value` is a date/time text string.
+
+### Dates
+
+The following block shows some possible input formats for dates, all of which equate to January 8, 1999:
+
+```text
+Example
+January 8, 1999
+1999-01-08
+1999-Jan-08
+Jan-08-1999
+08-Jan-1999
+08-Jan-99
+Jan-08-99
+19990108
+990108
+```
+
+You can assign the date values to a `DATE` or `TIMESTAMP` column or variable. The hour, minute, and seconds fields is set to zero if you don't append the date value with a time value.
+
+### Times
+
+Some examples of the time component of a date or time stamp are shown in the table.
+
+| Example        | Description                                |
+| -------------- | ------------------------------------------ |
+| `04:05:06.789` | ISO 8601                                   |
+| `04:05:06`     | ISO 8601                                   |
+| `04:05`        | ISO 8601                                   |
+| `040506`       | ISO 8601                                   |
+| `04:05 AM`     | Same as 04:05; AM does not affect value    |
+| `04:05 PM`     | Same as 16:05; input hour must be &lt;= 12 |
+
+### Time stamps
+
+Valid input for time stamps consists of a concatenation of a date and a time. You can format the date portion of the time according to any of the examples shown in [Dates](#dates). The time portion of the time stamp can be formatted according to any of examples shown in the table in [Times](#times).
+
+This example shows a time stamp that follows the Oracle default format:
+
+ `08-JAN-99 04:05:06`
+
+This example shows a time stamp that follows the ISO 8601 standard:
+
+ `1999-01-08 04:05:06`
+
+### Special Values 
+
+PostgreSQL supports several special date/time input values for convenience, as shown in the following table. The values `infinity` and `-infinity` are specially represented inside the system and are displayed unchanged; the others are simply notational shorthands that are converted to ordinary date/time values when read. (In particular, `now` and related strings are converted to a specific time value as soon as they are read.) All of these values must be enclosed in single quotes when used as constants in SQL commands.
+
+| Input String | Valid Types           | Description                                    |
+| ------------ | --------------------- | ---------------------------------------------- |
+| epoch        | date, timestamp       | 1970-01-01 00:00:00+00 (Unix system time zero) |
+| infinity     | date, timestamp       | later than all other time stamps               |
+| -infinity    | date, timestamp       | earlier than all other time stamps             |
+| now          | date, time, timestamp | current transaction's start time               |
+| today        | date, timestamp       | midnight (00:00) today                         |
+| tomorrow     | date, timestamp       | midnight (00:00) tomorrow                      |
+| yesterday    | date, timestamp       | midnight (00:00) yesterday                     |
+| allballs     | time                  | 00:00:00.00 UTC                                |
+
+The following SQL-compatible functions can also be used to obtain the current time value for the corresponding data type: 
+
+`CURRENT_DATE`
+`CURRENT_TIME`
+`CURRENT_TIMESTAMP`
+`LOCALTIME`
+`LOCALTIMESTAMP`
+
+Note that these are SQL functions and are not recognized in data input strings.
+
+!!!Note
+While the input strings `now`, `today`, `tomorrow`, and `yesterday` are fine to use in interactive SQL commands, they can have surprising behavior when the command is saved to be executed later, for example in prepared statements, views, and function definitions. The string can be converted to a specific time value that continues to be used long after it becomes stale. Use one of the SQL functions instead in such contexts. For example, `CURRENT_DATE + 1` is safer than `tomorrow::date`.
+!!!
+
+## Date/time output
+
+The default output format of the date/time types is either:
+
+-  (`dd-MON-yy`), referred to as the *Redwood date style*, compatible with Oracle databases 
+-  (`yyyy-mm-dd`) referred to as the ISO 8601 format
+
+The format you use depends on the application interface to the database. Applications that use JDBC, such as SQL Interactive, always present the date in ISO 8601 form. Other applications such as PSQL present the date in Redwood form.
+
+The following table shows examples of the output formats for the two styles: Redwood and ISO 8601.
+
+| Description           | Example               |
+| --------------------- | --------------------- |
+| Redwood style         | `31-DEC-05 07:37:16`  |
+| ISO 8601/SQL standard | `1997-12-17 07:37:16` |
+
+## Internals
+
+EDB Postgres Advanced Server uses Julian dates for all date/time calculations. Julian dates correctly predict or calculate any date after 4713 BC based on the assumption that the length of the year is 365.2425 days.
+
+## Time Zones 
+
+PostgreSQL uses the widely-used IANA (Olson) time zone database for information about historical time zone rules. For times in the future, the assumption is that the latest known rules for a given time zone will continue to be observed indefinitely far into the future.
+
+PostgreSQL endeavors to be compatible with the SQL standard definitions for typical usage. However, the SQL standard has an odd mix of date and time types and capabilities. Two obvious problems are:
+
+- Although the date type cannot have an associated time zone, the time type can. Time zones in the real world have little meaning unless associated with a date as well as a time, since the offset can vary through the year with daylight-saving time boundaries.
+
+- The default time zone is specified as a constant numeric offset from UTC. It is therefore impossible to adapt to daylight-saving time when doing date/time arithmetic across DST boundaries.
+
+To address these difficulties, we recommend using date/time types that contain both date and time when using time zones. We do not recommend using the type `time with time zone` (though it is supported by PostgreSQL for legacy applications and for compliance with the SQL standard). PostgreSQL assumes your local time zone for any type containing only date or time.
+
+All time zone-aware dates and times are stored internally in UTC. They are converted to local time in the zone specified by the `TimeZone` configuration parameter before being displayed to the client.
+
+PostgreSQL allows you to specify time zones in three different forms:
+
+- A full time zone name, for example America/New_York. The recognized time zone names are listed in the `pg_timezone_names` view. PostgreSQL uses the widely-used IANA time zone data for this purpose, so the same time zone names are also recognized by other software.
+
+- A time zone abbreviation, for example PST. Such a specification merely defines a particular offset from UTC, in contrast to full time zone names which can imply a set of daylight savings transition rules as well. The recognized abbreviations are listed in the `pg_timezone_abbrevs` view. You cannot set the configuration parameters `TimeZone` or `log_timezone` to a time zone abbreviation, but you can use abbreviations in date/time input values and with the `AT TIME ZONE` operator.
+
+- PostgreSQL also accepts POSIX-style time zone specifications. This option is not normally preferable to using a named time zone, but it may be necessary if no suitable IANA time zone entry is available.
+
+In short, this is the difference between abbreviations and full names: abbreviations represent a specific offset from UTC, whereas many of the full names imply a local daylight-savings time rule and so have two possible UTC offsets. As an example, 2014-06-04 12:00 America/New_York represents noon local time in New York, which for this particular date was Eastern Daylight Time (UTC-4). So 2014-06-04 12:00 EDT specifies that same time instant. But 2014-06-04 12:00 EST specifies noon Eastern Standard Time (UTC-5), regardless of whether daylight savings was nominally in effect on that date.
+
+To complicate matters, some jurisdictions have used the same time zone abbreviation to mean different UTC offsets at different times; for example, in Moscow MSK has meant UTC+3 in some years and UTC+4 in others. PostgreSQL interprets such abbreviations according to whatever they meant (or had most recently meant) on the specified date; but, as with the EST example above, this is not necessarily the same as local civil time on that date.
+
+In all cases, time zone names and abbreviations are recognized case-insensitively. (This is a change from PostgreSQL versions prior to 8.2, which were case-sensitive in some contexts but not others.)
+
+Neither time zone names nor abbreviations are hard-wired into the server; they are obtained from configuration files stored under `.../share/timezone/` and `.../share/timezonesets/` of the installation directory.
+
+The `TimeZone` configuration parameter can be set in the file `postgresql.conf`, or in any of the other standard ways using server configuration. There are also some special ways to set it:
+
+- The SQL command `SET TIME ZONE` sets the time zone for the session. This is an alternative spelling of `SET TIMEZONE TO` with a more SQL-spec-compatible syntax.
+
+- The `PGTZ` environment variable is used by libpq clients to send a `SET TIME ZONE` command to the server upon connection.
+
+## Interval Input 
+
+Interval values can be written using the following verbose syntax:
+
+```
+[@] quantity unit [quantity unit...] [direction]
+```
+
+where `quantity` is a number (possibly signed); `unit` is `microsecond`, `millisecond`, `second`, `minute`, `hour`, `day`, `week`, `month`, `year`, `decade`, `century`, `millennium`, or abbreviations or plurals of these units; `direction` can be `ago` or empty. The at sign (@) is optional noise. The amounts of the different units are implicitly added with appropriate sign accounting. `ago` negates all the fields. This syntax is also used for interval output if `IntervalStyle` is set to `postgres_verbose`.
+
+Quantities of days, hours, minutes, and seconds can be specified without explicit unit markings. For example, '1 12:59:10' is read the same as '1 day 12 hours 59 min 10 sec'. Also, a combination of years and months can be specified with a dash; for example '200-10' is read the same as '200 years 10 months'. (These shorter forms are in fact the only ones allowed by the SQL standard, and are used for output when `IntervalStyle` is set to `sql_standard`.)
+
+Interval values can also be written as ISO 8601 time intervals, using either the “format with designators” of the standard's section 4.4.3.2 or the “alternative format” of section 4.4.3.3. The format with designators looks like this:
+
+```
+P quantity unit [ quantity unit ...] [ T [ quantity unit ...]]
+```
+
+The string must start with a P, and may include a T that introduces the time-of-day units. The following table provides the available unit abbreviations. Units may be omitted, and may be specified in any order, but units smaller than a day must appear after T. In particular, the meaning of M depends on whether it is before or after T.
+
+| Abbreviation | Meaning                   |
+| ------------ | ------------------------- |
+| Y            | Years                     |
+| M            | Months (in the date part) |
+| W            | Weeks                     |
+| D            | Days                      |
+| H            | Hours                     |
+| M            | Minutes                   |
+| S            | Seconds                   |
+
+In the alternative format:
+
+```
+P [ years-months-days ] [ T hours:minutes:seconds ]
+```
+
+the string must begin with P, and a T separates the date and time parts of the interval. The values are given as numbers similar to ISO 8601 dates.
+
+When writing an interval constant with a fields specification, or when assigning a string to an interval column that was defined with a fields specification, the interpretation of unmarked quantities depends on the fields. For example `INTERVAL '1' YEAR` is read as 1 year, whereas `INTERVAL '1'` means 1 second. Also, field values “to the right” of the least significant field allowed by the fields specification are silently discarded. For example, writing `INTERVAL '1 day 2:03:04' HOUR TO MINUTE` results in dropping the seconds field, but not the day field.
+
+According to the SQL standard all fields of an interval value must have the same sign, so a leading negative sign applies to all fields; for example, the negative sign in the interval literal '-1 2:03:04' applies to both the days and hour/minute/second parts. PostgreSQL allows the fields to have different signs, and traditionally treats each field in the textual representation as independently signed, so that the hour/minute/second part is considered positive in this example. If `IntervalStyle` is set to `sql_standard` then a leading sign is considered to apply to all fields (but only if no additional signs appear). Otherwise the traditional PostgreSQL interpretation is used. To avoid ambiguity, it's recommended to attach an explicit sign to each field if any field is negative.
+
+Field values can have fractional parts: for example, '1.5 weeks' or '01:02:03.45'. However, because interval internally stores only three integer units (months, days, microseconds), fractional units must be spilled to smaller units. Fractional parts of units greater than months are rounded to be an integer number of months, for example, '1.5 years' becomes '1 year 6 mons'. Fractional parts of weeks and days are computed to be an integer number of days and microseconds, assuming 30 days per month and 24 hours per day, e.g., '1.75 months' becomes 1 mon 22 days 12:00:00. Only seconds will ever be shown as fractional on output.
+
+The following table shows some examples of valid interval input.
+
+| Example	                                           | Description                                                                     |
+| -------------------------------------------------- | ------------------------------------------------------------------------------- |
+| 1-2	                                               | SQL standard format: 1 year 2 months                                            |
+| 3 4:05:06	                                         | SQL standard format: 3 days 4 hours 5 minutes 6 seconds                         |
+| 1 year 2 months 3 days 4 hours 5 minutes 6 seconds | Traditional Postgres format: 1 year 2 months 3 days 4 hours 5 minutes 6 seconds |
+| P1Y2M3DT4H5M6S	                                   | ISO 8601 “format with designators”: same meaning as above                       |
+| P0001-02-03T04:05:06	                             | ISO 8601 “alternative format”: same meaning as above                            |
+
+Internally, interval values are stored as months, days, and microseconds. This is done because the number of days in a month varies, and a day can have 23 or 25 hours if a daylight savings time adjustment is involved. The months and days fields are integers while the microseconds field can store fractional seconds. Because intervals are usually created from constant strings or timestamp subtraction, this storage method works well in most cases, but can cause unexpected results:
+
+```
+SELECT EXTRACT(hours from '80 minutes'::interval);
+ date_part
+-----------
+         1
+
+SELECT EXTRACT(days from '80 hours'::interval);
+ date_part
+-----------
+         0        
+```
+
+Functions `justify_days` and `justify_hours` are available for adjusting days and hours that overflow their normal ranges.
+
+## Interval Output 
+
+Using the command `SET intervalstyle` you can set the output format of the interval type to one of four styles: `sql_standard`, `postgres`, `postgres_verbose`, or `iso_8601`. The default is the `postgres` format. The table in this section shows examples of each output style.
+
+The `sql_standard` style produces output that conforms to the SQL standard's specification for interval literal strings, if the interval value meets the standard's restrictions (either year-month only or day-time only, with no mixing of positive and negative components). Otherwise the output looks like a standard year-month literal string followed by a day-time literal string, with explicit signs added to disambiguate mixed-sign intervals.
+
+The output of the `postgres` style matches the output of PostgreSQL releases prior to 8.4 when the `DateStyle` parameter was set to ISO.
+
+The output of the `postgres_verbose` style matches the output of PostgreSQL releases prior to 8.4 when the `DateStyle` parameter was set to non-ISO output.
+
+The output of the `iso_8601` style matches the “format with designators” described in the ISO 8601 standard.
+
+| Style Specification	| Year-Month Interval	| Day-Time Interval	             | Mixed Interval                                    |
+| ------------------- | ------------------- | ------------------------------ | ------------------------------------------------- |
+| sql_standard        |	1-2	                | 3 4:05:06	                     | -1-2 +3 -4:05:06                                  |
+| postgres            |	1 year 2 mons	      | 3 days 04:05:06	               | -1 year -2 mons +3 days -04:05:06                 |
+| postgres_verbose    |	@ 1 year 2 mons	    | @ 3 days 4 hours 5 mins 6 secs | @ 1 year 2 mons -3 days 4 hours 5 mins 6 secs ago |
+| iso_8601            |	P1Y2M	              | P3DT4H5M6S	                   | P-1Y-2M3D​T-4H-5M-6S                               |
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/05_boolean_type.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/05_boolean_type.mdx
new file mode 100644
index 00000000000..4210d15a926
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/05_boolean_type.mdx
@@ -0,0 +1,41 @@
+---
+title: "Boolean types"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/05_boolean_type/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-boolean.html
+   timestamp: 2023-09-20
+---
+
+<div id="boolean_type" class="registered_link"></div>
+
+| Name      | Native | Alias | Description                                   |
+| --------- | ------ | ----- | --------------------------------------------- |
+| `BOOLEAN` | ✅     |       | Logical Boolean (true/false), 1 byte storage. |
+
+## Overview
+
+EDB Postgres Advanced Server provides the standard SQL type `BOOLEAN`. `BOOLEAN` can have one of only two states: `TRUE` or `FALSE`. A third state, `UNKNOWN`, is represented by the SQL `NULL` value.
+
+Literal values representing the `TRUE` state include 'TRUE', 'true', 'y', '1' and 't'. Literal values representing `FALSE` include 'FALSE', 'false', 'n', '0' and 'f'. There is no literal value for `UNKNOWN`; use `NULL`.
+
+The follow is an example using the boolean type:
+
+```sql
+CREATE TABLE test1 (a boolean, b text);
+INSERT INTO test1 VALUES (TRUE, 'sic est');
+INSERT INTO test1 VALUES (FALSE, 'non est');
+SELECT * FROM test1;
+ a |    b
+---+---------
+ t | sic est
+ f | non est
+
+SELECT * FROM test1 WHERE a;
+ a |    b
+---+---------
+ t | sic est
+ ```
+
+Note that the parser automatically understands that `TRUE` and `FALSE` are of type boolean, but this is not so for `NULL` because that can have any type. So in some contexts you might have to cast `NULL` to `BOOLEAN` explicitly.
+
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/06_xml_type.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/06_xml_type.mdx
new file mode 100644
index 00000000000..6a5034bd3e1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/06_xml_type.mdx
@@ -0,0 +1,115 @@
+---
+title: "XML type"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.016.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.048.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/06_xml_type/ #generated for docs/epas/reorg-role-use-case-mode
+source:
+   url: https://www.postgresql.org/docs/current/datatype-xml.html
+   timestamp: 2023-09-20
+---
+
+<div id="xml_type" class="registered_link"></div>
+
+| Name           | Native | Alias | Description                                   |
+| -------------- | ------ | ----- | --------------------------------------------- |
+| `XMLTYPE`      | ✅     |       | Data type used to store XML data.             |
+
+## Overview
+
+The `XMLTYPE` data type is used to store XML data. Its advantage over storing XML data in a character field is that it checks the input values for how well they're formed. Also, support functions perform type-safe operations on it.
+
+The XML type can store well-formed “documents,” as defined by the XML standard, as well as “content” fragments, which are defined by the production `XMLDecl? content` in the XML standard. Roughly, this means that content fragments can have more than one top-level element or character node.
+
+!!! Note
+    Oracle doesn't support storing content fragments in `XMLTYPE` columns.
+
+This example shows creating and inserting a row into a table with an `XMLTYPE` column:
+
+```sql
+CREATE TABLE books (
+    content         XMLTYPE
+);
+
+INSERT INTO books VALUES (XMLPARSE (DOCUMENT '<?xml
+version="1.0"?><book><title>Manual</title><chapter>...</chapter></book>'));
+
+SELECT * FROM books;
+__OUTPUT__
+                         content
+----------------------------------------------------------
+ <book><title>Manual</title><chapter>...</chapter></book>
+(1 row)
+```
+
+## Creating XML Values 
+
+To produce a value of type XML from character data, use the function `XMLPARSE`:
+
+```
+XMLPARSE ( { DOCUMENT | CONTENT } value)
+```
+
+Examples:
+
+```
+XMLPARSE (DOCUMENT '<?xml version="1.0"?><book><title>Manual</title><chapter>...</chapter></book>')
+XMLPARSE (CONTENT 'abc<foo>bar</foo><bar>foo</bar>')
+```
+
+While this is the only way to convert character strings into XML values according to the SQL standard, the PostgreSQL-specific syntaxes:
+
+```
+xml '<foo>bar</foo>'
+'<foo>bar</foo>'::xml
+```
+
+can also be used.
+
+The XML type does not validate input values against a document type declaration (DTD), even when the input value specifies a DTD. There is also currently no built-in support for validating against other XML schema languages such as XML Schema.
+
+The inverse operation, producing a character string value from XML, uses the function `XMLSERIALIZE`:
+
+```
+XMLSERIALIZE ( { DOCUMENT | CONTENT } value AS type [ [ NO ] INDENT ] )
+```
+
+`type` can be `character`, `character varying`, or `text` (or an alias for one of those). Again, according to the SQL standard, this is the only way to convert between type XML and character types, but PostgreSQL also allows you to simply cast the value.
+
+The `INDENT` option causes the result to be pretty-printed, while `NO INDENT` (which is the default) just emits the original input string. Casting to a character type likewise produces the original string.
+
+When a character string value is cast to or from type XML without going through `XMLPARSE` or `XMLSERIALIZE`, respectively, the choice of `DOCUMENT` versus `CONTENT` is determined by the “XML option” session configuration parameter, which can be set using the standard command:
+
+```
+SET XML OPTION { DOCUMENT | CONTENT };
+```
+
+or the more PostgreSQL-like syntax
+
+```
+SET xmloption TO { DOCUMENT | CONTENT };
+```
+
+The default is `CONTENT`, so all forms of XML data are allowed.
+
+## Encoding Handling 
+
+Take care when dealing with multiple character encodings on the client, server, and in the XML data passed through them. When using the text mode to pass queries to the server and query results to the client, which is the normal mode, PostgreSQL converts all character data passed between the client and the server and vice versa to the character encoding of the respective end. This includes string representations of XML values. This would ordinarily mean that encoding declarations contained in XML data can become invalid as the character data is converted to other encodings while traveling between client and server, because the embedded encoding declaration is not changed. To cope with this behavior, encoding declarations contained in character strings presented for input to the XML type are ignored, and content is assumed to be in the current server encoding. Consequently, for correct processing, character strings of XML data must be sent from the client in the current client encoding. It is the responsibility of the client to either convert documents to the current client encoding before sending them to the server, or to adjust the client encoding appropriately. On output, values of type XML will not have an encoding declaration, and clients should assume all data is in the current client encoding.
+
+When using binary mode to pass query parameters to the server and query results back to the client, no encoding conversion is performed, so the situation is different. In this case, an encoding declaration in the XML data will be observed, and if it is absent, the data will be assumed to be in UTF-8 (as required by the XML standard; note that PostgreSQL does not support UTF-16). On output, data will have an encoding declaration specifying the client encoding, unless the client encoding is UTF-8, in which case it will be omitted.
+
+Processing XML data with PostgreSQL will be less error-prone and more efficient if the XML data encoding, client encoding, and server encoding are the same. Since XML data is internally processed in UTF-8, computations will be most efficient if the server encoding is also UTF-8.
+
+!!!Note
+Some XML-related functions may not work at all on non-ASCII data when the server encoding is not UTF-8. This is known to be an issue for `xmltable()` and `xpath()` in particular.
+!!!
+
+## Accessing XML Values 
+
+The XML data type is unusual because it does not provide any comparison operators. This is because there is no well-defined and universally useful comparison algorithm for XML data. One consequence of this is that you cannot retrieve rows by comparing an XML column against a search value. XML values should therefore typically be accompanied by a separate key field such as an ID. An alternative solution for comparing XML values is to convert them to character strings first, but note that character string comparison has little to do with a useful XML comparison method.
+
+Because there are no comparison operators for the XML data type, it is not possible to create an index directly on a column of this type. If speedy searches in XML data are desired, possible workarounds include casting the expression to a character string type and indexing that, or indexing an XPath expression. Of course, the actual query would have to be adjusted to search by the indexed expression.
+
+The text-search functionality in PostgreSQL can also be used to speed up full-document searches of XML data. The necessary preprocessing support is, however, not yet available in the PostgreSQL distribution.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/array_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/array_types.mdx
new file mode 100644
index 00000000000..8099d71d5b7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/array_types.mdx
@@ -0,0 +1,457 @@
+---
+title: "Array types"
+---
+
+| Name                                                                 | Native | Alias | Description                                   |
+| -------------------------------------------------------------------- | ------ | ----- | --------------------------------------------- |
+| `<*built-in* \| *user-defined* \| *enum* \| *composite* type>` []... | ✅     |       | Variable-length multidimensional arrays.      |
+  
+## Overview
+
+PostgreSQL allows the columns of a table to be defined as variable-length multidimensional arrays. Arrays of any built-in or user-defined base type, enum type, or composite type can be created. Arrays of domains aren't yet supported. 
+
+## Declaration of array types
+
+To illustrate the use of array types, we can create the following table: 
+
+```sql
+CREATE TABLE sal_emp (
+    name            text,
+    pay_by_quarter  integer[],
+    schedule        text[][]
+);
+```
+
+As shown, an array data type is named by appending square brackets (`[]`) to the data type name of the array elements. The above command creates a table named `sal_emp` with a column of type text (`name`), a one-dimensional array of type integer (`pay_by_quarter`), which represents the employee's salary by quarter, and a two-dimensional array of text (`schedule`), which represents the employee's weekly schedule.
+
+The syntax for `CREATE TABLE` allows the exact size of arrays to be specified, for example:
+
+```sql
+CREATE TABLE tictactoe (
+    squares   integer[3][3]
+);
+```
+
+However, the current implementation ignores any supplied array size limits, that is, the behavior is the same as for arrays of unspecified length.
+
+The current implementation doesn't enforce the declared number of dimensions either. Arrays of a particular element type are all considered to be of the same type, regardless of size or number of dimensions. So, declaring the array size or number of dimensions in `CREATE TABLE` is simply documentation; it does not affect run-time behavior.
+
+An alternative syntax, which conforms to the SQL standard by using the keyword `ARRAY`, can be used for one-dimensional arrays. `pay_by_quarter` could have been defined as:
+
+```sql 
+pay_by_quarter  integer ARRAY[4],
+```
+
+Or, if no array size is to be specified:
+
+```sql
+pay_by_quarter  integer ARRAY,
+```
+
+As before, however, PostgreSQL does not enforce the size restriction in any case.
+
+## Array value input 
+
+To write an array value as a literal constant, enclose the element values within curly braces and separate them by commas. (If you know C, this is not unlike the C syntax for initializing structures.) You can put double quotes around any element value, and must do so if it contains commas or curly braces. (More details appear below.) Thus, the general format of an array constant is the following:
+
+```sql
+'{ val1 delim val2 delim ... }'
+```
+
+where `delim` is the delimiter character for the type, as recorded in its `pg_type` entry. Among the standard data types provided in the PostgreSQL distribution, all use a comma (`,`), except for type box which uses a semicolon (`;`). Each `val` is either a constant of the array element type, or a subarray. An example of an array constant is:
+
+```sql
+'{{1,2,3},{4,5,6},{7,8,9}}'
+```
+
+This constant is a two-dimensional, 3-by-3 array consisting of three subarrays of integers.
+
+To set an element of an array constant to NULL, write `NULL` for the element value. (Any upper- or lower-case variant of `NULL` will do.) If you want an actual string value "NULL", you must put double quotes around it.
+
+!!! Note
+    These kinds of array constants are actually only a special case of the generic type constants discussed in [Constants of Other Types](https://www.postgresql.org/docs/9.3/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS-GENERIC). The constant is initially treated as a string and passed to the array input conversion routine. An explicit type specification might be necessary.
+
+The following are `INSERT` statements:
+
+```sql 
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"training", "presentation"}}');
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    '{20000, 25000, 25000, 25000}',
+    '{{"breakfast", "consulting"}, {"meeting", "lunch"}}');
+__OUTPUT__
+SELECT * FROM sal_emp;
+ name  |      pay_by_quarter       |                 schedule
+-------+---------------------------+-------------------------------------------
+ Bill  | {10000,10000,10000,10000} | {{meeting,lunch},{training,presentation}}
+ Carol | {20000,25000,25000,25000} | {{breakfast,consulting},{meeting,lunch}}
+(2 rows)
+```
+
+Multidimensional arrays must have matching extents for each dimension. A mismatch causes an error, for example:
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    '{10000, 10000, 10000, 10000}',
+    '{{"meeting", "lunch"}, {"meeting"}}');
+ERROR:  multidimensional arrays must have array expressions with matching dimensions
+```
+
+The `ARRAY` constructor syntax can also be used:
+
+```sql
+INSERT INTO sal_emp
+    VALUES ('Bill',
+    ARRAY[10000, 10000, 10000, 10000],
+    ARRAY[['meeting', 'lunch'], ['training', 'presentation']]);
+
+INSERT INTO sal_emp
+    VALUES ('Carol',
+    ARRAY[20000, 25000, 25000, 25000],
+    ARRAY[['breakfast', 'consulting'], ['meeting', 'lunch']]);
+```
+
+Notice that the array elements are ordinary SQL constants or expressions; for instance, string literals are single quoted, instead of double quoted as they would be in an array literal. For more details on `ARRAY` constructor syntax, see [Array constructors](https://www.postgresql.org/docs/9.3/sql-expressions.html#SQL-SYNTAX-ARRAY-CONSTRUCTORS).
+
+## Accessing arrays
+
+Now, we can run some queries on the table. First, we show how to access a single element of an array. This query retrieves the names of the employees whose pay changed in the second quarter:
+
+```sql 
+SELECT name FROM sal_emp WHERE pay_by_quarter[1] <> pay_by_quarter[2];
+__OUTPUT__
+ name
+-------
+ Carol
+(1 row)
+```
+
+The array subscript numbers are written within square brackets. By default PostgreSQL uses a one-based numbering convention for arrays, that is, an array of `n` elements starts with `array[1]` and ends with `array[n]`.
+
+This query retrieves the third quarter pay of all employees:
+
+```sql
+SELECT pay_by_quarter[3] FROM sal_emp;
+__OUTPUT__
+ pay_by_quarter
+----------------
+          10000
+          25000
+(2 rows)
+```
+
+We can also access arbitrary rectangular slices of an array, or subarrays. An array slice is denoted by writing `lower-bound:upper-bound` for one or more array dimensions. For example, this query retrieves the first item on Bill's schedule for the first two days of the week:
+
+```sql
+SELECT schedule[1:2][1:1] FROM sal_emp WHERE name = 'Bill';
+__OUTPUT__
+        schedule
+------------------------
+ {{meeting},{training}}
+(1 row)
+```
+
+If any dimension is written as a slice, that is, contains a colon, then all dimensions are treated as slices. Any dimension that has only a single number (no colon) is treated as being from 1 to the number specified. For example, `[2]` is treated as `[1:2]`, as in this example:
+
+```sql
+SELECT schedule[1:2][2] FROM sal_emp WHERE name = 'Bill';
+__OUTPUT__
+                 schedule
+-------------------------------------------
+ {{meeting,lunch},{training,presentation}}
+(1 row)
+```
+
+To avoid confusion with the non-slice case, it's best to use slice syntax for all dimensions, for example, `[1:2][1:1]`, not `[2][1:1]`.
+
+An array subscript expression returns null if either the array itself or any of the subscript expressions are null. Also, null is returned if a subscript is outside the array bounds (this case does not raise an error). For example, if `schedule` currently has the dimensions `[1:3][1:2]` then referencing `schedule[3][3]` yields `NULL`. Similarly, an array reference with the wrong number of subscripts yields a null rather than an error.
+
+An array slice expression likewise yields null if the array itself or any of the subscript expressions are null. However, in other cases such as selecting an array slice that is completely outside the current array bounds, a slice expression yields an empty (zero-dimensional) array instead of null. (This does not match non-slice behavior and is done for historical reasons.) If the requested slice partially overlaps the array bounds, then it is silently reduced to just the overlapping region instead of returning null.
+
+The current dimensions of any array value can be retrieved with the `array_dims` function:
+
+```sql 
+SELECT array_dims(schedule) FROM sal_emp WHERE name = 'Carol';
+__OUTPUT__
+ array_dims
+------------
+ [1:2][1:2]
+(1 row)
+```
+
+`array_dims` produces a text result, which is convenient for people to read but perhaps inconvenient for programs. Dimensions can also be retrieved with `array_upper` and `array_lower`, which return the upper and lower bound of a specified array dimension, respectively:
+
+```sql
+SELECT array_upper(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+__OUTPUT__
+ array_upper
+-------------
+           2
+(1 row)
+```
+
+`array_length` returns the length of a specified array dimension:
+
+```sql
+SELECT array_length(schedule, 1) FROM sal_emp WHERE name = 'Carol';
+__OUTPUT__
+ array_length
+--------------
+            2
+(1 row)
+```
+
+## Modifying arrays
+
+An array value can be replaced completely:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = '{25000,25000,27000,27000}'
+    WHERE name = 'Carol';
+```
+
+or using the `ARRAY` expression syntax:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter = ARRAY[25000,25000,27000,27000]
+    WHERE name = 'Carol';
+```
+
+An array can also be updated at a single element:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[4] = 15000
+    WHERE name = 'Bill';
+```
+
+or updated in a slice:
+
+```sql
+UPDATE sal_emp SET pay_by_quarter[1:2] = '{27000,27000}'
+    WHERE name = 'Carol';
+```
+
+A stored array value can be enlarged by assigning to elements not already present. Any positions between those previously present and the newly assigned elements are filled with nulls. For example, if array `myarray` currently has 4 elements, it will have six elements after an update that assigns to `myarray[6]`; `myarray[5]` will contain null. Currently, enlargement in this fashion is only allowed for one-dimensional arrays, not multidimensional arrays.
+
+Subscripted assignment allows creation of arrays that do not use one-based subscripts. For example one might assign to `myarray[-2:7]` to create an array with subscript values from -2 to 7.
+
+New array values can also be constructed using the concatenation operator, `||`:
+
+```sql
+SELECT ARRAY[1,2] || ARRAY[3,4];
+__OUTPUT__
+ ?column?
+-----------
+ {1,2,3,4}
+(1 row)
+```
+```sql
+SELECT ARRAY[5,6] || ARRAY[[1,2],[3,4]];
+__OUTPUT__
+      ?column?
+---------------------
+ {{5,6},{1,2},{3,4}}
+(1 row)
+```
+
+The concatenation operator allows a single element to be pushed onto the beginning or end of a one-dimensional array. It also accepts two `N`-dimensional arrays, or an `N`-dimensional and an `N+1`-dimensional array.
+
+When a single element is pushed onto either the beginning or end of a one-dimensional array, the result is an array with the same lower bound subscript as the array operand. For example:
+
+```sql
+SELECT array_dims(1 || '[0:1]={2,3}'::int[]);
+__OUTPUT__
+ array_dims
+------------
+ [0:2]
+(1 row)
+```
+```sql
+SELECT array_dims(ARRAY[1,2] || 3);
+__OUTPUT__
+ array_dims
+------------
+ [1:3]
+(1 row)
+```
+
+When two arrays with an equal number of dimensions are concatenated, the result retains the lower bound subscript of the left-hand operand's outer dimension. The result is an array comprising every element of the left-hand operand followed by every element of the right-hand operand. For example:
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[3,4,5]);
+__OUTPUT__
+ array_dims
+------------
+ [1:5]
+(1 row)
+```
+```sql
+SELECT array_dims(ARRAY[[1,2],[3,4]] || ARRAY[[5,6],[7,8],[9,0]]);
+__OUTPUT__
+ array_dims
+------------
+ [1:5][1:2]
+(1 row)
+```
+
+When an `N`-dimensional array is pushed onto the beginning or end of an `N+1`-dimensional array, the result is analogous to the element-array case above. Each `N`-dimensional sub-array is essentially an element of the `N+1`-dimensional array's outer dimension. For example:
+
+```sql
+SELECT array_dims(ARRAY[1,2] || ARRAY[[3,4],[5,6]]);
+__OUTPUT__
+ array_dims
+------------
+ [1:3][1:2]
+(1 row)
+```
+
+An array can also be constructed by using the functions `array_prepend`, `array_append`, or `array_cat`. The first two only support one-dimensional arrays, but `array_cat` supports multidimensional arrays. Some examples:
+
+```sql
+SELECT array_prepend(1, ARRAY[2,3]);
+__OUTPUT__
+ array_prepend
+---------------
+ {1,2,3}
+(1 row)
+```
+```sql
+SELECT array_append(ARRAY[1,2], 3);
+__OUTPUT__
+ array_append
+--------------
+ {1,2,3}
+(1 row)
+```
+```sql
+SELECT array_cat(ARRAY[1,2], ARRAY[3,4]);
+__OUTPUT__
+ array_cat
+-----------
+ {1,2,3,4}
+(1 row)
+```
+```sql
+SELECT array_cat(ARRAY[[1,2],[3,4]], ARRAY[5,6]);
+__OUTPUT__
+      array_cat
+---------------------
+ {{1,2},{3,4},{5,6}}
+(1 row)
+```
+```sql
+SELECT array_cat(ARRAY[5,6], ARRAY[[1,2],[3,4]]);
+__OUTPUT__
+      array_cat
+---------------------
+ {{5,6},{1,2},{3,4}}
+ ```
+
+In simple cases, the concatenation operator discussed above is preferred over direct use of these functions. However, because the concatenation operator is overloaded to serve all three cases, there are situations where use of one of the functions is helpful to avoid ambiguity. For example consider:
+
+```sql
+SELECT ARRAY[1, 2] || '{3, 4}';  -- the untyped literal is taken as an array
+__OUTPUT__
+ ?column?
+-----------
+ {1,2,3,4}
+```
+```sql
+SELECT ARRAY[1, 2] || '7';                 -- so is this one
+__OUTPUT__
+ERROR:  malformed array literal: "7"
+```
+```sql
+SELECT ARRAY[1, 2] || NULL;                -- so is an undecorated NULL
+__OUTPUT__
+ ?column?
+----------
+ {1,2}
+(1 row)
+```
+```sql
+SELECT array_append(ARRAY[1, 2], NULL);    -- this might have been meant
+__OUTPUT__
+ array_append
+--------------
+ {1,2,NULL}
+```
+
+In the examples above, the parser sees an integer array on one side of the concatenation operator, and a constant of undetermined type on the other. The heuristic it uses to resolve the constant's type is to assume it's of the same type as the operator's other input — in this case, integer array. So the concatenation operator is presumed to represent `array_cat`, not `array_append`. When that's the wrong choice, it could be fixed by casting the constant to the array's element type; but explicit use of `array_append` might be a preferable solution.
+
+## Searching in arrays
+
+To search for a value in an array, each value must be checked. This can be done manually, if you know the size of the array. For example:
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter[1] = 10000 OR
+                            pay_by_quarter[2] = 10000 OR
+                            pay_by_quarter[3] = 10000 OR
+                            pay_by_quarter[4] = 10000;
+```
+
+However, this quickly becomes tedious for large arrays, and is not helpful if the size of the array is unknown. An alternative method is described in [Row and Array Comparisons](https://www.postgresql.org/docs/9.3/functions-comparisons.html). The above query could be replaced by:
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ANY (pay_by_quarter);
+```
+
+In addition, you can find rows where the array has all values equal to 10000 with:
+
+```sql
+SELECT * FROM sal_emp WHERE 10000 = ALL (pay_by_quarter);
+```
+
+Alternatively, the `generate_subscripts` function can be used. For example:
+
+```sql
+SELECT * FROM
+   (SELECT pay_by_quarter,
+           generate_subscripts(pay_by_quarter, 1) AS s
+      FROM sal_emp) AS foo
+ WHERE pay_by_quarter[s] = 10000;
+```
+
+You can also search an array using the `&&` operator, which checks whether the left operand overlaps with the right operand. For instance:
+
+```sql
+SELECT * FROM sal_emp WHERE pay_by_quarter && ARRAY[10000];
+```
+
+!!! Note
+    Arrays are not sets; searching for specific array elements can be a sign of database misdesign. Consider using a separate table with a row for each item that would be an array element. This is easier to search, and is likely to scale better for a large number of elements.
+
+## Array input and output syntax
+
+The external text representation of an array value consists of items that are interpreted according to the I/O conversion rules for the array's element type, plus decoration that indicates the array structure. The decoration consists of curly braces (`{` and `}`) around the array value plus delimiter characters between adjacent items. The delimiter character is usually a comma (`,`) but can be something else: it is determined by the `typdelim` setting for the array's element type. Among the standard data types provided in the PostgreSQL distribution, all use a comma, except for type box, which uses a semicolon (`;`). In a multidimensional array, each dimension (row, plane, cube, etc.) gets its own level of curly braces, and delimiters must be written between adjacent curly-braced entities of the same level.
+
+The array output routine will put double quotes around element values if they are empty strings, contain curly braces, delimiter characters, double quotes, backslashes, or white space, or match the word `NULL`. Double quotes and backslashes embedded in element values will be backslash-escaped. For numeric data types it is safe to assume that double quotes will never appear, but for textual data types one should be prepared to cope with either the presence or absence of quotes.
+
+By default, the lower bound index value of an array's dimensions is set to one. To represent arrays with other lower bounds, the array subscript ranges can be specified explicitly before writing the array contents. This decoration consists of square brackets (`[]`) around each array dimension's lower and upper bounds, with a colon (`:`) delimiter character in between. The array dimension decoration is followed by an equal sign (`=`). For example:
+
+```sql
+SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
+ FROM (SELECT '[1:1][-2:-1][3:5]={{{1,2,3},{4,5,6}}}'::int[] AS f1) AS ss;
+__OUTPUT__
+ e1 | e2
+----+----
+  1 |  6
+(1 row)
+```
+
+The array output routine includes explicit dimensions in its result only when there are one or more lower bounds different from one.
+
+If the value written for an element is `NULL` (in any case variant), the element is taken to be NULL. The presence of any quotes or backslashes disables this and allows the literal string value "NULL" to be entered. Also, for backward compatibility with pre-8.2 versions of PostgreSQL, the [`array_nulls`](https://www.postgresql.org/docs/9.3/runtime-config-compatible.html#GUC-ARRAY-NULLS) configuration parameter can be turned off to suppress recognition of `NULL` as a NULL.
+
+As shown previously, when writing an array value you can use double quotes around any individual array element. You must do so if the element value would otherwise confuse the array-value parser. For example, elements containing curly braces, commas (or the data type's delimiter character), double quotes, backslashes, or leading or trailing whitespace must be double-quoted. Empty strings and strings matching the word `NULL` must be quoted, too. To put a double quote or backslash in a quoted array element value, precede it with a backslash. Alternatively, you can avoid quotes and use backslash-escaping to protect all data characters that would otherwise be taken as array syntax.
+
+You can add whitespace before a left brace or after a right brace. You can also add whitespace before or after any individual item string. In all of these cases the whitespace will be ignored. However, whitespace within double-quoted elements, or surrounded on both sides by non-whitespace characters of an element, is not ignored.
+
+!!! Note
+    The `ARRAY` constructor syntax is often easier to work with than the array-literal syntax when writing array values in SQL commands. In `ARRAY`, individual element values are written the same way they would be written when not members of an array.
+
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/composite_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/composite_types.mdx
new file mode 100644
index 00000000000..f5a7f8f38e5
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/composite_types.mdx
@@ -0,0 +1,300 @@
+---
+title: "Composite types"
+---
+
+| Name                                                                 | Native | Alias | Description                                   |
+| -------------------------------------------------------------------- | ------ | ----- | --------------------------------------------- |
+| `CREATE TYPE <type_name> AS (col1 data type, col2 datatype,..)`      | ✅     |       | Structure of a row or record.                 |
+
+## Overview
+
+A composite type represents the structure of a row or record; it is essentially just a list of field names and their data types. PostgreSQL allows composite types to be used in many of the same ways that simple types can be used. For example, a column of a table can be declared to be of a composite type.
+
+## Declaration of composite types
+
+Here are two simple examples of defining composite types:
+
+```sql
+CREATE TYPE complex AS (
+    r       double precision,
+    i       double precision
+);
+
+CREATE TYPE inventory_item AS (
+    name            text,
+    supplier_id     integer,
+    price           numeric
+);
+```
+
+The syntax is comparable to `CREATE TABLE`, except that only field names and types can be specified. No constraints (such as `NOT NULL`) can presently be included. The AS keyword is essential because without it, the system will think a different kind of `CREATE TYPE` command is meant, and you can get odd syntax errors.
+
+Having defined the types, we can use them to create tables:
+
+```sql
+CREATE TABLE on_hand (
+    item      inventory_item,
+    count     integer
+);
+
+INSERT INTO on_hand VALUES (ROW('fuzzy dice', 42, 1.99), 1000);
+```
+
+or functions:
+
+```sql
+CREATE FUNCTION price_extension(inventory_item, integer) RETURNS numeric
+AS 'SELECT $1.price * $2' LANGUAGE SQL;
+
+SELECT price_extension(item, 10) FROM on_hand;
+```
+
+Whenever you create a table, a composite type is also automatically created, with the same name as the table, to represent the table's row type. For example, had we said:
+
+```sql
+CREATE TABLE inventory_item (
+    name            text,
+    supplier_id     integer REFERENCES suppliers,
+    price           numeric CHECK (price > 0)
+);
+```
+
+then the same `inventory_item` composite type shown above would come into being as a byproduct, and could be used just as above. However there is an important restriction of the current implementation: since no constraints are associated with a composite type, the constraints shown in the table definition do not apply to values of the composite type outside the table. (A partial workaround is to use domain types as members of composite types.)
+
+## Constructing composite values
+
+To write a composite value as a literal constant, enclose the field values in parentheses and separate them by commas. You can put double quotes around any field value, and must do so if it contains commas or parentheses. Therefore, the general format of a composite constant is the following:
+
+```sql 
+'( val1 , val2 , ... )'
+```
+
+An example is:
+
+```sql
+'("fuzzy dice",42,1.99)'
+```
+
+which would be a valid value of the `inventory_item` type defined above. To make a field be NULL, write no characters at all in its position in the list. For example, this constant specifies a NULL third field:
+
+```sql
+'("fuzzy dice",42,)'
+```
+
+If you want an empty string rather than NULL, write double quotes:
+
+```sql
+'("",42,)'
+```
+
+Here the first field is a non-NULL empty string, the third is NULL.
+
+!!! Note
+    These constants are actually only a special case of the generic type constants discussed in [Constants of Other Types](https://www.postgresql.org/docs/9.3/sql-syntax-lexical.html#SQL-SYNTAX-CONSTANTS-GENERIC). The constant is initially treated as a string and passed to the composite-type input conversion routine. An explicit type specification might be necessary to tell which type to convert the constant to.
+
+The `ROW` expression syntax can also be used to construct composite values. In most cases this is considerably simpler to use than the string-literal syntax since you don't have to worry about multiple layers of quoting. We already used this method above:
+
+```sql
+ROW('fuzzy dice', 42, 1.99)
+ROW('', 42, NULL)
+```
+
+The `ROW` keyword is actually optional as long as you have more than one field in the expression, so these can be simplified to:
+
+```sql
+('fuzzy dice', 42, 1.99)
+('', 42, NULL)
+```
+
+## Accessing composite types
+
+To access a field of a composite column, one writes a dot and the field name, much like selecting a field from a table name. In fact, it's so much like selecting from a table name that you often have to use parentheses to keep from confusing the parser. For example, you might try to select some subfields from our `on_hand` example table with something like:
+
+```sql
+SELECT item.name FROM on_hand WHERE item.price > 9.99;
+```
+
+However, that doesn't work since the name item is taken to be a table name, not a column name of `on_hand`, per SQL syntax rules. You must write it like this:
+
+```sql
+SELECT (item).name FROM on_hand WHERE (item).price > 9.99;
+```
+
+or if you need to use the table name as well (for instance in a multitable query), like this:
+
+```sql
+SELECT (on_hand.item).name FROM on_hand WHERE (on_hand.item).price > 9.99;
+```
+
+Now the parenthesized object is correctly interpreted as a reference to the item column, and then the subfield can be selected from it.
+
+Similar syntactic issues apply whenever you select a field from a composite value. For instance, to select just one field from the result of a function that returns a composite value, you'd need to write something like:
+
+```sql
+SELECT (my_func(...)).field FROM ...
+```
+
+Without the extra parentheses, this command generates a syntax error.
+
+## Modifying composite types
+
+Here are some examples of the proper syntax for inserting and updating composite columns. First, inserting or updating a whole column:
+
+```sql
+INSERT INTO mytab (complex_col) VALUES((1.1,2.2));
+
+UPDATE mytab SET complex_col = ROW(1.1,2.2) WHERE ...;
+```
+
+The first example omits `ROW`, the second uses it. It can be done either way.
+
+We can update an individual subfield of a composite column:
+
+```sql
+UPDATE mytab SET complex_col.r = (complex_col).r + 1 WHERE ...;
+```
+
+Notice here that we don't need to (and indeed cannot) put parentheses around the column name appearing just after `SET`, but we do need parentheses when referencing the same column in the expression to the right of the equal sign.
+
+And we can specify subfields as targets for `INSERT`, too:
+
+```sql
+INSERT INTO mytab (complex_col.r, complex_col.i) VALUES(1.1, 2.2);
+```
+
+Had we not supplied values for all the subfields of the column, the remaining subfields would have been filled with null values.
+
+## Using composite types in queries
+
+There are various special syntax rules and behaviors associated with composite types in queries. These rules provide useful shortcuts, but can be confusing if you don't know the logic behind them.
+
+In PostgreSQL, a reference to a table name (or alias) in a query is effectively a reference to the composite value of the table's current row. For example, if we had a table `inventory_item` as shown in [Declaration of composite types](#declaration-of-composite-types), we could write:
+
+```sql
+SELECT c FROM inventory_item c;
+```
+
+This query produces a single composite-valued column, so we might get output like:
+
+```sql
+__OUTPUT__
+           c
+------------------------
+ ("fuzzy dice",42,1.99)
+(1 row)
+```
+
+Simple names are matched to column names before table names, so this example works only because there is no column named `c` in the query's tables.
+
+The ordinary qualified-column-name syntax `table_name.column_name` can be understood as applying field selection to the composite value of the table's current row. For efficiency reasons, it's not actually implemented that way.
+
+When we write
+
+```sql
+SELECT c.* FROM inventory_item c;
+```
+
+then, according to the SQL standard, we should get the contents of the table expanded into separate columns:
+
+```sql
+__OUTPUT__
+    name    | supplier_id | price
+------------+-------------+-------
+ fuzzy dice |          42 |  1.99
+(1 row)
+```
+
+as if the query were:
+
+```sql
+SELECT c.name, c.supplier_id, c.price FROM inventory_item c;
+```
+
+PostgreSQL applies this expansion behavior to any composite-valued expression, although as shown in [Accessing composite types](#accessing-composite-types), you need to write parentheses around the value that `.*` is applied to whenever it's not a simple table name. For example, if `myfunc()` is a function returning a composite type with columns `a`, `b`, and `c`, then these two queries have the same result:
+
+```sql
+SELECT (myfunc(x)).* FROM some_table;
+SELECT (myfunc(x)).a, (myfunc(x)).b, (myfunc(x)).c FROM some_table;
+```
+
+!!! note Tip
+    PostgreSQL handles column expansion by actually transforming the first form into the second. So, in this example, `myfunc()` would get invoked three times per row with either syntax. If it's an expensive function you may wish to avoid that, which you can do with a query like:
+
+    ```sql
+    SELECT (m).* FROM (SELECT myfunc(x) AS m FROM some_table OFFSET 0) ss;
+    ```
+
+    The `OFFSET 0` clause keeps the optimizer from "flattening" the sub-select to arrive at the form with multiple calls of `myfunc()`.
+
+The `composite_value.*` syntax results in column expansion of this kind when it appears at the top level of a `SELECT` output list, a `RETURNING` list in `INSERT`/`UPDATE`/`DELETE`, a `VALUES` clause, or a row constructor. In all other contexts (including when nested inside one of those constructs), attaching `.*` to a composite value does not change the value, since it means "all columns" and so the same composite value is produced again. For example, if `somefunc()` accepts a composite-valued argument, these queries are the same:
+
+```sql
+SELECT somefunc(c.*) FROM inventory_item c;
+SELECT somefunc(c) FROM inventory_item c;
+```
+
+In both cases, the current row of `inventory_item` is passed to the function as a single composite-valued argument. Even though `.*` does nothing in such cases, using it is good style, since it makes clear that a composite value is intended. In particular, the parser considers `c` in `c.*` to refer to a table name or alias, not to a column name, so that there is no ambiguity; whereas without `.*`, it is not clear whether `c` means a table name or a column name, and in fact the column-name interpretation is preferred if there is a column named `c`.
+
+Another example demonstrating these concepts is that all these queries mean the same thing:
+
+```sql
+SELECT * FROM inventory_item c ORDER BY c;
+SELECT * FROM inventory_item c ORDER BY c.*;
+SELECT * FROM inventory_item c ORDER BY ROW(c.*);
+```
+
+All of these `ORDER BY` clauses specify the row's composite value. However, if `inventory_item` contained a column named `c`, the first case would be different from the others, as it would mean to sort by that column only. Given the column names previously shown, these queries are also equivalent to those above:
+
+```sql
+SELECT * FROM inventory_item c ORDER BY ROW(c.name, c.supplier_id, c.price);
+SELECT * FROM inventory_item c ORDER BY (c.name, c.supplier_id, c.price);
+```
+
+Another special syntactical behavior associated with composite values is that we can use functional notation for extracting a field of a composite value. The simple way to explain this is that the notations `field(table)` and `table.field` are interchangeable. For example, these queries are equivalent:
+
+```sql
+SELECT c.name FROM inventory_item c WHERE c.price > 1000;
+SELECT name(c) FROM inventory_item c WHERE price(c) > 1000;
+```
+
+Moreover, if we have a function that accepts a single argument of a composite type, we can call it with either notation. These queries are all equivalent:
+
+```sql
+SELECT somefunc(c) FROM inventory_item c;
+SELECT somefunc(c.*) FROM inventory_item c;
+SELECT c.somefunc FROM inventory_item c;
+```
+
+This equivalence between functional notation and field notation makes it possible to use functions on composite types to implement "computed fields". An application using the last query above wouldn't need to be directly aware that `somefunc` isn't a real column of the table.
+
+!!! note Tip
+    Because of this behavior, it's unwise to give a function that takes a single composite-type argument the same name as any of the fields of that composite type. If there is ambiguity, the field-name interpretation is preferred, so that such a function could not be called without tricks. One way to force the function interpretation is to schema-qualify the function name, that is, write `schema.func(compositevalue)`.
+
+## Composite type input and output syntax
+
+The external text representation of a composite value consists of items that are interpreted according to the I/O conversion rules for the individual field types, plus decoration that indicates the composite structure. The decoration consists of parentheses (`(` and `)`) around the whole value, plus commas (`,`) between adjacent items. Whitespace outside the parentheses is ignored, but within the parentheses it is considered part of the field value, and might or might not be significant depending on the input conversion rules for the field data type. For example, in:
+
+```sql
+'(  42)'
+```
+
+The whitespace is ignored if the field type is integer, but not if it is text.
+
+As shown previously, when writing a composite value you can write double quotes around any individual field value. You must do so if the field value would otherwise confuse the composite-value parser. In particular, fields containing parentheses, commas, double quotes, or backslashes must be double-quoted. To put a double quote or backslash in a quoted composite field value, precede it with a backslash. Also, a pair of double quotes within a double-quoted field value is taken to represent a double quote character, analogously to the rules for single quotes in SQL literal strings. Alternatively, you can avoid quoting and use backslash-escaping to protect all data characters that would otherwise be taken as composite syntax.
+
+A completely empty field value (no characters at all between the commas or parentheses) represents a NULL. To write a value that is an empty string rather than NULL, write `""`.
+
+The composite output routine puts double quotes around field values if they are empty strings or contain parentheses, commas, double quotes, backslashes, or white space. Doing so for white space is not essential, but aids legibility. Double quotes and backslashes embedded in field values are doubled.
+
+!!! Note
+    Remember that what you write in an SQL command is first interpreted as a string literal, and then as a composite. This doubles the number of backslashes you need (assuming escape string syntax is used). For example, to insert a text field containing a double quote and a backslash in a composite value, you'd need to write:
+    
+    ```sql
+    INSERT ... VALUES ('("\"\\")');
+    ```
+
+    The string-literal processor removes one level of backslashes, so that what arrives at the composite-value parser looks like (`"\"\\"`). In turn, the string fed to the text data type's input routine becomes `"\`. If we were working with a data type whose input routine also treated backslashes specially, `bytea` for example, we might need as many as eight backslashes in the command to get one backslash into the stored composite field. Dollar quoting can be used to avoid the need to double backslashes.
+
+!!! note Tip
+    The `ROW` constructor syntax is usually easier to work with than the composite-literal syntax when writing composite values in SQL commands. In `ROW`, individual field values are written the same way they would be written when not members of a composite.
+
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/enumerated_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/enumerated_types.mdx
new file mode 100644
index 00000000000..96b83bcba1e
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/enumerated_types.mdx
@@ -0,0 +1,32 @@
+---
+title: "Enumerated types"
+---
+
+
+| Name      | Native | Alias | Description                                   |
+| --------- | ------ | ----- | --------------------------------------------- |
+| `ENUM`    | ✅     |       | Static, ordered set of values, 4 bytes storage, max length is limited by `NAMEDATALEN` setting into PostgreSQL. |
+
+## Example
+
+This example shows how to create `ENUM` types and use it:
+
+```sql
+CREATE TYPE city AS ENUM('Pune','Mumbai','Chennai');
+
+CREATE TABLE shops(name text, location city);
+
+INSERT INTO shops VALUES('Puma',`Mumbai` );
+
+SELECT * FROM shops;
+__OUTPUT__
+  name  |  location
+--------+-----------
+  Puma  | Mumbai
+```
+
+`ENUM` types are case sensitive, and whitespace in `ENUM` types is also significant.
+
+The `ENUM` types and its labels are stored in `pg_enum` system catalog.
+
+For more information on enumerated data types, see [PostgreSQL docs](https://www.postgresql.org/docs/current/datatype-enum.html).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/geometric_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/geometric_types.mdx
new file mode 100644
index 00000000000..3447d7e6b9b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/geometric_types.mdx
@@ -0,0 +1,20 @@
+---
+title: "Geometric types"
+---
+
+| Name            | Native | Alias | Description                                                                                   |
+| --------------- | -------| ----- | ---------------------------------------------------------------------------------------------- |
+| `POINT`         | ✅     |       | Point on a plane, 16 bytes storage, represented as `(x,y)`.               |
+| `LINE`          | ✅     |       | Infinite line, 32 bytes storage, represented as `{A,B,C}`.                |
+| `LSEG`          | ✅     |       | Finite line segment, 32 bytes storage, represented as `((x1,y1),(x2,y2))`. |
+| `BOX`           | ✅     |       | Rectangular box, 32 bytes storage, represented as `((x1,y1),(x2,y2))`.    |
+| `PATH`          | ✅     |       | Closed path (similar to polygon), 16 + 16n bytes storage, represented as `((x1,y1),...)`. |
+| `PATH`          | ✅     |       | Open path, 16 + 16n bytes storage, represented as `[(x1,y1),...]`.  |
+| `POLYGON`       | ✅     |       | Polygon (similar to closed path), 40 + 16n bytes storage, represented as `((x1,y1),...)`. |
+| `CIRCLE`        | ✅     |       | Circle, 24 bytes storage, represented as `<(x,y),r>` (center point and radius).     |
+
+## Overview
+
+Geometric data types represent two-dimensional spatial objects.
+
+For more information on geometric data types, see [PostgreSQL docs](https://www.postgresql.org/docs/current/datatype-geometric.html).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/index.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/index.mdx
new file mode 100644
index 00000000000..dd13602a7d1
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/index.mdx
@@ -0,0 +1,31 @@
+---
+title: "Data types"
+indexCards: simple
+description: "Provides descriptive information about specific data types"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.011.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.043.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/02_data_types/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/02_data_types
+navigation:
+ - 01_numeric_types
+ - monetary_types
+ - 02_character_types
+ - 03_binary_data
+ - 04_date_time_types
+ - 05_boolean_type
+ - enumerated_types
+ - geometric_types
+ - network_address_types
+ - 06_xml_type
+ - array_types
+ - composite_types
+ - range_types
+ - object_identifier_types
+ - pseudo_types
+---
+
+<div id="data_types" class="registered_link"></div>
+EDB Postgres Advanced Server has the following data types.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/monetary_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/monetary_types.mdx
new file mode 100644
index 00000000000..928f51531e8
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/monetary_types.mdx
@@ -0,0 +1,32 @@
+---
+title: Monetary types
+source:
+   url: https://www.postgresql.org/docs/current/datatype-money.html
+   timestamp: 2023-09-11
+---
+
+| Data type | Native | Alias  |                                     Description                                       |
+| --------- | ------ | ------ | ------------------------------------------------------------------------------------- |
+| `MONEY`   |        | ✅     | Currency amount, 8 byte storage, -92233720368547758.08 to +92233720368547758.07 range |
+
+## Overview
+
+The `MONEY` type stores a currency amount with a fixed fractional precision. The fractional precision is determined by the database's `lc_monetary` setting. The range assumes there are two fractional digits. Input is accepted in a variety of formats, including integer and floating-point literals, as well as typical currency formatting, such as '$1,000.00'. Output is generally in the latter form but depends on the locale.
+
+Since the output of this data type is locale-sensitive, it might not work to load money data into a database that has a different setting of `lc_monetary`. To avoid problems, before restoring a dump into a new database make sure `lc_monetary` has the same or equivalent value as in the database that was dumped.
+
+Values of `NUMERIC`, `INT`, and `BIGINT` data types can be cast to `MONEY`. Conversion from `REAL` and `DOUBLE PRECISION` data types can be done by casting to `NUMERIC` first, for example:
+
+```sql
+SELECT '12.34'::float8::numeric::money;
+```
+
+However, this is not recommended. Floating point numbers shouldn't be used to handle money due to the potential for rounding errors.
+
+A money value can be cast to `NUMERIC` without loss of precision. Conversion to other types could potentially lose precision, and must also be done in two stages:
+
+```sql
+SELECT '52093.89'::money::numeric::float8;
+```
+
+Division of a money value by an integer value is performed with truncation of the fractional part towards zero. To get a rounded result, divide by a floating-point value, or cast the money value to numeric before dividing and back to money afterwards. (The latter is preferable to avoid risking precision loss.) When a money value is divided by another money value, the result is double precision (that is, a pure number, not money); the currency units cancel each other out in the division.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/network_address_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/network_address_types.mdx
new file mode 100644
index 00000000000..858c8f6a536
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/network_address_types.mdx
@@ -0,0 +1,18 @@
+---
+title: "Network address types"
+---
+
+| Name      | Native | Alias  | Description                                                                       |
+|-----------|--------|--------|-----------------------------------------------------------------------------------|
+| `CIDR`    | ✅     |        | IPV4 and IPV6 networks, 7 or 19 bytes storage.                                    |
+| `INET`    | ✅     |        | IPV4 and IPV6 hosts and networks, 7 or 19 bytes storage.                          |
+| `MACADDR` | ✅     |        | MAC addresses, 6 bytes storage.                                                   |
+| `MACADDR8`| ✅     |        | MAC addresses (EUI-64 format), 8 bytes storage.                                   |
+
+## Overview
+
+EDB Postgres Advanced Server offers data types to store IPV4, IPV6, and MAC addresses.
+
+These data types offer input error checking and specialized operators and functions.
+
+For more information on network address types, see [PostgreSQL docs](https://www.postgresql.org/docs/current/datatype-net-types.html).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/object_identifier_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/object_identifier_types.mdx
new file mode 100644
index 00000000000..0059b2366af
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/object_identifier_types.mdx
@@ -0,0 +1,63 @@
+---
+title: "Object identifier types"
+---
+
+|      Data type      | Native | Alias |                Description             |
+| ------------------- | ------ | ----- | -------------------------------------- |
+| `oid` | ✅ |     |  The numeric object identifier. | 
+| `regproc` | ✅ |      | The name of the function. | 
+| `regprocedure`| ✅ |      | The function with argument types. | 
+| `regoper` | ✅ |      | The name of the operator. | 
+| `regoperator` | ✅ |      | The operator with argument types. | 
+| `regclass` | ✅ |      | The name of the relation. | 
+| `regtype` | ✅ |      | The name of the data type. | 
+| `regconfig` | ✅ |      | The text search configuration. | 
+| `regdictionary` | ✅ |      | The text search dictionary. |
+
+## Overview
+
+Object identifiers (OIDs) are used internally by PostgreSQL as primary keys for various system tables. OIDs are not added to user-created tables, unless `WITH OIDS` is specified when the table is created, or the [`default_with_oids`](https://www.postgresql.org/docs/9.3/runtime-config-compatible.html#GUC-DEFAULT-WITH-OIDS) configuration variable is enabled. Type `oid` represents an object identifier. There are also several alias types for `oid`: `regproc`, `regprocedure`, `regoper`, `regoperator`, `regclass`, `regtype`, `regconfig`, and `regdictionary`. 
+
+The `oid` type is currently implemented as an unsigned four-byte integer. Therefore, it is not large enough to provide database-wide uniqueness in large databases, or even in large individual tables. So, using a user-created table's OID column as a primary key is discouraged. OIDs are best used only for references to system tables.
+
+The `oid` type itself has few operations beyond comparison. It can be cast to integer, however, and then manipulated using the standard integer operators. Beware of possible signed-versus-unsigned confusion if you do this.
+
+The OID alias types have no operations of their own except for specialized input and output routines. These routines are able to accept and display symbolic names for system objects, rather than the raw numeric value that type `oid` would use. The alias types allow simplified lookup of OID values for objects. For example, to examine the pg_attribute rows related to a table` mytable`, one could write:
+
+```sql
+SELECT * FROM pg_attribute WHERE attrelid = 'mytable'::regclass;
+```
+rather than:
+
+```sql
+SELECT * FROM pg_attribute
+  WHERE attrelid = (SELECT oid FROM pg_class WHERE relname = 'mytable');
+```
+
+While that doesn't look all that bad by itself, it's still oversimplified. A far more complicated sub-select would be needed to select the right OID if there are multiple tables named `mytable` in different schemas. The `regclass` input converter handles the table lookup according to the schema path setting, and so it does the "right thing" automatically. Similarly, casting a table's OID to `regclass` is handy for symbolic display of a numeric OID.
+
+The following table lists the available object identifier types:
+
+| Name | References | Description | Value example |
+| ---- | ---------- | ----------- | ------------- |
+| `oid` | Any | Numeric object identifier | `564182` |
+| `regproc` | `pg_proc` | Function name | `sum` |
+| `regprocedure` | `pg_proc	` | Function with argument types | `sum(int4)` |
+| `regoper` | `pg_operator` | Operator name	| `+` |
+| `regoperator` | `pg_operator` | Operator with argument types | `*(integer,integer) or -(NONE,integer)` |
+| `regclass` | `pg_class` | Relation name | `pg_type` |
+| `regtype` | `pg_type` | Data type name | `integer` |
+| `regconfig` | `pg_ts_config` | Text search configuration | `english` |
+| `regdictionary` | `pg_ts_dict` | Text search dictionary | `simple` |	
+
+All of the OID alias types accept schema-qualified names, and display schema-qualified names on output if the object can't be found in the current search path without being qualified. The `regproc` and `regoper` alias types accept only input names that are unique (not overloaded), so they are of limited use. For most uses, `regprocedure` or `regoperator` are more appropriate. For `regoperator`, unary operators are identified by writing `NONE` for the unused operand.
+
+An additional property of the OID alias types is the creation of dependencies. If a constant of one of these types appears in a stored expression (such as a column default expression or view), it creates a dependency on the referenced object. For example, if a column has a default expression `nextval('my_seq'::regclass)`, PostgreSQL understands that the default expression depends on the sequence `my_seq`. The system doesn't let the sequence be dropped without first removing the default expression.
+
+Another identifier type used by the system is `xid`, or transaction (abbreviated xact) identifier. This is the data type of the system columns `xmin` and `xmax`. Transaction identifiers are 32-bit quantities.
+
+A third identifier type used by the system is `cid`, or command identifier. This is the data type of the system columns `cmin` and `cmax`. Command identifiers are also 32-bit quantities.
+
+A final identifier type used by the system is `tid`, or tuple identifier (row identifier). This is the data type of the system column `ctid`. A tuple ID is a pair (block number, tuple index within block) that identifies the physical location of the row within its table.
+
+For more information on system columns, see the [PostgreSQL documentation](https://www.postgresql.org/docs/9.3/ddl-system-columns.html).
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/pseudo_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/pseudo_types.mdx
new file mode 100644
index 00000000000..ddb1b1c5926
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/pseudo_types.mdx
@@ -0,0 +1,31 @@
+---
+title: "Pseudo-types"
+---
+
+|      Data type      | Native | Alias |                Description             |
+| ------------------- | ------ | ----- | -------------------------------------- |
+| `any` | ✅  |        | Indicates that a function accepts any input data type. |
+| `anyelement` | ✅  |        | Indicates that a function accepts any data type. For more information, see [Polymorphic types](https://www.postgresql.org/docs/9.3/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC) in the PostgreSQL documentation. |
+| `anyarray` | ✅  |        | Indicates that a function accepts any array data type. For more information, see [Polymorphic types](https://www.postgresql.org/docs/9.3/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC) in the PostgreSQL documentation. |
+| `anynonarray` | ✅  |        | Indicates that a function accepts any non-array data type. For more information, see [Polymorphic types](https://www.postgresql.org/docs/9.3/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC) in the PostgreSQL documentation. |
+| `anyenum` | ✅  |        | Indicates that a function accepts any enum data type. For more information, see [Polymorphic types](https://www.postgresql.org/docs/9.3/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC) and [Enumerated types](https://www.postgresql.org/docs/9.3/datatype-enum.html) in the PostgreSQL documentation. |
+| `anyrange` | ✅  |        | Indicates that a function accepts any range data type. For more information, see [Polymorphic types](https://www.postgresql.org/docs/9.3/extend-type-system.html#EXTEND-TYPES-POLYMORPHIC) and [Range types](https://www.postgresql.org/docs/9.3/rangetypes.html) in the PostgreSQL documentation. |
+| `cstring` | ✅  |        | Indicates that a function accepts or returns a null-terminated C string. |
+| `internal` | ✅  |        | Indicates that a function accepts or returns a server-internal data type. |
+| `language_handler` | ✅  |        | A procedural language call handler is declared to return `language_handler`. |
+| `fdw_handler` | ✅  |        | A foreign-data wrapper handler is declared to return `fdw_handler`. |
+| `record` | ✅  |        | Identifies a function taking or returning an unspecified row type. |
+| `trigger` | ✅  |        | A trigger function is declared to return trigger. |
+| `event_trigger` | ✅  |        | An event trigger function is declared to return `event_trigger`. |
+| `void` | ✅  |        | Indicates that a function returns no value. |
+| `opaque` | ✅  |        | An obsolete type name that formerly served all the above purposes. |
+
+## Overview
+
+The PostgreSQL type system contains a number of special-purpose entries that are collectively called pseudo-types. A pseudo-type cannot be used as a column data type, but it can be used to declare a function's argument or result type. Each of the available pseudo-types is useful in situations where a function's behavior does not correspond to simply taking or returning a value of a specific SQL data type. 
+
+Functions coded in C (whether built-in or dynamically loaded) can be declared to accept or return any of these pseudo data types. It is up to the function author to ensure that the function will behave safely when a pseudo-type is used as an argument type.
+
+Functions coded in procedural languages can use pseudo-types only as allowed by their implementation languages. At present most procedural languages forbid use of a pseudo-type as an argument type, and allow only void and record as a result type (plus trigger or event_trigger when the function is used as a trigger or event trigger). Some also support polymorphic functions using the types `anyelement`, `anyarray`, `anynonarray`, `anyenum`, and `anyrange`.
+
+The `internal` pseudo-type is used to declare functions that are meant only to be called internally by the database system, and not by direct invocation in an SQL query. If a function has at least one internal-type argument then it cannot be called from SQL. To preserve the type safety of this restriction it is important to follow this coding rule: do not create any function that is declared to return `internal` unless it has at least one internal argument.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/02_data_types/range_types.mdx b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/range_types.mdx
new file mode 100644
index 00000000000..fcdd2bb4e13
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/02_data_types/range_types.mdx
@@ -0,0 +1,223 @@
+---
+title: "Range types"
+---
+
+|    Name     | Native | Alias |               Description               |
+| ----------- | ------ | ----- | --------------------------------------- |
+| `int4range` | ✅      |       | Range of `integer`.                     |
+| `int8range` | ✅      |       | Range of `bigint`.                      |
+| `numrange`  | ✅      |       | Range of `numeric`.                     |
+| `tsrange`   | ✅      |       | Range of `timestamp without time zone`. |
+| `tstzrange` | ✅      |       | Range of `timestamp with time zone`.    |
+| `daterange` | ✅      |       | Range of `date`.                        |
+
+
+## Overview
+
+Range types are data types representing a range of values of some element type (called the range's subtype). For instance, ranges of `timestamp` might be used to represent the ranges of time that a meeting room is reserved. In this case the data type is `tsrange` (short for timestamp range), and `timestamp` is the subtype. The subtype must have a total order so that it is well-defined whether element values are within, before, or after a range of values.
+
+Range types are useful because they represent many element values in a single range value, and because concepts such as overlapping ranges can be expressed clearly. The use of time and date ranges for scheduling purposes is the clearest example; but price ranges, measurement ranges from an instrument, and so forth can also be useful.
+
+## Built-in range types
+
+PostgreSQL comes with the following built-in range types:
+
+- `int4range` &mdash; Range of `integer`
+- `int8range` &mdash; Range of `bigint`
+- `numrange` &mdash; Range of `numeric`
+- `tsrange` &mdash; Range of `timestamp without time zone`
+- `tstzrange` &mdash; Range of `timestamp with time zone`
+- `daterange` &mdash; Range of `date`
+
+In addition, you can define your own range types. See the [PostgreSQL documentation](https://www.postgresql.org/docs/9.3/sql-createtype.html), for more information.
+
+## Examples 
+
+```sql
+CREATE TABLE reservation (room int, during tsrange);
+INSERT INTO reservation VALUES
+    (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
+
+-- Containment
+SELECT int4range(10, 20) @> 3;
+
+-- Overlaps
+SELECT numrange(11.1, 22.2) && numrange(20.0, 30.0);
+
+-- Extract the upper bound
+SELECT upper(int8range(15, 25));
+
+-- Compute the intersection
+SELECT int4range(10, 20) * int4range(15, 25);
+
+-- Is the range empty?
+SELECT isempty(numrange(1, 5));
+```
+
+## Inclusive and exclusive bounds
+
+Every non-empty range has two bounds, the lower bound and the upper bound. All points between these values are included in the range. An inclusive bound means that the boundary point itself is included in the range as well, while an exclusive bound means that the boundary point isn't included in the range.
+
+In the text form of a range, an inclusive lower bound is represented by "`[`" while an exclusive lower bound is represented by "`(`". Likewise, an inclusive upper bound is represented by "`]`", while an exclusive upper bound is represented by "`)`". 
+
+The functions `lower_inc` and `upper_inc` test the inclusivity of the lower and upper bounds of a range value, respectively.
+
+## Infinite (unbounded) ranges
+
+The lower bound of a range can be omitted, meaning that all points less than the upper bound are included in the range. Likewise, if the upper bound of the range is omitted, then all points greater than the lower bound are included in the range. If both lower and upper bounds are omitted, all values of the element type are considered to be in the range.
+
+Omitting the lower or upper bound is equivalent to considering that the lower bound is "minus infinity", or the upper bound is "plus infinity", respectively. But note that these infinite values are never values of the range's element type, and can never be part of the range. So there is no such thing as an inclusive infinite bound — if you try to write one, it automatically is converted to an exclusive bound.
+
+Also, some element types have a notion of "infinity", but that is just another value so far as the range type mechanisms are concerned. For example, in timestamp ranges, `[today,]` means the same thing as `[today,)`. But `[today,infinity]` means something different from `[today,infinity)` — the latter excludes the special timestamp value infinity.
+
+The functions `lower_inf` and `upper_inf` test for infinite lower and upper bounds of a range, respectively.
+
+## Range input/output
+
+The input for a range value must follow one of the following patterns:
+
+```sql
+(lower-bound,upper-bound)
+(lower-bound,upper-bound]
+[lower-bound,upper-bound)
+[lower-bound,upper-bound]
+empty
+```
+
+The parentheses or brackets indicate whether the lower and upper bounds are exclusive or inclusive, as described previously. Notice that the final pattern is empty, which represents an empty range (a range that contains no points).
+
+The lower-bound may be either a string that is valid input for the subtype, or empty to indicate no lower bound. Likewise, upper-bound may be either a string that is valid input for the subtype, or empty to indicate no upper bound.
+
+Each bound value can be quoted using double quotes (`"`). This is necessary if the bound value contains parentheses, brackets, commas, double quotes, or backslashes, since these characters would otherwise be taken as part of the range syntax. To put a double quote or backslash in a quoted bound value, precede it with a backslash. Also, a pair of double quotes within a double-quoted bound value is taken to represent a double quote character, analogously to the rules for single quotes in SQL literal strings. Alternatively, you can avoid quoting and use backslash-escaping to protect all data characters that would otherwise be taken as range syntax. Also, to write a bound value that is an empty string, write `""`, since writing nothing means an infinite bound.
+
+Whitespace is allowed before and after the range value, but any whitespace between the parentheses or brackets is taken as part of the lower or upper bound value. Depending on the element type, it might or might not be significant.
+
+Examples:
+
+```sql
+-- includes 3, does not include 7, and does include all points in between
+SELECT '[3,7)'::int4range;
+
+-- does not include either 3 or 7, but includes all points in between
+SELECT '(3,7)'::int4range;
+
+-- includes only the single point 4
+SELECT '[4,4]'::int4range;
+
+-- includes no points (and will be normalized to 'empty')
+SELECT '[4,4)'::int4range;
+```
+
+## Constructing ranges
+
+Each range type has a constructor function with the same name as the range type. Using the constructor function is frequently more convenient than writing a range literal constant, since it avoids the need for extra quoting of the bound values. The constructor function accepts two or three arguments. The two-argument form constructs a range in standard form (lower bound inclusive, upper bound exclusive), while the three-argument form constructs a range with bounds of the form specified by the third argument. The third argument must be one of the strings "`()`", "`(]`", "`[)`", or "`[]`". For example:
+
+```sql
+-- The full form is: lower bound, upper bound, and text argument indicating
+-- inclusivity/exclusivity of bounds.
+SELECT numrange(1.0, 14.0, '(]');
+
+-- If the third argument is omitted, '[)' is assumed.
+SELECT numrange(1.0, 14.0);
+
+-- Although '(]' is specified here, on display the value will be converted to
+-- canonical form, since int8range is a discrete range type (see below).
+SELECT int8range(1, 14, '(]');
+
+-- Using NULL for either bound causes the range to be unbounded on that side.
+SELECT numrange(NULL, 2.2);
+```
+## Discrete range types
+
+A discrete range is one whose element type has a well-defined "step", such as integer or date. In these types two elements can be said to be adjacent, when there are no valid values between them. This contrasts with continuous ranges, where it's always (or almost always) possible to identify other element values between two given values. For example, a range over the `numeric` type is continuous, as is a range over `timestamp`. Even though timestamp has limited precision, and so could theoretically be treated as discrete, it's better to consider it continuous since the step size is normally not of interest.
+
+Another way to think about a discrete range type is that there is a clear idea of a "next" or "previous" value for each element value. Knowing that, it is possible to convert between inclusive and exclusive representations of a range's bounds, by choosing the next or previous element value instead of the one originally given. For example, in an integer range type `[4,8]` and `(3,9)` denote the same set of values; but this would not be so for a range over numeric.
+
+A discrete range type should have a *canonicalization* function that is aware of the desired step size for the element type. The canonicalization function is charged with converting equivalent values of the range type to have identical representations, in particular consistently inclusive or exclusive bounds. If a canonicalization function is not specified, then ranges with different formatting are always treated as unequal, even though they might represent the same set of values in reality.
+
+The built-in range types `int4range`, `int8range`, and `daterange` all use a canonical form that includes the lower bound and excludes the upper bound; that is, `[)`. User-defined range types can use other conventions, however.
+
+## Defining new range types
+
+Users can define their own range types. The most common reason to do this is to use ranges over subtypes not provided among the built-in range types. For example, to define a new range type of subtype `float8`:
+
+```sql
+CREATE TYPE floatrange AS RANGE (
+    subtype = float8,
+    subtype_diff = float8mi
+);
+
+SELECT '[1.234, 5.678]'::floatrange;
+```
+
+Because `float8` has no meaningful "step", we do not define a canonicalization function in this example.
+
+If the subtype is considered to have discrete rather than continuous values, the `CREATE TYPE` command should specify a `canonical` function. The canonicalization function takes an input range value, and must return an equivalent range value that may have different bounds and formatting. The canonical output for two ranges that represent the same set of values, for example the integer ranges `[1, 7]` and `[1, 8)`, must be identical. It doesn't matter which representation you choose to be the canonical one, so long as two equivalent values with different formattings are always mapped to the same value with the same formatting. In addition to adjusting the inclusive/exclusive bounds format, a canonicalization function might round off boundary values, in case the desired step size is larger than what the subtype is capable of storing. For instance, a range type over timestamp could be defined to have a step size of an hour, in which case the canonicalization function would need to round off bounds that weren't a multiple of an hour, or perhaps throw an error instead.
+
+Defining your own range type also allows you to specify a different subtype B-tree operator class or collation to use, so as to change the sort ordering that determines which values fall into a given range.
+
+In addition, any range type that is meant to be used with GiST or SP-GiST indexes should define a subtype difference, or `subtype_diff`, function. The index still works without `subtype_diff`, but it is likely to be considerably less efficient than if a difference function is provided. The subtype difference function takes two input values of the subtype, and returns their difference, for example, `X` minus `Y`, represented as a `float8` value. In our example above, the function that underlies the regular `float8` minus operator can be used; but for any other subtype, some type conversion would be necessary. Some creative thought about how to represent differences as numbers might be needed, too. To the greatest extent possible, the `subtype_diff` function should agree with the sort ordering implied by the selected operator class and collation; that is, its result should be positive whenever its first argument is greater than its second according to the sort ordering.
+
+See the [PostgreSQL documentation](https://www.postgresql.org/docs/9.3/sql-createtype.html) for more information about creating range types.
+
+## Indexing
+
+GiST and SP-GiST indexes can be created for table columns of range types. For instance, to create a GiST index:
+
+```sql
+CREATE INDEX reservation_idx ON reservation USING gist (during);
+```
+
+A GiST or SP-GiST index can accelerate queries involving these range operators: `=`, `&&`, `<@`, `@>`, `<<`, `>>`, `-|-`, `&<`, and `&>`.
+
+In addition, B-tree and hash indexes can be created for table columns of range types. For these index types, basically the only useful range operation is equality. There is a B-tree sort ordering defined for range values, with corresponding `<` and `>` operators, but the ordering is rather arbitrary and not usually useful in the real world. Range types' B-tree and hash support is primarily meant to allow sorting and hashing internally in queries, rather than creation of actual indexes.
+
+## Constraints on ranges
+
+While `UNIQUE` is a natural constraint for scalar values, it is usually unsuitable for range types. Instead, an exclusion constraint is often more appropriate. Exclusion constraints allow the specification of constraints such as "non-overlapping" on a range type. For example:
+
+```sql
+CREATE TABLE reservation (
+    during tsrange,
+    EXCLUDE USING gist (during WITH &&)
+);
+```
+
+That constraint prevents any overlapping values from existing in the table at the same time:
+
+```sql
+INSERT INTO reservation VALUES
+    ('[2010-01-01 11:30, 2010-01-01 15:00)');
+INSERT 0 1
+
+INSERT INTO reservation VALUES
+    ('[2010-01-01 14:45, 2010-01-01 15:45)');
+ERROR:  conflicting key value violates exclusion constraint "reservation_during_excl"
+DETAIL:  Key (during)=(["2010-01-01 14:45:00","2010-01-01 15:45:00")) conflicts
+with existing key (during)=(["2010-01-01 11:30:00","2010-01-01 15:00:00")).
+```
+
+You can use the [`btree_gist`](https://www.postgresql.org/docs/9.3/btree-gist.html) extension to define exclusion constraints on plain scalar data types, which can then be combined with range exclusions for maximum flexibility. For example, after `btree_gist` is installed, the following constraint will reject overlapping ranges only if the meeting room numbers are equal:
+
+```sql
+CREATE EXTENSION btree_gist;
+CREATE TABLE room_reservation (
+    room text,
+    during tsrange,
+    EXCLUDE USING gist (room WITH =, during WITH &&)
+);
+
+INSERT INTO room_reservation VALUES
+    ('123A', '[2010-01-01 14:00, 2010-01-01 15:00)');
+INSERT 0 1
+
+INSERT INTO room_reservation VALUES
+    ('123A', '[2010-01-01 14:30, 2010-01-01 15:30)');
+ERROR:  conflicting key value violates exclusion constraint "room_reservation_room_during_excl"
+DETAIL:  Key (room, during)=(123A, ["2010-01-01 14:30:00","2010-01-01 15:30:00")) conflicts
+with existing key (room, during)=(123A, ["2010-01-01 14:00:00","2010-01-01 15:00:00")).
+
+INSERT INTO room_reservation VALUES
+    ('123B', '[2010-01-01 14:30, 2010-01-01 15:30)');
+INSERT 0 1
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/01_logical_operators.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/01_logical_operators.mdx
new file mode 100644
index 00000000000..e525ed3daab
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/01_logical_operators.mdx
@@ -0,0 +1,32 @@
+---
+title: "Logical operators"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/01_logical_operators/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="logical_operators" class="registered_link"></div>
+
+The usual logical operators are available: `AND`, `OR`, `NOT`
+
+SQL uses a three-valued Boolean logic where the null value represents "unknown". Observe the following truth tables.
+
+`AND/OR Truth Table`
+
+| a     | b     | a AND b | a OR b |
+| ----- | ----- | ------- | ------ |
+| True  | True  | True    | True   |
+| True  | False | False   | True   |
+| True  | Null  | Null    | True   |
+| False | False | False   | False  |
+| False | Null  | False   | Null   |
+| Null  | Null  | Null    | Null   |
+
+`NOT Truth Table`
+
+| a     | NOT a |
+| ----- | ----- |
+| True  | False |
+| False | True  |
+| Null  | Null  |
+
+The operators `AND` and `OR` are commutative. You can switch the left and right operand without affecting the result.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/02_comparison_operators.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/02_comparison_operators.mdx
new file mode 100644
index 00000000000..da5bc900b4f
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/02_comparison_operators.mdx
@@ -0,0 +1,54 @@
+---
+title: "Comparison operators"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.095.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.129.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.038.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/02_comparison_operators/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="comparison_operators" class="registered_link"></div>
+
+The usual comparison operators are shown in the table.
+
+| Operator | Description              |
+| -------- | ------------------------ |
+| `<`      | Less than                |
+| `>`      | Greater than             |
+| `<=`     | Less than or equal to    |
+| `>=`     | Greater than or equal to |
+| `=`      | Equal                    |
+| `<>`     | Not equal                |
+| `!=`     | Not equal                |
+
+Comparison operators are available for all data types where they makes sense. All comparison operators are binary operators that return values of type `BOOLEAN`. Expressions like `1 < 2 < 3` aren't valid because there is no `<` operator to compare a Boolean value with `3`.
+
+In addition to the comparison operators, the special `BETWEEN` construct is available.
+
+ `a BETWEEN x AND y`
+
+is equivalent to:
+
+ `a >= x AND a <= y`
+
+Similarly:
+
+ `a NOT BETWEEN x AND y`
+
+is equivalent to:
+
+ `a < x OR a > y`
+
+There's no difference between the two forms apart from the CPU cycles required to rewrite the first one into the second one internally.
+
+To check whether a value is null, use the constructs:
+
+ `expression IS NULL`
+
+ `expression IS NOT NULL`
+
+Don't write `expression = NULL` because `NULL` isn't "equal to" `NULL`. The null value represents an unknown value, and it isn't known whether two unknown values are equal. This behavior conforms to the SQL standard.
+
+Some applications might expect that `expression = NULL` returns true if `expression` evaluates to the null value. We highly recommend that you modify these applications to comply with the SQL standard.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/03_mathematical_functions_and_operators.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/03_mathematical_functions_and_operators.mdx
new file mode 100644
index 00000000000..0410c43183a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/03_mathematical_functions_and_operators.mdx
@@ -0,0 +1,129 @@
+---
+title: "Mathematical functions and operators"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.096.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.130.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.039.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/03_mathematical_functions_and_operators/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="mathematical_functions_and_operators" class="registered_link"></div>
+
+## Overview of mathematical operators 
+
+Mathematical operators are provided for many EDB Postgres Advanced Server types. The following table shows the available mathematical operators.
+
+| Operator | Description                       | Example  | Result |
+| -------- | --------------------------------- | -------- | ------ |
+| `+`      | Addition                          | `2 + 3`  | `5`    |
+| `-`      | Subtraction                       | `2 – 3`  | `-1`   |
+| `*`      | Multiplication                    | `2 * 3`  | `6`    |
+| `/`      | Division (See the following note) | `4 / 2`  | `2`    |
+| `**`     | Exponentiation Operator           | `2 ** 3` | `8`    |
+
+!!! Note
+    If the `db_dialect` configuration parameter in the `postgresql.conf` file is set to `redwood`, then division of a pair of `INTEGER` data types doesn't result in a truncated value. Any fractional result is retained as shown by the following example:
+
+```sql
+edb=# SET db_dialect TO redwood;
+SET
+edb=# SHOW db_dialect;
+__OUTPUT__
+ db_dialect
+------------
+ redwood
+(1 row)
+```
+```sql
+__OUTPUT__
+edb=# SELECT CAST('10' AS INTEGER) / CAST('3' AS INTEGER) FROM dual;
+      ?column?
+--------------------
+ 3.3333333333333333
+(1 row)
+```
+
+This behavior is compatible with Oracle databases where there is no native `INTEGER` data type. Any `INTEGER` data type specification is internally converted to `NUMBER(38)`, which results in retaining any fractional result.
+
+If the `db_dialect` configuration parameter is set to `postgres`, then division of a pair of `INTEGER` data types results in a truncated value:
+
+```sql
+edb=# SET db_dialect TO postgres;
+SET
+edb=# SHOW db_dialect;
+__OUTPUT__
+ db_dialect
+------------
+ postgres
+(1 row)
+```
+```sql
+edb=# SELECT CAST('10' AS INTEGER) / CAST('3' AS INTEGER) FROM dual;
+__OUTPUT__
+ ?column?
+----------
+        3
+(1 row)
+```
+
+This behavior is compatible with PostgreSQL databases where division involving any pair of `INTEGER`, `SMALLINT`, or `BIGINT` data types results in truncating the result. The same truncated result is returned by EDB Postgres Advanced Server when `db_dialect` is set to `postgres`.
+
+Even when `db_dialect` is set to `redwood`, only division with a pair of `INTEGER` data types results in no truncation of the result. Division that includes only `SMALLINT` or `BIGINT` data types, with or without an `INTEGER` data type, results in truncation in the PostgreSQL fashion without retaining the fractional portion. In this example, `INTEGER` and `SMALLINT` are involved in the division:
+
+```sql
+edb=# SHOW db_dialect;
+__OUTPUT__
+ db_dialect
+------------
+ redwood
+(1 row)
+```
+```sql
+edb=# SELECT CAST('10' AS INTEGER) / CAST('3' AS SMALLINT) FROM dual;
+__OUTPUT__
+ ?column?
+----------
+        3
+(1 row)
+```
+
+## Available mathematical functions
+
+The following table shows the available mathematical functions. Many of these functions are provided in multiple forms with different argument types. Except where noted, any given form of a function returns the same data type as its argument. The functions working with `DOUBLE PRECISION` data are mostly implemented on top of the host system’s C library. Accuracy and behavior in boundary cases might therefore vary depending on the host system.
+
+| Function                                                       | Return Type                                                            | Description                                                                                                                 | Example                               | Result                 |
+| -------------------------------------------------------------- | ---------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------- | ---------------------- |
+| `ABS(x)`                                                       | Same as `x`                                                            | Absolute value                                                                                                              | `ABS(-17.4)`                          | `17.4`                 |
+| `CEIL(DOUBLE PRECISION or NUMBER)`                             | Same as input                                                          | Smallest integer not less than argument                                                                                     | `CEIL(-42.8)`                         | `-42`                  |
+| `EXP(DOUBLE PRECISION or NUMBER)`                              | Same as input                                                          | Exponential                                                                                                                 | `EXP(1.0)`                            | `2.7182818284590452`   |
+| `FLOOR(DOUBLE PRECISION or NUMBER)`                            | Same as input                                                          | Largest integer not greater than argument                                                                                   | `FLOOR(-42.8)`                        | `43`                   |
+| `LN(DOUBLE PRECISION or NUMBER)`                               | Same as input                                                          | Natural logarithm                                                                                                           | `LN(2.0)`                             | `0.6931471805599453`   |
+| `LOG(b NUMBER, x NUMBER)`                                      | `NUMBER`                                                               | Logarithm to base `b`                                                                                                       | `LOG(2.0, 64.0)`                      | `6.0000000000000000`   |
+| `MOD(y, x)`                                                    | Same as argument types                                                 | Remainder of `y/x`                                                                                                          | `MOD(9, 4)`                           | `1`                    |
+| `NVL(x, y)`                                                    | Same as argument types; where both arguments are of the same data type | If `x` is null, then NVL returns `y`                                                                                        | `NVL(9, 0)`                           | `9`                    |
+| `POWER(a DOUBLE PRECISION, b DOUBLE PRECISION)`                | `DOUBLE PRECISION`                                                     | `a` raised to the power of `b`                                                                                              | `POWER(9.0, 3.0)`                     | `729.0000000000000000` |
+| `POWER(a NUMBER, b NUMBER)`                                    | `NUMBER`                                                               | `a` raised to the power of `b`                                                                                              | `POWER(9.0, 3.0)`                     | `729.0000000000000000` |
+| `ROUND(DOUBLE PRECISION or NUMBER)`                            | Same as input                                                          | Round to nearest integer                                                                                                    | `ROUND(42.4)`                         | `42`                   |
+| `ROUND(v NUMBER, s INTEGER)`                                   | `NUMBER`                                                               | Round to `s` decimal places                                                                                                 | `ROUND(42.4382, 2)`                   | `42.44`                |
+| `SIGN(DOUBLE PRECISION or NUMBER)`                             | Same as input                                                          | Sign of the argument (-1, 0, +1)                                                                                            | `SIGN(-8.4)`                          | `-1`                   |
+| `SQRT(DOUBLE PRECISION or NUMBER)`                             | Same as input                                                          | Square root                                                                                                                 | `SQRT(2.0)`                           | `1.414213562373095`    |
+| `TRUNC(DOUBLE PRECISION or NUMBER)`                            | Same as input                                                          | Truncate toward zero                                                                                                        | `TRUNC(42.8)`                         | `42`                   |
+| `TRUNC(v NUMBER, s INTEGER)`                                   | `NUMBER`                                                               | Truncate to `s` decimal places                                                                                              | `TRUNC(42.4382, 2)`                   | `42.43`                |
+| `WIDTH_BUCKET(op NUMBER, b1 NUMBER, b2 NUMBER, count INTEGER)` | `INTEGER`                                                              | Return the bucket to which `op` would be assigned in an equidepth histogram with `count` buckets, in the range `b1` to `b2` | `WIDTH_BUCKET(5.35, 0.024, 10.06, 5)` | `3`                    |
+
+
+## Available trigonometric functions
+
+The following table shows the available trigonometric functions. All trigonometric functions take arguments and return values of type `DOUBLE PRECISION`.
+
+| Function      | Description              |
+| ------------- | ------------------------ |
+| `ACOS(x)`     | Inverse cosine           |
+| `ASIN(x)`     | Inverse sine             |
+| `ATAN(x)`     | Inverse tangent          |
+| `ATAN2(x, y)` | Inverse tangent of `x/y` |
+| `COS(x)`      | Cosine                   |
+| `SIN(x)`      | Sine                     |
+| `TAN(x)`      | Tangent                  |
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/04_string_functions_and_operators.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/04_string_functions_and_operators.mdx
new file mode 100644
index 00000000000..1109ae8365c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/04_string_functions_and_operators.mdx
@@ -0,0 +1,194 @@
+---
+title: "String functions and operators"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.097.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.131.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.040.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/04_string_functions_and_operators/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="string_functions_and_operators" class="registered_link"></div>
+
+These functions and operators are for examining and manipulating string values. Strings in this context include values of the types `CHAR`, `VARCHAR2`, and `CLOB`. Unless otherwise noted, all of these functions work on all of these types, but be aware of potential effects of automatic padding when using the `CHAR` type. Generally, the functions described here also work on data of nonstring types by converting that data to a string representation first.
+
+## Overview of string functions
+
+| Function                                                           | Return type | Description                                                                                                                                                                                                                  | Example                                                               | Result         |
+| ------------------------------------------------------------------ | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------- | -------------- |
+| string \|\| string                                               | `CLOB`      | String concatenation.                                                                                                                                                                                                         | 'Enterprise' \|\| 'DB'                                                | `EnterpriseDB` |
+| `CONCAT(string, string)`                                           | `CLOB`      | String concatenation.                                                                                                                                                                                                         | 'a' \|\| 'b'                                                         | `ab`           |
+| `HEXTORAW(varchar2)`                                               | `RAW`       | Converts a `VARCHAR2` value to a `RAW value`.                                                                                                                                                                                 | `HEXTORAW('303132')`                                                  | `'012'`        |
+| `RAWTOHEX(raw)`                                                    | `VARCHAR2`  | Converts a `RAW` value to a `HEXADECIMAL` value.                                                                                                                                                                              | `RAWTOHEX('012')`                                                     | `'303132'`     |
+| `INSTR(string, set, [ start [, occurrence ] ])`                    | `INTEGER`   | Finds the location of a set of characters in a string, starting at position `start` in the string, `string`, and looking for the first, second, third and so on occurrences of the set. Returns `0` if the set isn't found. | `INSTR('PETER PIPER PICKED a PECK of PICKLED PEPPERS','PI',1,3)`      | `30`           |
+| `INSTRB(string, set)`                                              | `INTEGER`   | Returns the position of the `set` within the `string`. Returns `0` if `set` is not found.                                                                                                                                    | `INSTRB('PETER PIPER PICKED a PECK of PICKLED PEPPERS', 'PICK')`      | `13`           |
+| `INSTRB(string, set, start)`                                       | `INTEGER`   | Returns the position of the `set` within the `string`, beginning at `start`. Returns `0` if `set` is not found.                                                                                                              | `INSTRB('PETER PIPER PICKED a PECK of PICKLED PEPPERS','PICK', 14)`   | `30`           |
+| `INSTRB(string, set, start, occurrence)`                           | `INTEGER`   | Returns the position of the specified `occurrence` of `set` within the `string`, beginning at `start`. Returns `0` if `set` is not found.                                                                                    | `INSTRB('PETER PIPER PICKED a PECK of PICKLED PEPPERS','PICK', 1, 2)` | `30`           |
+| `LOWER(string)`                                                    | `CLOB`      | Converts `string` to lower case.                                                                                                                                                                                               | `LOWER('TOM')`                                                      | `tom`          |
+| `NLS_CHARSET_ID(string)`                                           | `NUMBER`    | Returns the character set ID number corresponding to the character set name `string`. The `string` argument is a runtime `VARCHAR2` value.                                                                                      | `NLS_CHARSET_ID('utf8')`                                              | `6`            |
+| `NLS_CHARSET_NAME(number)`                                         | `VARCHAR2`  | Returns the name of the character set corresponding to the ID number. The character set name is returned as a `VARCHAR2` value in the database character set.                                                                   | `NLS_CHARSET_NAME(6)`                                                  | `UTF8`          |
+| `NLS_CHARSET_DECL_LEN(byte_count, char_set_id)`                    | `NCHAR`     | Returns the declaration length in number of characters of an `NCHAR` column. The `byte_count` argument is the width of the column. The `char_set_id` argument is the character set ID of the column.                         | `NLS_CHARSET_DECL_LEN(100,nls_charset_id('utf8'))`                    | `100`          |
+| `SUBSTR(string, start [, count ])`                                 | `CLOB`      | Extracts substring starting from `start` and going for `count` characters. If `count` isn't specified, the string is clipped from the start till the end.                                                                    | `SUBSTR('This is a test',6,2)`                                        | `is`           |
+| `SUBSTRB(string, start [, count ])`                                | `CLOB`      | Same as `SUBSTR` except `start` and `count` are in number of bytes.                                                                                                                                                          | `SUBSTRB('abc',3)`, assuming a double-byte character set.             | `c`            |
+| `SUBSTR2(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTR`.                                                                                                                                                                                                          | `SUBSTR2('This is a test',6,2)`                                       | `is`           |
+| `SUBSTR2(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTRB`.                                                                                                                                                                                                         | `SUBSTR2('abc',3)` (assuming a double-byte character set)             | `c`            |
+| `SUBSTR4(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTR`.                                                                                                                                                                                                          | `SUBSTR4('This is a test',6,2)`                                       | `is`           |
+| `SUBSTR4(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTRB`.                                                                                                                                                                                                         | `SUBSTR4('abc',3)` (assuming a double-byte character set)             | `c`            |
+| `SUBSTRC(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTR`.                                                                                                                                                                                                          | `SUBSTRC('This is a test',6,2)`                                       | `is`           |
+| `SUBSTRC(string, start [, count ])`                                | `CLOB`      | Alias for `SUBSTRB`.                                                                                                                                                                                                         | `SUBSTRC('abc',3)` (assuming a double-byte character set)             | `c`            |
+| `TRIM(\[ LEADING \| TRAILING \| BOTH ] \[ characters ] FROM string)` | `CLOB`      | Removes the longest string containing only the characters (a space by default) from the start, end, or both ends of the string.                                                                                                 | `TRIM(BOTH 'x' FROM 'xTomxx')`                                        | `Tom`          |
+| `LTRIM(string [, set])`                                            | `CLOB`      | Removes all the characters specified in `set` from the left of a given `string`. If `set` isn't specified, a blank space is used by default.                                                                                 | `LTRIM('abcdefghi', 'abc')`                                           | `defghi`       |
+| `RTRIM(string [, set])`                                            | `CLOB`      | Removes all the characters specified in `set` from the right of a given `string`. If `set` isn't specified, a blank space is used by default.                                                                                | `RTRIM('abcdefghi', 'ghi')`                                           | `abcdef`       |
+| `UPPER(string)`                                                    | `CLOB`      | Converts `string` to upper case.                                                                                                                                                                                             | `UPPER('tom')`                                                        | `TOM`          |
+
+More string manipulation functions are available and are listed in the following table. Some of them are used internally to implement the SQL-standard string functions listed in the above table.
+
+| Function                                                         | Return type                                             | Description                                                                                                                                                                                                                               | Example                                               | Result      |
+| ---------------------------------------------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | ----------- |
+| `ASCII(string)`                                                  | `INTEGER`                                               | ASCII code of the first byte of the argument.                                                                                                                                                                                              | `ASCII('x')`                                          | `120`       |
+| `CHR(INTEGER)`                                                   | `CLOB`                                                  | Character with the given ASCII code.                                                                                                                                                                                                       | `CHR(65)`                                             | `A`         |
+| DECODE(expr, expr1a, expr1b [, expr2a, expr2b ]... [, default ]) | Same as argument types of `expr1b, expr2b,..., default` | Finds first match of `expr` with `expr1a, expr2a`, etc. When match found, returns corresponding parameter pair, `expr1b, expr2b`, etc. If no match found, returns `default`. If no match found and `default` not specified, returns null. | `DECODE(3, 1,'One', 2,'Two', 3,'Three', 'Not found')` | `Three`     |
+| `INITCAP(string)`                                                | `CLOB`                                                  | Converts the first letter of each word to upper case and the rest to lower case. Words are sequences of alphanumeric characters separated by non-alphanumeric characters.                                                                    | `INITCAP('hi THOMAS')`                                | `Hi Thomas` |
+| `LENGTH`                                                         | `INTEGER`                                               | Returns the number of characters in a string value.                                                                                                                                                                                       | `LENGTH('Côte d''Azur')`                              | `11`        |
+| `LENGTHC`                                                        | `INTEGER`                                               | This function is identical in functionality to `LENGTH`; the function name is supported for compatibility.                                                                                                                                | `LENGTHC('Côte d''Azur')`                             | `11`        |
+| `LENGTH2`                                                        | `INTEGER`                                               | This function is identical in functionality to `LENGTH`; the function name is supported for compatibility.                                                                                                                                | `LENGTH2('Côte d''Azur')`                             | `11`        |
+| `LENGTH4`                                                        | `INTEGER`                                               | This function is identical in functionality to `LENGTH`; the function name is supported for compatibility.                                                                                                                                | `LENGTH4('Côte d''Azur')`                             | `11`        |
+| `LENGTHB`                                                        | `INTEGER`                                               | Returns the number of bytes required to hold the given value.                                                                                                                                                                             | `LENGTHB('Côte d''Azur')`                             | `12`        |
+| `LPAD(string, length INTEGER [, fill ])`                         | `CLOB`                                                  | Fills up `string` to size `length` by prepending the characters `fill` (a space by default). If `string` is already longer than `length`, then it is truncated (on the right).                                                            | `LPAD('hi', 5, 'xy')`                                 | `xyxhi`     |
+| `REPLACE(string, search_string [, replace_string ]`              | `CLOB`                                                  | Replaces one value in a string with another. If you don't specify a value for `replace_string`, the `search_string` value, when found, is removed.                                                                                        | `REPLACE( 'GEORGE', 'GE', 'EG')`                      | `EGOREG`    |
+| `RPAD(string, length INTEGER [, fill ])`                         | `CLOB`                                                  | Fills up `string` to size `length` by appending the characters `fill` (a space by default). If `string` is already longer than `length`, then it is truncated.                                                                            | `RPAD('hi', 5, 'xy')`                                 | `hixyx`     |
+| `TRANSLATE(string, from, to)`                                    | `CLOB`                                                  | Any character in `string` that matches a character in the `from` set is replaced by the corresponding character in the `to` set.                                                                                                          | `TRANSLATE('12345', '14', 'ax')`                      | `a23x5`     |
+
+## Truncation of string text resulting from concatenation with NULL
+
+!!! Note
+    This functionality isn't compatible with Oracle databases, which can lead to some inconsistency when converting data from Oracle to EDB Postgres Advanced Server.
+
+For EDB Postgres Advanced Server, when a column value is `NULL`, the concatenation of the column with a text string can result in either of the following:
+
+-   Return of the text string
+-   Disappearance of the text string (that is, a null result)
+
+The result depends on the data type of the `NULL` column and the way in which the concatenation is done.
+
+If you use the string concatenation operator `‘||’`, then the types that have implicit coercion to text, as listed in the table Data Types with Implicit Coercion to Text, don't truncate the string if one of the input parameters is `NULL`. For other types, it truncates the string unless the explicit type cast is used (that is, `::text`). Also, to see the consistent behavior in the presence of nulls, you can use the `CONCAT` function.
+
+The following query lists the data types that have implicit coercion to text:
+
+```sql
+SELECT castsource::regtype, casttarget::regtype, castfunc::regproc,
+    CASE castcontext
+        WHEN 'e' THEN 'explicit'
+        WHEN 'a' THEN 'implicit in assignment'
+        WHEN 'i' THEN 'implicit in expressions'
+    END as castcontext,
+    CASE castmethod
+        WHEN 'f' THEN 'function'
+        WHEN 'i' THEN 'input/output function'
+        WHEN 'b' THEN 'binary-coercible'
+    END as castmethod
+FROM pg_cast
+    WHERE casttarget::regtype::text = 'text'
+      AND castcontext='i';
+```
+
+The result of the query is listed in the following table.
+
+| castsource                    | casttarget | castfunc          | castcontext               | castmethod              |
+| ----------------------------- | ---------- | ----------------- | ------------------------- | ----------------------- |
+| `character`                   | `text`     | `pg_catalog.text` | `implicit in expressions` | `function`              |
+| `character varying`           | `text`     | `-`               | `implicit in expressions` | `binary-coercible`      |
+| `"char"`                      | `text`     | `pg_catalog.text` | `implicit in expressions` | `function`              |
+| `name`                        | `text`     | `pg_catalog.text` | `implicit in expressions` | `function`              |
+| `pg_node_tree`                | `text`     | `-`               | `implicit in expressions` | `binary-coercible`      |
+| `pg_ndistinct`                | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `pg_dependencies`             | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `integer`                     | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `smallint`                    | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `oid`                         | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `date`                        | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `double precision`            | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `real`                        | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `time with time zone`         | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `time without time zone`      | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `timestamp with time zone`    | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `interval`                    | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `bigint`                      | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `numeric`                     | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `timestamp without time zone` | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `record`                      | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+| `boolean`                     | `text`     | `pg_catalog.text` | `implicit in expressions` | `function`              |
+| `bytea`                       | `text`     | `-`               | `implicit in expressions` | `input/output function` |
+
+For information on the column output, see the `pg_cast` system catalog in the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/catalog-pg-cast.html).
+
+So for example, data type `UUID` isn't in this list and therefore doesn't have the implicit coercion to text. As a result, certain concatenation attempts with a `NULL UUID` column results in a truncated text result.
+
+The following table is created for this example with a single row with all `NULL` column values:
+
+```sql
+CREATE TABLE null_concat_types (
+    boolean_type    BOOLEAN,
+    uuid_type       UUID,
+    char_type       CHARACTER
+);
+
+INSERT INTO null_concat_types VALUES (NULL, NULL, NULL);
+```
+
+Columns `boolean_type` and `char_type` have the implicit coercion to text while column `uuid_type` doesn't.
+
+Thus, string concatenation with the concatenation operator `‘||‘` against columns `boolean_type` or `char_type` results in the following:
+
+```sql
+SELECT 'x=' || boolean_type || 'y' FROM null_concat_types;
+__OUTPUT__
+ ?column?
+----------
+ x=y
+(1 row)
+```
+```sql
+SELECT 'x=' || char_type || 'y' FROM null_concat_types;
+__OUTPUT__
+ ?column?
+----------
+ x=y
+(1 row)
+```
+
+But concatenation with column `uuid_type` results in the loss of the `x=` string:
+
+```sql
+SELECT 'x=' || uuid_type || 'y' FROM null_concat_types;
+__OUTPUT__
+ ?column?
+----------
+ y
+(1 row)
+```
+
+However, using explicit casting with `::text` prevents the loss of the `x=` string:
+
+```sql
+SELECT 'x=' || uuid_type::text || 'y' FROM null_concat_types;
+__OUTPUT__
+ ?column?
+----------
+ x=y
+(1 row)
+```
+
+Using the `CONCAT` function also preserves the `x=` string:
+
+```sql
+SELECT CONCAT('x=',uuid_type) || 'y' FROM null_concat_types;
+__OUTPUT__
+ ?column?
+----------
+ x=y
+(1 row)
+```
+
+Thus, depending on the data type of a `NULL` column, use explicit casting or the `CONCAT` function to avoid losing some text strings.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/05_pattern_matching_string_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/05_pattern_matching_string_functions.mdx
new file mode 100644
index 00000000000..5c17a4c0077
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/05_pattern_matching_string_functions.mdx
@@ -0,0 +1,218 @@
+---
+title: "Pattern matching string functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.098.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.132.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.041.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/05_pattern_matching_string_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="pattern_matching_string_functions" class="registered_link"></div>
+
+EDB Postgres Advanced Server offers support for the `REGEXP_COUNT`, `REGEXP_INSTR`, and `REGEXP_SUBSTR` functions. These functions search a string for a pattern specified by a regular expression and return information about occurrences of the pattern in the string. Use a POSIX-style regular expression. For more information about forming a POSIX-style regular expression, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/functions-matching.html).
+
+## REGEXP_COUNT
+
+`REGEXP_COUNT` searches a string for a regular expression and returns a count of the times that the regular expression occurs. The signature is:
+
+```sql
+INTEGER REGEXP_COUNT
+(
+  srcstr    TEXT,
+  pattern   TEXT,
+  position  DEFAULT 1
+  modifier  DEFAULT NULL
+)
+```
+
+### Parameters
+
+`srcstr`
+
+ `srcstr` specifies the string to search.
+
+`pattern`
+
+ `pattern` specifies the regular expression `REGEXP_COUNT` searches for.
+
+`position`
+
+ `position` is an integer value that indicates the position in the source string where `REGEXP_COUNT` begins searching. The default value is `1`.
+
+`modifier`
+
+ `modifier` specifies values that control the pattern-matching behavior. The default value is `NULL`. For a complete list of the modifiers supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/functions-matching.html).
+
+### Example
+
+In this example, `REGEXP_COUNT` returns a count of the number of times the letter `i` is used in the character string `'reinitializing'`:
+
+```sql
+edb=# SELECT REGEXP_COUNT('reinitializing', 'i', 1) FROM DUAL;
+__OUTPUT__
+ regexp_count
+--------------
+            5
+(1 row)
+```
+
+The command instructs `REGEXP_COUNT` to begin counting in the first position. If you modify the command to start the count on the sixth position, `REGEXP_COUNT` returns `3`: 
+
+```sql
+edb=# SELECT REGEXP_COUNT('reinitializing', 'i', 6) FROM DUAL;
+__OUTPUT__
+ regexp_count
+--------------
+            3
+(1 row)
+```
+
+The count now excludes any occurrences of the letter `i` that occur before the sixth position.
+
+## REGEXP_INSTR
+
+`REGEXP_INSTR` searches a string for a POSIX-style regular expression. This function returns the position in the string where the match was located. The signature is:
+
+```sql
+INTEGER REGEXP_INSTR
+(
+  srcstr        TEXT,
+  pattern       TEXT,
+  position      INT  DEFAULT 1,
+  occurrence    INT  DEFAULT 1,
+  returnparam   INT  DEFAULT 0,
+  modifier      TEXT DEFAULT NULL,
+  subexpression INT  DEFAULT 0,
+)
+```
+
+### Parameters
+
+`srcstr`
+
+ `srcstr` specifies the string to search.
+
+`pattern`
+
+ `pattern` specifies the regular expression that `REGEXP_INSTR` searches for.
+
+`position`
+
+ `position` specifies an integer value that indicates the start position in a source string. The default value is `1`.
+
+`occurrence`
+
+ `occurrence` specifies the match to return if more than one occurrence of the pattern occurs in the string to search. The default value is `1`.
+
+`returnparam`
+
+ `returnparam` is an integer value that specifies the location in the string for `REGEXP_INSTR` to return. The default value is `0`. Specify:
+
+-   `0` to return the location in the string of the first character that matches `pattern`.
+
+-   A value greater than `0` to return the position of the first character following the end of the `pattern`.
+
+`modifier`
+
+ `modifier` specifies values that control the pattern-matching behavior. The default value is `NULL`. For a complete list of the modifiers supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/functions-matching.html).
+
+`subexpression`
+
+ `subexpression` is an integer value that identifies the portion of the `pattern` that's returned by `REGEXP_INSTR`. The default value of `subexpression` is `0`.
+
+ If you specify a value for `subexpression`, you must include one or more sets of parentheses in the `pattern` that isolate a portion of the value you are searching for. The value specified by `subexpression` indicates the set of parentheses to return. For example, if `subexpression` is `2`, `REGEXP_INSTR` returns the position of the second set of parentheses.
+
+### Example
+
+In this example, `REGEXP_INSTR` searches a string that contains a phone number for the first occurrence of a pattern that contains three consecutive digits:
+
+```sql
+edb=# SELECT REGEXP_INSTR('800-555-1212', '[0-9][0-9][0-9]', 1, 1) FROM DUAL;
+__OUTPUT__
+ regexp_instr
+--------------
+            1
+(1 row)
+```
+
+The command instructs `REGEXP_INSTR` to return the position of the first occurrence. If we modify the command to return the start of the second occurrence of three consecutive digits, `REGEXP_INSTR` returns `5`. The second occurrence of three consecutive digits begins in the fifth position.
+
+```sql
+edb=# SELECT REGEXP_INSTR('800-555-1212', '[0-9][0-9][0-9]', 1, 2) FROM DUAL;
+__OUTPUT__
+ regexp_instr
+--------------
+            5
+(1 row)
+```
+
+
+## REGEXP_SUBSTR
+
+The `REGEXP_SUBSTR` function searches a string for a pattern specified by a POSIX-compliant regular expression. `REGEXP_SUBSTR` returns the string that matches the pattern specified in the call to the function. The signature of the function is:
+
+```sql
+TEXT REGEXP_SUBSTR
+(
+  srcstr        TEXT,
+  pattern       TEXT,
+  position      INT  DEFAULT 1,
+  occurrence    INT  DEFAULT 1,
+  modifier      TEXT DEFAULT NULL,
+  subexpression INT  DEFAULT 0
+)
+```
+
+### Parameters
+
+`srcstr`
+
+ `srcstr` specifies the string to search.
+
+`pattern`
+
+ `pattern` specifies the regular expression `REGEXP_SUBSTR` searches for.
+
+`position`
+
+ `position` specifies an integer value that indicates the start position in a source string. The default value is `1`.
+
+`occurrence`
+
+ `occurrence` specifies the match returned if more than one occurrence of the search pattern occurs. The default value is `1`.
+
+`modifier`
+
+ `modifier` specifies values that control the pattern-matching behavior. The default value is `NULL`. For a complete list of the modifiers supported by EDB Postgres Advanced Server, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/functions-matching.html).
+
+`subexpression`
+
+ `subexpression` is an integer value that identifies the portion of the `pattern` that's returned by `REGEXP_SUBSTR`. The default value of `subexpression` is `0`.
+
+ If you specify a value for `subexpression`, you must include one or more sets of parentheses in the `pattern` that isolate a portion of the value being searched for. The value specified by `subexpression` indicates the set of parentheses to return. For example, if `subexpression` is `2`, `REGEXP_SUBSTR` returns the value contained in the second set of parentheses.
+
+### Example
+
+In this example, `REGEXP_SUBSTR` searches a string that contains a phone number for the first set of three consecutive digits:
+
+```sql
+edb=# SELECT REGEXP_SUBSTR('800-555-1212', '[0-9][0-9][0-9]', 1, 1) FROM DUAL;
+__OUTPUT__
+ regexp_substr
+---------------
+ 800
+(1 row)
+```
+
+It locates the first occurrence of three digits and returns the string `(800)`. If we modify the command to check for the second occurrence of three consecutive digits, `REGEXP_SUBSTR` returns `555`, the contents of the second substring.
+
+```sql
+edb=# SELECT REGEXP_SUBSTR('800-555-1212', '[0-9][0-9][0-9]', 1, 2) FROM DUAL;
+__OUTPUT__
+ regexp_substr
+---------------
+ 555
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/06_pattern_matching_using_the_like_operator.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/06_pattern_matching_using_the_like_operator.mdx
new file mode 100644
index 00000000000..126b4a6367a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/06_pattern_matching_using_the_like_operator.mdx
@@ -0,0 +1,40 @@
+---
+title: "Pattern matching using the LIKE operator"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.099.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.133.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.042.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/06_pattern_matching_using_the_like_operator/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="pattern_matching_using_the_like_operator" class="registered_link"></div>
+
+EDB Postgres Advanced Server provides pattern matching using the traditional SQL `LIKE` operator. The syntax for the `LIKE` operator is:
+
+```sql
+string LIKE pattern [ ESCAPE escape-character ]
+string NOT LIKE pattern [ ESCAPE escape-character ]
+```
+
+Every `pattern` defines a set of strings. The `LIKE` expression returns `TRUE` if `string` is contained in the set of strings represented by `pattern`. As expected, the `NOT LIKE` expression returns `FALSE` if `LIKE` returns `TRUE` and vice versa. An equivalent expression is `NOT (string LIKE pattern)`.
+
+If `pattern` doesn't contain percent signs or underscore, then the pattern represents only the string. In that case, `LIKE` acts like the equals operator. An underscore (`_`) in `pattern` matches any single character. A percent sign (`%`) matches any string of zero or more characters.
+
+Some examples:
+
+```sql
+'abc' LIKE 'abc'    true
+'abc' LIKE 'a%'     true
+'abc' LIKE '_b_'    true
+'abc' LIKE 'c'      false
+```
+
+`LIKE` pattern matches always cover the entire string. To match a pattern anywhere in a string, the pattern must start and end with a percent sign.
+
+To match a literal underscore or percent sign without matching other characters, place an escape character before the character in `pattern`. The default escape character is the backslash, but you can select a different one by using the `ESCAPE` clause. To match the escape character, enter two escape characters.
+
+The backslash already has a special meaning in string literals, so to write a pattern constant that contains a backslash you must write two backslashes in an SQL statement. Thus, writing a pattern that matches a literal backslash means writing four backslashes in the statement. You can avoid this by selecting a different escape character with `ESCAPE`. Then a backslash isn't special to `LIKE` anymore. However, it's still special to the string literal parser, so you still need two of them.
+
+It’s also possible to select no escape character by writing `ESCAPE ''`. This disables the escape mechanism, which makes it impossible to turn off the special meaning of underscore and percent signs in the pattern.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/07_data_type_formatting_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/07_data_type_formatting_functions.mdx
new file mode 100644
index 00000000000..4277ce04eed
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/07_data_type_formatting_functions.mdx
@@ -0,0 +1,424 @@
+---
+title: "Data type formatting functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.100.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.134.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.043.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/07_data_type_formatting_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+
+The EDB Postgres Advanced Server formatting functions provide a powerful set of tools for converting various data types (date/time, integer, floating point, numeric) to formatted strings and for converting from formatted strings to specific data types. These all functions follow a common calling convention: the first argument is the value to format and the second argument is a string template that defines the output or input format.
+
+## Overview of data type formatting functions
+
+| Function                            | Return type   | Description                                                                                    | Example                                                                                                    | Result                                                |
+| ----------------------------------- | ------------- | ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
+| `TO_BLOB(raw)`                      | `BLOB`        | Convert a `RAW` value to `BLOB` value.                                                         | `TO_BLOB('abc')`                                                                                           | `\x616263`                                            |
+| `TO_CLOB(string)`                   | `CLOB`        | Convert a `CHAR`, `VARCHAR`, `VARCHAR2`, `NCHAR`, `NVARCHAR2`, or `CLOB` values to `CLOB` values. | `TO_CLOB('aaaa')`                                                                                       | `aaaa`                                                |
+| `TO_CHAR(DATE [, format ])`         | `VARCHAR2`    | Convert a date/time to a string with output, `format`. The default format is DD-MON-YY.        | `TO_CHAR(SYSDATE, 'MM/DD/YYYY HH12:MI:SS AM')`                                                             | `07/25/2007 09:43:02 AM`                              |
+| `TO_CHAR(TIMESTAMP [, format ])`    | `VARCHAR2`    | Convert a timestamp to a string with output, `format`. The default format is DD-MON-YY.        | `TO_CHAR (CURRENT_TIMESTAMP, 'MM/DD/YYYY HH12:MI:SS AM')`                                                  | `08/13/2015 08:55:22 PM`                              |
+| `TO_CHAR(INTEGER [, format ])`      | `VARCHAR2`    | Convert an integer to a string with output, `format`                                           | `TO_CHAR(2412, '999,999S')`                                                                                | `2,412+`                                              |
+| `TO_CHAR(NUMBER [, format ])`       | `VARCHAR2`    | Convert a decimal number to a string with output, `format`                                     | `TO_CHAR(10125.35, '999,999.99')`                                                                          | `10,125.35`                                           |
+| `TO_CHAR(DOUBLE PRECISION, format)` | `VARCHAR2`    | Convert a floating-point number to a string with output, `format`                              | `TO_CHAR (CAST(123.5282 AS REAL), '999.99')`                                                               | `123.53`                                              |
+| `TO_DATE(string [, format ])`       | `TIMESTAMP`   | Convert a date or timestamp formatted string to a `TIMESTAMP` data type                        | `TO_DATE('2007-07-04 13:39:10', 'YYYY-MM-DD HH24:MI:SS')` <br /><br />`TO_DATE('2007-07-04','YYYY-MM-DD')` | `04-JUL-07 13:39:10` <br /><br />`04-JUL-07 00:00:00` |
+| `TO_DSINTERVAL(string)`             | `INTERVAL DAY TO SECOND` | Convert a character string of `CHAR`, `VARCHAR2`, `NCHAR`, or `NVARCHAR2` datatype to an INTERVAL DAY TO SECOND type. | `TO_DSINTERVAL('80 13:30:00')`                                           | `80 days 13:30:00`                                    |
+| `TO_NCHAR(string)`                  | `NVARCHAR2`   | Convert a `character string`, `CHAR`, `VARCHAR2`, `CLOB`, or `NCLOB` value to the national character set. | `TO_NCHAR('test')`                                                                              | `test`                                                | 
+| `TO_NCHAR(number [, format])`       | `NVARCHAR2`   | Convert a number formatted string to a national character data type.                           | `TO_NCHAR(7654321, 'C9G999G999D99')`                                                                       | `7,654,321.00`                                        |
+| `TO_NCHAR(DATE  [, format ])`       | `NVARCHAR2`   | Convert a date/time to a formatted string of national character data type.                     | `TO_NCHAR(timestamp '2022-04-20 17:31:12.66', 'Day: MONTH DD, YYYY')`                                      | `Wednesday: APRIL     20, 2022`                       |
+| `TO_NUMBER(string [, format ])`     | `NUMBER`      | Convert a number formatted string to a `NUMBER` data type.                                      | `TO_NUMBER('2,412-', '999,999S')`                                                                          | `-2412`                                               |
+| `TO_TIMESTAMP(string, format)`      | `TIMESTAMPTZ` | Convert a timestamp formatted string to a TIMESTAMP WITH TIME ZONE data type.                   | `TO_TIMESTAMP('05 Dec 2000 08:30:25 pm', 'DD Mon YYYY hh12:mi:ss pm')`                                     | `05-DEC-00 20:30:25 +05:30`                           |
+| `TO_TIMESTAMP_TZ(string[, format])`   | `TIMESTAMPTZ` | Convert a timestamp formatted string to a TIMESTAMP WITH TIME ZONE data type.                   | `TO_TIMESTAMP_TZ ('2003/12/13 10:13:18 -8:00', 'YYYY/MM/DD HH:MI:SS TZH:TZM')`                             | `13-DEC-03 23:43:18 +05:30`                           |
+| `FROM_TZ(timestamp_value, timezone_value)` | `TIMESTAMPTZ` | Convert a timestamp value and a timezone to a TIMESTAMP WITH TIME ZONE value.            | `FROM_TZ(TIMESTAMP '2017-08-08 08:09:10', 'Asia/Kolkata')`                                                 | `08-AUG-17 08:09:10 +05:30`                           |
+
+
+## Available template patterns for date values
+
+This table shows the template patterns available for formatting date values using the `TO_CHAR`, `TO_DATE`, `TO_TIMESTAMP`, and `TO_TIMESTAMP_TZ` functions.
+
+| Pattern                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `HH`                       | Hour of day (01-12)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `HH12`                     | Hour of day (01-12)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `HH24`                     | Hour of day (00-23)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `MI`                       | Minute (00-59)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `SS`                       | Second (00-59)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `SSSSS`                    | Seconds past midnight (0-86399)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `FFn`                      | Fractional seconds where `n` is an optional integer from 1 to 9 for the number of digits to return. The default is 6.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `AM or A.M. or PM or P.M.` | Meridian indicator (uppercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `am or a.m. or pm or p.m.` | Meridian indicator (lowercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `Y,YYY`                    | Year (4 and more digits) with comma                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `YEAR`                     | Year (spelled out)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `SYEAR`                    | Year (spelled out) (BC dates prefixed by a minus sign)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `YYYY`                     | Year (4 and more digits)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `SYYYY`                    | Year (4 and more digits) (BC dates prefixed by a minus sign)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `YYY`                      | Last 3 digits of year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `YY`                       | Last 2 digits of year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `Y`                        | Last digit of year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           |
+| `IYYY`                     | ISO year (4 and more digits)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `IYY`                      | Last 3 digits of ISO year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `IY`                       | Last 2 digits of ISO year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `I`                        | Last 1 digit of ISO year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `BC or B.C. or AD or A.D.` | Era indicator (uppercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `bc or b.c. or ad or a.d.` | Era indicator (lowercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `MONTH`                    | Full uppercase month name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `Month`                    | Full mixed-case month name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `month`                    | Full lowercase month name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `MON`                      | Abbreviated uppercase month name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `Mon`                      | Abbreviated mixed-case month name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `mon`                      | Abbreviated lowercase month name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                |
+| `MM`                       | Month number (01-12)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `DAY`                      | Full uppercase day name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `Day`                      | Full mixed-case day name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `day`                      | Full lowercase day name                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `DY`                       | Abbreviated uppercase day name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `Dy`                       | Abbreviated mixed-case day name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                 |
+| `dy`                       | Abbreviated lowercase day name (3 chars in English, localized lengths vary)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| `DDD`                      | Day of year (001-366)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        |
+| `DD`                       | Day of month (01-31)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
+| `D`                        | Day of week (1-7; Sunday is 1)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
+| `W`                        | Week of month (1-5); the first week starts on the first day of the month                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `WW`                       | Week number of year (1-53); the first week starts on the first day of the year                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `IW`                       | ISO week number of year; the first Thursday of the new year is in week 1                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
+| `CC`                       | Century (2 digits); the 21st century starts on 2001-01-01                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| `SCC`                      | Same as CC except BC dates are prefixed by a minus sign                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `J`                        | Julian Day (days since January 1, 4712 BC)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
+| `Q`                        | Quarter                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| `RM`                       | Month in Roman numerals (I-XII; I=January) (uppercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `rm`                       | Month in Roman numerals (i-xii; i=January) (lowercase)                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
+| `RR`                       | First 2 digits of the year when given only the last 2 digits of the year. Result is based upon an algorithm using the current year and the given 2-digit year. The first 2 digits of the given 2-digit year are the same as the first 2 digits of the current year with the following exceptions: If the given 2-digit year is &lt;50 and the last 2 digits of the current year is >= 50, then the first 2 digits for the given year is 1 greater than the first 2 digits of the current year. If the given 2-digit year is >= 50 and the last 2 digits of the current year is &lt;50, then the first 2 digits for the given year is 1 less than the first 2 digits of the current year. |
+| `RRRR`                     | Affects only `TO_DATE` function. Allows specification of 2-digit or 4-digit year. If 2-digit year given, then returns first 2 digits of year like RR format. If 4-digit year given, returns the given 4-digit year.                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| `TZH`                      | Time-zone hours                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                              |
+| `TZM`                      | Time-zone minutes                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
+
+### Date and time modifiers
+
+You can apply certain modifiers to any template pattern to alter its behavior. For example, `FMMonth` is the `Month` pattern with the `FM` modifier. This table shows the modifier patterns for date/time formatting.
+
+| Modifier    | Description                                   | Example           |
+| ----------- | --------------------------------------------- | ----------------- |
+| `FM` prefix | Fill mode (suppress padding blanks and zeros) | `FMMonth`         |
+| `TH` suffix | Uppercase ordinal number suffix               | `DDTH`            |
+| `th` suffix | Lowercase ordinal number suffix               | `DDth`            |
+| `FX` prefix | Fixed format global option (see usage notes)  | `FX Month DD Day` |
+| `SP` suffix | Spell mode                                    | `DDSP`            |
+
+Usage notes for date/time formatting:
+
+-   `FM` suppresses leading zeroes and trailing blanks that are otherwise added to make the output of a pattern fixed width.
+
+-   `TO_TIMESTAMP`, `TO_TIMESTAMP_TZ`, and `TO_DATE` skip multiple blank spaces in the input string if you don't use the `FX` option. You must use `FX` as the first item in the template. For example:
+
+    ```sql
+    TO_TIMESTAMP('2000 - JUN', 'YYYY-MON') is correct, but
+    TO_TIMESTAMP('2000    JUN', 'FXYYYY MON') and
+    TO_TIMESTAMP_TZ('2000    JUN', 'FXYYYY MON') returns an error
+    because TO_TIMESTAMP and TO_TIMESTAMP_TZ expects one space
+    only.
+    ```
+
+-   Ordinary text is allowed in `TO_CHAR` templates and is output literally.
+
+-   In conversions from string to `timestamp`, `timestamptz`, or `date`, the `CC` field is ignored if there is a `YYY`, `YYYY`, or `Y,YYY` field. If `CC` is used with `YY` or `Y`, then the year is computed as `(CC-1)*100+YY`.
+
+This table shows some examples of the use of the `TO_CHAR` and `TO_DATE` functions:
+
+| Expression                                               | Result                      |
+| -------------------------------------------------------- | --------------------------- |
+| `TO_CHAR(CURRENT_TIMESTAMP, 'Day, DD  HH12:MI:SS')`      | `'Tuesday  , 06  05:39:18'` |
+| `TO_CHAR(CURRENT_TIMESTAMP, 'FM-Day, FMDD  HH12:MI:SS')` | `'Tuesday, 6  05:39:18'`    |
+| `TO_CHAR(-0.1, '99.99')`                                 | `'  -.10'`                  |
+| `TO_CHAR(-0.1, 'FM9.99')`                                | `'-.1'`                     |
+| `TO_CHAR(0.1, '0.9')`                                    | `' 0.1'`                    |
+| `TO_CHAR(12, '9990999.9')`                               | `'    0012.0'`              |
+| `TO_CHAR(12, 'FM9990999.9')`                             | `'0012.'`                   |
+| `TO_CHAR(485, '999')`                                    | `' 485'`                    |
+| `TO_CHAR(-485, '999')`                                   | `'-485'`                    |
+| `TO_CHAR(1485, '9,999')`                                 | `' 1,485'`                  |
+| `TO_CHAR(1485, '9G999')`                                 | `' 1,485'`                  |
+| `TO_CHAR(148.5, '999.999')`                              | `' 148.500'`                |
+| `TO_CHAR(148.5, 'FM999.999')`                            | `'148.5'`                   |
+| `TO_CHAR(148.5, 'FM999.990')`                            | `'148.500'`                 |
+| `TO_CHAR(148.5, '999D999')`                              | `' 148.500'`                |
+| `TO_CHAR(3148.5, '9G999D999')`                           | `' 3,148.500'`              |
+| `TO_CHAR(-485, '999S')`                                  | `'485-'`                    |
+| `TO_CHAR(-485, '999MI')`                                 | `'485-'`                    |
+| `TO_CHAR(485, '999MI')`                                  | `'485 '`                    |
+| `TO_CHAR(485, 'FM999MI')`                                | `'485'`                     |
+| `TO_CHAR(-485, '999PR')`                                 | `'<485>'`                   |
+| `TO_CHAR(485, 'L999')`                                   | `'$ 485'`                   |
+| `TO_CHAR(485, 'RN')`                                     | `'        CDLXXXV'`         |
+| `TO_CHAR(485, 'FMRN')`                                   | `'CDLXXXV'`                 |
+| `TO_CHAR(5.2, 'FMRN')`                                   | `'V'`                       |
+| `TO_CHAR(12, '99V999')`                                  | `' 12000'`                  |
+| `TO_CHAR(12.4, '99V999')`                                | `' 12400'`                  |
+| `TO_CHAR(12.45, '99V9')`                                 | `' 125'`                    |
+
+This table shows some examples of the use of the `TO_TIMESTAMP_TZ` function:
+
+| Expression                                                                    | Result                            |
+| ----------------------------------------------------------------------------- | --------------------------------- |
+| `TO_TIMESTAMP_TZ('12-JAN-2010', 'DD-MONTH-YYYY')`                             | `'12-JAN-10 00:00:00 +05:30'`     |
+| `TO_TIMESTAMP_TZ('03-APR-07 09:12:21 P.M','DD-MON-YY HH12:MI:SS A.M')`        | `'03-APR-07 09:12:21 +05:30'`     |
+| `TO_TIMESTAMP_TZ('2003/12/13 10:13:18 -8:00', 'YYYY/MM/DD HH:MI:SS TZH:TZM')` | `'13-DEC-03 23:43:18 +05:30'`     |
+| `TO_TIMESTAMP_TZ('20-MAR-20 04:30:00 +08:00', 'DD-MON-YY HH:MI:SS TZH:TZM')`  | `'20-MAR-20 02:00:00 +05:30'`     |
+| `TO_TIMESTAMP_TZ('10-Sep-02 14:10:10.123000', 'DD-MON-RR HH24:MI:SS.FF')`     | `'10-SEP-02 14:10:10.123 +05:30'` |
+| `TO_TIMESTAMP_TZ('20-MAR-20 04:30:00.123456 PM +03:00')`                      | `'20-MAR-20 09:30:00.123456 -04:00'` |
+
+<div id="immutable_to_char_function" class="registered_link"></div>
+
+## Available template patterns for numeric values
+
+This table lists the template patterns available for formatting numeric values:
+
+| Pattern      | Description                               |
+| ------------ | ----------------------------------------- |
+| `9`          | Value with the specified number of digits |
+| `0`          | Value with leading zeroes                 |
+| `. (period)` | Decimal point                             |
+| `, (comma)`  | Group (thousand) separator                |
+| `$`          | Dollar sign                               |
+| `S`          | Sign anchored to number (uses locale).    |
+| `L`          | Currency symbol (uses locale)             |
+
+The pattern `9` results in a value with the same number of digits as there are 9s. If a digit isn't available, the server ignores the corresponding 9s. The `S` pattern doesn't support `+`, and the `$` pattern doesn't support decimal points in the expression.
+
+This table shows some examples of the use of the `TO_NUMBER` function:
+
+| Expression                                 | Result         |
+| ------------------------------------------ | -------------- |
+| `TO_NUMBER('-65', 'S99')`                  | `' -65'`       |
+| `TO_NUMBER('$65', 'L99')`                  | `' 65'`        |
+| `TO_NUMBER('9678584', '9999999')`          | `' 9678584'`   |
+| `TO_NUMBER('123,456,789', '999,999,999')`  | `' 123456789'` |
+| `TO_NUMBER('1210.73', '9999.99')`          | `' 1210.73'`   |
+| `TO_NUMBER('1210.73')`                     | `' 1210.73'`   |
+| `TO_NUMBER('0101.010','FM99999999.99999')` | `' 101.010'`   |
+
+### Numeric modifiers
+
+This table shows the modifier pattern for numeric formatting:
+
+| Pattern     | Description                                             | Example   |
+| ----------- | ------------------------------------------------------- | --------- |
+| `FM` prefix | Fill mode (suppress trailing zeroes and padding blanks) | `FM99.99` |
+
+
+## Output formats for string and date functions
+
+In an output template string (for `TO_CHAR`), certain patterns are recognized and replaced with appropriately formatted data from the value to format. Any text that isn't a template pattern is copied verbatim. Similarly, in an input template string (for anything but `TO_CHAR`), template patterns identify the parts of the input data string to look at and the values to find there.
+
+If you don't specify a date, month, or year when calling `TO_TIMESTAMP`, `TO_TIMESTAMP_TZ`, or `TO_DATE`, then by default the output format considers the first date of a current month or current year. In the following example, date, month, and year isn't specified in the input string. `TO_TIMESTAMP`, `TO_TIMESTAMP_TZ`, and `TO_DATE` returns a default value of the first date of a current month and current year.
+
+```sql
+edb=# select to_timestamp('12', 'HH');
+__OUTPUT__
+      to_timestamp
+---------------------------
+ 01-MAY-20 12:00:00 +05:30
+(1 row)
+```
+
+```sql
+edb=# select to_timestamp_tz('12', 'HH');
+__OUTPUT__
+      to_timestamp_tz
+---------------------------
+ 01-MAY-20 12:00:00 +05:30
+(1 row)
+```
+
+```sql
+edb=# select to_date('12', 'HH');
+__OUTPUT__
+      to_date
+--------------------
+ 01-MAY-20 12:00:00
+(1 row)
+```
+
+## Altering the output format
+
+Alter the output format of `TO_DSINTERVAL(string)` using the `intervalstyle` GUC setting. For example:
+
+```sql
+edb=# SET intervalstyle = 'sql_standard';
+SET
+
+edb=# select to_dsinterval('80 13:30:00') from dual;
+__OUTPUT__
+to_dsinterval 
+---------------
+80 13:30:00
+```
+
+```sql
+edb=# SET intervalstyle = 'postgres_verbose';
+SET
+edb=# select to_dsinterval('80 13:30:00') from dual;
+__OUTPUT__
+to_dsinterval        
+----------------------------
+@ 80 days 13 hours 30 mins
+```
+
+## Creating an index with the IMMUTABLE form of the TO_CHAR function
+
+Certain cases of the `TO_CHAR` function results in usage of an `IMMUTABLE` form of the function. A function is `IMMUTABLE` if the function doesn't modify the database, and the function returns the same, consistent value dependent upon only its input parameters. That is, the settings of configuration parameters, the locale, the content of the database, and so on don't affect the results returned by the function.
+
+For more information about function volatility categories `VOLATILE`, `STABLE`, and `IMMUTABLE`, see the [function volatility doc](https://www.postgresql.org/docs/current/static/xfunc-volatility.html).
+
+A particular advantage of an `IMMUTABLE` function is that you can use it in the `CREATE INDEX` command to create an index based on that function.
+
+For the `TO_CHAR` function to use the `IMMUTABLE` form, you must satisfy these conditions:
+
+-   The first parameter of the `TO_CHAR` function must be of data type `TIMESTAMP`.
+-   The format specified in the second parameter of the `TO_CHAR` function must not affect the return value of the function based on factors such as language and locale. For example, you can use a format of `'YYYY-MM-DD HH24:MI:SS'` for an `IMMUTABLE` form of the function since the result of the function is the date and time expressed solely in numeric form, regardless of locale settings. However, you can't use a format of `'DD-MON-YYYY'` for an `IMMUTABLE` form of the function because the three-character abbreviation of the month can return different results depending upon the locale setting.
+
+Format patterns that result in a non-immutable function include any variations of spelled out or abbreviated months `(MONTH, MON)`, days `(DAY, DY)`, median indicators `(AM, PM)`, or era indicators `(BC, AD)`.
+
+For this example, a table with a `TIMESTAMP` column is created:
+
+```sql
+CREATE TABLE ts_tbl (ts_col TIMESTAMP);
+```
+
+This example shows the successful creation of an index with the `IMMUTABLE` form of the `TO_CHAR` function.
+
+```sql
+edb=# CREATE INDEX ts_idx ON ts_tbl (TO_CHAR(ts_col,'YYYY-MM-DD HH24:MI:SS'));
+CREATE INDEX
+edb=# \dS ts_idx
+__OUTPUT__
+                                   Index "public.ts_idx"
+ Column  |       Type        |                         Definition
+---------+-------------------+------------------------------------------------------------
+ to_char | character varying | to_char(ts_col, 'YYYY-MM-DD HH24:MI:SS'::character varying)
+btree, for table "public.ts_tbl"
+```
+
+This results in an error because the format specified in the `TO_CHAR` function prevents the use of the `IMMUTABLE` form since the three-character month abbreviation, `MON`, can result in different return values based on the locale setting.
+
+```sql
+edb=# CREATE INDEX ts_idx_2 ON ts_tbl (TO_CHAR(ts_col, 'DD-MON-YYYY'));
+ERROR:  functions in index expression must be marked IMMUTABLE
+```
+
+### Difference TO_CHAR, TO_NUMBER, and SUBSTR functions 
+
+Initialize the database using the `INITDBOPTS` variable to create clusters in a mode compatible with Oracle databases. The clusters created in PostgreSQL mode don't include compatibility features. To create a new cluster in PostgreSQL mode, use the `"--no-redwood-compat"` option, which offers a similar behavior to PostgreSQL. 
+
+A `SELECT` statement that contains one of the functions shown in the following table returns the indicated result in EDB Postgres Advanced Server and PostgreSQL. Listed are the following differences for `TO_CHAR`, `TO_NUMBER`, and `SUBSTR` functions.
+
+**TO_CHAR**: Converts the timestamp to string according to a given format. 
+
+!!! Note
+    -  The `'syear'`, `'syyyy'`, `'year'`, `'rrrr'`, `'sp'`, `'spth'`, `'scc'`, `'rr'`, `'ff'`, `'ff7'`, `'ff8'`, `'ff9'`, and lowercase `'of'`, `'tzh'`, and `'tzm'` patterns aren't supported in PostgreSQL.
+    -  `'TH'` modifier adds fewer padding zeros in EDB Postgres Advanced Server.
+    -  The upper case `'TH'` pattern, which displays the suffix in uppercase, isn't supported in EDB Postgres Advanced Server. If you specify the `'TH/th'` pattern, the suffix is always displayed in lower case.  
+    -  A modifier can appear in an `'FM'` pattern, and each occurrence toggles the modifier's effect. To toggle the effect of the `'FM'` pattern, specify it an even number of times to turn off the effect and specify it an odd number of times to turn on the effect of the `'FM'` pattern in PostgreSQL. However, in EDB Postgres Advanced Server, specifying the `'FM'` pattern always turns on the effect of the `'FM'` pattern.
+
+This table shows the examples for `TO_CHAR(timestamp, text)` function:
+
+| Examples                                                                                                                                                                                                                               | Result                                                                                                 |                                                                                                    
+| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------- |
+|                                                                                                                                                                                                                                        | **EDB Postgres Advanced Server** | **PostgreSQL**                                                                   |
+| `SELECT TO_CHAR(current_timestamp, 'of');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'OF');`                                                                                                                                     | `+05:30`            | `of` <br /><br /> `+05:30`                                                       | 
+| `SELECT TO_CHAR(current_timestamp, 'syear');`                                                                                                                                                                                          | `twenty twenty one` | `s1ear`                                                                          | 
+| `SELECT TO_CHAR(current_timestamp, 'syyyy');`                                                                                                                                                                                          | `2021`              | `s2021`                                                                          |
+| `SELECT TO_CHAR(current_timestamp, 'year');`                                                                                                                                                                                           | `twenty twenty one` | `1ear`                                                                           |
+| `SELECT TO_CHAR(current_timestamp, 'rrrr');`                                                                                                                                                                                           | `2021`              | `rrrr`                                                                           |
+| `SELECT TO_CHAR(current_timestamp, 'hhsp');`                                                                                                                                                                                           | `five`              | `05sp`                                                                           |
+| `SELECT TO_CHAR(current_timestamp, 'hhspth');`                                                                                                                                                                                         | `fifth`             | `05spth`                                                                         |
+| `SELECT TO_CHAR(current_timestamp, 'scc');`                                                                                                                                                                                            | `21`                | `s21`                                                                            |
+| `SELECT TO_CHAR(current_timestamp, 'rr');`                                                                                                                                                                                             | `21`                | `rr`                                                                             |
+| `SELECT TO_CHAR(current_timestamp, 'ff');`                                                                                                                                                                                             | `923202`            | `ff`                                                                             |
+| `SELECT TO_CHAR(current_timestamp, 'ff7');`                                                                                                                                                                                            | `4192310`           | `ff7`                                                                            |
+| `SELECT TO_CHAR(current_timestamp, 'ff8');`                                                                                                                                                                                            | `36181700`          | `ff8`                                                                            |
+| `SELECT TO_CHAR(current_timestamp, 'ff9');`                                                                                                                                                                                            | `640405000`         | `ff9`                                                                            |
+| `SELECT TO_CHAR(current_timestamp, 'tzh');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'TZH');`                                                                                                                                   | `+05`               | `isth` <br /><br /> `+05`                                                        |  
+| `SELECT TO_CHAR(current_timestamp, 'TZM');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'tzm');`                                                                                                                                   | `30`                | `30` <br /><br /> `istm`                                                         | 
+| `SELECT TO_CHAR(current_timestamp, 'iddd');`                                                                                                                                                                                           | `1134`              | `131`                                                                            |                                                                                   
+| `SELECT TO_CHAR(current_timestamp, 'id');`                                                                                                                                                                                             | `16`                | `5`                                                                              |
+| `SELECT TO_CHAR(current_timestamp, 'ssss');`                                                                                                                                                                                           | `5555`              | `64490`                                                                          |
+| `SELECT TO_CHAR(current_timestamp, 'hhthth');`                                                                                                                                                                                         | Invalid format      | `11thth`                                                                         |
+| `SELECT TO_CHAR(current_timestamp, 'rmth');`                                                                                                                                                                                           | Invalid format      | `v`                                                                              |
+| `SELECT TO_CHAR(current_timestamp, 'FMOF');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'FMFMOF');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'FMFMFMOF');` <br /><br /> `SELECT TO_CHAR(current_timestamp, 'FMFMFMFMOF');` | `+5:30`             | `+5:30` <br /><br /> `FM+05:30` <br /><br /> `FM+5:30` <br /><br /> `FMFM+05:30` |
+| `SELECT TO_CHAR(timestamptz'5-MAY-21 17:37:14 +05:30', 'DDTH');`                                                                                                                                                                       | `05th`              | `05TH`                                                                           |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'FMY,YYY');`                                                                                                                                                                  | `1`                 | `0,001`                                                                          |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'Y,YYYTH');`                                                                                                                                                                  | `01st`              | `0,001ST`                                                                        |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'IYYYTH');`                                                                                                                                                                   | `01st`              | `0001ST`                                                                         |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'YYYYTH');`                                                                                                                                                                   | `01st`              | `0001ST`                                                                         |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'IYYTH');`                                                                                                                                                                    | `01st`              | `001ST`                                                                          |
+| `SELECT TO_CHAR(timestamptz'5-JAN-0001 17:37:14 +05:30', 'YYYTH');`                                                                                                                                                                    | `01st`              | `001ST`                                                                          |
+
+**TO_NUMBER**: Converts the string to numeric according to a given format.
+
+!!! Note
+    -  PostgreSQL doesn't strictly check the format options. In contrast, EDB Postgres Advanced Server checks the format except in a few cases when the input string has `'-'` or `','` at the beginning. You don't have to provide the pattern for these characters in the corresponding location in the format string.
+    -  In PostgreSQL, you don't have to match all the digits of the input string with the patterns. It outputs the number of digits from the input string for which the valid patterns are present. EDB Postgres Advanced Server throws an error if you don't provide patterns for all the digits present in the input string.
+    -  PostgreSQL ignores any invalid characters present in the input or the format string. EDB Postgres Advanced Server throws an error. This kind of behavior can lead to many differences with different types of patterns.
+    -  The patterns `'PL'`, `'PR'`, and `'SG'` aren't supported in EDB Postgres Advanced Server.
+
+This table shows the examples for the `TO_NUMBER(text, text)` function:
+
+| Examples                                                                                         | Result                                                                                         |                                                                            
+| ------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------- | -------------------------- | 
+|                                                                                                  | **EDB Postgres Advanced Server**                                               | **PostgreSQL**             |
+| `SELECT TO_NUMBER('$1', '00');`                                                                  | Invalid input syntax for type numeric: "$1"                       | `1`                        |
+| `SELECT TO_NUMBER('$$1', '$$0');`                                                                | Invalid format string: "$$0"                                      | `1`                        |
+| `SELECT TO_NUMBER('1$', '0$');`                                                                  | Invalid input syntax for type numeric: "1."                       | `1`                        |
+| `SELECT TO_NUMBER('$1$', '$0$');`                                                                | Invalid format string: "$0$"                                      | `1`                        |
+| `SELECT TO_NUMBER('1$$1', '0$L0');`                                                              | Invalid input syntax for type numeric: "1.$1"                     | `11`                       |
+| `SELECT TO_NUMBER('1,11', '000');`                                                               | `111`                                                             | `11`                       |
+| `SELECT TO_NUMBER('1,11', '0,0');`                                                               | Invalid input syntax for type numeric: "111"                      | `11`                       |
+| `SELECT TO_NUMBER('1-1', '0S0');`                                                                | Invalid format string: "0S0"                                      | `-11`                      |
+| `SELECT TO_NUMBER('1-1', '000');`                                                                | Invalid input syntax for type numeric: "1-1"                      | `11`                       |
+| `SELECT TO_NUMBER('1.11', '000');`                                                               | Invalid input syntax for type numeric: "1.11"                     | `11`                       |    
+| `SELECT TO_NUMBER('1..1', '0.0');`                                                               | Invalid input syntax for type numeric: "1..1"                     | `1`                        |
+| `SELECT TO_NUMBER('$11-', '$00S');`                                                              | Invalid input syntax for type numeric: "-$11"                     | `-11`                      |
+| `SELECT TO_NUMBER('11', '');`                                                                    | Invalid input syntax for type numeric: "11"                       | Returns blank              |
+| `SELECT TO_NUMBER(' ', '');`                                                                     | Invalid input syntax for type numeric: ""                         | Returns blank              |
+| `SELECT TO_NUMBER('$12.345', 'L00.000');`                                                        | Invalid format string: "L00.000"                                  | `12.345`                   |
+| `SELECT TO_NUMBER('$12.345', 'L00D000');`                                                        | Invalid format string: "L00.000"                                  | `12.345`                   |
+| `SELECT TO_NUMBER('11-', '9MMI');`                                                               | Invalid format string: "9MMI"                                     | `-1`                       |
+| `SELECT TO_NUMBER('-11', 'MI99');`                                                               | Invalid input syntax for type numeric: "-11"                      | `-11`                      |
+| `SELECT TO_NUMBER('000011', 'FMFM000000');`                                                      | Invalid format string: "FMFM000000"                               | `11`                       |
+| `SELECT TO_NUMBER('+11', 'S99');`  <br /><br /> `SELECT TO_NUMBER('11+', '99S');`                | Invalid input syntax for type numeric: "+11"  <br /><br />  `11`  | `11`  <br /><br />  `11`   |
+| `SELECT TO_NUMBER('+11', 'PL99');`                                                               | Invalid format string: "PL99"                                     | `11`                       |
+| `SELECT TO_NUMBER('-11', '99PR');`                                                               | Invalid format string: "99PR"                                     | `-11`                      |
+| `SELECT TO_NUMBER('1+1-1', '9SG9SG9');`                                                          | Invalid format string: "9SG9SG9"                                  | `-111`                     |
+| `SELECT TO_NUMBER('01,000', '99G999');`  <br /><br /> `SELECT TO_NUMBER('01,000', 'FM99G999');`  | `1000`                                                            | `1000` <br /><br />  `100` |
+
+**SUBSTR**: Returns a substring of a character value. 
+
+!!! Note
+    -   The index of the string starts from `1`. In PostgreSQL, if zero is the start parameter to fetch only one character, the result returns blank. If you try to fetch two characters, the result shows one character since zero is specified in the start position. However, in EDB Postgres Advanced Server, if zero is the start parameter, internally it converts to `1` and starts the searching.
+    -   Negative values at the start parameter aren't allowed in PostgreSQL. In EDB Postgres Advanced Server, negative values cause a reverse search to occur.
+    -   PostgreSQL throws an error if a numeric value is passed for start and length parameter. EDB Postgres Advanced Server converts it to an integer.
+
+This table shows the examples for `SUBSTR(string, from, count)`, `SUBSTR(string, from)`, `SUBSTR(string, from, count)::bytea`, and `SUBSTR(string, from)::bytea` function:
+
+| Examples                                                                          | Result                                                                                   |                                                                            
+| --------------------------------------------------------------------------------- | -------------------- | ----------------------------------------------------------------- | 
+|                                                                                   | **EDB Postgres Advanced Server**  | **PostgreSQL**                                                    |
+| `SELECT (SUBSTR('ABCDEFGH', 0, 1));`                                              | `A`                  | Returns blank                                                     | 
+| `SELECT (SUBSTR('ABCD', -1, 1));`  <br /><br /> `SELECT (SUBSTR('ABCD', -4, 1));` | `D` <br /><br /> `A` | Returns blank                                                     |
+| `SELECT (SUBSTR('ABCD', 1, -1));`                                                 | Returns blank        | ERROR: negative substring length not allowed                      |
+| `SELECT (SUBSTR('ABCD', 1.1, 1));`                                                | `A`                  | ERROR: function substr(unknown, numeric, integer) does not exist  |
+| `SELECT (SUBSTR('ABCD', 1, 1.1));`                                                | `A`                  | ERROR: function substr(unknown, integer, numeric) does not exist  | 
+| `SELECT (SUBSTR('ABCD', -1));`                                                    | `D`                  | `ABCD`                                                            |
+| `SELECT (SUBSTR('ABCD', 1.1));`                                                   | `ABCD`               | ERROR: function substr(unknown, numeric) does not exist           |
+| `SELECT (SUBSTR('ABCDEFGH', 0, 1))::bytea;`                                       | `\x41`               | `\x`                                                              |
+| `SELECT (SUBSTR('ABCD', 5,1))::bytea;`                                            | Returns blank        | `\x`                                                              |
+| `SELECT (SUBSTR('ABCDEFGH', -1, 1))::bytea;`                                      | `\x48`               | `\x`                                                              |
+| `SELECT (SUBSTR('ABCD', -5, 1))::bytea;`                                          | Returns blank        | `\x`                                                              |
+| `SELECT (SUBSTR('ABCD', 1, -1))::bytea;`                                          | Returns blank        | ERROR: negative substring length not allowed                      |
+| `SELECT (SUBSTR('ABCD', 1.1, 1))::bytea;`                                         | `\x41`               | ERROR: function substr(unknown, numeric, integer) does not exist  |
+| `SELECT (SUBSTR('ABCD', 1, 1.1))::bytea;`                                         | `\x41`               | ERROR: function substr(unknown, integer, numeric) does not exist  |
+| `SELECT (SUBSTR('ABCD', 5))::bytea;`                                              | Returns blank        | `\x`                                                              |
+| `SELECT (SUBSTR('ABCD', -1))::bytea;`                                             | `\x44`               | `\x41424344`                                                      |
+| `SELECT (SUBSTR('ABCD', 1.1))::bytea;`                                            | `\x41424344`         | ERROR: function substr(unknown, numeric) does not exist           |
+                                                                                                          
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/08_date_time_functions_and_operators.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/08_date_time_functions_and_operators.mdx
new file mode 100644
index 00000000000..b14dd43173c
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/08_date_time_functions_and_operators.mdx
@@ -0,0 +1,853 @@
+---
+title: "Date/time functions and operators"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.101.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.135.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.044.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/08_date_time_functions_and_operators/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+The date/time functions table shows the available functions for date/time value processing. 
+
+## Overview of basic arithmetic operators
+
+The following table shows the behaviors of the basic arithmetic operators `(+, -)`. For formatting functions, refer to [IMMUTABLE TO_CHAR(TIMESTAMP, format)](07_data_type_formatting_functions/#immutable_to_char_function). For more information on date/time data types, see [Date/time types](../02_data_types/04_date_time_types/#date_time_types).
+
+| Operator    | Example                                                             | Result               |
+| ----------- | ------------------------------------------------------------------- | -------------------- |
+| plus `(+)`  | `DATE '2001-09-28' + 7`                                             | `05-OCT-01 00:00:00` |
+| plus `(+)`  | `TIMESTAMP '2001-09-28 13:30:00' + 3`                               | `01-OCT-01 13:30:00` |
+| minus `(-)` | `DATE '2001-10-01' – 7`                                             | `24-SEP-01 00:00:00` |
+| minus `(-)` | `TIMESTAMP '2001-09-28 13:30:00' - 3`                               | `25-SEP-01 13:30:00` |
+| minus `(-)` | `TIMESTAMP '2001-09-29 03:00:00' - TIMESTAMP '2001-09-27 12:00:00'` | `@ 1 day 15 hours`   |
+
+## Overview of date and time functions
+
+In the date/time functions of the following table the use of the `DATE` and `TIMESTAMP` data types are interchangeable.
+
+| Function                                    | Return type        | Description                                                                                                                                               | Example                                                                             | Result                              |
+| ------------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | ----------------------------------- |
+| `ADD_MONTHS (DATE, NUMBER)`                 | `DATE`             | Adds months to a date.                                                                                                                                      | `ADD_MONTHS ('28-FEB-97', ,3.8)`                                                    | `31-MAY-97 00:00:00`                |
+| `CURRENT_DATE`                              | `DATE`             | Current date.                                                                                                                                              | `CURRENT_DATE`                                                                      | `04-JUL-07`                         |
+| `CURRENT_TIMESTAMP`                         | `TIMESTAMP`        | Returns the current date and time.                                                                                                                         | `CURRENT_TIMESTAMP`                                                                 | `04-JUL-07 15:33:23.484`            |
+| `EXTRACT(field FROM TIMESTAMP)`             | `DOUBLE PRECISION` | Gets subfield.                                                                                                                                              | `EXTRACT(hour FROM TIMESTAMP '2001-02-16 20:38:40')`                                | `20`                                |
+| `LAST_DAY(DATE)`                            | `DATE`             | Returns the last day of the month represented by the given date. If the given date contains a time portion, it's carried forward to the result unchanged. | `LAST_DAY('14-APR-98')`                                                             | `30-APR-98 00:00:00`                |
+| `LOCALTIMESTAMP [ (precision) ]`            | `TIMESTAMP`        | Current date and time (start of current transaction).                                                                                                      | `LOCALTIMESTAMP`                                                                    | `04-JUL-07 15:33:23.484`            |
+| `MONTHS_BETWEEN (DATE, DATE)`               | `NUMBER`           | Number of months between two dates.                                                                                                                        | `MONTHS_BETWEEN ('28-FEB-07', '30-NOV-06')`                                         | `3`                                 |
+| `NEXT_DAY(DATE, dayofweek)`                 | `DATE`             | Date falling on `dayofweek` following specified date.                                                                                                      | `NEXT_DAY('16-APR-07',FRI' )`                                                       | `20-APR-07 00:00:00`                |
+| `NEW_TIME(DATE, VARCHAR, VARCHAR)`          | `DATE`             | Converts a date and time to an alternate time zone.                                                                                                        | `NEW_TIME (TO_DATE '2005/05/29 01:45', 'AST', 'PST')`                               | `2005/05/29 21:45:00`               |
+| `NUMTODSINTERVAL(NUMBER, INTERVAL)`         | `INTERVAL`         | Converts a number to a specified day or second interval.                                                                                                   | `SELECT numtodsinterval(100, ‘hour’);`                                              | `4 days 04:00:00`                   |
+| `NUMTOYMINTERVAL(NUMBER, INTERVAL)`         | `INTERVAL`         | Converts a number to a specified year or month interval.                                                                                                   | `SELECT numtoyminterval(100, ‘month’);`                                             | `8 years 4 mons`                    |
+| `ROUND(DATE [, format ])`                   | `DATE`             | Date rounded according to `format`.                                                                                                                        | `ROUND(TO_DATE('29-MAY-05'),'MON')`                                                 | `01-JUN-05 00:00:00`                |
+| `SYS_EXTRACT_UTC(TIMESTAMP WITH TIME ZONE)` | `TIMESTAMP`        | Returns Coordinated Universal Time.                                                                                                                        | `SYS_EXTRACT_UTC(CAST ('24-MAR-11 12:30:00PM -04:00' AS TIMESTAMP WITH TIME ZONE))` | ` 24-MAR-11 16:30:00`               |
+| `SYSDATE`                                   | `DATE`             | Returns current date and time.                                                                                                                             | `SYSDATE`                                                                           | `01-AUG-12 11:12:34`                |
+| `SYSTIMESTAMP()`                            | `TIMESTAMP`        | Returns current date and time.                                                                                                                             | `SYSTIMESTAMP`                                                                      | `01-AUG-12 11:11:23. 665229 -07:00` |
+| `TRUNC(DATE [format])`                      | `DATE`             | Truncates according to `format`.                                                                                                                            | `TRUNC(TO_DATE ('29-MAY-05'), 'MON')`                                              | `01-MAY-05 00:00:00`                |
+| `DBTIMEZONE`                                | `[+\|-]TZH:TZM` or time zone region name    | Returns time zone offset in the format `[+\|-]TZH:TZM` or time zone region name.                                                     | `DBTIMEZONE`                                                                       | `-9:00` or `Europe/London`          |
+| `SESSIONTIMEZONE`                           | `[+\|-]TZH:TZM` or time zone region name    | Returns time zone offset in the format `[+\|-]TZH:TZM` or time zone region name.                                                     | `SESSIONTIMEZONE`                                                                  | `-9:00` or `Europe/London`          |
+
+## ADD_MONTHS
+
+The `ADD_MONTHS` functions adds or subtracts the specified number of months to or from the given date. Use a negative value to subtract. The resulting day of the month is the same as the day of the month of the given date except when the day is the last day of the month. In that case, the resulting date always falls on the last day of the month.
+
+Any fractional portion of the number of months parameter is truncated before performing the calculation.
+
+If the given date contains a time portion, it's carried forward to the result unchanged.
+
+These examples show the `ADD_MONTHS` function:
+
+```sql
+SELECT ADD_MONTHS('13-JUN-07',4) FROM DUAL;
+__OUTPUT__
+     add_months
+--------------------
+ 13-OCT-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ADD_MONTHS('31-DEC-06',2) FROM DUAL;
+__OUTPUT__
+     add_months
+--------------------
+ 28-FEB-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ADD_MONTHS('31-MAY-04',-3) FROM DUAL;
+__OUTPUT__
+     add_months
+--------------------
+ 29-FEB-04 00:00:00
+(1 row)
+```
+
+## CURRENT DATE/TIME
+
+EDB Postgres Advanced Server provides functions that return values related to the current date and time. These functions return values based on the start time of the current transaction:
+
+-   `CURRENT_DATE`
+-   `CURRENT_TIMESTAMP`
+-   `LOCALTIMESTAMP`
+-   `LOCALTIMESTAMP(precision)`
+
+`CURRENT_DATE` returns the current date and time based on the start time of the current transaction. The value of `CURRENT_DATE` doesn't change if called multiple times in a transaction.
+
+```sql
+SELECT CURRENT_DATE FROM DUAL;
+__OUTPUT__
+   date
+-----------
+ 06-AUG-07
+```
+
+`CURRENT_TIMESTAMP` returns the current date and time. When called from a single SQL statement, it returns the same value for each occurrence in the statement. If called from multiple statements in a transaction, it might return different values for each occurrence. If called from a function, it might return a value different from the one returned by `current_timestamp` in the caller.
+
+```sql
+SELECT CURRENT_TIMESTAMP, CURRENT_TIMESTAMP FROM DUAL;
+__OUTPUT__
+                current_timestamp | current_timestamp
+----------------------------------+----------------------------------
+ 02-SEP-13 17:52:29.261473 +05:00 | 02-SEP-13 17:52:29.261474 +05:00
+```
+
+You can optionally give `LOCALTIMESTAMP` a precision parameter. The parameter causes the result to be rounded to the specified number of fractional digits in the seconds field. Without a precision parameter, the result is given to the full available precision.
+
+```sql
+SELECT LOCALTIMESTAMP FROM DUAL;
+__OUTPUT__
+       timestamp
+------------------------
+ 06-AUG-07 16:11:35.973
+(1 row)
+```
+```sql
+SELECT LOCALTIMESTAMP(2) FROM DUAL;
+__OUTPUT__
+       timestamp
+-----------------------
+ 06-AUG-07 16:11:44.58
+(1 row)
+```
+
+Since these functions return the start time of the current transaction, their values don't change during the transaction. The intent is to allow a single transaction to have a consistent notion of the “current” time, so that multiple modifications in the same transaction have the same timestamp. Other database systems might advance these values more frequently.
+
+## TIMEZONE functions
+
+EDB Postgres Advanced Server provides functions that return timezone set values.
+
+### DBTIMEZONE
+
+`DBTIMEZONE` returns the value of the database time zone. The return type is a time zone offset in the format `[+\|-]TZH:TZM` or a time zone region name. The return type depends on the database time zone value specified in the recent `CREATE DATABASE` or `ALTER DATABASE` statement.
+
+```sql
+ALTER DATABASE edb SET TIMEZONE='-09:00';
+SELECT dbtimezone FROM DUAL;
+__OUTPUT__
+ dbtimezone 
+------------
+ -09:00
+(1 row)
+```
+
+```sql
+ALTER DATABASE edb SET TIMEZONE='Europe/London';
+SELECT dbtimezone FROM DUAL;
+__OUTPUT__
+  dbtimezone   
+---------------
+ Europe/London
+(1 row)
+```
+### SESSIONTIMEZONE
+
+`SESSIONTIMEZONE` returns the time zone of the current session. The return type is a time zone offset in the format `[+\|-]TZH:TZM` or a time zone region name. The return type depends on the session time zone value specified in the recent `ALTER SESSION` or `SET` statement.
+
+```sql
+ALTER SESSION SET timezone to 'America/New_York';
+SELECT sessiontimezone() FROM dual;
+__OUTPUT__
+ sessiontimezone  
+------------------
+ America/New_York
+(1 row)
+```
+
+```sql
+SET timezone TO '+5:30';
+SELECT sessiontimezone() FROM dual;
+__OUTPUT__
+ sessiontimezone 
+-----------------
+ +5:30
+(1 row)
+```
+
+## EXTRACT
+
+The `EXTRACT` function retrieves subfields such as year or hour from date/time values. The `EXTRACT` function returns values of type `DOUBLE PRECISION`. The following are valid field names:
+
+`YEAR`
+
+ The year field.
+
+```sql
+SELECT EXTRACT(YEAR FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+     2001
+(1 row)
+```
+
+`MONTH`
+
+ The number of the month in the year (1 - 12).
+
+```sql
+SELECT EXTRACT(MONTH FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+       2
+(1 row)
+```
+
+`DAY`
+
+ The day of the month field (1 - 31).
+
+```sql
+SELECT EXTRACT(DAY FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+       16
+(1 row)
+```
+
+`HOUR`
+
+ The hour field (0 - 23).
+
+```sql
+SELECT EXTRACT(HOUR FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+       20
+(1 row)
+```
+
+`MINUTE`
+
+ The minutes field (0 - 59).
+
+```sql
+SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+       38
+(1 row)
+```
+
+`SECOND`
+
+ The seconds field, including fractional parts (0 - 59).
+
+```sql
+SELECT EXTRACT(SECOND FROM TIMESTAMP '2001-02-16 20:38:40') FROM DUAL;
+__OUTPUT__
+ date_part
+-----------
+       40
+(1 row)
+```
+
+## MONTHS_BETWEEN
+
+The `MONTHS_BETWEEN` function returns the number of months between two dates. The result is a numeric value that's positive if the first date is greater than the second date. It's negative if the first date is less than the second date.
+
+The result is always a whole number of months if the day of the month of both date parameters is the same or both date parameters fall on the last day of their respective months.
+
+These examples show the `MONTHS_BETWEEN` function:
+
+```sql
+SELECT MONTHS_BETWEEN('15-DEC-06','15-OCT-06') FROM DUAL;
+__OUTPUT__
+ months_between
+----------------
+              2
+(1 row)
+```
+```sql
+SELECT MONTHS_BETWEEN('15-OCT-06','15-DEC-06') FROM DUAL;
+__OUTPUT__
+ months_between
+----------------
+             -2
+(1 row)
+```
+```sql
+SELECT MONTHS_BETWEEN('31-JUL-00','01-JUL-00') FROM DUAL;
+__OUTPUT__
+ months_between
+----------------
+    0.967741935
+(1 row)
+```
+```sql
+SELECT MONTHS_BETWEEN('01-JAN-07','01-JAN-06') FROM DUAL;
+__OUTPUT__
+ months_between
+----------------
+             12
+(1 row)
+```
+
+## NEXT_DAY
+
+The `NEXT_DAY` function returns the first occurrence of the given weekday strictly greater than the given date. You must specify at least the first three letters of the weekday, for example, `SAT`. If the given date contains a time portion, it's carried forward to the result unchanged.
+
+These examples show the `NEXT_DAY` function.
+
+```sql
+SELECT NEXT_DAY(TO_DATE('13-AUG-07','DD-MON-YY'),'SUNDAY') FROM DUAL;
+__OUTPUT__
+      next_day
+--------------------
+ 19-AUG-07 00:00:00
+(1 row)
+```
+```sql
+SELECT NEXT_DAY(TO_DATE('13-AUG-07','DD-MON-YY'),'MON') FROM DUAL;
+__OUTPUT__
+      next_day
+--------------------
+ 20-AUG-07 00:00:00
+(1 row)
+```
+
+## NEW_TIME
+
+The `NEW_TIME` function converts a date and time from one time zone to another. `NEW_TIME` returns a value of type `DATE`. The syntax is:
+
+```sql
+NEW_TIME(DATE, time_zone1, time_zone2)
+```
+
+`time_zone1` and `time_zone2` must be string values from the **Time zone** column of the following table.
+
+| Time zone | Offset from UTC | Description                 |
+| --------- | --------------- | --------------------------- |
+| `AST`     | UTC+4           | Atlantic Standard Time      |
+| `ADT`     | UTC+3           | Atlantic Daylight Time      |
+| `BST`     | UTC+11          | Bering Standard Time        |
+| `BDT`     | UTC+10          | Bering Daylight Time        |
+| `CST`     | UTC+6           | Central Standard Time       |
+| `CDT`     | UTC+5           | Central Daylight Time       |
+| `EST`     | UTC+5           | Eastern Standard Time       |
+| `EDT`     | UTC+4           | Eastern Daylight Time       |
+| `GMT`     | UTC             | Greenwich Mean Time         |
+| `HST`     | UTC+10          | Alaska-Hawaii Standard Time |
+| `HDT`     | UTC+9           | Alaska-Hawaii Daylight Time |
+| `MST`     | UTC+7           | Mountain Standard Time      |
+| `MDT`     | UTC+6           | Mountain Daylight Time      |
+| `NST`     | UTC+3:30        | Newfoundland Standard Time  |
+| `PST`     | UTC+8           | Pacific Standard Time       |
+| `PDT`     | UTC+7           | Pacific Daylight Time       |
+| `YST`     | UTC+9           | Yukon Standard Time         |
+| `YDT`     | UTC+8           | Yukon Daylight Time         |
+
+This example shows the `NEW_TIME` function:
+
+```sql
+SELECT NEW_TIME(TO_DATE('08-13-07 10:35:15','MM-DD-YY HH24:MI:SS'),'AST',
+'PST') "Pacific Standard Time" FROM DUAL;
+__OUTPUT__
+Pacific Standard Time
+---------------------
+ 13-AUG-07 06:35:15
+(1 row)
+```
+
+## NUMTODSINTERVAL
+
+The `NUMTODSINTERVAL` function converts a numeric value to a time interval that includes day-through-second interval units. When calling the function, specify the smallest fractional interval type to include in the result set. The valid interval types are `DAY`, `HOUR`, `MINUTE`, and `SECOND`.
+
+This example converts a numeric value to a time interval that includes days and hours:
+
+```sql
+SELECT numtodsinterval(100, ‘hour’);
+__OUTPUT__
+numtodsinterval
+---------------
+4 days 04:00:00
+(1 row)
+```
+
+This example converts a numeric value to a time interval that includes minutes and seconds:
+
+```sql
+SELECT numtodsinterval(100, ‘second’);
+__OUTPUT__
+numtodsinterval
+---------------
+1 min 40 secs
+(1 row)
+```
+
+## NUMTOYMINTERVAL
+
+The `NUMTOYMINTERVAL` function converts a numeric value to a time interval that includes year-through-month interval units. When calling the function, specify the smallest fractional interval type to include in the result set. The valid interval types are `YEAR` and `MONTH`.
+
+This example converts a numeric value to a time interval that includes years and months:
+
+```sql
+SELECT numtoyminterval(100, ‘month’);
+__OUTPUT__
+numtoyminterval
+---------------
+8 years 4 mons
+(1 row)
+```
+
+This example converts a numeric value to a time interval that includes years only:
+
+```sql
+SELECT numtoyminterval(100, ‘year’);
+__OUTPUT__
+numtoyminterval
+---------------
+100 years
+(1 row)
+```
+
+## ROUND
+
+The `ROUND` function returns a date rounded according to a specified template pattern. If you omit the template pattern, the date is rounded to the nearest day. The following table shows the template patterns for the `ROUND` function.
+
+| Pattern                               | Description                                                                                                                                                                                                                                          |
+| ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `CC, SCC`                             | Returns January 1, `cc`01 where `cc` is first 2 digits of the given year if last 2 digits &lt;= 50, or 1 greater than the first 2 digits of the given year if last 2 digits > 50; (for AD years)                                                     |
+| `SYYY, YYYY, YEAR, SYEAR, YYY, YY, Y` | Returns January 1, `yyyy` where `yyyy` is rounded to the nearest year; rounds down on June 30, rounds up on July 1                                                                                                                                   |
+| `IYYY, IYY, IY, I`                    | Rounds to the beginning of the ISO year, which is determined by rounding down if the month and day is on or before June 30th or by rounding up if the month and day is July 1st or later                                                             |
+| `Q`                                   | Returns the first day of the quarter determined by rounding down if the month and day is on or before the 15th of the second month of the quarter or by rounding up if the month and day is on the 16th of the second month or later of the quarter |
+| `MONTH, MON, MM, RM`                  | Returns the first day of the specified month if the day of the month is on or prior to the 15th; returns the first day of the following month if the day of the month is on the 16th or later                                                        |
+| `WW`                                  | Rounds to the nearest date that corresponds to the same day of the week as the first day of the year                                                                                                                                                  |
+| `IW`                                  | Rounds to the nearest date that corresponds to the same day of the week as the first day of the ISO year                                                                                                                                              |
+| `W`                                   | Rounds to the nearest date that corresponds to the same day of the week as the first day of the month                                                                                                                                                 |
+| `DDD, DD, J`                          | Rounds to the start of the nearest day; 11:59:59 AM or earlier rounds to the start of the same day; 12:00:00 PM or later rounds to the start of the next day                                                                                         |
+| `DAY, DY, D`                          | Rounds to the nearest Sunday                                                                                                                                                                                                                         |
+| `HH, HH12, HH24`                      | Round to the nearest hour                                                                                                                                                                                                                            |
+| `MI`                                  | Rounds to the nearest minute                                                                                                                                                                                                                          |
+
+These examples show the use of the `ROUND` function.
+
+These examples round to the nearest hundred years:
+
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('1950','YYYY'),'CC'),'DD-MON-YYYY') "Century" FROM DUAL;
+__OUTPUT__
+   Century
+-------------
+ 01-JAN-1901
+(1 row)
+```
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('1951','YYYY'),'CC'),'DD-MON-YYYY') "Century" FROM DUAL;
+__OUTPUT__
+   Century
+-------------
+ 01-JAN-2001
+(1 row)
+```
+
+These examples round to the nearest year:
+
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('30-JUN-1999','DD-MON-YYYY'),'Y'),'DD-MON-YYYY') "Year" FROM DUAL;
+__OUTPUT__
+    Year
+-------------
+ 01-JAN-1999
+(1 row)
+```
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('01-JUL-1999','DD-MON-YYYY'),'Y'),'DD-MON-YYYY') "Year" FROM DUAL;
+__OUTPUT__
+    Year
+-------------
+ 01-JAN-2000
+(1 row)
+```
+
+These examples round to the nearest ISO year. The first example rounds to 2004, and the ISO year for 2004 begins on December 29, 2003. The second example rounds to 2005, and the ISO year for 2005 begins on January 3 of that same year.
+
+(An ISO year begins on the first Monday from which a seven-day span, Monday through Sunday, contains at least four days of the new year. It's possible for the beginning of an ISO year to start in December of the prior year.)
+
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('30-JUN-2004','DD-MON-YYYY'),'IYYY'),'DD-MON-YYYY') "ISO Year" FROM DUAL;
+__OUTPUT__
+  ISO Year
+-------------
+ 29-DEC-2003
+(1 row)
+```
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('01-JUL-2004','DD-MON-YYYY'),'IYYY'),'DD-MON-YYYY') "ISO Year" FROM DUAL;
+__OUTPUT__
+  ISO Year
+-------------
+ 03-JAN-2005
+(1 row)
+```
+
+These examples round to the nearest quarter:
+
+```sql
+SELECT ROUND(TO_DATE('15-FEB-07','DD-MON-YY'),'Q') "Quarter" FROM DUAL;
+__OUTPUT__
+      Quarter
+--------------------
+ 01-JAN-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('16-FEB-07','DD-MON-YY'),'Q') "Quarter" FROM DUAL;
+__OUTPUT__
+      Quarter
+--------------------
+ 01-APR-07 00:00:00
+(1 row)
+```
+
+These examples round to the nearest month:
+
+```sql
+SELECT ROUND(TO_DATE('15-DEC-07','DD-MON-YY'),'MONTH') "Month" FROM DUAL;
+__OUTPUT__
+       Month
+--------------------
+ 01-DEC-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('16-DEC-07','DD-MON-YY'),'MONTH') "Month" FROM DUAL;
+__OUTPUT__
+       Month
+--------------------
+ 01-JAN-08 00:00:00
+(1 row)
+```
+
+These examples round to the nearest week. The first day of 2007 lands on a Monday. In the first example, January 18 is closest to the Monday that lands on January 15. In the second example, January 19 is closer to the Monday that falls on January 22.
+
+```sql
+SELECT ROUND(TO_DATE('18-JAN-07','DD-MON-YY'),'WW') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 15-JAN-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('19-JAN-07','DD-MON-YY'),'WW') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 22-JAN-07 00:00:00
+(1 row)
+```
+
+These examples round to the nearest ISO week. An ISO week begins on a Monday. In the first example, January 1, 2004 is closest to the Monday that lands on December 29, 2003. In the second example, January 2, 2004 is closer to the Monday that lands on January 5, 2004.
+
+```sql
+SELECT ROUND(TO_DATE('01-JAN-04','DD-MON-YY'),'IW') "ISO Week" FROM DUAL;
+__OUTPUT__
+      ISO Week
+--------------------
+ 29-DEC-03 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('02-JAN-04','DD-MON-YY'),'IW') "ISO Week" FROM DUAL;
+__OUTPUT__
+      ISO Week
+--------------------
+ 05-JAN-04 00:00:00
+(1 row)
+```
+
+These examples round to the nearest week, where a week is considered to start on the same day as the first day of the month:
+
+```sql
+SELECT ROUND(TO_DATE('05-MAR-07','DD-MON-YY'),'W') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 08-MAR-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('04-MAR-07','DD-MON-YY'),'W') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 01-MAR-07 00:00:00
+(1 row)
+```
+
+These examples round to the nearest day:
+
+```sql
+SELECT ROUND(TO_DATE('04-AUG-07 11:59:59 AM','DD-MON-YY HH:MI:SS AM'),'J')
+"Day" FROM DUAL;
+__OUTPUT__
+        Day
+--------------------
+ 04-AUG-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('04-AUG-07 12:00:00 PM','DD-MON-YY HH:MI:SS AM'),'J')
+"Day" FROM DUAL;
+__OUTPUT__
+        Day
+--------------------
+ 05-AUG-07 00:00:00
+(1 row)
+```
+
+These examples round to the start of the nearest day of the week (Sunday):
+
+```sql
+SELECT ROUND(TO_DATE('08-AUG-07','DD-MON-YY'),'DAY') "Day of Week" FROM DUAL;
+__OUTPUT__
+    Day of Week
+--------------------
+ 05-AUG-07 00:00:00
+(1 row)
+```
+```sql
+SELECT ROUND(TO_DATE('09-AUG-07','DD-MON-YY'),'DAY') "Day of Week" FROM DUAL;
+__OUTPUT__
+    Day of Week
+--------------------
+ 12-AUG-07 00:00:00
+(1 row)
+```
+
+These examples round to the nearest hour:
+
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('09-AUG-07 08:29','DD-MON-YY HH:MI'),'HH'),'DD-MON-YY HH24:MI:SS') "Hour" FROM DUAL;
+__OUTPUT__
+        Hour
+--------------------
+ 09-AUG-07 08:00:00
+(1 row)
+```
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('09-AUG-07 08:30','DD-MON-YY HH:MI'),'HH'),'DD-MON-YY HH24:MI:SS') "Hour" FROM DUAL;
+__OUTPUT__
+        Hour
+--------------------
+ 09-AUG-07 09:00:00
+(1 row)
+```
+
+These examples round to the nearest minute:
+
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('09-AUG-07 08:30:29','DD-MON-YY
+HH:MI:SS'),'MI'),'DD-MON-YY HH24:MI:SS') "Minute" FROM DUAL;
+__OUTPUT__
+       Minute
+--------------------
+ 09-AUG-07 08:30:00
+(1 row)
+```
+```sql
+SELECT TO_CHAR(ROUND(TO_DATE('09-AUG-07 08:30:30','DD-MON-YY
+HH:MI:SS'),'MI'),'DD-MON-YY HH24:MI:SS') "Minute" FROM DUAL;
+__OUTPUT__
+       Minute
+--------------------
+ 09-AUG-07 08:31:00
+(1 row)
+```
+
+## SYSDATE
+
+The `SYSDATE` function returns the current date and time (timestamp without timezone) of the operating system on which the database server resides. The function is `STABLE` and requires no arguments.
+
+When called from a single SQL statement, it returns the same value for each occurrence in the statement. If called from multiple statements in a transaction, it might return different values for each occurrence. If called from a function, it might return a value different from the one returned by `SYSDATE` in the caller.
+
+This example shows a call to `SYSDATE`:
+
+```sql
+SELECT SYSDATE, SYSDATE FROM DUAL;
+__OUTPUT__
+   sysdate          |      sysdate
+--------------------+--------------------
+ 28-APR-20 16:45:28 | 28-APR-20 16:45:28
+(1 row)
+```
+
+## TRUNC
+
+The `TRUNC` function returns a date truncated according to a specified template pattern. If you omit the template pattern, the date is truncated to the nearest day. The following table shows the template patterns for the `TRUNC` function.
+
+| Pattern                               | Description                                                                                                                                      |
+| ------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
+| `CC, SCC`                             | Returns January 1, `cc` 01 where `cc` is first 2 digits of the given year                                                                        |
+| `SYYY, YYYY, YEAR, SYEAR, YYY, YY, Y` | Returns January 1, `yyyy` where `yyyy` is the given year                                                                                         |
+| `IYYY, IYY, IY, I`                    | Returns the start date of the ISO year containing the given date                                                                                 |
+| `Q`                                   | Returns the first day of the quarter containing the given date                                                                                   |
+| `MONTH, MON, MM, RM`                  | Returns the first day of the specified month                                                                                                     |
+| `WW`                                  | Returns the largest date just prior to or the same as the given date that corresponds to the same day of the week as the first day of the year  |
+| `IW`                                  | Returns the start of the ISO week containing the given date                                                                                      |
+| `W`                                   | Returns the largest date just prior to, or the same as the given date that corresponds to the same day of the week as the first day of the month |
+| `DDD, DD, J`                          | Returns the start of the day for the given date                                                                                                  |
+| `DAY, DY, D`                          | Returns the start of the week (Sunday) containing the given date                                                                                 |
+| `HH, HH12, HH24`                      | Returns the start of the hour                                                                                                                    |
+| `MI`                                  | Returns the start of the minute                                                                                                                  |
+
+Following are examples that use the `TRUNC` function.
+
+This example truncates down to the hundred-years unit:
+
+```sql
+SELECT TO_CHAR(TRUNC(TO_DATE('1951','YYYY'),'CC'),'DD-MON-YYYY') "Century" FROM DUAL;
+__OUTPUT__
+   Century
+-------------
+ 01-JAN-1901
+(1 row)
+```
+
+This example truncates down to the year:
+
+```sql
+SELECT TO_CHAR(TRUNC(TO_DATE('01-JUL-1999','DD-MON-YYYY'),'Y'),'DD-MON-YYYY') "Year" FROM DUAL;
+__OUTPUT__
+    Year
+-------------
+ 01-JAN-1999
+(1 row)
+```
+
+This example truncates down to the beginning of the ISO year:
+
+```sql
+SELECT TO_CHAR(TRUNC(TO_DATE('01-JUL-2004','DD-MON-YYYY'),'IYYY'),'DD-MON-YYYY') "ISO Year" FROM DUAL;
+__OUTPUT__
+  ISO Year
+-------------
+ 29-DEC-2003
+(1 row)
+```
+
+This example truncates down to the start date of the quarter:
+
+```sql
+SELECT TRUNC(TO_DATE('16-FEB-07','DD-MON-YY'),'Q') "Quarter" FROM DUAL;
+__OUTPUT__
+      Quarter
+--------------------
+ 01-JAN-07 00:00:00
+(1 row)
+```
+
+This example truncates to the start of the month:
+
+```sql
+SELECT TRUNC(TO_DATE('16-DEC-07','DD-MON-YY'),'MONTH') "Month" FROM DUAL;
+__OUTPUT__
+       Month
+--------------------
+ 01-DEC-07 00:00:00
+(1 row)
+```
+
+This example truncates down to the start of the week determined by the first day of the year. The first day of 2007 lands on a Monday, so the Monday just prior to January 19 is January 15.
+
+```sql
+SELECT TRUNC(TO_DATE('19-JAN-07','DD-MON-YY'),'WW') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 15-JAN-07 00:00:00
+(1 row)
+```
+
+This example truncates to the start of an ISO week. An ISO week begins on a Monday. January 2, 2004 falls in the ISO week that starts on Monday, December 29, 2003.
+
+```sql
+SELECT TRUNC(TO_DATE('02-JAN-04','DD-MON-YY'),'IW') "ISO Week" FROM DUAL;
+__OUTPUT__
+      ISO Week
+--------------------
+ 29-DEC-03 00:00:00
+(1 row)
+```
+
+This example truncates to the start of the week, where a week is considered to start on the same day as the first day of the month:
+
+```sql
+SELECT TRUNC(TO_DATE('21-MAR-07','DD-MON-YY'),'W') "Week" FROM DUAL;
+__OUTPUT__
+        Week
+--------------------
+ 15-MAR-07 00:00:00
+(1 row)
+```
+
+This example truncates to the start of the day:
+
+```sql
+SELECT TRUNC(TO_DATE('04-AUG-07 12:00:00 PM','DD-MON-YY HH:MI:SS AM'),'J')
+"Day" FROM DUAL;
+__OUTPUT__
+        Day
+--------------------
+ 04-AUG-07 00:00:00
+(1 row)
+```
+
+This example truncates to the start of the week (Sunday):
+
+```sql
+SELECT TRUNC(TO_DATE('09-AUG-07','DD-MON-YY'),'DAY') "Day of Week" FROM DUAL;
+__OUTPUT__
+    Day of Week
+--------------------
+ 05-AUG-07 00:00:00
+(1 row)
+```
+
+This example truncates to the start of the hour:
+
+```sql
+SELECT TO_CHAR(TRUNC(TO_DATE('09-AUG-07 08:30','DD-MON-YY HH:MI'),'HH'),'DD-MON-YY HH24:MI:SS') "Hour" FROM DUAL;
+__OUTPUT__
+        Hour
+--------------------
+ 09-AUG-07 08:00:00
+(1 row)
+```
+
+This example truncates to the minute:
+
+```sql
+SELECT TO_CHAR(TRUNC(TO_DATE('09-AUG-07 08:30:30','DD-MON-YY
+HH:MI:SS'),'MI'),'DD-MON-YY HH24:MI:SS') "Minute" FROM DUAL;
+__OUTPUT__
+       Minute
+--------------------
+ 09-AUG-07 08:30:00
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/09_sequence_manipulation_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/09_sequence_manipulation_functions.mdx
new file mode 100644
index 00000000000..7c7f5d72391
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/09_sequence_manipulation_functions.mdx
@@ -0,0 +1,34 @@
+---
+title: "Sequence manipulation functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.102.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.136.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.045.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/09_sequence_manipulation_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="sequence_manipulation_functions" class="registered_link"></div>
+
+Sequence objects, which are also called sequence generators or sequences, are special single-row tables created with the `CREATE SEQUENCE` command. You usually use a sequence to generate unique identifiers for rows of a table. The sequence functions provide simple, multiuser-safe methods for obtaining successive sequence values from sequence objects.
+
+```sql
+sequence.NEXTVAL
+sequence.CURRVAL
+```
+
+`sequence` is the identifier assigned to the sequence in the `CREATE SEQUENCE` command. 
+
+`NEXTVAL`
+
+ Advance the sequence object to its next value and return that value. This is done atomically: even if multiple sessions execute `NEXTVAL` concurrently, each safely receives a distinct sequence value.
+
+`CURRVAL`
+
+ Return the value most recently obtained by `NEXTVAL` for this sequence in the current session. An error is reported if `NEXTVAL` was never called for this sequence in this session. Because this is returning a session-local value, it gives a predictable answer whether or not other sessions executed `NEXTVAL` since the current session did.
+
+If a sequence object was created with default parameters, `NEXTVAL` calls on it return successive values beginning with 1. Use special parameters in the `CREATE SEQUENCE` command for other behaviors.
+
+!!! important
+    To avoid blocking of concurrent transactions that obtain numbers from the same sequence, a `NEXTVAL` operation is never rolled back. After a value is fetched it is considered used, even if the transaction that did the `NEXTVAL` later aborts. This means that aborted transactions can leave unused "holes" in the sequence of assigned values.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/10_conditional_expressions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/10_conditional_expressions.mdx
new file mode 100644
index 00000000000..f467e099057
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/10_conditional_expressions.mdx
@@ -0,0 +1,291 @@
+---
+title: "Conditional expressions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.103.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.137.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.046.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/10_conditional_expressions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="conditional_expressions" class="registered_link"></div>
+
+SQL-compliant conditional expressions are available in EDB Postgres Advanced Server.
+
+## CASE
+
+The SQL `CASE` expression is a generic conditional expression, similar to if/else statements in other languages:
+
+```sql
+CASE WHEN condition THEN result
+   [ WHEN ... ]
+   [ ELSE result ]
+END
+```
+
+You can use `CASE` clauses wherever an expression is valid. `condition` is an expression that returns a `BOOLEAN` result. If the result is `TRUE`, then the value of the `CASE` expression is the `result` that follows the condition. If the result is `FALSE`, any subsequent `WHEN` clauses are searched in the same manner. If `no WHEN condition` is `TRUE`, then the value of the `CASE` expression is the `result` in the `ELSE` clause. If the `ELSE` clause is omitted and no condition matches, the result is `NULL`.
+
+For example:
+
+```sql
+SELECT * FROM test;
+__OUTPUT__
+ a
+---
+ 1
+ 2
+ 3
+(3 rows)
+```
+```sql
+SELECT a,
+    CASE WHEN a=1 THEN 'one'
+         WHEN a=2 THEN 'two'
+         ELSE 'other'
+    END
+FROM test;
+__OUTPUT__
+ a | case
+---+-------
+ 1 | one
+ 2 | two
+ 3 | other
+(3 rows)
+```
+
+The data types of all the `result` expressions must be convertible to a single output type.
+
+The following simple `CASE` expression is a specialized variant of the general form:
+
+```sql
+CASE expression
+    WHEN value THEN result
+  [ WHEN ... ]
+  [ ELSE result ]
+END
+```
+
+The `expression` is computed and compared to all the `value` specifications in the `WHEN` clauses until one is found that is equal. If no match is found, the `result` in the `ELSE` clause (or a null value) is returned.
+
+This same example can be written using the simple `CASE` syntax:
+
+```sql
+SELECT a,
+    CASE a WHEN 1 THEN 'one'
+           WHEN 2 THEN 'two'
+           ELSE 'other'
+    END
+FROM test;
+__OUTPUT__
+ a | case
+---+-------
+ 1 | one
+ 2 | two
+ 3 | other
+(3 rows)
+```
+
+A `CASE` expression doesn't evaluate any subexpressions that aren't needed to determine the result. For example, this is a possible way of avoiding a division-by-zero failure:
+
+```sql
+SELECT ... WHERE CASE WHEN x <> 0 THEN y/x > 1.5 ELSE false END;
+```
+
+## COALESCE
+
+The `COALESCE` function returns the first of its arguments that isn't null. Null is returned only if all arguments are null.
+
+```sql
+COALESCE(value [, value2 ] ... )
+```
+
+It's often used to substitute a default value for null values when data is retrieved for display or further computation. For example:
+
+```sql
+SELECT COALESCE(description, short_description, '(none)') ...
+```
+
+Like a `CASE` expression, `COALESCE` doesn't evaluate arguments that aren't needed to determine the result. Arguments to the right of the first non-null argument aren't evaluated. This SQL-standard function provides capabilities similar to `NVL` and `IFNULL`, which are used in some other database systems.
+
+## NULLIF
+
+The `NULLIF` function returns a null value if `value1` and `value2` are equal. Otherwise it returns `value1`.
+
+```sql
+NULLIF(value1, value2)
+```
+
+You can use this to perform the inverse operation of the `COALESCE` example:
+
+```sql
+SELECT NULLIF(value1, '(none)') ...
+```
+
+If `value1` is (none), return a null. Otherwise return `value1`.
+
+## NVL
+
+The `NVL` function returns the first of its arguments that isn't null. `NVL` evaluates the first expression. If that expression evaluates to `NULL`, `NVL` returns the second expression.
+
+```sql
+NVL(expr1, expr2)
+```
+
+The return type is the same as the argument types. All arguments must have the same data type or be coercible to a common type. `NVL` returns `NULL` if all arguments are `NULL`. `''` is considered as unknown, and if the arguments data type aren't coercible to the common data type, then `NVL` throws an error.
+
+### Examples
+
+This example computes a bonus for noncommissioned employees. If an employee is a commissioned employee, this expression returns the employee's commission. If the employee isn't a commissioned employee, that is, their commission is `NULL`, this expression returns a bonus that's 10% of their salary.
+
+```text
+bonus = NVL(emp.commission, emp.salary * .10)
+```
+
+In this example, the type of `1` is numeric and the type of `''` is considered as unknown. Therefore PostgreSQL decides that the common type is numeric. It tries to interpret the empty string as a numeric value, which produces the indicated error:
+
+```sql
+edb=# select nvl('',1);
+ERROR:  invalid input syntax for type numeric: ""
+```
+
+In this example, if `33` is type casted to double precision, it converts to double precision and returns the value as double precision. If `33` is type casted to numeric, it converts to numeric and returns the value as numeric.
+
+```sql
+edb=# select NVL(33::double precision,0), pg_typeof(NVL(33::double precision,0)), pg_typeof(NVL(33::numeric,0));
+__OUTPUT__
+ nvl |    pg_typeof     | pg_typeof
+-----+------------------+-----------
+  33 | double precision | numeric
+(1 row)
+```
+
+## NVL2
+
+`NVL2` evaluates an expression and returns either the second or third expression, depending on the value of the first expression. If the first expression isn't `NULL`, `NVL2` returns the value in `expr2`. If the first expression is `NULL`, `NVL2` returns the value in `expr3`.
+
+```sql
+NVL2(expr1, expr2, expr3)
+```
+
+The return type is the same as the argument types. All arguments must have the same data type or be coercible to a common type.
+
+This example computes a bonus for commissioned employees. If a given employee is a commissioned employee, this expression returns an amount equal to 110% of their commission. If the employee isn't a commissioned employee, that is, their commission is `NULL`, this expression returns `0`.
+
+```sql
+bonus = NVL2(emp.commission, emp.commission * 1.1, 0)
+```
+## NANVL
+
+The `NANVL` function returns the first of its arguments that is not-a-number (NaN) value. `NANVL` evaluates the first expression. If that expression evaluates to a NAN value, `NANVL` returns the second expression. If the first expression evaluates to a number value, `NANVL` returns the first expression. The `NANVL` function is useful only for floating-point numbers of type `BINARY_FLOAT` or `BINARY_DOUBLE`.
+
+```sql
+NANVL(expr1,expr2)
+```
+
+This function takes any numeric data type or any non-numeric data type that can be implicitly converted to a numeric data type as arguments. EDB Postres Advanced Server determines the argument with the highest numeric precedence, implicitly converts the remaining arguments to that data type, and returns that data type.
+
+### Examples
+
+```sql
+SELECT nanvl(124346, 1), nanvl('NaN', 2), nanvl(124346::int, 3), nanvl(124346::int8, 4);
+__OUTPUT__
+ nanvl  | nanvl | nanvl  | nanvl  
+--------+-------+--------+--------
+ 124346 |     2 | 124346 | 124346
+(1 row)
+```
+
+```sql
+SELECT nanvl('NaN', 1::int2), nanvl(124346::int, 2::int2), nanvl(124346::int8, 3::int2);
+__OUTPUT__
+ nanvl | nanvl  | nanvl  
+-------+--------+--------
+     1 | 124346 | 124346
+(1 row)
+```
+
+```sql
+select nanvl('NAN',2::int2);
+__OUTPUT__
+ nanvl 
+-------
+     2
+(1 row)
+```
+
+## LNNVL
+
+The `LNNVL` function provides a concise way to evaluate a condition when one or both operands of the condition might be null. 
+
+```sql
+LNNVL(condition)
+```
+
+The function returns `TRUE` if the condition is `FALSE` or `UNKNOWN` and `FALSE` if the condition is `TRUE`.
+
+The condition can evaluate any scalar values but can't be a compound condition containing `AND`, `OR`, or `BETWEEN`.
+
+Use the `LNNVL` function:
+- In the `WHERE` clause of a query.
+- In the `WHEN` condition in a searched `CASE` expression.
+- Anywhere a scalar expression appears, even in contexts where the `IS [NOT] NULL`, `AND`, or `OR` conditions aren't valid but otherwise are required to account for potential nulls.
+
+### Examples
+
+Create a table and insert data:
+
+```sql
+CREATE TABLE t1 (id INT, col1 INT);
+INSERT INTO t1 VALUES (10, NULL), (1,1),(2,2), (3,3);
+```
+
+Use the `LNNVL` function in a `SELECT` query:
+
+```sql
+SELECT * FROM t1 WHERE lnnvl(col1 > 2) ORDER BY id;
+__OUTPUT__
+id | col1 
+----+------+  
+ 1 |    1
+ 2 |    2 
+10 |     
+(3 rows)
+```
+
+```sql
+SELECT * FROM t1 WHERE lnnvl(col1 < 2) ORDER BY id;
+__OUTPUT__
+id | col1 
+----+------+  
+ 2 |    2
+ 3 |    3
+10 |     
+(3 rows)
+```
+
+```sql
+SELECT * FROM t1 WHERE lnnvl(col1 > NULL) ORDER BY id; 
+__OUTPUT__
+id | col1 
+----+------+  
+ 1 |    1  
+ 2 |    2
+ 3 |    3
+10 |     
+(4 rows)
+```
+
+## GREATEST and LEAST
+
+The `GREATEST` and `LEAST` functions select the largest or smallest value from a list of any number of expressions.
+
+```sql
+GREATEST(value [, value2 ] ... )
+LEAST(value [, value2 ] ... )
+```
+
+All of the expressions must be convertible to a common data type, which becomes the type of the result. Null values in the list are ignored. The result is null only if all the expressions evaluate to null.
+
+!!! Note
+    The `GREATEST` and `LEAST` aren't in the SQL standard but are a common extension.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/11_aggregate_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/11_aggregate_functions.mdx
new file mode 100644
index 00000000000..414ce6b635d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/11_aggregate_functions.mdx
@@ -0,0 +1,417 @@
+---
+title: "Aggregate functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.104.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/11_aggregate_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="aggregate_functions" class="registered_link"></div>
+
+Aggregate functions compute a single result value from a set of input values. 
+
+## Built-in aggregate functions
+
+The built-in aggregate functions are listed in the following tables.
+
+| Function              | Argument type                                                                                 | Return type                                                                                                                                                                    | Description                                                        |
+| --------------------- | --------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------ |
+| `AVG (expression)`    | `INTEGER, REAL, DOUBLE PRECISION, NUMBER`                                                     | `NUMBER` for any integer type, `DOUBLE PRECISION` for a floating-point argument, otherwise the same as the argument data type                                                  | The average (arithmetic mean) of all input values                  |
+| `COUNT(*)`            |                                                                                               | `BIGINT`                                                                                                                                                                       | Number of input rows                                               |
+| `COUNT (expression)`  | Any                                                                                           | `BIGINT`                                                                                                                                                                       | Number of input rows for which the value of expression is not null |
+| `MAX (expression)`    | Any numeric, string, date/time, or bytea type                                                 | Same as argument type                                                                                                                                                          | Maximum value of expression across all input values                |
+| `MIN (expression)`    | Any numeric, string, date/time, or bytea type                                                 | Same as argument type                                                                                                                                                          | Minimum value of expression across all input values                |
+| `SUM (expression)`    | `INTEGER, REAL, DOUBLE PRECISION, NUMBER`                                                     | `BIGINT` for `SMALLINT` or `INTEGER` arguments, `NUMBER` for `BIGINT` arguments, `DOUBLE PRECISION` for floating-point arguments, otherwise the same as the argument data type | Sum of expression across all input values                          |
+
+Except for `COUNT`, these functions return a null value when no rows are selected. In particular, `SUM` of no rows returns null, not zero. You can use the `COALESCE` function to substitute zero for null when necessary.
+
+## Aggregate functions for statistical analysis
+
+The following table shows the aggregate functions typically used in statistical analysis. Where the description mentions `N`, it means the number of input rows for which all the input expressions are non-null. In all cases, null is returned if the computation is meaningless, for example when `N` is zero.
+
+| Function                  | Argument type                             | Return type                                                         | Description                                                                                     |
+| ------------------------- | ----------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
+| `CORR(Y, X)`              | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Correlation coefficient                                                                         |
+| `COVAR_POP(Y, X)`         | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Population covariance                                                                           |
+| `COVAR_SAMP(Y, X)`        | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Sample covariance                                                                               |
+| `REGR_AVGX(Y, X)`         | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Average of the independent variable (sum`(X) / N`)                                              |
+| `REGR_AVGY(Y, X)`         | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Average of the dependent variable (sum`(Y) / N`)                                                |
+| `REGR_COUNT(Y, X)`        | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Number of input rows in which both expressions are nonnull                                      |
+| `REGR_INTERCEPT(Y, X)`    | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | y-intercept of the least-squares-fit linear equation determined by the `(X, Y)` pairs           |
+| `REGR_R2(Y, X)`           | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Square of the correlation coefficient                                                           |
+| `REGR_SLOPE(Y, X)`        | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Slope of the least-squares-fit linear equation determined by the `(X, Y)` pairs                 |
+| `REGR_SXX(Y, X)`          | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Sum (X<sup>2</sup>) – sum (X) <sup>2</sup> / N (“sum of squares” of the independent variable)   |
+| `REGR_SXY(Y, X)`          | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Sum (X\*Y) – sum (X) \* sum (Y) / N (“sum of products” of independent times dependent variable) |
+| `REGR_SYY(Y, X)`          | `DOUBLE PRECISION`                        | `DOUBLE PRECISION`                                                  | Sum (Y<sup>2</sup>) – sum (Y) <sup>2</sup> / N (“sum of squares” of the dependent variable)     |
+| `STDDEV(expression)`      | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Historic alias for `STDDEV_SAMP`                                                                |
+| `STDDEV_POP(expression)`  | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Population standard deviation of the input values                                               |
+| `STDDEV_SAMP(expression)` | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Sample standard deviation of the input values                                                   |
+| `VARIANCE(expression)`    | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Historical alias for `VAR_SAMP`                                                                 |
+| `VAR_POP(expression)`     | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Population variance of the input values (square of the population standard deviation)           |
+| `VAR_SAMP(expression)`    | `INTEGER, REAL, DOUBLE PRECISION, NUMBER` | `DOUBLE PRECISION` for floating-point arguments, otherwise `NUMBER` | Sample variance of the input values (square of the sample standard deviation)                   |
+
+## LISTAGG
+
+`LISTAGG` is an aggregate function that concatenates data from multiple rows into a single row in an ordered manner. You can optionally include a custom delimiter for your data.
+
+The `LISTAGG` function mandates the use of an `ORDER BY` clause under a `WITHIN GROUP` clause to concatenate values of the measure column and then generate the ordered aggregated data.
+
+### Objective
+
+-   You can use `LISTAGG` without any grouping. In this case, the `LISTAGG` function operates on all rows in a table and returns a single row.
+-   You can use `LISTAGG` with the `GROUP BY` clause. In this case, the `LISTAGG` function operates on each group and returns an aggregated output for each group.
+-   You can use `LISTAGG` with the `OVER` clause. In this case, the `LISTAGG` function partitions a query result set into groups based on the expression in the `query_partition_by_clause` and then aggregates data in each group.
+
+### Synopsis
+
+```sql
+LISTAGG( <measure_expr> [, <delimiter> ]) WITHIN GROUP( <order_by_clause> )
+[ OVER <query_partition_by_clause> ]
+```
+
+### Parameters
+
+`measure_expr`
+
+ `measure_expr` (mandatory) specifies the column or expression that assigns a value to aggregate. `NULL` values are ignored.
+
+`delimiter`
+
+ `delimiter` (optional) specifies a string that separates the concatenated values in the result row. The `delimiter` can be a `NULL` value, string, character literal, column name, or constant expression. If ignored, the `LISTAGG` function uses a `NULL` value by default.
+
+`order_by_clause`
+
+ `order_by_clause` (mandatory) determines the sort order in which the concatenated values are returned.
+
+`query_partition_by_clause`
+
+ `query_partition_by_clause` (optional) allows the `LISTAGG` function to be used as an analytic function and sets the range of records for each group in the `OVER` clause.
+
+### Return type
+
+The `LISTAGG` function returns a string value.
+
+### Examples
+
+This example concatenates the values in the `emp` table and lists all the employees separated by a `delimiter` comma. First, create a table named `emp`. Then insert records into the `emp` table.
+
+```sql
+edb=# CREATE TABLE emp
+edb-#        (EMPNO NUMBER(4) NOT NULL,
+edb(#         ENAME VARCHAR2(10),
+edb(#         JOB VARCHAR2(9),
+edb(#         MGR NUMBER(4),
+edb(#         HIREDATE DATE,
+edb(#         SAL NUMBER(7, 2),
+edb(#         COMM NUMBER(7, 2),
+edb(#         DEPTNO NUMBER(2));
+CREATE TABLE
+```
+
+```sql
+edb=# INSERT INTO emp VALUES
+edb-#         (7499, 'ALLEN',  'SALESMAN',  7698,
+edb(#         TO_DATE('20-FEB-1981', 'DD-MON-YYYY'), 1600,  300, 30);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES
+edb-#         (7521, 'WARD',   'SALESMAN',  7698,
+edb(#         TO_DATE('22-FEB-1981', 'DD-MON-YYYY'), 1250,  500, 30);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES
+edb-#         (7566, 'JONES',  'MANAGER',   7839,
+edb(#         TO_DATE('2-APR-1981', 'DD-MON-YYYY'),  2975, NULL, 20);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES
+edb-#         (7654, 'MARTIN', 'SALESMAN',  7698,
+edb(#         TO_DATE('28-SEP-1981', 'DD-MON-YYYY'), 1250, 1400, 30);
+INSERT 0 1
+edb=# INSERT INTO emp VALUES
+edb-#         (7698, 'BLAKE',  'MANAGER',   7839,
+edb(#         TO_DATE('1-MAY-1981', 'DD-MON-YYYY'),  2850, NULL, 30);
+INSERT 0 1
+__OUTPUT__
+edb=# SELECT LISTAGG(ENAME, ',') WITHIN GROUP (ORDER BY ENAME) FROM emp;
+               listagg
+-------------------------------------
+ ALLEN,BLAKE,JONES,MARTIN,WARD
+(1 row)
+```
+
+This example uses a `PARTITION BY` clause with `LISTAGG` in the `emp` table. It generates output based on a partition by `deptno` that applies to each partition and not on the entire table.
+
+```sql
+edb=# SELECT DISTINCT DEPTNO, LISTAGG(ENAME, ',') WITHIN GROUP (ORDER BY
+ENAME) OVER(PARTITION BY DEPTNO) FROM emp;
+__OUTPUT__
+ deptno |         listagg
+--------+-------------------------
+     30 | ALLEN,BLAKE,MARTIN,WARD
+     20 | JONES
+(2 rows)
+```
+
+This example includes the `GROUP BY` clause.
+
+```sql
+edb=# SELECT DEPTNO, LISTAGG(ENAME, ',') WITHIN GROUP (ORDER BY ENAME) FROM
+emp GROUP BY DEPTNO;
+__OUTPUT__
+ deptno |         listagg
+--------+-------------------------
+     20 | JONES
+     30 | ALLEN,BLAKE,MARTIN,WARD
+(2 rows)
+```
+
+## MEDIAN
+
+The `MEDIAN` function calculates the middle value of an expression from a given range of values. `NULL` values are ignored. The `MEDIAN` function returns an error if a query doesn't reference the user-defined table.
+
+### Objective
+
+-   You can  use `MEDIAN` without any grouping. In this case, the `MEDIAN` function operates on all rows in a table and returns a single row.
+-   You can use `MEDIAN` with the `OVER` clause. In this case, the `MEDIAN` function partitions a query result set into groups based on the `expression` specified in the `PARTITION BY` clause. It then aggregates data in each group.
+
+### Synopsis
+
+```sql
+MEDIAN( <median_expression> ) [ OVER ( [ PARTITION BY... ] ) ]
+```
+
+### Parameters
+
+`median_expression`
+
+ `median_expression` (mandatory) is a target column or expression that the `MEDIAN` function operates on and returns a median value. It can be a numeric, datetime, or interval data type.
+
+`PARTITION BY`
+
+ `PARTITION BY` clause (optional) allows you to use `MEDIAN` as an analytic function and sets the range of records for each group in the `OVER` clause.
+
+### Return types
+
+The return type is determined by the input data type of `expression`. The following table shows the return type for each input type.
+
+| Input type                | Return type        |
+| ------------------------- | ------------------ |
+| `BIGINT`                  | `NUMERIC`          |
+| `FLOAT, DOUBLE PRECISION` | `DOUBLE PRECISION` |
+| `INTEGER`                 | `NUMERIC`          |
+| `INTERVAL`                | `INTERVAL`         |
+| `NUMERIC`                 | `NUMERIC`          |
+| `REAL`                    | `REAL`             |
+| `SMALLINT`                | `NUMERIC`          |
+| `TIMESTAMP`               | `TIMESTAMP`        |
+| `TIMESTAMPTZ`             | `TIMESTAMPTZ`      |
+
+### Examples
+
+In this example, a query returns the median salary for each department in the `emp` table:
+
+```sql
+edb=# SELECT * FROM emp;
+__OUTPUT__
+ empno| ename |   job   | mgr  |      hiredate     |   sal  | comm   | deptno
+ -----+-------+---------+------+-------------------+--------+--------+-------
+ 7369 | SMITH | CLERK   | 7902 | 17-DEC-80 00:00:00|  800.00|        |   20
+ 7499 | ALLEN | SALESMAN| 7698 | 20-FEB-81 00:00:00| 1600.00| 300.0  |   30
+ 7521 | WARD  | SALESMAN| 7698 | 22-FEB-81 00:00:00| 1250.00| 500.00 |   30
+ 7566 | JONES | MANAGER | 7839 | 02-APR-81 00:00:00| 2975.00|        |   20
+ 7654 | MARTIN| SALESMAN| 7698 | 28-SEP-81 00:00:00| 1250.00| 1400.00|   30
+(5 rows)
+```
+```sql
+ edb=# SELECT MEDIAN (SAL) FROM emp;
+ __OUTPUT__
+  median
+ --------
+    1250
+ (1 row)
+```
+
+This example uses the `PARTITION BY` clause with `MEDIAN` in the `emp` table and returns the median salary based on a partition by `deptno`:
+
+```sql
+edb=# SELECT EMPNO, ENAME, DEPTNO, MEDIAN (SAL) OVER (PARTITION BY DEPTNO)
+FROM emp;
+__OUTPUT__
+ empno | ename  | deptno | median
+-------+--------+--------+--------
+  7369 | SMITH  |     20 | 1887.5
+  7566 | JONES  |     20 | 1887.5
+  7499 | ALLEN  |     30 |   1250
+  7521 | WARD   |     30 |   1250
+  7654 | MARTIN |     30 |   1250
+(5 rows)
+```
+
+You can compare the `MEDIAN` function with `PERCENTILE_CONT`. In this example, `MEDIAN` generates the same result as `PERCENTILE_CONT`:
+
+```sql
+edb=# SELECT MEDIAN (SAL), PERCENTILE_CONT(0.5) WITHIN GROUP(ORDER BY SAL)
+FROM emp;
+__OUTPUT__
+ median | percentile_cont
+--------+-----------------
+   1250 |            1250
+(1 row)
+```
+
+## STATS_MODE
+
+The `STATS_MODE` function takes a set of values as an argument and returns the value that occurs with the highest frequency. If multiple values appear with the same frequency, the `STATS_MODE` function arbitrarily chooses the first value and returns only that one value.
+
+### Objective
+
+-   You can use `STATS_MODE` without any grouping. In this case, the `STATS_MODE` function operates on all the rows in a table and returns a single value.
+-   You can use `STATS_MODE` as an ordered-set aggregate function using the `WITHIN GROUP` clause. In this case, the `STATS_MODE` function operates on the ordered data set.
+-   You can use `STATS_MODE` with the `GROUP BY` clause. In this case, the `STATS_MODE` function operates on each group and returns the most frequent and aggregated output for each group.
+
+### Synopsis
+
+```sql
+STATS_MODE( <expr> )
+```
+
+Or
+
+```sql
+STATS_MODE() WITHIN GROUP ( ORDER BY sort_expression )
+```
+
+### Parameters
+
+`expr`
+
+ An expression or value to assign to the column.
+
+### Return type
+
+The `STATS_MODE` function returns a value that appears frequently. However, if all the values of a column are `NULL`, `STATS_MODE` returns `NULL`.
+
+### Examples
+
+This example returns the mode of salary in the `emp` table:
+
+```sql
+edb=# SELECT * FROM emp;
+__OUTPUT__
+ empno| ename |   job   | mgr  |      hiredate     |   sal  | comm   | deptno
+------+-------+---------+------+-------------------+--------+--------+-------
+ 7369 | SMITH | CLERK   | 7902 | 17-DEC-80 00:00:00|  800.00|        |   20
+ 7499 | ALLEN | SALESMAN| 7698 | 20-FEB-81 00:00:00| 1600.00| 300.0  |   30
+ 7521 | WARD  | SALESMAN| 7698 | 22-FEB-81 00:00:00| 1250.00| 500.00 |   30
+ 7566 | JONES | MANAGER | 7839 | 02-APR-81 00:00:00| 2975.00|        |   20
+ 7654 | MARTIN| SALESMAN| 7698 | 28-SEP-81 00:00:00| 1250.00| 1400.00|   30
+(5 rows)
+```
+```sql
+edb=# SELECT STATS_MODE(SAL) FROM emp;
+__OUTPUT__
+ stats_mode
+------------
+   1250.00
+(1 row)
+```
+
+This example uses `GROUP BY` and `ORDER BY` clauses with `STATS_MODE` in the `emp` table and returns the salary based on a partition by `deptno`:
+
+```sql
+edb=# SELECT STATS_MODE(SAL) FROM emp GROUP BY DEPTNO ORDER BY DEPTNO;
+__OUTPUT__
+ stats_mode
+------------
+   800.00
+   1250.00
+(2 rows)
+```
+
+This example uses the `WITHIN GROUP` clause with `STATS_MODE` to perform aggregation on the ordered data set.
+
+```sql
+SELECT STATS_MODE() WITHIN GROUP(ORDER BY SAL) FROM emp;
+__OUTPUT__
+ stats_mode
+------------
+   1250.00
+(1 row)
+```
+
+## BIT_AND_AGG
+
+`BIT_AND_AGG` is a bitwise aggregation function that performs a bitwise `AND` operation and returns a value based on the data type of input argument.
+
+### Objective
+
+-  You can use the `BIT_AND_AGG` function with the `GROUP BY` clause. In this case, the `BIT_AND_AGG` function operates on a group and returns the result of a bitwise `AND` operation.
+-  You can use the `DISTINCT` or `UNIQUE` keywords with the `BIT_AND_AGG` function to ensure that unique values in the `expr` are used for computation.
+
+### Synopsis
+
+```sql
+BIT_AND_AGG ( [DISTINCT | ALL | UNIQUE]  <expr> )
+```
+
+### Parameters
+
+`expr`
+
+ An expression or value to assign to the column.
+
+### Return Type
+
+The `BIT_AND_AGG` function returns the same value as the data type of the input argument. However, if all the values of a column are `NULL`, the `BIT_AND_AGG` returns `NULL`.
+
+### Examples
+
+This example applies the `BIT_AND_AGG` function to the `sal` column in an `emp` table and groups the result by `deptno`: 
+
+```sql
+edb=# SELECT deptno,BIT_AND_AGG(DISTINCT sal) FROM emp GROUP BY deptno;
+__OUTPUT__
+ deptno | bit_and_agg 
+--------+-------------
+     20 |     2975.00
+     30 |           0
+(2 rows)
+```
+
+## BIT_OR_AGG
+
+`BIT_OR_AGG` is a bitwise aggregation function that performs a bitwise `OR` operation and returns a value based on the data type of input argument.
+
+### Objective
+
+-  You can use the `BIT_OR_AGG` function with the `GROUP BY` clause. In this case, the `BIT_OR_AGG` function operates on a group and returns the result of a bitwise `OR` operation. 
+-  You can use the `DISTINCT` or `UNIQUE` keywords with the `BIT_OR_AGG` function to ensure that unique values in the `expr` are used for computation.
+
+### Synopsis
+
+```sql
+BIT_OR_AGG ( [DISTINCT | ALL | UNIQUE]  <expr> )
+```
+
+### Parameters
+
+`expr`
+
+ An expression or value to assign to the column.
+
+### Return type
+
+The `BIT_OR_AGG` function returns the same value as the data type of the input argument. However, if all the values of a column are `NULL`, `BIT_OR_AGG` returns `NULL`. 
+
+### Examples
+
+This example applies `BIT_OR_AGG` to the `sal` column in an `emp` table and groups the result by `deptno`: 
+
+```sql
+edb=# SELECT deptno,BIT_OR_AGG(DISTINCT sal) FROM emp GROUP BY deptno;
+__OUTPUT__
+ deptno | bit_or_agg 
+--------+------------
+     20 |    2975.00
+     30 |       4066
+(2 rows)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/12_subquery_expressions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/12_subquery_expressions.mdx
new file mode 100644
index 00000000000..ffca7a7a09d
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/12_subquery_expressions.mdx
@@ -0,0 +1,91 @@
+---
+title: "Subquery expressions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.105.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.139.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.048.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/12_subquery_expressions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="subquery_expressions" class="registered_link"></div>
+
+SQL-compliant subquery expressions are available in EDB Postgres Advanced Server. All of these expression forms return Boolean `(TRUE/FALSE)` results.
+
+## EXISTS
+
+The argument of `EXISTS` is an arbitrary `SELECT` statement or subquery. The subquery is evaluated to determine whether it returns any rows. If it returns at least one row, the result of `EXISTS` is `TRUE`. If the subquery returns no rows, the result of `EXISTS` is `FALSE`.
+
+```sql
+EXISTS(subquery)
+```
+
+The subquery can refer to variables from the surrounding query that act as constants during any one evaluation of the subquery.
+
+The subquery is generally executed only far enough to determine whether at least one row is returned, not all the way to completion. We recommend that you don't write a subquery that has any side effects (such as calling sequence functions). Whether the side effects occur might be difficult to predict.
+
+Since the result depends only on whether any rows are returned and not on the contents of those rows, the output list of the subquery is normally uninteresting. A common coding convention is to write all `EXISTS` tests in the form `EXISTS(SELECT 1 WHERE ...)`. There are exceptions to this rule, however, such as subqueries that use `INTERSECT`.
+
+This simple example is like an inner join on `deptno`, but it produces at most one output row for each `dept` row, even though there are multiple matching `emp` rows:
+
+```sql
+SELECT dname FROM dept WHERE EXISTS (SELECT 1 FROM emp WHERE emp.deptno =
+dept.deptno);
+__OUTPUT__
+   dname
+------------
+ ACCOUNTING
+ RESEARCH
+ SALES
+(3 rows)
+```
+
+## IN
+
+The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result. The result of `IN` is `TRUE` if any equal subquery row is found. The result is `FALSE` if no equal row is found (including the special case where the subquery returns no rows).
+
+```sql
+expression IN (subquery)
+```
+
+If the left-hand expression yields `NULL`, or if there are no equal right-hand values and at least one right-hand row yields `NULL`, the result of the `IN` construct is `NULL`, not `FALSE`. This is in accordance with SQL’s normal rules for Boolean combinations of null values.
+
+As with `EXISTS`, you can't assume that the subquery will evaluate completely.
+
+## NOT IN
+
+The right-hand side is a parenthesized subquery that must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result. The result of `NOT IN` is `TRUE` if only unequal subquery rows are found (including the special case where the subquery returns no rows). The result is `FALSE` if any equal row is found.
+
+```sql
+expression NOT IN (subquery)
+```
+
+If the left-hand expression yields `NULL`, or if there are no equal right-hand values and at least one right-hand row yields `NULL`, the result of the `NOT IN` construct is `NULL`, not `TRUE`. This is in accordance with SQL’s normal rules for Boolean combinations of null values.
+
+As with `EXISTS`, you can't assume that the subquery will evaluate completely.
+
+## ANY/SOME
+
+The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result using the given operator, which must yield a Boolean result. The result of `ANY` is `TRUE` if any true result is obtained. The result is `FALSE` if no true result is found (including the special case where the subquery returns no rows).
+
+```sql
+expression operator ANY (subquery)
+expression operator SOME (subquery)
+```
+
+`SOME` is a synonym for `ANY`. `IN` is equivalent to `= ANY`.
+
+If there are no successes and at least one right-hand row yields `NULL` for the operator’s result, the result of the `ANY` construct is `NULL`, not `FALSE`. This is in accordance with SQL’s normal rules for Boolean combinations of null values.
+
+As with `EXISTS`, you can't assume that the subquery will evaluate completely.
+
+## ALL
+
+The right-hand side is a parenthesized subquery, which must return exactly one column. The left-hand expression is evaluated and compared to each row of the subquery result using the given operator, which must yield a Boolean result. The result of `ALL` is `TRUE` if all rows yield true (including the special case where the subquery returns no rows). The result is `FALSE` if any false result is found. The result is `NULL` if the comparison doesn't return `FALSE` for any row and it returns `NULL` for at least one row.
+
+```sql
+expression operator ALL (subquery)
+```
+
+`NOT IN` is equivalent to `<> ALL`. As with `EXISTS`, you can't assume that the subquery will evaluate completely.
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/13_identifier_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/13_identifier_functions.mdx
new file mode 100644
index 00000000000..85dd39ab886
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/13_identifier_functions.mdx
@@ -0,0 +1,200 @@
+---
+title: "Identifier functions"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/13_identifier_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="identifier_functions" class="registered_link"></div>
+
+Identifier functions that information about the instance and session.
+
+## SYS_GUID
+
+The `SYS_GUID` function generates and returns a globally unique identifier. The identifier takes the form of 16 bytes of `RAW` data. The `SYS_GUID` function is based on the `uuid-ossp` module to generate universally unique identifiers. The signature is:
+
+```sql
+SYS_GUID()
+```
+
+### Example
+
+This example adds a column to the table `EMP`, inserts a unique identifier, and returns a `16-byte RAW` value:
+
+```sql
+edb=# CREATE TABLE EMP(C1 RAW (16) DEFAULT SYS_GUID() PRIMARY KEY, C2 INT);
+CREATE TABLE
+edb=# INSERT INTO EMP(C2) VALUES (1);
+INSERT 0 1
+edb=# SELECT * FROM EMP;
+__OUTPUT__
+                 c1                 | c2
+------------------------------------+----
+ \xb944970d3a1b42a7a2119265c49cbb7f |  1
+(1 row)
+```
+
+## USERENV
+
+The `USERENV` function retrieves information about the current session. The signature is:
+
+```sql
+USERENV(<parameter>)
+```
+
+The `parameter` specifies a value to return from the current session. The table shows the possible `parameter` values.
+
+| Parameter   | Description                                                                                                                               |                                                                         
+| ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- | 
+| `ISDBA`     | Returns `TRUE` if the current user has DBA privileges, otherwise `FALSE`.                                                                 |                                                                                                         
+| `LANGUAGE`  | The language, territory, and character set of the current session in the following format: `language_territory.characterset`              |                                                                           
+| `LANG`      | The ISO abbreviation for the language name, a short name for the existing `LANGUAGE` parameter.                                           |              
+| `SID`       | The current session identifier.                                                                                                           | 
+| `TERMINAL`  | The current session's operating system terminal identifier.                                                                               |
+
+### Examples
+
+This example returns the `ISDBA` parameter of the current session:
+
+```sql
+edb=# SELECT USERENV('ISDBA') FROM DUAL;   
+__OUTPUT__  
+ userenv 
+---------
+ TRUE
+(1 row)
+```
+
+This example returns the `LANG` parameter of the current session:
+
+```sql
+edb=# SELECT USERENV('LANG') FROM DUAL; 
+__OUTPUT__     
+ userenv 
+---------
+ en
+(1 row)
+```
+
+This example returns the `LANGUAGE` parameter of the current session:
+
+```sql
+edb=# SELECT USERENV('LANGUAGE') FROM DUAL;
+__OUTPUT__  
+      userenv      
+-------------------
+ English_USA.UTF-8
+(1 row)
+```
+
+This example returns the `TERMINAL` identifier:
+
+```sql
+edb=# SELECT USERENV('TERMINAL') FROM DUAL; 
+__OUTPUT__
+ userenv 
+---------
+ [local]
+(1 row)
+```
+
+This example returns the `SID` number of the current session:
+
+```sql
+edb=# SELECT USERENV('SID') FROM DUAL;  
+__OUTPUT__
+ userenv 
+---------
+ 56867
+(1 row)
+```
+
+## SYS_CONTEXT
+
+The `SYS_CONTEXT` function returns the value of a `parameter` associated with the context `namespace` in the current session. The signature is:
+
+```sql
+SYS_CONTEXT(<namespace>, <parameter>)
+```
+
+Or
+
+```sql
+SYS_CONTEXT(<userenv>, <parameter>)
+```
+
+### Parameters
+
+`namespace`
+
+ `namespace` can be any named context. `USERENV` is a built-in context that shows information about the current session. 
+
+`parameter`
+
+ The `parameter` is a defined attribute of a namespace. The following table lists predefined attributes of the `USERENV` namespace.
+
+ | Parameter   | Description                                                                                                                               |                                                                         
+ | ----------- | ----------------------------------------------------------------------------------------------------------------------------------------- | 
+ | `ISDBA`     | Returns `TRUE` if the current user has DBA privileges, otherwise `FALSE`.                                                                 |                                                                                                         
+ | `LANGUAGE`  | The language, territory, and character set of the current session in the following format: `language_territory.characterset` |                                                                           
+ | `LANG`      | The ISO abbreviation for the language name, a short name for the existing `LANGUAGE` parameter.                                           |              
+ | `SID`       | The current session identifier.                                                                                                           | 
+ | `TERMINAL`  | The current session's operating system terminal identifier.         
+
+### Examples
+
+In these examples, the built-in `USERENV` namespace is used with the `SYS_CONTEXT` function.
+
+This example returns the `ISDBA` parameter of the current session:
+
+```sql
+edb=# SELECT SYS_CONTEXT('USERENV','ISDBA') AS ISDBA FROM DUAL;
+__OUTPUT__
+ isdba 
+-------
+ TRUE
+(1 row)
+```
+
+This example returns the `LANG` parameter of the current session:
+
+```sql
+edb=# SELECT SYS_CONTEXT('USERENV','LANG') AS LANG FROM DUAL;
+__OUTPUT__
+ lang 
+------
+ en
+(1 row)
+```
+
+This example returns the `LANGUAGE` parameter of the current session:
+
+```sql
+edb=# SELECT SYS_CONTEXT('USERENV','LANGUAGE') AS LANGUAGE FROM DUAL;
+__OUTPUT__
+     language      
+-------------------
+ English_USA.UTF-8
+(1 row)
+```
+
+This example returns the `TERMINAL` identifier:
+
+```sql
+edb=# SELECT SYS_CONTEXT('USERENV','TERMINAL') AS TERMINAL FROM DUAL;
+__OUTPUT__
+ terminal 
+----------
+ [local]
+(1 row)
+```
+
+This example returns the `SID` number of the current session:
+
+```sql
+edb=# SELECT SYS_CONTEXT('USERENV','SID') AS SID FROM DUAL;
+__OUTPUT__
+  sid  
+-------
+ 56867
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/14_bitwise_functions.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/14_bitwise_functions.mdx
new file mode 100644
index 00000000000..42854487247
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/14_bitwise_functions.mdx
@@ -0,0 +1,95 @@
+---
+title: "Bitwise functions"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/14_bitwise_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="numeric_functions" class="registered_link"></div>
+
+The bitwise functions include `BITAND` and `BITOR`.
+
+## BITAND
+
+The `BITAND` function performs a bitwise `AND` operation and returns a value based on the data type of input argument. The signature is:
+
+```sql
+BITAND(<expr1>, <expr2>)
+```
+
+The input data type of `expr1` and `expr2` is a `NUMBER` on which the bitwise `AND` operation is performed. The `BITAND` compares each bit of `expr1` value to the corresponding bit of `exp2` using a bitwise `AND` operation. It returns the value based on the data type of the input argument. If either argument to `BITAND` is `NULL`, the result is a `NULL` value.
+
+### Return types
+
+The `BITAND` function returns the same value as the data type of the input argument.
+
+### Examples
+
+This example performs an `AND` operation on the numbers 10 and 11.
+
+```sql
+edb=# SELECT BITAND(10,11) FROM DUAL;
+__OUTPUT__
+ bitand 
+--------
+     10
+(1 row)
+```
+
+## BITOR
+
+The `BITOR` function performs a bitwise `OR` operation and returns a value based on the data type of the input argument. The signature is:
+
+```sql
+BITOR(<expr1>, <expr2>)
+```
+
+The `BITOR` compares each bit of `expr1` value to the corresponding bit of `exp2` using a bitwise `OR` operation. It returns the value based on the data type of the input argument.
+
+### Return types
+
+The `BITOR` function returns the same value as the data type of the input argument. If all the values of a column are `NULL`, the `BITOR` returns `NULL`.
+
+### Examples
+
+This example performs an `OR` operation on the numbers 10 and 11.
+
+```sql
+edb=# SELECT BITOR(10,11) FROM DUAL;
+__OUTPUT__
+ bitor 
+-------
+    11
+(1 row)
+```
+
+## BITWISE OPERATORS
+
+The bitwise operators perform the same operation as `BITAND` and `BITOR`. The bitwise operators are:
+
+-  `&`: `(Bitwise AND)` Return the result of a bitwise `AND` operation performed on the input type.
+
+-  `|`: `(Bitwise OR)` Return the result of a bitwise `OR` operation performed on the input type.
+
+### Examples
+
+This example uses the `&` operator and returns the output as `BITAND` of the input:
+
+```sql
+edb=# SELECT 10&11 FROM DUAL;
+__OUTPUT__
+ ?column? 
+----------
+       10
+(1 row)
+```
+
+This example uses the `|` operator and returns the output as `BITOR` of the input:
+
+```sql
+edb=# SELECT 10|11 FROM DUAL;
+__OUTPUT__
+ ?column? 
+----------
+       11
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/dump_function.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/dump_function.mdx
new file mode 100644
index 00000000000..47b377bcff7
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/dump_function.mdx
@@ -0,0 +1,66 @@
+---
+title: "DUMP function"
+---
+
+The DUMP function returns a VARCHAR2 value that contains the datatype code, length in bytes, and internal representation of the expression.
+
+```sql
+DUMP(expr[, <return_fmt> [, <start_position> [, <length> ] ] ])
+```
+
+Where `return_fmt` specifies the format of the any of these return values:
+- `8` returns the result in octal notation.
+- `10` returns the result in decimal notation.
+- `16` returns the result in hexadecimal notation.
+- `17` returns each byte printed as a character only if it can be interpreted as a printable character in the character set of the compiler.
+
+The arguments `start_position` and `length` combine to determine the portion of the internal representation to return. The default is to return the entire internal representation in decimal notation.
+
+If `expr` is null, then the function returns `NULL`.
+
+## Examples
+
+```sql
+SELECT dump('abc', 10);
+__OUTPUT__
+          dump          
+------------------------
+ Typ=25 Len=3: 97,98,99
+(1 row)
+```
+
+```sql
+SELECT dump('huvudvärke', 1017) FROM dual;
+__OUTPUT__
+                           dump                           
+----------------------------------------------------------
+ Typ=25 Len=11 CharacterSet=UTF8: h,u,v,u,d,v,c3,a4,r,k,e
+(1 row)
+```
+
+```sql
+SELECT dump ('edbpostgres', 8,2,3) FROM dual;
+__OUTPUT__
+            dump            
+----------------------------
+ Typ=25 Len=11: 144,142,160
+(1 row)
+```
+
+```sql
+SELECT dump(to_timestamp('11-06-2021 12:45:24','MM-DD-YYYY HH:MI:SS'), 1008) FROM dual;
+__OUTPUT__
+                           dump                            
+-----------------------------------------------------------
+ Typ=1184 Len=8 CharacterSet=UTF8: 0,355,12,266,30,163,2,0
+(1 row)
+```
+
+```sql
+SELECT dump(100/4, 10) FROM dual;
+__OUTPUT__
+            dump            
+----------------------------
+ Typ=1700 Len=4: 0,128,25,0
+(1 row)
+```
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/index.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/index.mdx
new file mode 100644
index 00000000000..fad0080520a
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/index.mdx
@@ -0,0 +1,22 @@
+---
+title: "Functions and operators"
+indexCards: simple
+description: "Provides descriptions of functions and operators for the built-in data types"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.094.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.128.html"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../../reference/sql_reference/02_the_sql_language/03_functions_and_operators
+---
+
+<div id="functions_and_operators" class="registered_link"></div>
+
+EDB Postgres Advanced Server provides functions and operators for the built-in data types.
+
+<div class="toctree" maxdepth="3">
+
+logical_operators comparison_operators mathematical_functions_and_operators string_functions_and_operators pattern_matching_string_functions pattern_matching_using_the_like_operator data_type_formatting_functions date_time_functions_and_operators sequence_manipulation_functions conditional_expressions aggregate_functions subquery_expressions identifier_functions bitwise_functions
+
+</div>
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_multi_byte.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_multi_byte.mdx
new file mode 100644
index 00000000000..a92dfee6293
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_multi_byte.mdx
@@ -0,0 +1,65 @@
+---
+title: "TO_MULTI_BYTE function"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/to_multi_byte/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+`TO_MULTI_BYTE` returns char with all its single-byte characters converted to their corresponding multibyte characters. Char can be of data type `CHAR`, `VARCHAR2`, `NCHAR`, or `NVARCHAR2`. The value returned is in the same data type as char.
+
+Any single-byte characters in char with no multibyte equivalents appear in the output string as single-byte characters. This function applies if your database character set contains single-byte and multibyte characters.
+
+## Examples
+
+```sql
+SELECT to_multi_byte('ABC&123') FROM dual;
+__OUTPUT__
+ to_multi_byte  
+----------------
+ＡＢＣ＆１２３
+(1 row)
+```
+
+```sql
+SELECT octet_length('A') FROM dual;
+__OUTPUT__
+ octet_length 
+--------------
+            1
+(1 row)
+```
+
+```sql
+SELECT octet_length(to_multi_byte('A')) FROM dual;
+__OUTPUT__
+ octet_length 
+--------------
+            3
+(1 row)
+```
+
+```sql
+SELECT bit_length(to_multi_byte('A')) FROM dual;
+__OUTPUT__
+ bit_length 
+------------
+         24
+(1 row)
+```
+
+```sql
+SELECT ascii(to_multi_byte('A')) FROM dual;
+__OUTPUT__
+ ascii 
+-------
+ 65313
+(1 row)
+```
+
+```sql
+SELECT to_hex(ascii(to_multi_byte('A'))) FROM dual;
+__OUTPUT__
+ to_hex 
+--------
+ ff21
+(1 row)
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_single_byte.mdx b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_single_byte.mdx
new file mode 100644
index 00000000000..2aea88fc259
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/03_functions_and_operators/to_single_byte.mdx
@@ -0,0 +1,74 @@
+---
+title: "TO_SINGLE_BYTE function"
+redirects:
+  - /epas/latest/epas_compat_reference/02_the_sql_language/03_functions_and_operators/to_single_byte/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+`TO_SINGLE_BYTE` returns char with all its multibyte characters converted to their corresponding single-byte characters. Char can be of data type `CHAR`, `VARCHAR2`, `NCHAR`, or `NVARCHAR2`. The value returned is in the same data type as char.
+
+Any multibyte characters in char that have no single-byte equivalents appear in the output as multibyte characters. This function applies if your database character set contains single-byte and multibyte characters.
+
+## Examples
+
+```sql
+SELECT to_single_byte('ＡＢＣ＆１２３') FROM dual;
+__OUTPUT__
+ to_single_byte 
+----------------
+ ABC&123
+(1 row)
+```
+
+```sql
+SELECT octet_length('Ａ') FROM dual;
+__OUTPUT__
+ octet_length 
+--------------
+            3
+(1 row)
+```
+
+```sql
+SELECT octet_length(to_single_byte('Ａ')) FROM dual;
+__OUTPUT__
+ octet_length 
+--------------
+            1
+(1 row)
+```
+
+```sql
+SELECT bit_length(to_single_byte('Ａ')) FROM dual;
+__OUTPUT__
+ bit_length 
+------------
+          8
+(1 row)
+```
+
+```sql
+SELECT ascii(to_single_byte('Ａ')) FROM dual;
+__OUTPUT__
+ ascii 
+-------
+    65
+(1 row)
+```
+
+```sql
+SELECT to_hex(ascii(to_single_byte('Ａ'))) FROM dual;
+__OUTPUT__
+ to_hex 
+--------
+ 41
+(1 row)
+```
+
+```sql
+SELECT TO_SINGLE_BYTE( CHR(65313)) FROM dual;
+__OUTPUT__
+ to_single_byte 
+----------------
+ A
+(1 row)
+```
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/reference/sql_reference/index.mdx b/product_docs/docs/epas/16/reference/sql_reference/index.mdx
new file mode 100644
index 00000000000..6eb9c772e7b
--- /dev/null
+++ b/product_docs/docs/epas/16/reference/sql_reference/index.mdx
@@ -0,0 +1,24 @@
+---
+navTitle: SQL reference
+title: "SQL reference"
+indexCards: simple
+description: "Describes the subset of the EDB Postgres Advanced Server SQL language that is compatible with Oracle databases"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.001.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/toc.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/reference/database-compatibility-for-oracle-developers-reference-guide/9.6/Database_Compatibility_for_Oracle_Developers_Reference_Guide.1.005.html"
+redirects:
+  - /epas/latest/epas_compat_reference/ #generated for docs/epas/reorg-role-use-case-mode
+  - /epas/latest/epas_compat_reference/02_the_sql_language #generated for docs/epas/reorg-role-use-case-mode
+  - ../../reference/sql_reference/02_the_sql_language/
+---
+
+<div id="introduction" class="registered_link"></div>
+
+This SQL reference information applies to organizations migrating their Oracle applications to use EDB Postgres Advanced Server.
+
+A subset of the EDB Postgres Advanced Server SQL language is compatible with Oracle databases. These SQL syntaxes, data types, and functions work in both EDB Postgres Advanced Server and Oracle.
+
+!!! Note
+    The EDB Postgres Advanced Server also includes syntax and commands for extended functionality (functionality that doesn't provide database compatibility for Oracle or support Oracle-styled applications) that aren't included here.
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm.mdx
new file mode 100644
index 00000000000..b76706c076d
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/06_unicode_collation_algorithm.mdx
@@ -0,0 +1,330 @@
+---
+title: "Unicode Collation Algorithm"
+description: "How to use the Unicode Collation Algorithm specification to collate and compare Unicode data"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.25.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.23.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.21.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.22.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.023.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.025.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.022.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.021.html"
+redirects:
+  - /epas/latest/epas_guide/03_database_administration/06_unicode_collation_algorithm/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="unicode_collation_algorithm" class="registered_link"></div>
+
+The Unicode Collation Algorithm (UCA) is a specification (*Unicode Technical Report #10*) that defines a customizable method of collating and comparing Unicode data. *Collation* means how data is sorted, as with a `SELECT … ORDER BY` clause. *Comparison* is relevant for searches that use ranges with less than, greater than, or equal to operators.
+
+## Benefits
+
+Customizability is an important factor for various reasons:
+
+-   Unicode supports many languages. Letters that might be common to several languages might collate in different orders depending on the language.
+-   Characters that appear with letters in certain languages, such as accents or umlauts, have an impact on the expected collation depending on the language.
+-   In some languages, combinations of several consecutive characters are treated as a single character with regard to their collation sequence.
+-   There might be certain preferences as to collating letters according to case. For example, the lowercase form of a letter might collate before the uppercase form of the same letter or vice versa.
+-   There might be preferences as to whether punctuation marks like underscore characters, hyphens, or space characters are considered in the collating sequence or whether they're ignored.
+
+Given all of these variations with the many languages supported by Unicode, a method is needed to select the specific criteria for determining a collating sequence. This is what the Unicode Collation Algorithm defines.
+
+!!! Note
+    Another advantage for using ICU collations (the implementation of the Unicode Collation Algorithm) is for performance. Sorting tasks, including B-tree index creation, can complete in less than half the time it takes with a non-ICU collation. The exact performance gain depends on your operating system version, the language of your text data, and other factors.
+
+## Basic Unicode Collation Algorithm concepts
+
+The official information for the Unicode Collation Algorithm is specified in [Unicode Technical Report #10](http://www.unicode.org/reports/tr10/).
+
+The International Components for Unicode (ICU) also provides useful information. You can find an explanation of the collation concepts on the [ICU website](http://userguide.icu-project.org/collation/concepts).
+
+The basic concept behind the Unicode Collation Algorithm is the use of multilevel comparison. This means that a number of levels are defined, which are listed as level 1 through level 5 in the following bullet points. Each level defines a type of comparison. Strings are first compared using the primary level, also called level 1.
+
+If the order can be determined based on the primary level, then the algorithm is done. If the order can't be determined based on the primary level, then the secondary level, level 2, is applied. If the order can be determined based on the secondary level, then the algorithm is done, otherwise the tertiary level is applied, and so on. There is typically a final, tie-breaking level to determine the order if it can't be resolved by the prior levels.
+
+-   **Level 1 – Primary level for base characters** &mdash; The order of basic characters such as letters and digits determines the difference, such as `A < B`.
+-   **Level 2 – Secondary level for accents** &mdash; If there are no primary level differences, then the presence or absence of accents and other such characters determines the order, such as `a < á`.
+-   **Level 3 – Tertiary level for case** &mdash; If there are no primary level or secondary level differences, then a difference in case determines the order, such as `a < A`.
+-   **Level 4 – Quaternary level for punctuation** &mdash; If there are no primary, secondary, or tertiary level differences, then the presence or absence of white-space characters, control characters, and punctuation determine the order, such as `-A < A`.
+-   **Level 5 – Identical level for tie breaking** &mdash; If there are no primary, secondary, tertiary, or quaternary level differences, then some other difference such as the code point values determines the order.
+
+## International components for Unicode
+
+The Unicode Collation Algorithm is implemented by open source software provided by the International Components for Unicode (ICU). The software is a set of C/C++ and Java libraries.
+
+When you use EDB Postgres Advanced Server to create a collation that invokes the ICU components to produce the collation, the result is referred to as an *ICU collation*.
+
+### Locale collations
+
+When creating a collation for a locale, a predefined *ICU short form* name for the given locale is typically provided. An ICU short form is a method of specifying *collation attributes*, which are the properties of a collation. See [Collation attributes](#collation-attributes) for more information.
+
+There are predefined ICU short forms for locales. The ICU short form for a locale incorporates the collation attribute settings typically used for the given locale. The short form simplifies the collation creation process by eliminating the need to specify the entire list of collation attributes for that locale.
+
+The system catalog `pg_catalog.pg_icu_collate_names` contains a list of the names of the ICU short forms for locales. The ICU short form name is listed in column `icu_short_form`.
+
+```sql
+edb=# SELECT icu_short_form, valid_locale FROM pg_icu_collate_names ORDER BY
+valid_locale;
+__OUTPUT__
+ icu_short_form | valid_locale
+----------------+--------------
+ LAF            | af
+ LAR            | ar
+ LAS            | as
+ LAZ            | az
+ LBE            | be
+ LBG            | bg
+ LBN            | bn
+ LBS            | bs
+ LBS_ZCYRL      | bs_Cyrl
+ LROOT          | ca
+ LROOT          | chr
+ LCS            | cs
+ LCY            | cy
+ LDA            | da
+ LROOT          | de
+ LROOT          | dz
+ LEE            | ee
+ LEL            | el
+ LROOT          | en
+ LROOT          | en_US
+ LEN_RUS_VPOSIX | en_US_POSIX
+ LEO            | eo
+ LES            | es
+ LET            | et
+ LFA            | fa
+ LFA_RAF        | fa_AF
+    .
+    .
+    .
+```
+
+If needed, you can override the default characteristics of an ICU short form for a given locale by specifying the collation attributes to override that property. 
+
+### Collation attributes
+
+When creating an ICU collation, you must specify the desired characteristics of the collation. As discussed in [Locale collations](#locale-collations), you can typically do this with an ICU short form for the desired locale. However, if you need more specific information, you can specify the collation properties using *collation attributes*.
+
+Collation attributes define the rules of how to compare characters for determining the collation sequence of text strings. As Unicode covers many languages in numerous variations according to country, territory, and culture, these collation attributes are complex.
+
+For the complete and precise meaning and usage of collation attributes, see “Collator Naming Scheme” on the [ICU – International Components for Unicode website](http://userguide.icu-project.org/collation/concepts).
+
+Each collation attribute is represented by an uppercase letter. The possible valid values for each attribute are given by codes shown in the parentheses. Some codes have general meanings for all attributes. **X** means to set the attribute off. **O** means to set the attribute on. **D** means to set the attribute to its default value.
+
+-   **A – Alternate (N, S, D)** &mdash; Handles treatment of *variable* characters such as white spaces, punctuation marks, and symbols. When set to non-ignorable (N), differences in variable characters are treated with the same importance as differences in letters. When set to shifted (S), then differences in variable characters are of minor importance (that is, the variable character is ignored when comparing base characters).
+-   **C – Case first (X, L, U, D)** &mdash; Controls whether a lowercase letter sorts before the same uppercase letter (L), or the uppercase letter sorts before the same lowercase letter (U). You typically specify off (X) when you want lowercase first (L).
+-   **E – Case level (X, O, D)**. Set in combination with the Strength attribute, use the Case Level attribute when you want to ignore accents but not case.
+-   **F – French collation (X, O, D)** &mdash; When set to on, secondary differences (presence of accents) are sorted from the back of the string as done in the French Canadian locale.
+-   **H – Hiragana quaternary (X, O, D)** &mdash; Introduces an additional level to distinguish between the Hiragana and Katakana characters for compatibility with the JIS X 4061 collation of Japanese character strings.
+-   **N – Normalization checking (X, O, D)** &mdash; Controls whether text is thoroughly normalized for comparison. Normalization deals with the issue of canonical equivalence of text whereby different code point sequences represent the same character. This occurrence then presents issues when sorting or comparing such characters &mdash; For languages such as Arabic, ancient Greek, Hebrew, Hindi, Thai, or Vietnamese, set normalization checking to on.
+-   **S – Strength (1, 2, 3, 4, I, D)** &mdash; Maximum collation level used for comparison. Influences whether accents or case are taken into account when collating or comparing strings. Each number represents a level. A setting of I represents identical strength (that is, level 5).
+-   **T – Variable top (hexadecimal digits)** &mdash; Applies only when the Alternate attribute isn't set to non-ignorable (N). The hexadecimal digits specify the highest character sequence to consider ignorable. For example, if white space is ignorable but visible variable characters aren't, then set Variable Top to 0020 along with the Alternate attribute set to S and the Strength attribute set to 3. (The space character is hexadecimal 0020. Other nonvisible variable characters, such as backspace, tab, line feed, and carriage return, have values less than 0020. All visible punctuation marks have values greater than 0020.)
+
+A set of collation attributes and their values is represented by a text string consisting of the collation attribute letter concatenated with the desired attribute value. Each attribute/value pair is joined to the next pair with an underscore character:
+
+ `AN_CX_EX_FX_HX_NO_S3`
+
+You can specify collation attributes with a locale’s ICU short form name to override those default attribute settings of the locale.
+
+In this example, the ICU short form named `LROOT` is modified with a number of other collation attribute/value pairs:
+
+ `AN_CX_EX_LROOT_NO_S3`
+
+The Alternate attribute (`A`) is set to non-ignorable (`N`). The Case First attribute (`C`) is set to off (`X`). The Case Level attribute (`E`) is set to off (`X`). The Normalization attribute (`N`) is set to on (`O`). The Strength attribute (`S`) is set to the tertiary level `3`. `LROOT` is the ICU short form to which these other attributes are applying modifications.
+
+## Using a collation
+
+You can use a newly defined ICU collation anywhere you can use the `COLLATION "collation_name"` clause in a SQL command. For example, you can use it in the column specifications of the `CREATE TABLE` command or appended to an expression in the `ORDER BY` clause of a `SELECT` command.
+
+The following are some examples of creating and using ICU collations based on the English language in the United States (`en_US.UTF8`). In these examples, ICU collations are created with the following characteristics:
+
+-  Collation `icu_collate_lowercase` forces the lowercase form of a letter to sort before its uppercase counterpart (`CL`).
+
+-  Collation `icu_collate_uppercase` forces the uppercase form of a letter to sort before its lowercase counterpart (`CU`).
+
+-  Collation `icu_collate_ignore_punct` causes variable characters (white space and punctuation marks) to be ignored during sorting (`AS`).
+
+-  Collation `icu_collate_ignore_white_sp` causes white space and other nonvisible variable characters to be ignored during sorting, but visible variable characters (punctuation marks) aren't ignored (`AS`, `T0020`).
+
+```sql
+CREATE COLLATION icu_collate_lowercase (
+    LOCALE = 'en_US.UTF8',
+    ICU_SHORT_FORM = 'AN_CL_EX_NX_LROOT'
+);
+
+CREATE COLLATION icu_collate_uppercase (
+    LOCALE = 'en_US.UTF8',
+    ICU_SHORT_FORM = 'AN_CU_EX_NX_LROOT'
+);
+
+CREATE COLLATION icu_collate_ignore_punct (
+    LOCALE = 'en_US.UTF8',
+    ICU_SHORT_FORM = 'AS_CX_EX_NX_LROOT_L3'
+);
+
+CREATE COLLATION icu_collate_ignore_white_sp (
+    LOCALE = 'en_US.UTF8',
+    ICU_SHORT_FORM = 'AS_CX_EX_NX_LROOT_L3_T0020'
+);
+```
+
+!!! Note
+    When creating collations, ICU might generate notice and warning messages when attributes are given to modify the `LROOT` collation.
+
+The following `psql` command lists the collations:
+
+```sql
+edb=# \dO
+__OUTPUT__
+                                      List of collations
+    Schema    |            Name             |  Collate   |   Ctype    |     ICU
+--------------+-----------------------------+------------+------------+----------------------------
+ enterprisedb | icu_collate_ignore_punct    | en_US.UTF8 | en_US.UTF8 | AS_CX_EX_NX_LROOT_L3
+ enterprisedb | icu_collate_ignore_white_sp | en_US.UTF8 | en_US.UTF8 |
+ AS_CX_EX_NX_LROOT_L3_T0020
+ enterprisedb | icu_collate_lowercase       | en_US.UTF8 | en_US.UTF8 | AN_CL_EX_NX_LROOT
+ enterprisedb | icu_collate_uppercase       | en_US.UTF8 | en_US.UTF8 | AN_CU_EX_NX_LROOT
+(4 rows)
+```
+
+The following table is created and populated:
+
+```sql
+CREATE TABLE collate_tbl (
+    id              INTEGER,
+    c2              VARCHAR(2)
+);
+
+INSERT INTO collate_tbl VALUES (1, 'A');
+INSERT INTO collate_tbl VALUES (2, 'B');
+INSERT INTO collate_tbl VALUES (3, 'C');
+INSERT INTO collate_tbl VALUES (4, 'a');
+INSERT INTO collate_tbl VALUES (5, 'b');
+INSERT INTO collate_tbl VALUES (6, 'c');
+INSERT INTO collate_tbl VALUES (7, '1');
+INSERT INTO collate_tbl VALUES (8, '2');
+INSERT INTO collate_tbl VALUES (9, '.B');
+INSERT INTO collate_tbl VALUES (10, '-B');
+INSERT INTO collate_tbl VALUES (11, ' B');
+```
+
+### Using the default collation
+
+The following query sorts on column `c2` using the default collation. Variable characters (white space and punctuation marks) with `id` column values of `9`, `10`, and `11` are ignored and sort with the letter `B`.
+
+```sql
+edb=# SELECT * FROM collate_tbl ORDER BY c2;
+__OUTPUT__
+ id  | c2
+-----+----
+ 7   | 1
+ 8   | 2
+ 4   | a
+ 1   | A
+ 5   | b
+ 2   | B
+ 11  | B
+ 10  | -B
+ 9   | .B
+ 6   | c
+ 3   | C
+(11 rows)
+```
+
+### Using collation icu_collate_lowercase
+
+The following query sorts on column `c2` using collation `icu_collate_lowercase`. This collation forces the lowercase form of a letter to sort before the uppercase form of the same base letter. The `AN` attribute forces the sort order to include variable characters at the same level when comparing base characters. Thus rows with `id` values of `9`, `10`, and `11` appear at the beginning of the sort list before all letters and numbers.
+
+```sql
+edb=# SELECT * FROM collate_tbl ORDER BY c2 COLLATE "icu_collate_lowercase";
+__OUTPUT__
+ id | c2
+----+----
+ 11 |  B
+ 10 | -B
+ 9  | .B
+ 7  | 1
+ 8  | 2
+ 4  | a
+ 1  | A
+ 5  | b
+ 2  | B
+ 6  | c
+ 3  | C
+(11 rows)
+```
+
+### Using collation icu_collate_uppercase
+
+The following query sorts on column `c2` using collation `icu_collate_uppercase`. This collations forces the uppercase form of a letter to sort before the lowercase form of the same base letter.
+
+```sql
+edb=# SELECT * FROM collate_tbl ORDER BY c2 COLLATE "icu_collate_uppercase";
+__OUTPUT__
+ id | c2
+----+----
+ 11 |  B
+ 10 | -B
+ 9  | .B
+ 7  | 1
+ 8  | 2
+ 1  | A
+ 4  | a
+ 2  | B
+ 5  | b
+ 3  | C
+ 6  | c
+(11 rows)
+```
+
+### Using collation icu_collate_ignore_punct
+
+The following query sorts on column `c2` using collation `icu_collate_ignore_punct`. This collation causes variable characters to be ignored so rows with id values of `9`, `10`, and `11` sort with the letter `B`, the character immediately following the ignored variable character.
+
+```sql
+edb=# SELECT * FROM collate_tbl ORDER BY c2 COLLATE
+"icu_collate_ignore_punct";
+__OUTPUT__
+ id  | c2
+-----+----
+  7  | 1
+  8  | 2
+  4  | a
+  1  | A
+  5  | b
+  11 |  B
+  2  | B
+  9  | .B
+  10 | -B
+  6  | c
+  3  | C
+(11 rows)
+```
+
+### Using collation icu_collate_ignore_white_sp
+
+The following query sorts on column `c2` using collation `icu_collate_ignore_white_sp`. The `AS` and `T0020` attributes of the collation cause variable characters with code points less than or equal to hexadecimal `0020` to be ignored while variable characters with code points greater than hexadecimal `0020` are included in the sort.
+
+The row with `id` value of `11`, which starts with a space character (hexadecimal `0020`), sorts with the letter `B`. The rows with `id` values of `9` and `10`, which start with visible punctuation marks greater than hexadecimal `0020`, appear at the beginning of the sort list. These particular variable characters are included in the sort order at the same level when comparing base characters.
+
+```sql
+edb=# SELECT * FROM collate_tbl ORDER BY c2 COLLATE
+"icu_collate_ignore_white_sp";
+__OUTPUT__
+ id | c2
+----+----
+ 10 | -B
+ 9  | .B
+ 7  | 1
+ 8  | 2
+ 4  | a
+ 1  | A
+ 5  | b
+ 11 |  B
+ 2  | B
+ 6  | c
+ 3  | C
+(11 rows)
+```
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/10_ecpgplus.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/10_ecpgplus.mdx
new file mode 100644
index 00000000000..26246b7e678
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/10_ecpgplus.mdx
@@ -0,0 +1,25 @@
+---
+title: "ECPGPlus"
+description: "How to use ECPGPlus to include embedded SQL commands in C applications"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.122.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.347.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/10_ecpgplus/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="ecpgplus" class="registered_link"></div>
+
+EDB has enhanced ECPG (the PostgreSQL precompiler) to create ECPGPlus. ECPGPlus allows you to include embedded SQL commands in C applications. When you use ECPGPlus to compile an application that contains embedded SQL commands, the SQL code is syntax checked and translated into C.
+
+ECPGPlus supports Pro\*C-compatible syntax in C programs when connected to an EDB Postgres Advanced Server database. ECPGPlus supports:
+
+-   Oracle Dynamic SQL – Method 4 (ODS-M4)
+-   Pro\*C-compatible anonymous blocks
+-   A `CALL` statement compatible with Oracle databases
+
+As part of ECPGPlus' Pro\*C compatibility, you don't need to include the `BEGIN DECLARE SECTION` and `END DECLARE SECTION` directives.
+
+See [ECPGPlus overview](../../application_programming/ecpgplus_guide/02_overview/) for details about installing and configuring the utility.
+
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/11_libpq_c_library.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/11_libpq_c_library.mdx
new file mode 100644
index 00000000000..e50328e1972
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/11_libpq_c_library.mdx
@@ -0,0 +1,500 @@
+---
+title: "libpq C library"
+description: "How to use the libpq C library functions in client programs to pass queries to the EDB Postgres Advanced Server"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.39.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.38.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.222.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.108.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.098.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.097.html"
+redirects:
+  - /epas/latest/epas_guide/11_libpq_c_library/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+libpq is the C application programmer’s interface to EDB Postgres Advanced Server. libpq is a set of library functions that allow client programs to pass queries to the EDB Postgres Advanced Server and to receive the results of these queries.
+
+libpq is also the underlying engine for several other EDB application interfaces, including those written for C++, Perl, Python, Tcl, and ECPG. Some aspects of libpq’s behavior are important to you if you are using one of those packages.
+
+## Prerequisites
+
+Client programs that use libpq must include the header file `libpq-fe.h` and must link with the `libpq` library.
+
+## Using libpq with EDB SPL
+
+You can use the EDB SPL language with the libpq interface library, providing support for:
+
+-   Procedures, functions, packages
+-   Prepared statements
+-   `REFCURSORs`
+-   Static cursors
+-   `structs` and `typedefs`
+-   Arrays
+-   DML and DDL operations
+-   `IN`/`OUT`/`IN OUT` parameters
+
+## REFCURSOR support
+
+In earlier releases, EDB Postgres Advanced Server provided support for REFCURSORs through the following libpq functions. These functions are now deprecated:
+
+-   `PQCursorResult()`
+-   `PQgetCursorResult()`
+-   `PQnCursor()`
+
+You can now use `PQexec()` and `PQgetvalue()` to retrieve a `REFCURSOR` returned by an SPL (or PL/pgSQL) function. A `REFCURSOR` is returned in the form of a null-terminated string indicating the name of the cursor. Once you have the name of the cursor, you can execute one or more `FETCH` statements to retrieve the values exposed through the cursor.
+
+!!! Note
+    The examples that follow don't include the error-handling code required in a real-world client application.
+
+### Returning a single REFCURSOR
+
+This example shows an SPL function that returns a value of type `REFCURSOR`:
+
+```sql
+CREATE OR REPLACE FUNCTION getEmployees(p_deptno NUMERIC)
+RETURN REFCURSOR AS
+  result REFCURSOR;
+BEGIN
+  OPEN result FOR SELECT * FROM emp WHERE deptno = p_deptno;
+
+  RETURN result;
+END;
+```
+
+This function expects a single parameter, `p_deptno`, and returns a `REFCURSOR` that holds the result set for the `SELECT` query shown in the `OPEN` statement. The `OPEN` statement executes the query and stores the result set in a cursor. The server constructs a name for that cursor and stores the name in a variable named `result`. The function then returns the name of the cursor to the caller.
+
+To call this function from a C client using libpq, you can use `PQexec()` and `PQgetvalue()`:
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include "libpq-fe.h"
+
+static void fetchAllRows(PGconn *conn,
+                         const char *cursorName,
+                         const char *description);
+static void fail(PGconn *conn, const char *msg);
+
+int
+main(int argc, char *argv[])
+{
+  PGconn    *conn = PQconnectdb(argv[1]);
+  PGresult  *result;
+
+  if (PQstatus(conn) != CONNECTION_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  result = PQexec(conn, "BEGIN TRANSACTION");
+
+  if (PQresultStatus(result) != PGRES_COMMAND_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  PQclear(result);
+
+  result = PQexec(conn, "SELECT * FROM getEmployees(10)");
+
+  if (PQresultStatus(result) != PGRES_TUPLES_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  fetchAllRows(conn, PQgetvalue(result, 0, 0), "employees");
+
+  PQclear(result);
+
+  PQexec(conn, "COMMIT");
+
+  PQfinish(conn);
+
+  exit(0);
+}
+
+static void
+fetchAllRows(PGconn *conn,
+             const char *cursorName,
+             const char *description)
+{
+  size_t  commandLength = strlen("FETCH ALL FROM ") +
+                          strlen(cursorName) + 3;
+
+  char   *commandText = malloc(commandLength);
+  PGresult *result;
+  int       row;
+
+  sprintf(commandText, "FETCH ALL FROM \"%s\"", cursorName);
+
+  result = PQexec(conn, commandText);
+
+  if (PQresultStatus(result) != PGRES_TUPLES_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  printf("-- %s --\n", description);
+
+  for (row = 0; row < PQntuples(result); row++)
+  {
+    const char *delimiter = "\t";
+    int         col;
+
+    for (col = 0; col < PQnfields(result); col++)
+    {
+      printf("%s%s", delimiter, PQgetvalue(result, row, col));
+      delimiter = ",";
+    }
+
+    printf("\n");
+  }
+
+  PQclear(result);
+  free(commandText);
+}
+
+static void
+fail(PGconn *conn, const char *msg)
+{
+  fprintf(stderr, "%s\n", msg);
+
+  if (conn != NULL)
+    PQfinish(conn);
+
+  exit(-1);
+}
+```
+
+The code sample contains a line of code that calls the `getEmployees()` function and returns a result set that contains all of the employees in department `10`:
+
+```sql
+result = PQexec(conn, "SELECT * FROM getEmployees(10)");
+```
+
+The `PQexec()` function returns a result set handle to the C program. The result set contains one value:  the name of the cursor returned by `getEmployees()`.
+
+Once you have the name of the cursor, you can use the SQL `FETCH` statement to retrieve the rows in that cursor. The function `fetchAllRows()` builds a `FETCH ALL` statement, executes that statement, and then prints the result set of the `FETCH ALL` statement.
+
+The output of this program is:
+
+```sql
+-- employees --
+    7782,CLARK,MANAGER,7839,09-JUN-81 00:00:00,2450.00,,10
+    7839,KING,PRESIDENT,,17-NOV-81 00:00:00,5000.00,,10
+    7934,MILLER,CLERK,7782,23-JAN-82 00:00:00,1300.00,,10
+```
+
+### Returning multiple REFCURSORs
+
+The next example returns two `REFCURSORs`:
+
+-   The first `REFCURSOR` contains the name of a cursor (`employees`) that contains all employees who work in a department in the range specified by the caller.
+-   The second `REFCURSOR` contains the name of a cursor (`departments`) that contains all of the departments in the range specified by the caller.
+
+In this example, instead of returning a single `REFCURSOR`, the function returns a `SETOF REFCURSOR`, which means 0 or more `REFCURSORS`. One other important difference is that the libpq program must not expect a single `REFCURSOR` in the result set. It must expect two rows, each of which contains a single value. The first row contains the name of the `employees` cursor, and the second row contains the name of the `departments` cursor.
+
+```sql
+CREATE OR REPLACE FUNCTION getEmpsAndDepts(p_min NUMERIC,
+                                           p_max NUMERIC)
+RETURN SETOF REFCURSOR AS
+  employees   REFCURSOR;
+  departments REFCURSOR;
+BEGIN
+  OPEN employees FOR
+    SELECT * FROM emp WHERE deptno BETWEEN p_min AND p_max;
+  RETURN NEXT employees;
+
+  OPEN departments FOR
+    SELECT * FROM dept WHERE deptno BETWEEN p_min AND p_max;
+  RETURN NEXT departments;
+END;
+```
+
+As in the previous example, you can use `PQexec()` and `PQgetvalue()` to call the SPL function:
+
+```c
+#include <stdio.h>
+#include <stdlib.h>
+#include "libpq-fe.h"
+
+static void fetchAllRows(PGconn *conn,
+                         const char *cursorName,
+                         const char *description);
+static void fail(PGconn *conn, const char *msg);
+
+int
+main(int argc, char *argv[])
+{
+  PGconn *conn = PQconnectdb(argv[1]);
+  PGresult *result;
+
+  if (PQstatus(conn) != CONNECTION_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  result = PQexec(conn, "BEGIN TRANSACTION");
+
+  if (PQresultStatus(result) != PGRES_COMMAND_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  PQclear(result);
+
+  result = PQexec(conn, "SELECT * FROM getEmpsAndDepts(20, 30)");
+
+  if (PQresultStatus(result) != PGRES_TUPLES_OK)
+    fail(conn, PQerrorMessage(conn));
+
+  fetchAllRows(conn, PQgetvalue(result, 0, 0), "employees");
+  fetchAllRows(conn, PQgetvalue(result, 1, 0), "departments");
+
+  PQclear(result);
+
+  PQexec(conn, "COMMIT");
+
+  PQfinish(conn);
+
+  exit(0);
+}
+
+static void
+fetchAllRows(PGconn *conn,
+             const char *cursorName,
+             const char *description)
+{
+  size_t     commandLength = strlen("FETCH ALL FROM ") +
+                             strlen(cursorName) + 3;
+  char        *commandText     = malloc(commandLength);
+  PGresult  *result;
+  int        row;
+
+  sprintf(commandText, "FETCH ALL FROM \"%s\"", cursorName);
+
+  result = PQexec(conn, commandText);
+
+  if (PQresultStatus(result) != PGRES_TUPLES_OK)
+  fail(conn, PQerrorMessage(conn));
+
+  printf("-- %s --\n", description);
+
+  for (row = 0; row < PQntuples(result); row++)
+  {
+    const char *delimiter = "\t";
+    int         col;
+
+    for (col = 0; col < PQnfields(result); col++)
+    {
+      printf("%s%s", delimiter, PQgetvalue(result, row, col));
+      delimiter = ",";
+    }
+
+    printf("\n");
+  }
+
+  PQclear(result);
+  free(commandText);
+}
+
+static void
+fail(PGconn *conn, const char *msg)
+{
+  fprintf(stderr, "%s\n", msg);
+
+  if (conn != NULL)
+    PQfinish(conn);
+
+  exit(-1);
+}
+```
+
+If you call `getEmpsAndDepts(20, 30)`, the server returns a cursor that contains all employees who work in department 20 or 30 and a second cursor containing the description of departments 20 and 30.
+
+```sql
+-- employees --
+  7369,SMITH,CLERK,7902,17-DEC-80 00:00:00,800.00,,20
+  7499,ALLEN,SALESMAN,7698,20-FEB-81 00:00:00,1600.00,300.00,30
+  7521,WARD,SALESMAN,7698,22-FEB-81 00:00:00,1250.00,500.00,30
+  7566,JONES,MANAGER,7839,02-APR-81 00:00:00,2975.00,,20
+  7654,MARTIN,SALESMAN,7698,28-SEP-81 00:00:00,1250.00,1400.00,30
+  7698,BLAKE,MANAGER,7839,01-MAY-81 00:00:00,2850.00,,30
+  7788,SCOTT,ANALYST,7566,19-APR-87 00:00:00,3000.00,,20
+  7844,TURNER,SALESMAN,7698,08-SEP-81 00:00:00,1500.00,0.00,30
+  7876,ADAMS,CLERK,7788,23-MAY-87 00:00:00,1100.00,,20
+  7900,JAMES,CLERK,7698,03-DEC-81 00:00:00,950.00,,30
+  7902,FORD,ANALYST,7566,03-DEC-81 00:00:00,3000.00,,20
+-- departments --
+  20,RESEARCH,DALLAS
+  30,SALES,CHICAGO
+```
+
+## Binding arrays of parameters
+
+EDB Postgres Advanced Server's array binding functionality allows you to send an array of data across the network in a single round trip. When the back end receives the bulk data, it can use the data to perform insert or update operations.
+
+Perform bulk operations with a prepared statement. Use the following function to prepare the statement:
+
+```c
+PGresult *PQprepare(PGconn *conn,
+                    const char *stmtName,
+                    const char *query,
+                    int nParams,
+                    const Oid *paramTypes);
+```
+
+You can find details of `PQprepare()` in the prepared statement section.
+
+You can use the following functions to perform bulk operations:
+
+-   `PQBulkStart`
+-   `PQexecBulk`
+-   `PQBulkFinish`
+-   `PQexecBulkPrepared`
+
+### PQBulkStart
+
+`PQBulkStart()` initializes bulk operations on the server. You must call this function before sending bulk data to the server. `PQBulkStart()` initializes the prepared statement specified in `stmtName` to receive data in a format specified by `paramFmts`.
+
+#### API definition
+
+```c
+PGresult *PQBulkStart(PGconn *conn,
+                      const char *Stmt_Name,
+                      unsigned int nCol,
+                      const int *paramFmts);
+```
+
+### PQexecBulk
+
+Use `PQexecBulk()` to supply data `(paramValues)` for a statement that was previously initialized for bulk operation using `PQBulkStart()`.
+
+You can use this function more than once after `PQBulkStart()` to send multiple blocks of data. 
+
+#### API definition
+
+```c
+PGresult *PQexecBulk(PGconn *conn,
+                     unsigned int nRows,
+                     const char *const * paramValues,
+                     const int *paramLengths);
+```
+
+### PQBulkFinish
+
+This function completes the current bulk operation. You can use the prepared statement again without preparing it again.
+
+#### API definition
+
+```c
+PGresult *PQBulkFinish(PGconn *conn);
+```
+
+### PQexecBulkPrepared
+
+Alternatively, you can use the `PQexecBulkPrepared()` function to perform a bulk operation with a single function call. `PQexecBulkPrepared()` sends a request to execute a prepared statement with the given parameters and waits for the result. This function combines the functionality of `PQbulkStart()`, `PQexecBulk()`, and `PQBulkFinish()`. When using this function, you don't need to initialize or terminate the bulk operation. This function starts the bulk operation, passes the data to the server, and terminates the bulk operation.
+
+Specify a previously prepared statement in the place of `stmtName`. Commands that are used repeatedly are parsed and planned just once, rather than each time they're executed.
+
+#### API definition
+
+```c
+PGresult *PQexecBulkPrepared(PGconn *conn,
+                             const char *stmtName,
+                             unsigned int nCols,
+                             unsigned int nRows,
+                             const char *const *paramValues,
+                             const int *paramLengths,
+                             const int *paramFormats);
+```
+
+### Using PQBulkStart, PQexecBulk, PQBulkFinish
+
+This example uses `PGBulkStart`, `PQexecBulk`, and `PQBulkFinish`:
+
+```c
+void InsertDataUsingBulkStyle( PGconn *conn )
+{
+    PGresult            *res;
+    Oid                 paramTypes[2];
+    char                *paramVals[5][2];
+    int                 paramLens[5][2];
+    int                 paramFmts[2];
+    int                 i;
+
+    int                 a[5] = { 10, 20, 30, 40, 50 };
+    char                b[5][10] = { "Test_1", "Test_2", "Test_3",
+"Test_4", "Test_5" };
+
+
+    paramTypes[0] = 23;
+    paramTypes[1] = 1043;
+    res = PQprepare( conn, "stmt_1", "INSERT INTO testtable1 values( $1, $2
+)", 2, paramTypes );
+    PQclear( res );
+
+    paramFmts[0] = 1;   /* Binary format */
+    paramFmts[1] = 0;
+
+    for( i = 0; i < 5; i++ )
+    {
+        a[i] = htonl( a[i] );
+        paramVals[i][0] = &(a[i]);
+        paramVals[i][1] = b[i];
+
+        paramLens[i][0] = 4;
+        paramLens[i][1] = strlen( b[i] );
+    }
+
+       res = PQBulkStart(conn, "stmt_1", 2, paramFmts);
+       PQclear( res );
+       printf( "< -- PQBulkStart -- >\n" );
+
+       res = PQexecBulk(conn, 5, (const char *const *)paramVals, (const
+     int*)paramLens);
+       PQclear( res );
+       printf( "< -- PQexecBulk -- >\n" );
+
+       res = PQexecBulk(conn, 5, (const char *const *)paramVals, (const
+     int*)paramLens);
+       PQclear( res );
+       printf( "< -- PQexecBulk -- >\n" );
+
+       res = PQBulkFinish(conn);
+       PQclear( res );
+       printf( "< -- PQBulkFinish -- >\n" );
+}
+```
+
+### Using PQexecBulkPrepared
+
+This example uses `PQexecBulkPrepared`:
+
+```c
+void InsertDataUsingBulkStyleCombinedVersion( PGconn *conn )
+{
+       PGresult            *res;
+       Oid                 paramTypes[2];
+       char                *paramVals[5][2];
+       int                 paramLens[5][2];
+       int                 paramFmts[2];
+       int                 i;
+
+       int                 a[5] = { 10, 20, 30, 40, 50 };
+       char                b[5][10] = { "Test_1", "Test_2", "Test_3",
+"Test_4", "Test_5" };
+
+       paramTypes[0] = 23;
+       paramTypes[1] = 1043;
+       res = PQprepare( conn, "stmt_2", "INSERT INTO testtable1 values(
+     $1, $2)", 2, paramTypes );
+       PQclear( res );
+
+       paramFmts[0] = 1;   /* Binary format */
+       paramFmts[1] = 0;
+
+       for( i = 0; i < 5; i++ )
+       {
+                a[i] = htonl( a[i] );
+                paramVals[i][0] = &(a[i]);
+                paramVals[i][1] = b[i];
+
+                paramLens[i][0] = 4;
+                paramLens[i][1] = strlen( b[i] );
+       }
+
+res = PQexecBulkPrepared(conn, "stmt_2", 2, 5, (const char *const
+*)paramVals,(const int *)paramLens, (const int *)paramFmts);
+       PQclear( res );
+}
+```
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/index.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/index.mdx
new file mode 100644
index 00000000000..8b485255030
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/application_developer_tools/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Application programmer tools"
+description: "Describes the EDB Postgres Advanced Server tools designed to assist the application programmer"
+indexCards: simple
+redirects:
+  - /epas/latest/tools_utilities_and_components/application_programmer_tools/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+These EDB Postgres Advanced Server tools are designed to help the application programmer.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/connectors.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/connectors.mdx
new file mode 100644
index 00000000000..45f88266d80
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/connectors.mdx
@@ -0,0 +1,22 @@
+---
+title: Connecting to your database
+description: "Provides a listing of the components used to connect to your EDB Postgres Advanced Server database server"
+redirects:
+  - /epas/latest/connectors/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+We package and support a number of components to connect to your EDB Postgres Advanced Server database server. These EDB components are enhanced versions of the corresponding PostgreSQL components and are intended to support additional EDB Postgres Advanced Server capabilities.     
+
+The EDB components for connecting to your database include:
+
+- [EDB JDBC Connector](/jdbc_connector/latest/) &mdash; Provides connectivity between a Java application and a Postgres database server. 
+
+- [EDB .NET Connector](/net_connector/latest/) &mdash; Provides connectivity between a .NET client application and a Postgres database server
+
+- [EDB OCL Connector](/jdbc_connector/latest/) &mdash; Provides an API similar to the Oracle Call Interface that you can use to interact with a Postgres database server.
+
+- [EDB ODBC Connector](/odbc_connector/latest/) &mdash; Allows an ODBC-compliant client application to connect to a Postgres database server
+
+You can use the PostgreSQL community components with EDB Postgres Advanced Server. However, if your applications require EDB Postgres Advanced Server features, use the EDB components.
+
+
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/data_sources.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/data_sources.mdx
new file mode 100644
index 00000000000..90e139b0202
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/data_sources.mdx
@@ -0,0 +1,18 @@
+---
+title: Connecting to external data sources
+description: "Provides a list of components you can use to connect your Postgres database server to external data sources"
+redirects:
+  - /epas/latest/data_sources/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+We package and support a number of open source components to connect your Postgres database server to external data sources. These EDB components are enhanced versions of the corresponding PostgreSQL components and are intended to support additional EDB Postgres Advanced Server capabilities. 
+
+The EDB components to connect external data sources include:
+
+  - [EDB Hadoop Foreign Data Wrapper](/hadoop_data_adapter/latest/) &mdash;  accesses data that resides on a Hadoop file system from a Postgres database server
+
+  - [MongoDB Foreign Data Wrapper](/mongo_data_adapter/latest/) &mdash;  accesses data that resides on a MongoDB database from a Postgres database server
+
+  - [MySQL Foreign Data Wrapper](/mysql_data_adapter/latest/) &mdash;  accesses data that resides on a MySQL database from a Postgres database server
+
+
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/index.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/index.mdx
new file mode 100644
index 00000000000..8b79913013b
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Connectivity tools"
+description: "Describes the supported open source components you can use to connect to as well as manage your Postgres database"
+indexCards: simple
+redirects:
+  - /epas/latest/tools_utilities_and_components/connectivity_tools/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+We package and support a number of open source components you can use to connect to as well as manage your Postgres database. In addition, we package and support open-source components to connect your server to external data sources. These EDB components are enhanced versions of the corresponding PostgreSQL components and are intended to support additional EDB Postgres Advanced Server capabilities.
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/managing_connections.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/managing_connections.mdx
new file mode 100644
index 00000000000..7339b099271
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/connectivity_tools/managing_connections.mdx
@@ -0,0 +1,18 @@
+---
+title: Managing your database connections
+description: "Provides a list of open source components used to manage the connections to the EDB Postgres Advanced Server database server"
+redirects:
+  - /epas/latest/managing_connections/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+We package and support a number of open source components to manage your connections to your EDB Postgres Advanced Server database server. These EDB components are enhanced versions of the corresponding PostgreSQL components and are intended to support additional EDB Postgres Advanced Server capabilities.  
+
+The EDB components for managing your database connections include:
+
+- [EDB PgBouncer](/pgbouncer/latest/) &mdash; a lightweight connection pooling utility for Postgres installations
+
+- [EDB Pgpool-II](/pgpool/latest/) &mdash; acts as middleware between client applications and a Postgres database server
+
+
+
+
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx
new file mode 100644
index 00000000000..55745a0d639
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/09_tools_and_utilities.mdx
@@ -0,0 +1,18 @@
+---
+title: "Tools and utilities overview"
+description: "Provides an overview of the supported Oracle compatible tools and utility programs"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.099.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/09_tools_and_utilities/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="tools_and_utilities" class="registered_link"></div>
+
+Oracle-compatible tools and utility programs allow you to work with EDB Postgres Advanced Server in a familiar environment. The tools supported by EDB Postgres Advanced Server include:
+
+-   [EDB\*Plus](https://www.enterprisedb.com/docs/edb_plus/latest/)
+-   [EDB\*Loader](../../database_administration/02_edb_loader/)
+-   [EDB\*Wrap](../../epas_security_guide/03_edb_wrap/)
+-   [The Dynamic Runtime Instrumentation Tools Architecture (DRITA)](../../managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/)
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_clone_schema_overview.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_clone_schema_overview.mdx
new file mode 100644
index 00000000000..885e65d58d2
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_clone_schema_overview.mdx
@@ -0,0 +1,14 @@
+---
+title: "EDB clone schema"
+description: "Describes how to use the EDB Clone Schema extension module to copy a schema from a local or remote database"
+---
+
+EDB Clone Schema is an extension module for EDB Postgres Advanced Server that allows you to copy a schema and its database objects from a local or remote database (the source database) to a receiving database (the target database).
+
+The source and target databases can be either:
+
+-  The same physical database 
+-  Different databases in the same database cluster
+-  Separate databases running under different database clusters on separate database server hosts
+
+For details about using the tool, see [Copying a database](../../database_administration/14_edb_clone_schema/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx
new file mode 100644
index 00000000000..d36f8bac96d
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_loader_overview.mdx
@@ -0,0 +1,8 @@
+---
+title: "EDB*Loader"
+description: "Provides an overview of the EDB*Loader high-performance bulk data loader"
+---
+
+EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader.
+
+For details about using the tool, see [Loading bulk data](../../database_administration/02_edb_loader/).
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_resource_manager_overview.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_resource_manager_overview.mdx
new file mode 100644
index 00000000000..bf76c988830
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/edb_resource_manager_overview.mdx
@@ -0,0 +1,10 @@
+---
+title: "EDB Resource Manager"
+description: "How to use the EDB Resource Manager to control the use of operating system resources used by EDB Postgres Advanced Server processes"
+---
+
+EDB Resource Manager is an EDB Postgres Advanced Server feature that lets you control the use of operating system resources used by EDB Postgres Advanced Server processes.
+
+This capability allows you to protect the system from processes that might uncontrollably overuse and monopolize certain system resources.
+
+For details about using the utility, see [Throttling CPU and I/O at the process level](../../database_administration/10_edb_resource_manager/).
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/index.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/index.mdx
new file mode 100644
index 00000000000..1076e358c52
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/database_administration_tools/index.mdx
@@ -0,0 +1,9 @@
+---
+title: "Database administrator tools"
+description: "Describes the EDB Postgres Advanced Server features designed to increase database administrator productivity"
+indexCards: simple
+redirects:
+  - /epas/latest/tools_utilities_and_components/database_administrator_tools/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server includes features designed to increase database administrator productivity, such as enabling DBAs to prioritize different workloads using the Resource Manager feature. 
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/epas_compat_tools_guide/index.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/epas_compat_tools_guide/index.mdx
new file mode 100644
index 00000000000..173e95f0c75
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/epas_compat_tools_guide/index.mdx
@@ -0,0 +1,33 @@
+---
+navTitle: Oracle-compatibility tools
+title: "Oracle-compatibility tools"
+description: "Describes the tools and utilities that enable developers working with Oracle utilities to work with EDB Postgres Advanced Server in a familiar environment"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/DB_Compat_for_Oracle_Dev_Tools_Guide.1.01.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-tools-and-utilities-guide/9.6/toc.html"
+redirects:
+  - /epas/latest/epas_compat_tools_guide/ #generated for docs/epas/reorg-role-use-case-mode
+  - ../../epas_compat_tools_guide/
+---
+
+<div id="introduction" class="registered_link"></div>
+
+These tools and utilities allow a developer that works with Oracle utilities to work with EDB Postgres Advanced Server in a familiar environment.
+
+These compatible tools and utilities that are supported by EDB Postgres Advanced Server:
+
+-   [EDB\*Loader](../../database_administration/02_edb_loader/)
+-   [EDB\*Wrap](../../epas_security_guide/03_edb_wrap/)
+-   [Dynamic Runtime Instrumentation](../../managing_performance/04_dynamic_runtime_instrumentation_tools_architecture_DRITA/)
+
+The EDB\*Plus command line client provides a user interface to EDB Postgres Advanced Server that supports SQL\*Plus commands; EDB\*Plus allows you to:
+
+-   Query database objects
+-   Execute stored procedures
+-   Format output from SQL commands
+-   Execute batch scripts
+-   Execute OS commands
+-   Record output
+
+See [EDB\*Plus](/edb_plus/latest/) for detailed installation and usage information about EDB\*Plus.
diff --git a/product_docs/docs/epas/16/tools_utilities_and_components/index.mdx b/product_docs/docs/epas/16/tools_utilities_and_components/index.mdx
new file mode 100644
index 00000000000..2a1f075ff35
--- /dev/null
+++ b/product_docs/docs/epas/16/tools_utilities_and_components/index.mdx
@@ -0,0 +1,6 @@
+---
+title: "Tools, utilities, and components"
+indexCards: simple
+---
+
+Various tools and utilities are available with EDB Postgres Advanced Server.
diff --git a/product_docs/docs/epas/16/upgrading/index.mdx b/product_docs/docs/epas/16/upgrading/index.mdx
new file mode 100644
index 00000000000..1b3c895d2ec
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/index.mdx
@@ -0,0 +1,13 @@
+---
+navTitle: Upgrading
+title: "EDB Postgres Advanced Server upgrade"
+indexCards: simple
+redirects:
+- /epas/latest/epas_upgrade_guide/
+---
+
+Upgrading an EDB Postgres Advanced Server installation varies depending on whether you want to perform a major or minor version upgrade. 
+
+-   Use pg_upgrade to perform upgrades between major versions of EDB Postgres Advanced Server. 
+-   Use DNF, apt-get, or StackBuilder Plus to perform upgrades between minor versions of EDB Postgres Advanced Server. The method you use depends on the underlying operating system. 
+
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
new file mode 100644
index 00000000000..9e8ac90e11c
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/01_linking_versus_copying.mdx
@@ -0,0 +1,15 @@
+---
+title: "Linking versus copying"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/01_linking_versus_copying/
+---
+
+<div id="linking_versus_copying" class="registered_link"></div>
+
+When invoking `pg_upgrade`, you can use a command-line option to specify whether to copy or link each table and index in the old cluster to the new cluster.
+
+Linking is much faster because `pg_upgrade` creates a second name (a hard link) for each file in the cluster. Linking also requires no extra workspace because `pg_upgrade` doesn't make a copy of the original data. When linking the old cluster and the new cluster, the old and new clusters share the data. After starting the new cluster, you can no longer use your data with the previous version of EDB Postgres Advanced Server.
+
+If you choose to copy data from the old cluster to the new cluster, `pg_upgrade` still reduces the time required to perform an upgrade compared to the traditional `dump/restore` procedure. `pg_upgrade` uses a file-at-a-time mechanism to copy data files from the old cluster to the new cluster versus the row-by-row mechanism used by `dump/restore`. When you use `pg_upgrade`, you avoid building indexes in the new cluster. Each index is instead copied from the old cluster to the new cluster. Finally, using a `dump/restore` procedure to upgrade requires a lot of workspace to hold the intermediate text-based dump of all of your data, while `pg_upgrade` requires very little extra workspace.
+
+Data that's stored in user-defined tablespaces isn't copied to the new cluster. It stays in the same location in the file system but is copied into a subdirectory whose name shows the version number of the new cluster. To manually relocate files that are stored in a tablespace after upgrading, move the files to the new location and update the symbolic links to point to the files. The symbolic links are located in the `pg_tblspc` directory under your cluster's `data` directory.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx
new file mode 100644
index 00000000000..d34de70e7a0
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/01_performing_an_upgrade/index.mdx
@@ -0,0 +1,38 @@
+---
+title: "Performing an upgrade"
+description: "Describes how to upgrade an earlier version of EDB Postgres Advanced Server to the current version."
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade/
+- /epas/latest/upgrading/04_upgrading_an_installation_with_pg_upgrade/01_performing_an_upgrade
+---
+
+To upgrade an earlier version of EDB Postgres Advanced Server to the current version:
+
+1.   Install the current version of EDB Postgres Advanced Server. The new installation must contain the same supporting server components as the old installation.
+1.   Empty the target database or create a new target cluster with `initdb`.
+1.   To avoid authentication conflicts, place the `pg_hba.conf` file for both databases in `trust` authentication mode.
+1.   Shut down the old and new EDB Postgres Advanced Server services.
+1.   Invoke the `pg_upgrade` utility.
+
+When `pg_upgrade` starts, it performs a compatibility check to ensure that all required executables are present and contain the expected version numbers. The verification process also checks the old and new `$PGDATA` directories to ensure that the expected files and subdirectories are in place. If the verification process succeeds, `pg_upgrade` starts the old `postmaster` and runs `pg_dumpall --schema-only` to capture the metadata contained in the old cluster. The script produced by `pg_dumpall` is used in later to re-create all user-defined objects in the new cluster.
+
+The script produced by `pg_dumpall` re-creates only user-defined objects and not system-defined objects. The new cluster already contains the system-defined objects created by the latest version of EDB Postgres Advanced Server.
+
+After extracting the metadata from the old cluster, `pg_upgrade` performs the bookkeeping tasks required to sync the new cluster with the existing data.
+
+`pg_upgrade` runs the `pg_dumpall` script against the new cluster to create empty database objects of the same shape and type as those found in the old cluster. Then, `pg_upgrade` links or copies each table and index from the old cluster to the new cluster.
+
+If you're upgrading to EDB Postgres Advanced Server and installed the `edb_dblink_oci` or `edb_dblink_libpq` extension, drop the extension before performing an upgrade. To drop the extension, connect to the server with the psql or PEM client, and invoke the commands:
+
+```sql
+DROP EXTENSION edb_dblink_oci;
+DROP EXTENSION edb_dblink_libpq;
+```
+
+When you finish upgrading, you can use the `CREATE EXTENSION` command to add the current versions of the extensions to your installation.
+
+<div class="toctree" maxdepth="3">
+
+linking_versus_copying
+
+</div>
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
new file mode 100644
index 00000000000..adb0e2d782a
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference.mdx
@@ -0,0 +1,93 @@
+---
+title: "Command line options for pg_upgrade"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/01_command_line_options_reference/
+---
+
+`pg_upgrade` accepts the following command line options. Each option is available in a long form or a short form:
+
+`-b path_to_old_bin_directory`  
+`--old-bindir path_to_old_bin_directory`
+
+Use the `-b` or `--old-bindir` keyword to specify the location of the old cluster's executable directory.
+
+`-B path_to_new_bin_directory`  
+`--new-bindir path_to_new_bin_directory`
+
+Use the `-B` or `--new-bindir` keyword to specify the location of the new cluster's executable directory.
+
+`-c`  
+`--check`
+
+Include the `-c` or `--check` keyword to specify for `pg_upgrade` to perform a consistency check on the old and new cluster without performing a version upgrade.
+
+`-d path_to_old_data_directory`  
+`--old-datadir path_to_old_data_directory`
+
+Use the `-d` or `--old-datadir` keyword to specify the location of the old cluster's `data` directory.
+
+`-D path_to_new_data_directory`  
+`--new-datadir path_to_new_data_directory`
+
+Use the `-D` or `--new-datadir` keyword to specify the location of the new cluster's `data` directory.
+
+Data that's stored in user-defined tablespaces isn't copied to the new cluster. It stays in the same location in the file system but is copied into a subdirectory whose name reflects the version number of the new cluster. To manually relocate files that are stored in a tablespace after upgrading, you must move the files to the new location and update the symbolic links (located in the `pg_tblspc` directory under your cluster's `data` directory) to point to the files.
+
+`-j`  
+`--jobs`
+
+Include the `-j` or `--jobs` keyword to specify the number of simultaneous processes or threads to use during the upgrade.
+
+`-k`  
+`--link`
+
+Include the `-k` or `--link` keyword to create a hard link from the new cluster to the old cluster. See [Linking versus copying](../01_performing_an_upgrade/01_linking_versus_copying/#linking_versus_copying) for more information about using a symbolic link.
+
+`-o options`  
+`--old-options options`
+
+Use the `-o` or `--old-options` keyword to specify options to pass to the old `postgres` command. Enclose options in single or double quotes to ensure that they're passed as a group.
+
+`-O options`  
+`--new-options options`
+
+Use the `-O` or `--new-options` keyword to specify options to pass to the new `postgres` command. Enclose options in single or double quotes to ensure that they're passed as a group.
+
+`-p old_port_number`  
+`--old-port old_port_number`
+
+Include the `-p` or `--old-port` keyword to specify the port number of the EDB Postgres Advanced Server installation that you're upgrading.
+
+`-P new_port_number`  
+`--new-port new_port_number`
+
+Include the `-P` or `--new-port` keyword to specify the port number of the new EDB Postgres Advanced Server installation.
+
+!!! Note
+    If the original EDB Postgres Advanced Server installation is using port number `5444` when you invoke the EDB Postgres Advanced Server installer, the installer recommends using listener port `5445` for the new installation of EDB Postgres Advanced Server.
+
+`-r`  
+`--retain`
+
+During the upgrade process, `pg_upgrade` creates four append-only log files. When the upgrade is completed, `pg_upgrade` deletes these files. Include the `-r` or `--retain` option to retain the `pg_upgrade` log files.
+
+`-U user_name`  
+`--username user_name`
+
+Include the `-U` or `--username` keyword to specify the name of the EDB Postgres Advanced Server database superuser. The same superuser must exist in both clusters.
+
+`-v`  
+`--verbose`
+
+Include the `-v` or `--verbose` keyword to enable verbose output during the upgrade process.
+
+`-V`  
+`--version`
+
+Use the `-V` or `--version` keyword to display version information for `pg_upgrade`.
+
+`-?`  
+`-h`  
+`--help`
+
+Use `-?`, `-h,` or `--help` options to display `pg_upgrade` help information.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx
new file mode 100644
index 00000000000..7911fdb92b4
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/02_invoking_pg_upgrade/index.mdx
@@ -0,0 +1,56 @@
+---
+title: "Invoking pg_upgrade"
+description: "Describes how to invoke the pg_upgrade utility"
+redirects: 
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/02_invoking_pg_upgrade/
+---
+
+When invoking `pg_upgrade`, you must specify the location of the old and new cluster's `PGDATA` and executable (`/bin`) directories, the name of the EDB Postgres Advanced Server superuser, and the ports on which the installations are listening. A typical call to invoke `pg_upgrade` to migrate from EDB Postgres Advanced Server 15 to EDB Postgres Advanced Server 16 takes the form:
+
+```shell
+pg_upgrade
+--old-datadir <path_to_15_data_directory>
+--new-datadir <path_to_16_data_directory>
+--user <superuser_name>
+--old-bindir <path_to_15_bin_directory>
+--new-bindir <path_to_16_bin_directory>
+--old-port <15_port> --new-port <15_port>
+```
+
+Where:
+
+`--old-datadir path_to_15_data_directory`
+
+Use the `--old-datadir` option to specify the complete path to the `data` directory in the EDB Postgres Advanced Server 15 installation.
+
+`--new-datadir path_to_16_data_directory`
+
+Use the `--new-datadir` option to specify the complete path to the `data` directory in the EDB Postgres Advanced Server 16 installation.
+
+`--username superuser_name`
+
+Include the `--username` option to specify the name of the EDB Postgres Advanced Server superuser. The superuser name must be the same in both versions of EDB Postgres Advanced Server. By default, when EDB Postgres Advanced Server is installed in Oracle mode, the superuser is named `enterprisedb`. If installed in PostgreSQL mode, the superuser is named `postgres`.
+
+If the EDB Postgres Advanced Server superuser name isn't the same in both clusters, the clusters won't pass the `pg_upgrade` consistency check.
+
+`--old-bindir path_to_15_bin_directory`
+
+Use the `--old-bindir` option to specify the complete path to the `bin` directory in the EDB Postgres Advanced Server 15 installation.
+
+`--new-bindir path_to_16_bin_directory`
+
+Use the `--new-bindir` option to specify the complete path to the `bin` directory in the EDB Postgres Advanced Server 16 installation.
+
+`--old-port 15_port`
+
+Include the `--old-port` option to specify the port on which EDB Postgres Advanced Server 15 listens for connections.
+
+`--new-port 16_port`
+
+Include the `--new-port` option to specify the port on which EDB Postgres Advanced Server 16 listens for connections.
+
+<div class="toctree" maxdepth="3">
+
+command_line_options_reference
+
+</div>
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx
new file mode 100644
index 00000000000..9a6223105da
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/03_limitations.mdx
@@ -0,0 +1,25 @@
+---
+title: "Upgrade considerations"
+description: "Outlines the requirements and limitations to review prior to upgrading"
+redirects:
+- /epas/latest/epas_upgrade_guide/03_limitations/
+---
+
+The `pg_upgrade` executable is distributed with EDB Postgres Advanced Server and is installed as part of the Database Server component. You don't need to further install or configure it. The `pg_upgrade` utility performs an in-place transfer of existing data between EDB Postgres Advanced Server and any later version.
+
+Several factors determine if an in-place upgrade is practical:
+
+-   The on-disk representation of user-defined tables must not change between the original version and the upgraded version.
+-   The on-disk representation of data types must not change between the original version and the upgraded version.
+-   To upgrade between major versions of EDB Postgres Advanced Server with `pg_upgrade`, both versions must share a common binary representation for each data type. Therefore, you can't use `pg_upgrade` to migrate from a 32-bit to a 64-bit Linux platform.
+
+Before performing a version upgrade, `pg_upgrade` verifies that the old cluster and the new cluster are compatible.
+
+If the upgrade involves a change in the on-disk representation of database objects or data, or if it involves a change in the binary representation of data types, `pg_upgrade` can't perform the upgrade. To upgrade, you have to `pg_dump` the old data and then import that data to the new cluster, as described below.
+
+1.  Export all of your data using `pg_dump`. 
+1.  Install the new release. 
+1.  Run `initdb` to create a new cluster. 
+1.  Import your old data.
+
+If you're using an ODBC, JDBC, OCI, or .NET driver to connect to your database applications and upgrading to a new major version of EDB Postgres Advanced Server, upgrade your driver to the latest version when upgrading EDB Postgres Advanced Server.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx
new file mode 100644
index 00000000000..f28041ca8c1
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/03_upgrading_to_advanced_server.mdx
@@ -0,0 +1,292 @@
+---
+title: "Upgrading to EDB Postgres Advanced Server"
+description: "Describes how to upgrade into a cluster"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/03_upgrading_to_advanced_server/
+---
+
+You can use `pg_upgrade` to upgrade from an existing installation of EDB Postgres Advanced Server into the cluster built by the EDB Postgres Advanced Server installer or into an alternative cluster created using the `initdb` command. 
+
+The basic steps to perform an upgrade into an empty cluster created with the `initdb` command are the same as the steps to upgrade into the cluster created by the EDB Postgres Advanced Server installer. However, you can omit Step 2 - Empty the edb database and substitute the location of the alternative cluster when specifying a target cluster for the upgrade.
+
+If a problem occurs during the upgrade process, you can revert to the previous version. See [Reverting to the old cluster](06_reverting_to_the_old_cluster/#reverting_to_the_old_cluster) for detailed information about this process.
+
+You must be an operating system superuser or Windows Administrator to perform an EDB Postgres Advanced Server upgrade.
+
+## Step 1 - Install the new server
+
+Install the new version of EDB Postgres Advanced Server, specifying the same non-server components that were installed during the previous EDB Postgres Advanced Server installation. The new cluster and the old cluster must reside in different directories.
+
+## Step 2 - Empty the target database
+
+The target cluster must not contain any data. You can create an empty cluster using the `initdb` command, or you can empty a database that was created during the installation of EDB Postgres Advanced Server. If you installed EDB Postgres Advanced Server in PostgreSQL mode, the installer creates a single database named `postgres`. Installing EDB Postgres Advanced Server in Oracle mode creates a database named `postgres` and a database named `edb`.
+
+The easiest way to empty the target database is to drop the database and then create a new database. Before invoking the `DROP DATABASE` command, you must disconnect any users and halt any services that are currently using the database.
+
+On Windows, from the Control Panel, go to the Services manager. Select each service in the **Services** list, and select **Stop**.
+
+On Linux, open a terminal window, assume superuser privileges, and manually stop each service. For example, invoke the following command to stop the pgAgent service:
+
+```shell
+service edb-pgagent-16 stop
+```
+
+After stopping any services that are currently connected to EDB Postgres Advanced Server, you can use the EDB-PSQL command line client to drop and create a database. When the client opens, connect to the `template1` database as the database superuser. If prompted, provide authentication information. Then, use the following command to drop your database:
+
+```sql
+DROP DATABASE <database_name>;
+```
+
+Where `database_name` is the name of the database.
+
+Then, create an empty database based on the contents of the `template1` database.
+
+```sql
+CREATE DATABASE <database_name>;
+```
+
+## Step 3 - Set both servers in trust mode
+
+During the upgrade process, `pg_upgrade` connects to the old and new servers several times. To make the connection process easier, you can edit the `pg_hba.conf` file, setting the authentication mode to `trust`. To modify the `pg_hba.conf` file, from the Start menu, select **EDB Postgres > EDB Postgres Advanced Server > Expert Configuration**. Select **Edit pg_hba.conf** to open the `pg_hba.conf` file.
+
+You must allow trust authentication for the previous EDB Postgres Advanced Server installation and EDB Postgres Advanced Server servers. Edit the `pg_hba.conf` file for both installations of EDB Postgres Advanced Server as shown in the figure.
+
+![Configuring EDB Postgres Advanced Server to use trust authentication.](../../images/configuring_advanced_server_to_use_trust_authentication.png)
+
+After editing each file, save the file and exit the editor.
+
+If the system is required to maintain `md5` authentication mode during the upgrade process, you can specify user passwords for the database superuser in a password file (`pgpass.conf` on Windows, `.pgpass` on Linux). For more information about configuring a password file, see the [PostgreSQL core documentation](https://www.postgresql.org/docs/current/static/libpq-pgpass.html).
+
+## Step 4 - Stop all component services and servers
+
+Before you invoke `pg_upgrade`, you must stop any services that belong to the original EDB Postgres Advanced Server installation, EDB Postgres Advanced Server, or the supporting components. Stopping these services ensures that a service doesn't attempt to access either cluster during the upgrade process.
+
+The services in the table are most likely to be running in your installation.
+
+
+| Service                                        | On Linux                               | On Windows                                                 |
+| ---------------------------------------------- | -------------------------------------- | ---------------------------------------------------------- |
+| EnterprisEDB Postgres Advanced Server 9.6      | edb-as-9.6                             | edb-as-9.6                                                 |
+| EnterprisEDB Postgres Advanced Server 10       | edb-as-10                              | edb-as-10                                                  |
+| EnterprisEDB Postgres Advanced Server 11       | edb-as-11                              | edb-as-11                                                  |
+| EnterprisEDB Postgres Advanced Server 12       | edb-as-12                              | edb-as-12                                                  |
+| EnterprisEDB Postgres Advanced Server 13       | edb-as-13                              | edb-as-13                                                  |
+| EnterprisEDB Postgres Advanced Server 14       | edb-as-14                              | edb-as-14                                                  |
+| EnterprisEDB Postgres Advanced Server 15       | edb-as-15                              | edb-as-15                                                  |
+| EnterprisEDB Postgres Advanced Server 16       | edb-as-16                              | edb-as-16                                                  |
+| EDB Postgres Advanced Server 9.6 Scheduling Agent (pgAgent) | edb-pgagent-9.6                        | EnterprisEDB Postgres Advanced Server 9.6 Scheduling Agent |
+| Infinite Cache 9.6                             | edb-icache                             | N/A                                                        |
+| Infinite Cache 10                              | edb-icache                             | N/A                                                        |
+| PgBouncer                                      | Pgbouncer                              | Pgbouncer                                                  |
+| PgBouncer 1.21                                 | edb-pgbouncer-1.21                     | edb-pgbouncer-1.21                                          |
+| PgPool                                         | ppas-pgpool                            | N/A                                                        |
+| PgPool 3.4                                     | ppas-pgpool-3.4 or ppas-pgpool34       | N/A                                                        |
+| pgPool-II                                      | edb-pgpool-4.4                            | N/A                                                        |
+| Slony 9.6                                      | edb-slony-replication-9.6              | edb-slony-replication-9.6                                  |
+| xDB Publication Server 9.0                     | edb-xdbpubserver-90                    | Publication Service 90                                     |
+| xDB Publication Server 9.1                     | edb-xdbpubserver-91                    | Publication Service 91                                     |
+| xDB Subscription Server                        | edb-xdbsubserver-90                    | Subscription Service 90                                    |
+| xDB Subscription Server                        | edb-xdbsubserver-91                    | Subscription Service 91                                    |
+| EDB Replication Server v6.x                    | edb-xdbpubserver                       | Publication Service for xDB Replication Server             |
+| EDB Subscription Server v6.x                   | edb-xdbsubserver                       | Subscription Service for xDB Replication Server            |
+
+### To stop a service on Windows
+
+Open the Services applet. Select each EDB Postgres Advanced Server or supporting component service displayed in the list, and select **Stop**.
+
+### To stop a service on Linux
+
+Open a terminal window and manually stop each service at the command line.
+
+## Step 5 for Linux only - Assume the identity of the cluster owner
+
+If you're using Linux, assume the identity of the EDB Postgres Advanced Server cluster owner. This example assumes EDB Postgres Advanced Server was installed in the default, compatibility-with-Oracle database mode, assigning `enterprisedb` as the cluster owner. (If installed in compatibility-with-PostgreSQL database mode, `postgres` is the cluster owner.)
+
+```shell
+su - enterprisedb
+```
+
+If prompted, enter the EDB Postgres Advanced Server cluster owner password. Then, set the path to include the location of the `pg_upgrade` executable:
+
+```shell
+export PATH=$PATH:/usr/edb/as16/bin
+```
+
+During the upgrade process, `pg_upgrade` writes a file to the current working directory of the `enterprisedb` user. You must invoke `pg_upgrade` from a directory where the `enterprisedb` user has write privileges. After performing the previous commands, navigate to a directory in which the `enterprisedb` user has sufficient privileges to write a file.
+
+```shell
+cd /tmp
+```
+
+## Step 5 for Windows only - Assume the identity of the cluster owner
+
+If you're using Windows, open a terminal window, assume the identity of the EDB Postgres Advanced Server cluster owner, and set the path to the `pg_upgrade` executable.
+
+If the `--serviceaccount service_account_user` parameter was specified during the initial installation of EDB Postgres Advanced Server, then `service_account_user` is the EDB Postgres Advanced Server cluster owner. In that case, give this user with the `RUNAS` command:
+
+```sql
+RUNAS /USER:service_account_user "CMD.EXE"
+SET PATH=%PATH%;C:\Program Files\edb\as16\bin
+```
+
+During the upgrade process, `pg_upgrade` writes a file to the current working directory of the service account user. You must invoke `pg_upgrade` from a directory where the service account user has write privileges. After performing the previous commands, navigate to a directory in which the service account user has privileges to write a file:
+
+```shell
+cd %TEMP%
+```
+
+If you omitted the `--serviceaccount` parameter during the initial installation of EDB Postgres Advanced Server, then the default owner of the EDB Postgres Advanced Server service and the database cluster is `NT AUTHORITY\NetworkService`.
+
+When `NT AUTHORITY\NetworkService` is the service account user, the `RUNAS` command might not be usable. It prompts for a password, and the `NT AUTHORITY\NetworkService` account isn't assigned a password. Thus, there's typically a failure with an error message such as “Unable to acquire user password.”
+
+Under this circumstance, you must use the Windows utility program `PsExec` to run `CMD.EXE` as the service account `NT AUTHORITY\NetworkService`.
+
+Obtain the `PsExec` program by downloading `PsTools`, which is available at the [Microsoft site](https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx).
+
+You can then use the following command to run `CMD.EXE` as `NT AUTHORITY\NetworkService`. Then set the path to the `pg_upgrade` executable:
+
+```shell
+psexec.exe -u "NT AUTHORITY\NetworkService" CMD.EXE
+SET PATH=%PATH%;C:\Program Files\edb\as16\bin
+```
+
+During the upgrade process, `pg_upgrade` writes a file to the current working directory of the service account user. You must invoke `pg_upgrade` from a directory where the service account user has write privileges. After performing the previous commands, navigate to a directory in which the service account user has privileges to write a file:
+
+```shell
+cd %TEMP%
+```
+
+## Step 6 - Perform a consistency check
+
+Before attempting an upgrade, perform a consistency check to ensure that the old and new clusters are compatible and properly configured. Include the `--check` option to instruct `pg_upgrade` to perform the consistency check.
+
+This example shows invoking `pg_upgrade` to perform a consistency check on Linux:
+
+```shell
+pg_upgrade -d /var/lib/edb/as15/data
+-D /var/lib/edb/as16/data -U enterprisedb
+-b /usr/edb/as15/bin -B /usr/edb/as16/bin -p 5444 -P 5445 --check
+```
+
+If the command is successful, it returns `*Clusters are compatible*`.
+
+If you're using Windows, quote any directory names that contain a space:
+
+```shell
+pg_upgrade.exe
+-d "C:\Program Files\ PostgresPlus\15AS\data"
+-D "C:\Program Files\edb\as16\data" -U enterprisedb
+-b "C:\Program Files\PostgresPlus\15AS\bin"
+-B "C:\Program Files\edb\as16\bin" -p 5444 -P 5445 --check
+```
+
+During the consistency checking process, `pg_upgrade` logs any discrepancies that it finds to a file located in the directory from which you invoked `pg_upgrade`. When the consistency check completes, review the file to identify any missing components or upgrade conflicts. Resolve any conflicts before invoking `pg_upgrade` to perform a version upgrade.
+
+If `pg_upgrade` alerts you to a missing component, you can use StackBuilder Plus to add the component that contains the component. Before using StackBuilder Plus, restart the EDB Postgres Advanced Server service. Then, open StackBuilder Plus by selecting from the Start menu **EDB Postgres Advanced Server *version* > StackBuilder Plus**. Follow the onscreen advice of the StackBuilder Plus wizard to download and install the missing components.
+
+After `pg_upgrade` confirms that the clusters are compatible, you can perform a version upgrade.
+
+## Step 7 - Run pg_upgrade
+
+After confirming that the clusters are compatible, you can invoke `pg_upgrade` to upgrade the old cluster to the new version of EDB Postgres Advanced Server.
+
+On Linux:
+
+```shell
+pg_upgrade -d /var/lib/edb/as15/data
+-D /var/lib/edb/as16/data -U enterprisedb
+-b /usr/edb/as15/bin -B /usr/edb/as16/bin -p 5444 -P 5445
+```
+
+On Windows:
+
+```shell
+pg_upgrade.exe -d "C:\Program Files\PostgresPlus\15AS\data"
+-D "C:\Program Files\edb\as16\data" -U enterprisedb
+-b "C:\Program Files\PostgresPlus\15AS\bin"
+-B "C:\Program Files\edb\as16\bin" -p 5444 -P 5445
+```
+
+`pg_upgrade` displays the progress of the upgrade onscreen:
+
+```shell
+$ pg_upgrade -d /var/lib/edb/as15/data -D /var/lib/edb/as16/data -U
+enterprisedb -b /usr/edb/as15/bin -B /usr/edb/as16/bin -p 5444 -P 5445
+Performing Consistency Checks
+-----------------------------
+Checking current, bin, and data directories            ok
+Checking cluster versions                              ok
+Checking database user is a superuser                  ok
+Checking for prepared transactions                     ok
+Checking for reg* system OID user data types           ok
+Checking for contrib/isn with bigint-passing mismatch  ok
+Creating catalog dump                                  ok
+Checking for presence of required libraries            ok
+Checking database user is a superuser                  ok
+Checking for prepared transactions                     ok
+
+```
+
+If `pg_upgrade` fails after this point, you must re-initdb the new cluster before continuing. Otherwise, it continues as follows:
+
+```shell
+Performing Upgrade
+------------------
+Analyzing all rows in the new cluster                  ok
+Freezing all rows on the new cluster                   ok
+Deleting files from new pg_clog                        ok
+Copying old pg_clog to new server                      ok
+Setting next transaction ID for new cluster            ok
+Resetting WAL archives                                 ok
+Setting frozenxid counters in new cluster              ok
+Creating databases in the new cluster                  ok
+Adding support functions to new cluster                ok
+Restoring database schema to new cluster               ok
+Removing support functions from new cluster            ok
+Copying user relation files                            ok
+
+Setting next OID for new cluster                       ok
+Creating script to analyze new cluster                 ok
+Creating script to delete old cluster                  ok
+
+Upgrade Complete
+----------------
+Optimizer statistics are not transferred by pg_upgrade so,
+once you start the new server, consider running:
+    analyze_new_cluster.sh
+
+Running this script will delete the old cluster's data files:
+    delete_old_cluster.sh
+```
+
+While `pg_upgrade` runs, it might generate SQL scripts that handle special circumstances that it encountered during your upgrade. For example, if the old cluster contains large objects, you might need to invoke a script that defines the default permissions for the objects in the new cluster. When performing the pre-upgrade consistency check, `pg_upgrade` alerts you to any script that you might need to run manually.
+
+You must invoke the scripts after `pg_upgrade` completes. To invoke the scripts, connect to the new cluster as a database superuser with the EDB-PSQL command-line client, and invoke each script using the `\i` option:
+
+```shell
+\i complete_path_to_script/script.sql
+```
+
+It's generally unsafe to access tables referenced in rebuild scripts until the rebuild scripts finish. Accessing the tables might yield incorrect results or poor performance. You can access tables not referenced in rebuild scripts immediately.
+
+If `pg_upgrade` fails to complete the upgrade process, the old cluster is unchanged except that `$PGDATA/global/pg_control` is renamed to `pg_control.old` and each tablespace is renamed to `tablespace.old`. To revert to the pre-invocation state:
+
+1.  Delete any tablespace directories created by the new cluster.
+2.  Rename `$PGDATA/global/pg_control`, removing the `.old` suffix.
+3.  Rename the old cluster tablespace directory names, removing the `.old` suffix.
+4.  Remove any database objects from the new cluster that were moved before the upgrade failed.
+
+Then, resolve any upgrade conflicts encountered and try the upgrade again.
+
+When the upgrade is complete, `pg_upgrade` might also recommend vacuuming the new cluster. It provides a script that allows you to delete the old cluster.
+
+!!! Note
+    In case you need to revert to a previous version, before removing the old cluster, make sure that you have a backup of the cluster and that the cluster was upgraded.
+
+## Step 8 - Restore the authentication settings in the pg_hba.conf file
+
+If you modified the `pg_hba.conf` file to permit `trust` authentication, update the contents of the `pg_hba.conf` file to reflect your preferred authentication settings.
+
+## Step 9 - Move and identify user-defined tablespaces (optional)
+
+If you have data stored in a user-defined tablespace, you must manually relocate tablespace files after upgrading. Move the files to the new location, and update the symbolic links to point to the files. The symbolic links are located in the `pg_tblspc` directory under your cluster's `data` directory.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx
new file mode 100644
index 00000000000..04f08483afb
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/04_upgrading_a_pgAgent_installation.mdx
@@ -0,0 +1,13 @@
+---
+title: "Upgrading a pgAgent installation"
+description: "Describes how to use the script provided with the EDB Postgres Advanced Server installer to update pgAgent"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/04_upgrading_a_pgAgent_installation/
+---
+
+If your existing EDB Postgres Advanced Server installation uses pgAgent, you can use a script provided with the EDB Postgres Advanced Server installer to update pgAgent. The script is named `dbms_job.upgrade.script.sql` and is located in the `/share/contrib/` directory under your EDB Postgres Advanced Server installation.
+
+If you're using `pg_upgrade` to upgrade your installation:
+
+1.  Perform the upgrade.
+2.  Invoke the `dbms_job.upgrade.script.sql` script to update the catalog files. If your existing pgAgent installation was performed with a script, the update converts the installation to an extension.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx
new file mode 100644
index 00000000000..bc0848f006c
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/05_pg_upgrade_troubleshooting.mdx
@@ -0,0 +1,34 @@
+---
+title: "Troubleshooting pg_upgrade"
+description: "Provides tips for problems you might encounter during upgrade"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/05_pg_upgrade_troubleshooting/
+---
+
+These troubleshooting tips address problems you might encounter when using `pg_upgrade`.
+
+## Upgrade Error - There seems to be a postmaster servicing the cluster
+
+If `pg_upgrade` reports that a postmaster is servicing the cluster, stop all EDB Postgres Advanced Server services and try the upgrade again.
+
+## Upgrade Error - fe_sendauth: no password supplied
+
+If `pg_upgrade` reports an authentication error that references a missing password, modify the `pg_hba.conf` files in the old and new cluster to enable `trust` authentication, or configure the system to use a `pgpass.conf` file.
+
+## Upgrade Error - New cluster is not empty; exiting
+
+If `pg_upgrade` reports that the new cluster isn't empty, empty the new cluster. The target cluster might not contain any user-defined databases.
+
+## Upgrade Error - Failed to load library
+
+If the original EDB Postgres Advanced Server cluster included libraries that aren't included in the EDB Postgres Advanced Server cluster, `pg_upgrade` alerts you to the missing component during the consistency check by writing an entry to the `loadable_libraries.txt` file in the directory from which you invoked `pg_upgrade`. Generally, for missing libraries that aren't part of a major component upgrade:
+
+1.  Restart the EDB Postgres Advanced Server service.
+
+2.  Use StackBuilder Plus to download and install the missing module. 
+
+3.  Stop the EDB Postgres Advanced Server service.
+
+4.  Resume the upgrade process. Invoke `pg_upgrade` to perform consistency checking.
+
+4.  After you resolve any remaining problems noted in the consistency checks, invoke `pg_upgrade` to perform the data migration from the old cluster to the new cluster.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx
new file mode 100644
index 00000000000..9b4fa3ec285
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/06_reverting_to_the_old_cluster.mdx
@@ -0,0 +1,15 @@
+---
+title: "Reverting to the old cluster"
+description: "Describes the various method you can use to revert to a previous cluster"
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/06_reverting_to_the_old_cluster/
+---
+
+<div id="reverting_to_the_old_cluster" class="registered_link"></div>
+
+The method you use to revert to a previous cluster varies with the options specified when invoking `pg_upgrade`:
+
+-   If you specified the `--check` option when invoking `pg_upgrade`, an upgrade wasn't performed and no modifications were made to the old cluster. You can reuse the old cluster at any time.
+-   If you included the `--link` option when invoking `pg_upgrade`, the data files are shared between the old and new cluster after the upgrade completes. If you started the server that's servicing the new cluster, the new server wrote to those shared files, and it's unsafe to use the old cluster.
+-   If you ran `pg_upgrade` without the `--link` specification or haven't started the new server, the old cluster is unchanged except that the `.old` suffix was appended to the `$PGDATA/global/pg_control` and tablespace directories.
+-   To reuse the old cluster, delete the tablespace directories created by the new cluster. Remove the `.old` suffix from `$PGDATA/global/pg_control` and the old cluster tablespace directory names. Restart the server that services the old cluster.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx
new file mode 100644
index 00000000000..0e770a29418
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/how_pg_upgrade_works.mdx
@@ -0,0 +1,30 @@
+---
+title: "About pg_upgrade"
+description: "Describes how the upgrade utility works"
+---
+
+The `pg_upgrade` executable is distributed with EDB Postgres Advanced Server and is installed as part of the Database Server component. You don't need to further install or configure it.
+
+The `pg_upgrade` utility performs an in-place transfer of existing data between EDB Postgres Advanced Server and any later version.
+
+Before performing a version upgrade, `pg_upgrade` verifies that the old cluster and the new cluster are compatible.
+
+When `pg_upgrade` starts, it performs a compatibility check to ensure that all required executables are present and contain the expected version numbers. The verification process also checks the old and new `$PGDATA` directories to ensure that the expected files and subdirectories are in place. If the verification process succeeds, `pg_upgrade` starts the old `postmaster` and runs `pg_dumpall --schema-only` to capture the metadata contained in the old cluster. The script produced by `pg_dumpall` is used in later to re-create all user-defined objects in the new cluster.
+
+The script produced by `pg_dumpall` re-creates only user-defined objects and not system-defined objects. The new cluster already contains the system-defined objects created by the latest version of EDB Postgres Advanced Server.
+
+After extracting the metadata from the old cluster, `pg_upgrade` performs the bookkeeping tasks required to sync the new cluster with the existing data.
+
+`pg_upgrade` runs the `pg_dumpall` script against the new cluster to create empty database objects of the same shape and type as those found in the old cluster. Then, `pg_upgrade` links or copies each table and index from the old cluster to the new cluster.
+
+If you're upgrading to EDB Postgres Advanced Server and installed the `edb_dblink_oci` or `edb_dblink_libpq` extension, drop the extension before performing an upgrade. To drop the extension, connect to the server with the psql or PEM client, and invoke the commands:
+
+```sql
+DROP EXTENSION edb_dblink_oci;
+DROP EXTENSION edb_dblink_libpq;
+```
+
+When you finish upgrading, you can use the `CREATE EXTENSION` command to add the current versions of the extensions to your installation.
+
+!!! Note
+    If the upgrade involves a change in the on-disk representation of database objects or data, or if it involves a change in the binary representation of data types, `pg_upgrade` can't perform the upgrade. To upgrade, you have to `pg_dump` the old data and then import that data to the new cluster.
diff --git a/product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx
new file mode 100644
index 00000000000..8875082a540
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/major_upgrade/index.mdx
@@ -0,0 +1,32 @@
+---
+title: "Major version upgrade with pg_upgrade"
+description: "Describes using pg_upgrade to migrate from an earlier major version of EDB Postgres Advanced Server to the most recent version."
+indexCards: simple
+navigation:
+- 03_limitations
+- how_pg_upgrade_works
+- 01_performing_an_upgrade
+- 02_invoking_pg_upgrade
+- 03_upgrading_to_advanced_server
+- 04_upgrading_a_pgAgent_installation
+- 05_pg_upgrade_troubleshooting
+- 06_reverting_to_the_old_cluster
+redirects:
+- /epas/latest/epas_upgrade_guide/04_upgrading_an_installation_with_pg_upgrade/
+- /epas/latest/upgrading/04_upgrading_an_installation_with_pg_upgrade
+---
+
+<div id="upgrading_an_installation_with_pg_upgrade" class="registered_link"></div>
+
+!!! Note
+    Review the [upgrade considerations](03_limitations) prior to performing an upgrade with the `pg_upgrade` utility.
+
+While minor upgrades between versions are fairly simple and require only installing new executables, past major version upgrades were both expensive and time consuming. `pg_upgrade` eases migration between any version of EDB Postgres Advanced Server (version 9.0 or later) and any later release of EDB Postgres Advanced Server that's supported on the same platform.
+
+Using `pg_upgrade` can reduce both the amount of time and the disk space required for many major-version upgrades.
+
+<div class="toctree" maxdepth="3">
+
+performing_an_upgrade invoking_pg_upgrade upgrading_to_advanced_server upgrading_a_pgAgent_installation pg_upgrade_troubleshooting reverting_to_the_old_cluster
+
+</div>
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
new file mode 100644
index 00000000000..714a7204f5b
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/minor_upgrade/05_performing_a_minor_version_update_of_an_rpm_installation.mdx
@@ -0,0 +1,61 @@
+---
+title: "Performing a minor version upgrade on an RPM installation"
+description: "For RPM package installs, how to perform a minor version upgrade to a more recent version."
+redirects:
+- /epas/latest/epas_upgrade_guide/05_performing_a_minor_version_update_of_an_rpm_installation/
+---
+
+If you're upgrading a Red Hat Enterprise Linux-based system or a compatible system such as Rocky Linux, Alma Linux, Oracle Linux, then you used an RPM package to install EDB Postgres Advanced Server. To perform a minor upgrade on these systems, use the DNF package manager.
+
+!!! Note
+    This procedure performs an upgrade only between minor EDB Postgres Advanced Server releases. To upgrade to a later major release, use the [`pg_upgrade` procedure](../major_upgrade/).
+
+1.  To list the package updates that are available for your system, open a command line, assume root privileges, and run:
+
+    ```shell
+    dnf check-update <package_name>
+    ```
+
+    Where `package_name` is the search term for which you want to list available updates. You can include wildcard values in the search to list multiple related packages with a single command. For example, use the following command to list all packages with names that start with `edb`:
+
+    ```shell
+    dnf check-update edb*
+    ```
+    
+1.  After you identify the packages, update them:
+
+    ```shell
+    dnf update <package_name>
+    ```
+
+    Where `package_name` is the name of the package you want to update. You can include wildcard values to update multiple related packages with a single command. For example, use the following command to update all packages with names that start with `edb`:
+
+    ```shell
+    dnf update edb*
+    ```
+
+1.  To complete the upgrade, restart your server. 
+
+For more information about using DNF commands and options, enter `dnf --help` at the command line.
+
+!!! Important
+    
+If upgrading to version 15.4  or later, run `edb_sqlpatch`.
+
+The command might respond that it has a number of patches that need to be applied, for example:
+
+```console
+* database edb
+0 patches were previously applied to this database.
+58 patches need to be applied to this database.
+```
+
+In this case, you need to run edb_sqlpatch to patch the system catalog:
+
+```shell
+edb_sqlpatch -af
+```
+
+For more information about using edb_sqlpatch commands and options, see [edb_sqlpatch](/tools/edb_sqlpatch/).
+
+!!!
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
new file mode 100644
index 00000000000..775e428780e
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/minor_upgrade/06_using_stackbuilder_plus_to_perform_a_minor_version_update.mdx
@@ -0,0 +1,50 @@
+---
+title: "Using StackBuilder Plus to perform a minor version upgrade"
+description: "How to use the StackBuilder Plus utility to install supporting modules."
+redirects:
+- /epas/latest/epas_upgrade_guide/06_using_stackbuilder_plus_to_perform_a_minor_version_update/
+---
+
+!!! Note
+    StackBuilder Plus is only supported on Windows systems.
+
+The StackBuilder Plus utility provides a graphical interface that simplifies the process of updating, downloading, and installing modules that complement your EDB Postgres Advanced Server installation. When you install a module with StackBuilder Plus, StackBuilder Plus resolves any software dependencies.
+
+1.  To invoke StackBuilder Plus at any time after the installation has completed, select **Apps > StackBuilder Plus**. Enter your system password if prompted, and the StackBuilder Plus welcome window opens.
+
+    ![The StackBuilder Plus welcome window](../../images/the-stackbuilder-plus-welcome.png)
+
+1.  Select your EDB Postgres Advanced Server installation.
+
+    StackBuilder Plus requires internet access. If your installation of EDB Postgres Advanced Server is behind a firewall (with restricted internet access), StackBuilder Plus can download program installers through a proxy server. The module provider determines if the module can be accessed through an HTTP proxy or an FTP proxy. Currently, all updates are transferred by an HTTP proxy, and the FTP proxy information isn't used.
+
+1.  If the selected EDB Postgres Advanced Server installation has restricted Internet access, on the Welcome screen, select **Proxy Servers** to open the Proxy servers dialog box:
+
+    ![The Proxy servers dialog](../../images/the-proxy-servers-dialog.png)
+
+1.  On the dialog box, enter the IP address and port number of the proxy server in the **HTTP proxy** box. Currently, all StackBuilder Plus modules are distributed by HTTP proxy (FTP proxy information is ignored). Select **OK**.
+
+    ![The StackBuilder Plus module selection window](../../images/the-stackbuilder-plus-module-selection-window.png)
+
+    The tree control on the StackBuilder Plus module selection window displays a node for each module category.
+
+1.  To add a component to the selected EDB Postgres Advanced Server installation or to upgrade a component, select the box to the left of the module name, and select **Next**. 
+
+1.  If prompted, enter your email address and password on the StackBuilder Plus registration window.
+
+    ![A summary window displays a list of selected packages](../../images/selected-packages-summary-window.png)
+
+    StackBuilder Plus confirms the packages selected. The Selected packages dialog box displays the name and version of the installer. Select **Next**.
+
+    When the download completes, a window opens that confirms the installation files were downloaded and are ready for installation.
+
+    ![Confirmation that the download process is complete](../../images/download-complete-confirmation.png)
+
+1.  Leave the **Skip Installation** check box cleared and select **Next** to start the installation process. (Select the check box and select **Next** to exit StackBuilder Plus without installing the downloaded files.)
+
+    ![StackBuilder Plus confirms the completed installation](../../images/stackbuilder-plus-confirms-the-completed-installation.png)
+
+When the upgrade is complete, StackBuilder Plus alerts you to the success or failure of the installation of the requested package. If you were prompted by an installer to restart your computer, restart now.
+
+If the update fails to install, StackBuilder Plus alerts you to the installation error and writes a message to the log file at `%TEMP%`.
+
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx
new file mode 100644
index 00000000000..1246373f5c8
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/minor_upgrade/index.mdx
@@ -0,0 +1,18 @@
+---
+title: "Minor version upgrade with a package manager"
+description: "Describes using a package manager to perform a minor version upgrade of EDB Postgres Advanced Server."
+navigation:
+- 05_performing_a_minor_version_update_of_an_rpm_installation
+- performing_a_minor_version_update_of_deb_installation
+- 06_using_stackbuilder_plus_to_perform_a_minor_version_update
+---
+
+Minor version upgrades require only updating existing executables and restarting the database server. 
+
+Select the minor upgrade method according to the underlying operating system of your database server:
+
+- If you installed an RPM package of EDB Postgres Advanced Server (on RHEL, AlmaLinux, Rocky Linux) with `dnf`, see [Performing a minor version upgrade of an RPM installation](05_performing_a_minor_version_update_of_an_rpm_installation).
+
+- If you installed a Debian package of EDB Postgres Advanced Server (on Ubuntu, Debian) with `apt-get`, see [Performing a minor version upgrade of a Debian installation](performing_a_minor_version_update_of_deb_installation).
+
+- If you installed EDB Postgres Advanced Server with StackBuilder Plus, see [Using StackBuilder Plus to perform a minor version upgrade](06_using_stackbuilder_plus_to_perform_a_minor_version_update).
diff --git a/product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_deb_installation.mdx b/product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_deb_installation.mdx
new file mode 100644
index 00000000000..33feba99e26
--- /dev/null
+++ b/product_docs/docs/epas/16/upgrading/minor_upgrade/performing_a_minor_version_update_of_deb_installation.mdx
@@ -0,0 +1,68 @@
+---
+title: "Performing a minor version upgrade on a Debian installation"
+description: "For Debian package installs, how to perform a minor version upgrade to a more recent version."
+---
+
+If you're upgrading a Debian-based system (or a compatible system such as Ubuntu), then you used a Debian package to install EDB Postgres Advanced Server. To perform a minor upgrade on these systems, use the `apt-get` package manager.
+
+!!! Note
+    This procedure performs an upgrade only between minor EDB Postgres Advanced Server releases. To upgrade to a later major release, use the [pg_upgrade procedure](../major_upgrade/).
+
+1.  To list the package updates that are available for your system, open a command line, assume root privileges, and run:
+
+    ```shell
+    apt-get install --simulate <package_name>
+    ```
+
+    Where `package_name` is the search term for which you want to list available updates. You can include wildcard values in the search to list multiple related packages with a single command. For example, use the following command to list all packages with names that start with `edb`:
+
+    ```shell
+    apt-get install --simulate edb*
+    ```
+    
+1.  After you identify the packages, update them:
+
+    ```shell
+    apt-get install <package_name>
+    ```
+
+    Where `package_name` is the name of the package you want to update. You can include wildcard values to update multiple related packages with a single command. For example, use the following command to update all packages with names that start with `edb`:
+
+    ```shell
+    apt-get update edb*
+    ```
+
+1.  The output asks for confirmation to install the packages: 
+
+    ```console
+    After this operation, <number> kB of additional disk space will be used.
+    Do you want to continue? [Y/n] Y
+    ```
+
+1.  Type `Y` and press **Enter**. 
+
+1.  To complete the upgrade, restart your server. 
+
+For more information about using `apt-get` commands and options, enter `apt-get --help` at the command line.
+
+!!! Important
+    
+If upgrading to version 15.4 or later, run `edb_sqlpatch`.
+
+The command might respond that it has a number of patches needing to be applied, for example:
+
+```console
+* database edb
+0 patches were previously applied to this database.
+58 patches need to be applied to this database.
+```
+
+In this case, you need to run `edb_sqlpatch` to patch the system catalog:
+
+```shell
+edb_sqlpatch -af
+```
+
+For more information about using `edb_sqlpatch` commands and options, see [edb_sqlpatch](/tools/edb_sqlpatch/).
+
+!!!
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/02_enhanced_compatibility_features.mdx b/product_docs/docs/epas/16/working_with_oracle_data/02_enhanced_compatibility_features.mdx
new file mode 100644
index 00000000000..4bb47bed869
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/02_enhanced_compatibility_features.mdx
@@ -0,0 +1,204 @@
+---
+title: "Enhanced compatibility features"
+description: "Provides an overview of the compatability features included in EDB Postgres Advanced Server that support migrating Oracle applications"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.66.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.64.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.65.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.61.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.63.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.62.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.6/EDB_Postgres_Advanced_Server_Guide.1.67.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.100.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.325.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.303.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.189.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.105.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.099.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.050.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/user-guide/9.5/EDB_Postgres_Enterprise_Guide.1.026.html"
+redirects:
+  - /epas/latest/epas_guide/02_enhanced_compatibility_features/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+EDB Postgres Advanced Server includes extended functionality that provides compatibility for syntax supported by Oracle applications. See [Database compatibility for Oracle developers](../fundamentals/epas_fundamentals/epas_compat_ora_dev_guide/) for additional information about the compatibility features supported by EDB Postgres Advanced Server.
+
+## Enabling compatibility features
+
+You can install EDB Postgres Advanced Server in several ways to enable compatibility features:
+
+-   Before initializing your cluster, use the `INITDBOPTS` variable in the EDB Postgres Advanced Server service configuration file to specify `--redwood-like`.
+-   Include the `--redwood-like` parameter when using `initdb` to initialize your cluster.
+
+See [Configuration parameters compatible with Oracle databases](../reference/database_administrator_reference/02_summary_of_configuration_parameters/) and [Managing an EDB Postgres Advanced Server installation](../installing/linux_install_details/managing_an_advanced_server_installation/) for more information about the installation options supported by the EDB Postgres Advanced Server installers.
+
+!!! Note
+    Database link is not supported in PostgreSQL-compatible mode because it requires Oracle compatibility.
+
+## Stored procedural language
+
+EDB Postgres Advanced Server supports a highly productive procedural language that allows you to write custom procedures, functions, triggers, and packages. This procedural language:
+
+-   Complements the SQL language and built-in packages.
+-   Provides a seamless development and testing environment.
+-   Allows you to create reusable code.
+
+See [Stored procedural language](../application_programming/epas_compat_spl/) for more information.
+
+## Optimizer hints
+
+When you invoke a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command, the server generates a set of execution plans. After analyzing those execution plans, the server selects a plan that generally returns the result set in the least amount of time. The server's choice of plan depends on several factors:
+
+-   The estimated execution cost of data-handling operations
+-   Parameter values assigned in the Query Tuning section of the `postgresql.conf` file
+-   Column statistics that are gathered by the `ANALYZE` command
+
+As a rule, the query planner selects the least expensive plan. You can use an *optimizer hint* to influence the server as it selects a query plan. An optimizer hint is one or more directives embedded in a comment-like syntax that immediately follows a `DELETE`, `INSERT`, `SELECT`, or `UPDATE` command. Keywords in the comment instruct the server to use or avoid a specific plan when producing the result set. See [Optimizer hints](../application_programming/optimizing_code/05_optimizer_hints/) for more information.
+
+## Data dictionary views
+
+EDB Postgres Advanced Server includes a set of views that provide information about database objects in a manner compatible with the Oracle data dictionary views. See [Database compatibility for Oracle developers: catalog views](../reference/oracle_compatibility_reference/epas_compat_cat_views/) for detailed information about the views available with EDB Postgres Advanced Server.
+
+## dblink_ora
+
+dblink_ora provides an OCI-based database link that allows you to `SELECT`, `INSERT`, `UPDATE`, or `DELETE` data stored on an Oracle system from EDB Postgres Advanced Server. See [dblink_ora](06_dblink_ora/) for detailed information about using `dblink_ora` and the supported functions and procedures.
+
+## Profile management
+
+EDB Postgres Advanced Server supports compatible SQL syntax for profile management. Profile management commands allow a database superuser to create and manage named *profiles*. A profile is a named set of attributes that allow you to easily manage a group of roles that share comparable authentication requirements. Each profile defines rules for password management that augment password and md5 authentication. The rules in a profile can:
+
+-   Count failed login attempts
+-   Lock an account due to excessive failed login attempts
+-   Mark a password for expiration
+-   Define a grace period after a password expiration
+-   Define rules for password complexity
+-   Define rules that limit password reuse
+
+After creating the profile, you can associate the profile with one or more users. If password requirements change, you can modify the profile to apply the new requirements to each user that's associated with that profile.
+
+When a user connects to the server, the server enforces the profile that's associated with their login role. 
+
+Profiles are shared by all databases in a cluster, but each cluster can have multiple profiles. A single user with access to multiple databases uses the same profile when connecting to each database in the cluster.
+
+See [Profile management](../epas_security_guide/04_profile_management/) for information about using profile management commands.
+
+## Built-in packages
+
+EDB Postgres Advanced Server supports a number of built-in packages that provide compatibility with Oracle procedures and functions.
+
+| Package name   | Description                                                                                                                                                                                                       |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `DBMS_ALERT`     | Lets you register for, send, and receive alerts.                                                                                                                         |
+| `DBMS_AQ`        | Provides message queueing and processing for EDB Postgres Advanced Server.                                                                                                                                 |
+| `DBMS_AQADM`     | Provides supporting procedures for Advanced Queueing functionality.                                                                                                                        |
+| `DBMS_CRYPTO`    | Provides functions and procedures that allow you to encrypt or decrypt RAW, BLOB, or CLOB data. You can also use `DBMS_CRYPTO` functions to generate cryptographically strong random values. |
+| `DBMS_JOB`       | Provides for creating, scheduling, and managing jobs.                                                                                                                                 |
+| `DBMS_LOB`       | Lets you operate on large objects.                                                                                                                                         |
+| `DBMS_LOCK`      | Provides support for the `DBMS_LOCK.SLEEP` procedure.                                                                                                                                               |
+| `DBMS_MVIEW`     | Use to manage and refresh materialized views and their dependencies.                                                                                                         |
+| `DBMS_OUTPUT`    | Lets you send messages to a message buffer or get messages from the message buffer.                                                                                    |
+| `DBMS_PIPE`      | Lets you send messages through a pipe in or between sessions connected to the same database cluster.                                                                  |
+| `DBMS_PROFILER`  | Collects and stores performance information about the PL/pgSQL and SPL statements that are executed during a performance profiling session.                                             |
+| `DBMS_RANDOM`    | Provides methods to generate random values.                                                                                                                                   |
+| `DBMS_REDACT`    | Enables redacting or masking data that's returned by a query.                                                                                                                     |
+| `DBMS_RLS`       | Enables implementing Virtual Private Database on certain EDB Postgres Advanced Server database objects.                                                                                          |
+| `DBMS_SCHEDULER` | Lets you create and manage jobs, programs, and job schedules.                                                                                                                  |
+| `DBMS_SESSION`   | Provides support for the `DBMS_SESSION.SET_ROLE` procedure.                                                                                                                                         |
+| `DBMS_SQL`       | Provides an application interface to the EDB dynamic SQL functionality.                                                                                                                      |
+| `DBMS_UTILITY`   | Provides various utility programs.                                                                                                                                                       |
+| `UTL_ENCODE`     | Provides a way to encode and decode data.                                                                                                                                                  |
+| `UTL_FILE`       | Lets you read from and write to files on the operating system’s file system.                                                                                              |
+| `UTL_HTTP`       | Lets you use the HTTP or HTTPS protocol to retrieve information found at a URL.                                                                                                    |
+| `UTL_MAIL`       | Lets you manage email.                                                                                                                                                    |
+| `UTL_RAW`        | Allows you to manipulate or retrieve the length of raw data types.                                                                                                                            |
+| `UTL_SMTP`       | Lets you send emails over the Simple Mail Transfer Protocol (SMTP).                                                                                                       |
+| `UTL_URL`        | Provides a way to escape illegal and reserved characters in a URL.                                                                                                                       |
+
+See [Built-in packages](../reference/oracle_compatibility_reference/epas_compat_bip_guide/03_built-in_packages/) for detailed information about the procedures and functions available in each package.
+
+## Open Client Library
+
+The Open Client Library provides application interoperability with the Oracle Call Interface. An application that was formerly “locked in” can now work with either an EDB Postgres Advanced Server or an Oracle database with minimal to no changes to the application code. The EDB implementation of the Open Client Library is written in C.
+
+The following diagram compares the Open Client Library and Oracle Call Interface application stacks.
+
+![The Open Client Library](../images/open_client_library.png)
+
+For detailed information about the functions supported by the Open Client Library, see [EDB OCL Connector](/ocl_connector/15/).
+
+## Utilities
+
+For detailed information about the compatible syntax supported by these utilities, see [Tools, utilities, and components](../tools_utilities_and_components/epas_compat_tools_guide/).
+
+### EDB\*Plus
+
+EDB\*Plus is a utility program that provides a command line user interface to the EDB Postgres Advanced Server that's familiar to Oracle developers and users. EDB\*Plus accepts SQL commands, SPL anonymous blocks, and EDB\*Plus commands.
+
+EDB\*Plus allows you to:
+
+-   Query certain database objects
+-   Execute stored procedures
+-   Format output from SQL commands
+-   Execute batch scripts
+-   Execute OS commands
+-   Record output
+
+See [EDB\*Plus](/edb_plus/41/) for more information.
+
+### EDB\*Loader
+
+EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader.
+
+EDB\*Loader features include:
+
+-   Support for the Oracle SQL\*Loader data loading methods&mdash;conventional path load, direct path load, and parallel direct path load
+-   Oracle SQL\*Loader-compatible syntax for control file directives
+-   Input data with delimiter-separated or fixed-width fields
+-   Bad file for collecting rejected records
+-   Loading of multiple target tables
+-   Discard file for collecting records that don't meet the selection criteria of any target table
+-   Data loading from standard input and remote loading
+
+See [Loading bulk data](../database_administration/02_edb_loader/) for information.
+
+### EDB\*Wrap
+
+The EDB\*Wrap utility protects proprietary source code and programs (functions, stored procedures, triggers, and packages) from unauthorized scrutiny. The EDB\*Wrap program translates a file that contains SPL or PL/pgSQL source code (the plaintext) into a file that contains the same code in a form that's nearly impossible to read. Once you have the obfuscated form of the code, you can send that code to EDB Postgres Advanced Server, which stores those programs in obfuscated form. While EDB\*Wrap does obscure code, table definitions are still exposed.
+
+Everything you wrap is stored in obfuscated form. If you wrap an entire package, the package body source as well as the prototypes contained in the package header and the functions and procedures contained in the package body are stored in obfuscated form.
+
+See [Protecting proprietary source code](../epas_security_guide/03_edb_wrap/) for information.
+
+### Dynamic Runtime Instrumentation Tools Architecture (DRITA)
+
+DRITA allows a DBA to query catalog views to determine the *wait events* that affect the performance of individual sessions or the system as a whole. DRITA records the number of times each event occurs as well as the time spent waiting. You can use this information to diagnose performance problems. DRITA offers this functionality while consuming minimal system resources.
+
+DRITA compares *snapshots* to evaluate the performance of a system. A snapshot is a saved set of system performance data at a given point in time. A unique ID number identifies each snapshot. You can use snapshot ID numbers with DRITA reporting functions to return system performance statistics.
+
+See [Using dynamic resource tuning](../managing_performance/using_dynatune/) for information.
+
+## ECPGPlus
+
+EDB enhanced ECPG (the PostgreSQL precompiler) to create ECPGPlus. ECPGPlus allows you to include embedded SQL commands in C applications. When you use ECPGPlus to compile an application that contains embedded SQL commands, the SQL code is syntax checked and translated to C.
+
+ECPGPlus supports Pro\*C syntax in C programs when connected to an EDB Postgres Advanced Server database. ECPGPlus supports:
+
+-   Oracle Dynamic SQL – Method 4 (ODS-M4)
+-   Pro\*C-compatible anonymous blocks
+-   A `CALL` statement compatible with Oracle databases
+
+See [ECPGPlus](../tools_utilities_and_components/application_developer_tools/10_ecpgplus/) for information.
+
+## Table partitioning
+
+In a partitioned table, one logically large table is broken into smaller physical pieces. Partitioning can provide several benefits:
+
+-   Query performance can be improved dramatically in certain situations, particularly when most of the heavily accessed rows of the table are in a single partition or a small number of partitions. Partitioning allows you to omit the partition column from the front of an index, reducing index size and making it more likely that the heavily used parts of the index fit in memory.
+-   When a query or update accesses a large percentage of a single partition, performance might improve because the server performs a sequential scan of the partition instead of using an index and random access reads scattered across the whole table.
+-   If you plan the requirement into the partitioning design, you can implement bulk load or unload by adding or removing partitions. `ALTER TABLE` is faster than a bulk operation. It also avoids the `VACUUM` overhead caused by a bulk `DELETE`.
+-   You can migrate seldom-used data to less expensive or slower storage media.
+
+Table partitioning is worthwhile only when a table would otherwise be very large. The exact point at which a table benefits from partitioning depends on the application. A good estimation is when the size of the table exceeds the physical memory of the database server.
+
+For information about database compatibility features supported by EDB Postgres Advanced Server, see [Table partitioning](../application_programming/epas_compat_table_partitioning/).
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/02_calling_dblink_ora_functions.mdx b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/02_calling_dblink_ora_functions.mdx
new file mode 100644
index 00000000000..8e32516d61f
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/02_calling_dblink_ora_functions.mdx
@@ -0,0 +1,59 @@
+---
+title: "Calling dblink_ora functions"
+description: "Describes how to call the dblink_ora functions"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.125.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.355.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/02_calling_dblink_ora_functions/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="calling_dblink_ora_functions" class="registered_link"></div>
+
+## Using the dblink_ora_connect function
+
+The following command establishes a connection using the `dblink_ora_connect()` function:
+
+```sql
+SELECT dblink_ora_connect('acctg', 'localhost', 'xe', 'hr', 'pwd', 1521);
+```
+
+The example connects to:
+-  A service named `xe` 
+-  Running on port `1521` on the `localhost` 
+-  With a user name of `hr` 
+-  With a password of `pwd`
+
+You can use the connection name `acctg` to refer to this connection when calling other dblink_ora functions.
+
+## Using the dblink_ora_copy function
+
+The following command uses the `dblink_ora_copy()` function over a connection named `edb_conn`. It copies the `empid` and `deptno` columns from a table on an Oracle server named `ora_acctg` to a table located in the `public` schema on an instance of EDB Postgres Advanced Server named `as_acctg`. The `TRUNCATE` option is enforced, and a feedback count of `3` is specified:
+
+```sql
+edb=# SELECT dblink_ora_copy('edb_conn','select empid, deptno FROM
+ora_acctg', 'public', 'as_acctg', true, 3);
+__OUTPUT__
+INFO:  Row: 0
+INFO:  Row: 3
+INFO:  Row: 6
+INFO:  Row: 9
+INFO:  Row: 12
+
+ dblink_ora_copy
+-----------------
+ 12
+
+(1 row)
+```
+
+## Using the dblink_ora_record function
+
+The following `SELECT` statement uses the `dblink_ora_record()` function and the `acctg` connection to retrieve information from the Oracle server:
+
+```sql
+SELECT * FROM dblink_ora_record( 'acctg', 'SELECT first_name from employees') AS t1(id VARCHAR);
+```
+
+The command retrieves a list that includes all of the entries in the `first_name` column of the `employees` table.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/connecting_to_oracle.mdx b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/connecting_to_oracle.mdx
new file mode 100644
index 00000000000..74a92b99d6a
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/connecting_to_oracle.mdx
@@ -0,0 +1,46 @@
+---
+title: "Connecting to an Oracle database"
+description: "Describes how to create a link to an Oracle server"
+---
+
+To enable Oracle connectivity, download Oracle's freely available OCI drivers from [their website](http://www.oracle.com/technetwork/database/database-technologies/instant-client/overview/index.html).
+
+## Creating a symbolic link 
+
+For Linux, if the Oracle instant client that you downloaded doesn't include the `libclntsh.so` library, you must create a symbolic link named `libclntsh.so` that points to the downloaded version. Navigate to the instant client directory and execute the following command:
+
+```shell
+ln -s libclntsh.so.<version> libclntsh.so
+```
+
+Where `version` is the version number of the `libclntsh.so` library. For example:
+
+```shell
+ln -s libclntsh.so.12.1 libclntsh.so
+```
+## Setting the environment variable
+
+Before creating a link to an Oracle server, you must direct EDB Postgres Advanced Server to the correct Oracle home directory. Set the `LD_LIBRARY_PATH` environment variable on Linux or `PATH` on Windows to the `lib` directory of the Oracle client installation directory.
+
+## Setting the oracle_home configuration parameter
+
+Alternatively, you can set the value of the `oracle_home` configuration parameter in the `postgresql.conf` file. The value specified in the `oracle_home` configuration parameter overrides the `LD_LIBRARY_PATH` environment variable in Linux and `PATH` environment variable in Windows.
+
+!!! Note
+    The `oracle_home` configuration parameter provides the correct path to the Oracle client, that is, the `OCI` library.
+
+To set the `oracle_home` configuration parameter in the `postgresql.conf` file, edit the file and add the following line:
+
+```ini
+oracle_home = 'lib_directory'
+```
+
+In place of `<lib_directory>`, substitute the name of the `oracle_home` path to the Oracle client installation directory that contains `libclntsh.so` in Linux and `oci.dll` in Windows.
+
+## Restarting the server
+
+After setting the `oracle_home` configuration parameter, you must restart the server for the changes to take effect. Restart the server:
+
+-   On Linux, using the `systemctl` command or `pg_ctl` services.
+
+-   On Windows, from the Windows Services console.
\ No newline at end of file
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/index.mdx b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/index.mdx
new file mode 100644
index 00000000000..ad2be4cde70
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/06_dblink_ora/index.mdx
@@ -0,0 +1,14 @@
+---
+title: "Querying an Oracle server"
+indexCards: simple
+description: "How to use the dblink_ora utility to query a remote Oracle server"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.123.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.353.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/06_dblink_ora/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+
+dblink_ora enables you to issue arbitrary queries to a remote Oracle server. It provides an OCI-based database link that enables you to `SELECT`, `INSERT`, `UPDATE`, or `DELETE` data stored on an Oracle system from EDB Postgres Advanced Server.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/07_open_client_library.mdx b/product_docs/docs/epas/16/working_with_oracle_data/07_open_client_library.mdx
new file mode 100644
index 00000000000..ee272d58a4a
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/07_open_client_library.mdx
@@ -0,0 +1,23 @@
+---
+title: "Using Open Client Library"
+description: "Introduces the EDB OCL Connector, used to compile Oracle Call Interface applications to interact with an EDB Postgres Advanced Server database"
+legacyRedirectsGenerated:
+  # This list is generated by a script. If you need add entries, use the `legacyRedirects` key.
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.6/Database_Compatibility_for_Oracle_Developers_Guide_v9.6.1.097.html"
+  - "/edb-docs/d/edb-postgres-advanced-server/user-guides/database-compatibility-for-oracle-developers-guide/9.5/Database_Compatibility_for_Oracle_Developers_Guide.1.219.html"
+redirects:
+  - /epas/latest/epas_compat_ora_dev_guide/07_open_client_library/ #generated for docs/epas/reorg-role-use-case-mode
+---
+
+<div id="open_client_library" class="registered_link"></div>
+
+The Open Client Library provides application interoperability with the Oracle Call Interface. An application that was formerly “locked in” can now work with either an EDB Postgres Advanced Server or an Oracle database with minimal to no changes to the application code. The EDB implementation of the Open Client Library is written in C.
+
+The following diagram compares the Open Client Library and Oracle Call Interface application stacks.
+
+![Open Client Library](../images/open_client_library.png)
+
+For detailed usage information about the Open Client Library and the supported functions, see [EDB OCL Connector](/ocl_connector/15/).
+
+!!! Note
+    EDB doesn't support the use of the Open Client Library with Oracle Real Application Clusters (RAC) and Oracle Exadata. These Oracle products haven't been evaluated or certified with this EDB product.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/embedded_sql_commands.mdx b/product_docs/docs/epas/16/working_with_oracle_data/embedded_sql_commands.mdx
new file mode 100644
index 00000000000..1431f87fd23
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/embedded_sql_commands.mdx
@@ -0,0 +1,9 @@
+---
+navTitle: Including embedded SQL commands
+title: "Including embedded SQL commands in C applications (ECPGPlus)"
+description: "Overview of using the ECPGPlus utility to embed SQL commands in C applications"
+---
+
+EDB has enhanced ECPG (the PostgreSQL precompiler) to create ECPGPlus. ECPGPlus allows you to include embedded SQL commands in C applications. When you use ECPGPlus to compile an application that contains embedded SQL commands, the SQL code is syntax checked and translated into C.
+
+See [ECPGPlus overview](../application_programming/ecpgplus_guide/02_overview/) for details about installing and configuring the utility.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/index.mdx b/product_docs/docs/epas/16/working_with_oracle_data/index.mdx
new file mode 100644
index 00000000000..c588fe41795
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/index.mdx
@@ -0,0 +1,6 @@
+---
+title: "Working with Oracle data"
+indexCards: simple
+---
+
+EDB Postgres Advanced Server makes Postgres look, feel, and operate more like Oracle. So when you migrate, there's less code to rewrite, and you can be up and running quickly. The Oracle compatibility features allow you to run many applications written for Oracle in EDB Postgres Advanced Server with minimal to no changes.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/loading_bulk_data.mdx b/product_docs/docs/epas/16/working_with_oracle_data/loading_bulk_data.mdx
new file mode 100644
index 00000000000..044efa20b12
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/loading_bulk_data.mdx
@@ -0,0 +1,9 @@
+---
+navTitle: Loading bulk data
+title: "Loading bulk data (EDB*Loader)"
+description: "Overview of loading bulk data with EDB*Loader"
+---
+
+EDB\*Loader is a high-performance bulk data loader that provides an interface compatible with Oracle databases for EDB Postgres Advanced Server. The EDB\*Loader command line utility loads data from an input source, typically a file, into one or more tables using a subset of the parameters offered by Oracle SQL\*Loader.
+
+See [EDB*Loader](../database_administration/02_edb_loader/) for details about using the utility.
diff --git a/product_docs/docs/epas/16/working_with_oracle_data/proprietary_source_code.mdx b/product_docs/docs/epas/16/working_with_oracle_data/proprietary_source_code.mdx
new file mode 100644
index 00000000000..c493aad88af
--- /dev/null
+++ b/product_docs/docs/epas/16/working_with_oracle_data/proprietary_source_code.mdx
@@ -0,0 +1,10 @@
+---
+navTitle: Protecting proprietary code
+title: "Protecting proprietary source code (EDB*Wrap)"
+description: "Overview of the EDB*Wrap utility, which you use to protect proprietary source code and programs"
+---
+
+The EDB\*Wrap utility protects proprietary source code and programs like functions, stored procedures, triggers, and packages from unauthorized scrutiny. The EDB\*Wrap program translates a plaintext file that contains SPL or PL/pgSQL source code into a file that contains the same code in a form that's nearly impossible to read. Once you have the obfuscated form of the code, you can send that code to the PostgreSQL server, and the server stores those programs in obfuscated form. While EDB\*Wrap does obscure code, table definitions are still exposed.
+
+See [EDB\*Wrap](../epas_security_guide/03_edb_wrap/) for details about using the utility.
+