After upgrading the operating system from RHEL 8 to RHEL 9, SPL2 features such as the SPL2 search dropdown and Modules page fail to load with the following message:
"Unable to access SPL2 modules because the required "data orchestrator" component is not available. Contact Splunk Support for assistance."
This occurs because the PostgreSQL sidecar service, which manages SPL2 metadata, fails to start due to a collation version mismatch between the existing database files and the new OS libraries.
2026-05-29 09:59:49.025 PDT [3733270] ERROR: template database "template1" has a collation version mismatch 2026-05-29 09:59:49.025 PDT [3733270] DETAIL: The template database was created using collation version 2.28, but the operating system provides version 2.34.
1. Review PostgreSQL logs for "collation version mismatch" errors.
2. Confirm that port 9800 (Orchestrator) and port 5432 (PostgreSQL) are active.
To fix the collation mismatch, reinitialize the PostgreSQL sidecar database directory. This allows Splunk to rebuild the database using the OS-provided collation version.
1. Stop Splunk Enterprise.
2. Navigate to the sidecar database directory:
cd $SPLUNK_HOME/var/packages/data/postgres
3. Rename the db folder to db.backup:
mv db db.backup
4. Start Splunk Enterprise.
5. Verify that a new db folder is created automatically.
6. Confirm SPL2 functionality is restored in the Search & Reporting GUI.
How to fix postgres sidecar collation errors
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
01-Oct-2026
|
Initial Release |