Your issue is similar to ours. we are also trying to upgrade from 23r2 to 25r1 and got same error message.
In our case, the Kube log also contained the following output:
  ERROR: Failed to start server in (production) mode
  ERROR: Failed to update database
  ERROR: liquibase.exception.LiquibaseException: liquibase.exception.MigrationFailedException: Migration failed for changeset META-INF/jpa-changelog-25.0.0.xml::25.0.0-org::keycloak:\n
       Reason: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object\n\n
       https://docs.oracle.com/error-help/db/ora-00955/ 
       bFailed SQL: (955) CREATE TABLE IFSIAMSYS.ORG (ID VARCHAR2(255) NOT NULL, ENABLED NUMBER(1) NOT NULL, REALM_ID VARCHAR2(255) NOT NULL, GROUP_ID VARCHAR2(255) NOT NULL, NAME VARCHAR2(255) NOT NULL, DESCRIPTION VARCHAR2(4000), CONSTRAINT PK_ORG PRIMARY KEY (ID))]
  ERROR: liquibase.exception.MigrationFailedException: Migration failed for changeset META-INF/jpa-changelog-25.0.0.xml::25.0.0-org::keycloak:\n
       Reason: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object\n\n
       https://docs.oracle.com/error-help/db/ora-00955/ 
       /Failed SQL: (955) CREATE TABLE IFSIAMSYS.ORG (ID VARCHAR2(255) NOT NULL, ENABLED NUMBER(1) NOT NULL, REALM_ID VARCHAR2(255) NOT NULL, GROUP_ID VARCHAR2(255) NOT NULL, NAME VARCHAR2(255) NOT NULL, DESCRIPTION VARCHAR2(4000), CONSTRAINT PK_ORG PRIMARY KEY (ID))]
  ERROR: Migration failed for changeset META-INF/jpa-changelog-25.0.0.xml::25.0.0-org::keycloak:\n
       Reason: liquibase.exception.DatabaseException: ORA-00955: name is already used by an existing object\n\n
       https://docs.oracle.com/error-help/db/ora-00955/ 
       /Failed SQL: (955) CREATE TABLE IFSIAMSYS.ORG (ID VARCHAR2(255) NOT NULL, ENABLED NUMBER(1) NOT NULL, REALM_ID VARCHAR2(255) NOT NULL, GROUP_ID VARCHAR2(255) NOT NULL, NAME VARCHAR2(255) NOT NULL, DESCRIPTION VARCHAR2(4000), CONSTRAINT PK_ORG PRIMARY KEY (ID))]
  ERROR: ORA-00955: name is already used by an existing object\n\nhttps://docs.oracle.com/error-help/db/ora-00955/ 
       lFailed SQL: (955) CREATE TABLE IFSIAMSYS.ORG (ID VARCHAR2(255) NOT NULL, ENABLED NUMBER(1) NOT NULL, REALM_ID VARCHAR2(255) NOT NULL, GROUP_ID VARCHAR2(255) NOT NULL, NAME VARCHAR2(255) NOT NULL, DESCRIPTION VARCHAR2(4000), CONSTRAINT PK_ORG PRIMARY KEY (ID))]
  ERROR: ORA-00955: name is already used by an existing object\n\nhttps://docs.oracle.com/error-help/db/ora-00955/
  ERROR: ORA-00955: name is already used by an existing object\n

We were able to resolve the issue by the following steps:
1. Connect to the database as the IFSIAMSYS user, and drop the IFSIAMSYS.ORG tables and the IFSIAMSYS.ORG_DOMAIN table.
   select * from IFSIAMSYS.ORG;
    -> no rows selected
   select * from IFSIAMSYS.ORG_DOMAIN;
    -> no rows selected
   drop table IFSIAMSYS.ORG ;
    -> Table dropped.
   drop table IFSIAMSYS.ORG_DOMAIN;
    -> Table dropped.
2. After waiting about 10 minutes, the ifsapp-iam status changed to Running,
   and the Kube log also contained the following message.
   
   $ sudo microk8s.kubectl logs -n myifs ifsapp-iam-XXXX -c ifsapp-iam
   ...
   Service account found - service-account-ifs_xdiv
   Setup completed.
   $

3. After confirming the above, you are able to log in.

However, we believe we made some fundamental mistake in the upgrade procedure,
so there may still be another problem.
so I would like to try the upgrade again from the 23r2 state later.

have you monitored the status of the ifs-ingress pods?. Sometimes, problems like this happen due to an unstable environment or performance issues with the middleware.