Issues after migrating PostgreSQL from 11.5 to 16

Experience Manager (PaaS/OnPrem)
1

Π‘Π½ΠΈΠΌΠΎΠΊ экрана 2025-08-26 Π² 09.52.44
Π‘Π½ΠΈΠΌΠΎΠΊ экрана 2025-08-26 Π² 09.52.441920Γ—531 35.8 KB

Hello,

I encountered a problem after migrating the PostgreSQL database to a new server and would like to clarify the correct sequence of steps.

What I did:

* On the old server, PostgreSQL version 11.5 was used, while on the new server version 16 was installed.

* In `Repository.xml`, I simply changed the database `url` to the new one, without shutting down the current site instance.

* Then I performed a *redeploy* and launched the site with the new database.

**After this, I started receiving frequent errors.**

For example, when working with documents (unpublish), the following error occurs:

org.onehippo.repository.api.WorkflowException: 

org.apache.jackrabbit.core.state.ItemStateException: 

Unable to resolve path for item: 85bf1d53-ba9b-455d-9f66-87360b683451/{http://www.jcp.org/jcr/1.0}successors

I would like to ask you:

1. In what cases do such errors typically occur when working with Bloomreach CMS?

2. Which steps did I perform incorrectly during the database migration?

3. What should be the correct sequence of actions when upgrading the repository from PostgreSQL 11.5 to PostgreSQL 16?

I would greatly appreciate any recommendations or best practices.

Thank you
If additional information is needed, I am ready to provide it in this thread. Please help me :heart: :melting_face:

1 Like
2

duplicate of Publish/Unpublish Error

Have you tried to perform re-indexing as suggested in above thread?

If re-indexing doesn’t help, you might need to upgrade DB via migration, see:

(above setups are mostly used to transfer data between different databases but can also be used for same database in case upgrades to different versions)

3

I’ve encountered a similar issue after migrating the database. When I try to search for a document via the console, it doesn’t show up, even though the content is visible in the admin panel. As a workaround, I create a copy of the document, but it’s not very convenient. Also, the CMS has become noticeably slower.

I’m also curious about the conditions under which this happens, and where the keys are stored. For instance, I can find documents using their UUIDs (which seem to work fine), but I can’t locate them in the PostgreSQL database.