From 2efd27caf1489ea442e736bbe53a7b71f1c309c8 Mon Sep 17 00:00:00 2001 From: yuki-tei <57980555+yuki-tei@users.noreply.github.com> Date: Fri, 6 Mar 2026 10:02:14 +0900 Subject: [PATCH] Update direct_path_load.mdx --- .../02_edb_loader/invoking_edb_loader/direct_path_load.mdx | 3 +++ 1 file changed, 3 insertions(+) diff --git a/product_docs/docs/epas/18/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx b/product_docs/docs/epas/18/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx index 81d8b11aaf..9d46eca1f6 100644 --- a/product_docs/docs/epas/18/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx +++ b/product_docs/docs/epas/18/database_administration/02_edb_loader/invoking_edb_loader/direct_path_load.mdx @@ -32,6 +32,9 @@ The restrictions on the target table of a direct path load are: - 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. +!!! Warning + Currently, a direct path load toward TDE database shall not be performed, because it will cause permanent and unrecoverable damage to the relation files in data-block level. + ## Running the direct path load To run a direct path load, add the `DIRECT=TRUE` option: