You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When configuring transaction recovery in OpenLiberty with the <transaction> element and setting the recoveryGroup and recoveryIdentity attributes, the server automatically tries to create tables for transaction logging (e.g., WAS_TRAN_LOG), appending the recoveryIdentity to the table names. (See documentation here).
In environments where the database user has limited permissions (DML & DQL only, no DDL), this causes failures, as OpenLiberty cannot create the required tables. The documentation mentions the possibility of manually pre-creating tables for recovery, but this approach also fails because the table names include a dynamic suffix derived from the recoveryIdentity value. As a result, the table names cannot be determined in advance for manual creation.
Did I miss something in the configuration, or is it expected that transaction recovery requires dynamically created tables at runtime? If so, is there a way to configure static table names to enable manual table creation in restricted environments?
The text was updated successfully, but these errors were encountered:
When configuring transaction recovery in OpenLiberty with the
<transaction>
element and setting therecoveryGroup
andrecoveryIdentity
attributes, the server automatically tries to create tables for transaction logging (e.g.,WAS_TRAN_LOG
), appending therecoveryIdentity
to the table names. (See documentation here).In environments where the database user has limited permissions (DML & DQL only, no DDL), this causes failures, as OpenLiberty cannot create the required tables. The documentation mentions the possibility of manually pre-creating tables for recovery, but this approach also fails because the table names include a dynamic suffix derived from the
recoveryIdentity
value. As a result, the table names cannot be determined in advance for manual creation.Did I miss something in the configuration, or is it expected that transaction recovery requires dynamically created tables at runtime? If so, is there a way to configure static table names to enable manual table creation in restricted environments?
The text was updated successfully, but these errors were encountered: