You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

WSO2 IS 5.9配置PostgreSQL数据源启动报错求助

Troubleshooting "relation 'um_domain' does not exist" in WSO2 Identity Server 5.9 with PostgreSQL

Hey there! Let's work through this issue step by step—since the um_domain table belongs to the User Manager module, the problem usually ties back to missing database scripts or misconfigured datasources. Here's what to check:

1. Ensure All Required Database Scripts Are Executed

The um_domain table is part of the User Management (UM) schema, not just the Identity schema. It sounds like you ran the identity scripts, but you might have missed the user management ones:

  • Navigate to <IS-HOME>/dbscripts/user-mgt/ and execute the postgresql.sql script against your PostgreSQL database.
  • Don’t forget the Registry schema scripts in <IS-HOME>/dbscripts/registry/postgresql.sql—WSO2 IS relies on both UM and Registry schemas for core functionality.

Pro tip: Run these scripts with a database user that has full CREATE/ALTER permissions to avoid partial table creation failures.

2. Double-Check Your deployment.toml Configuration

Make sure you’ve fully replaced all default H2 datasources with PostgreSQL settings. WSO2 IS uses three core datasources, and all need to point to your PostgreSQL instance:

# User Manager Datasource
[datasource.WSO2_USER_DB]
url = "jdbc:postgresql://localhost:5432/your_wso2_db_name"
username = "your_db_user"
password = "your_db_password"
driver_class_name = "org.postgresql.Driver"

# Identity Datasource
[datasource.WSO2_IDENTITY_DB]
url = "jdbc:postgresql://localhost:5432/your_wso2_db_name"
username = "your_db_user"
password = "your_db_password"
driver_class_name = "org.postgresql.Driver"

# Registry Datasource
[datasource.WSO2_REGISTRY_DB]
url = "jdbc:postgresql://localhost:5432/your_wso2_db_name"
username = "your_db_user"
password = "your_db_password"
driver_class_name = "org.postgresql.Driver"

Also, ensure no H2 datasource entries are left uncommented in the file—this can cause conflicts during server startup.

3. Clean Cache and Temporary Files

Old cached configurations or temp files can cause unexpected behavior. Clear these out before restarting:

  • Delete the <IS-HOME>/tmp directory
  • Delete the <IS-HOME>/repository/temp directory
  • Restart the server to let it pick up fresh configurations and schema.

4. Verify the um_domain Table Exists

Log into your PostgreSQL database and run this query to confirm the table exists:

SELECT * FROM um_domain;

If this returns an error, the User Management script didn’t run successfully. Check your database logs for execution errors—common issues include missing permissions, typos in script paths, or version mismatches between your PostgreSQL server and the script syntax.

5. Confirm JDBC Driver Placement

Just to be thorough: Ensure the PostgreSQL JDBC driver (e.g., postgresql-42.2.XX.jar) is placed in <IS-HOME>/repository/components/lib/. You mentioned you already have it, but double-check the driver version is compatible with your PostgreSQL server (WSO2 IS 5.9 works best with PostgreSQL 9.6+).


内容的提问来源于stack exchange,提问作者CLIFFORD P Y

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.06 18:17:34