From 35df0140eeeef9af687292b57c5b07d4eef85c99 Mon Sep 17 00:00:00 2001 From: vramik Date: Thu, 16 May 2024 12:43:27 +0200 Subject: [PATCH] Add a note to the migration guide about index name length for Oracle database Closes #29594 Signed-off-by: vramik --- .../documentation/upgrading/topics/changes/changes-24_0_0.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/documentation/upgrading/topics/changes/changes-24_0_0.adoc b/docs/documentation/upgrading/topics/changes/changes-24_0_0.adoc index 40b92c70765..fc0a54fe353 100644 --- a/docs/documentation/upgrading/topics/changes/changes-24_0_0.adoc +++ b/docs/documentation/upgrading/topics/changes/changes-24_0_0.adoc @@ -313,6 +313,9 @@ This change adds new indexes on the tables `USER_ATTRIBUTE` and `FED_USER_ATTRIB If those tables contain more than 300000 entries, {project_name} will skip the index creation by default during the automatic schema migration and instead log the SQL statement on the console during migration to be applied manually after {project_name}'s startup. See the link:{upgradingguide_link}[{upgradingguide_name}] for details on how to configure a different limit. +NOTE: The newly added indexes `USER_ATTR_LONG_VALUES_LOWER_CASE` and `FED_USER_ATTR_LONG_VALUES_LOWER_CASE` may exceed the maximum limit of 30 characters set by Oracle, +in case the database is running in compatibility mode. Since Oracle version 12.2, there is a support for longer index names. + == Additional migration steps for LDAP This is for installations that match all the following criteria: