Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transaction recovery without DDL permissions on database not possible in cloud environment #30630

Open
iambastian opened this issue Jan 23, 2025 · 0 comments

Comments

@iambastian
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant